mirror of
https://github.com/fish-shell/fish-shell.git
synced 2024-11-23 06:05:39 +08:00
47aa79813d
Fish functions are great for configuring fish but they don't integrate
seamlessly with the rest of the system. For tasks that can run outside fish,
writing scripts is the natural approach.
To edit my scripts I frequently run
$EDITOR (which my-script)
Would be great to reduce the amount typing for this common case (the names
of editor and scripts are usually short, so that's a lot of typing spent on
the boring part).
Our Alt+o binding opens the file at the cursor in a pager. When the cursor
is in command position, it doesn't do anything (unless the command is actually
a valid file path). Let's make it open the resolved file path in an editor.
In future, we should teach this binding to delegate to "funced" upon seeing
a function instead of a script. I didn't do it yet because funced prints
messages, so it will mess with the commandline rendering if used from
a binding. (The fact that funced encourages overwriting functions that
ship with fish is worrysome. Also I'm not sure why funced doesn't open the
function's source file directly (if not sourced from stdin). Persisting the
function should probably be the default.)
Alternative approach: I think other shells expand "=my-script" to
"/path/to/my-script". That is certainly an option -- if we do that we'd want
to teach fish to complete command names after "=". Since I don't remember
scenarios where I care about the full path of a script beyond opening it in
my editor, I didn't look further into this.
Closes #10266
|
||
|---|---|---|
| .. | ||
| cmds | ||
| python_docs_theme | ||
| commands.rst | ||
| completions.rst | ||
| conf.py | ||
| contributing.rst | ||
| design.rst | ||
| faq.rst | ||
| fish_for_bash_users.rst | ||
| fish_indent_lexer.py | ||
| fish_synopsis.py | ||
| index.rst | ||
| interactive.rst | ||
| language.rst | ||
| license.rst | ||
| prompt.rst | ||
| relnotes.rst | ||
| tutorial.rst | ||