mirror of
https://github.com/fish-shell/fish-shell.git
synced 2026-05-14 22:11:16 -03:00
First stab at directory transition. Test with care...
darcs-hash:20061019115023-ac50b-30c3fd51d8af8a616d63dfcac39370d7fe6d144e.gz
This commit is contained in:
@@ -279,8 +279,8 @@ automatically loaded when needed. A function definition file must have
|
||||
a filename consisting of the name of the function plus the suffix
|
||||
'.fish'.
|
||||
|
||||
The default value for \$fish_function_path is \c ~/.fish.d/functions
|
||||
\c /etc/fish.d/functions \c /usr/share/fish/functions. The exact path
|
||||
The default value for \$fish_function_path is \c ~/.config/fish/functions
|
||||
\c /etc/fish/functions \c /usr/share/fish/functions. The exact path
|
||||
to the last two of these may be slighly different depending on what
|
||||
install path prefix was chosen at configuration time. The rationale
|
||||
behind having three different directories is that the first one is for
|
||||
@@ -404,8 +404,8 @@ searches through any directories in the array variable
|
||||
loaded when needed. A completion file must have a filename consisting
|
||||
of the name of the command to complete and the suffix '.fish'.
|
||||
|
||||
The default value for \$fish_complete_path is ~/.fish.d/completions,
|
||||
/etc/fish.d/completions and /usr/share/fish/completions. The exact
|
||||
The default value for \$fish_complete_path is ~/.config/fish/completions,
|
||||
/etc/fish/completions and /usr/share/fish/completions. The exact
|
||||
path to the last two of these may be slighly different depending on
|
||||
what install path prefix was chosen at configuration time. If a
|
||||
suitable file is found in one of these directories, it will be
|
||||
@@ -972,8 +972,8 @@ Here are some of the commands available in the editor:
|
||||
- Alt-p adds the string '| less;' to the end of the job under the cursor. The result is that the output of the command will be paged.
|
||||
|
||||
You can change these key bindings by making an inputrc file. To do
|
||||
this, copy the file /etc/fish_inputrc to your home directory and
|
||||
rename it to '.fish_inputrc'. Now you can edit the file .fish_inputrc,
|
||||
this, copy the file /etc/fish/fish_inputrc to your home directory and
|
||||
rename it to '.config/fish/fish_inputrc'. Now you can edit the file
|
||||
to change your key bindings. The fileformat of this file is described
|
||||
in the manual page for readline. Use the command <code>man readline</code>
|
||||
to read up on this syntax. Please note that the list of key binding
|
||||
@@ -1041,7 +1041,7 @@ cursor when the search began.
|
||||
|
||||
History searches can be aborted by pressing the escape key.
|
||||
|
||||
The history is stored in the file '.fish_history'. It is automatically
|
||||
The history is stored in the file '~/.config/fish/fish_history'. It is automatically
|
||||
read on startup and merged on program exit.
|
||||
|
||||
Example:
|
||||
@@ -1065,20 +1065,23 @@ which the user can change <code>fish</code>'s behaviour.
|
||||
|
||||
\section initialization Initialization files
|
||||
|
||||
On startup, \c fish evaluates the files /usr/share/fish/fish,
|
||||
/etc/fish (Or ~/etc/fish if you installed fish in your home directory)
|
||||
and ~/.fish, in that order. The first file should not be directly
|
||||
edited, the second one is meant for systemwide configuration and the
|
||||
last one is meant for user configuration. If you want to run a command
|
||||
only on starting an interactive shell, use the exit status of the
|
||||
command 'status --is-interactive' to determine if the shell is
|
||||
interactive. If you want to run a command only when using a login
|
||||
shell, use 'status --is-login' instead.
|
||||
On startup, \c fish evaluates the files /usr/share/fish/config.fish
|
||||
(Or /usr/local/fish... if you installed fish in /usr/local),
|
||||
/etc/fish/config.fish (Or ~/etc/fish/... if you installed fish in your
|
||||
home directory) and ~/.config/fish/config.fish (Or any other directory
|
||||
specified by the \$XDG_CONFIG_HOME variable), in that order. The first
|
||||
file should not be directly edited, the second one is meant for
|
||||
systemwide configuration and the last one is meant for user
|
||||
configuration. If you want to run a command only on starting an
|
||||
interactive shell, use the exit status of the command 'status
|
||||
--is-interactive' to determine if the shell is interactive. If you
|
||||
want to run a command only when using a login shell, use 'status
|
||||
--is-login' instead.
|
||||
|
||||
Examples:
|
||||
|
||||
If you want to add the directory ~/linux/bin to your PATH variable
|
||||
when using a login shell, add the following to your ~/.fish file:
|
||||
when using a login shell, add the following to your ~/.config/fish/config.fish file:
|
||||
|
||||
<pre>if status --is-login
|
||||
set PATH $PATH ~/linux/bin
|
||||
@@ -1093,7 +1096,7 @@ shell:
|
||||
end</pre>
|
||||
|
||||
<a href="#variables-universal">Universal variables</a> are stored in
|
||||
the file .fishd.HOSTNAME, where HOSTNAME is the name of your
|
||||
the file .config/fish/fishd.HOSTNAME, where HOSTNAME is the name of your
|
||||
computer. Do not edit this file directly, edit them through fish
|
||||
scripts or by using fish interactively instead.
|
||||
|
||||
@@ -1302,7 +1305,7 @@ g++, javac, java, gcj, lpr, doxygen, whois, find)
|
||||
- With a bit of tweakage, quite a few of the readline key-binding functions could be implemented in shellscript.
|
||||
- Highlight beginning/end of block when moving over a block command
|
||||
- Inclusion guards for the init files to make them evaluate only once, even if the user has installed fish both in /etc and in $HOME
|
||||
- Do not actually load/parse .fish_history, only mmap it and use some clever string handling. Should save ~150 kB of memory permanently, but is very hard to implement.
|
||||
- Do not actually load/parse fish_history, only mmap it and use some clever string handling. Should save ~150 kB of memory permanently, but is very hard to implement.
|
||||
- command specific wildcarding (use case * instead of case '*', etc.)
|
||||
- Map variables. (export only the values. When expanding with no key specified, expand to all values.)
|
||||
- Descriptions for variables using 'set -d'.
|
||||
|
||||
Reference in New Issue
Block a user