mirror of
git://git.code.sf.net/p/zsh/code
synced 2025-09-04 10:41:11 +02:00
zsh-users/19551: history documentation.
Note in a couple of places that history file reading and writing is only done in interactive shells.
This commit is contained in:
parent
e12b515082
commit
4042640eee
3 changed files with 15 additions and 1 deletions
|
@ -1,3 +1,9 @@
|
|||
2014-12-17 Peter Stephenson <p.stephenson@samsung.com>
|
||||
|
||||
* users/19551: Doc/builtins.yo, Doc/Zsh/roadmap.yo: better
|
||||
documentation that history file reading and writing is only
|
||||
done in interactive shells.
|
||||
|
||||
2014-12-16 Barton E. Schaefer <schaefer@zsh.org>
|
||||
|
||||
* Jun Kuriyama: 33984: Src/builtin.c: bin_dirs() should use
|
||||
|
|
|
@ -657,6 +657,12 @@ xitem(tt( )[ var(old)tt(=)var(new) ... ] [ var(first) [ var(last) ] ])
|
|||
xitem(tt(fc) tt(-p) [ tt(-a) ] [ var(filename) [ var(histsize) [ var(savehistsize) ] ] ])
|
||||
xitem(tt(fc) tt(-P))
|
||||
item(tt(fc) tt(-ARWI) [ var(filename) ])(
|
||||
The tt(fc) command controls the interactive history mechanism. Note
|
||||
that reading and writing of history options is only performed if the
|
||||
shell is interactive. Usually this is detected automatically, but
|
||||
it can be forced by setting the tt(interactive) option when starting the
|
||||
shell.
|
||||
|
||||
Select a range of commands from var(first) to var(last) from the
|
||||
history list.
|
||||
The arguments var(first) and var(last) may be specified as a
|
||||
|
|
|
@ -41,7 +41,9 @@ set appropriate variables, and the number of history lines retained by
|
|||
default is quite small (30 lines). See the description of the shell
|
||||
variables (referred to in the documentation as parameters) tt(HISTFILE),
|
||||
tt(HISTSIZE) and tt(SAVEHIST) in ifzman(zmanref(zshparam))\
|
||||
ifnzman(noderef(Parameters Used By The Shell)).
|
||||
ifnzman(noderef(Parameters Used By The Shell)). Note that it's
|
||||
currently only possible to read and write files saving history
|
||||
when the shell is interactive, i.e. it does not work from scripts.
|
||||
|
||||
The shell now supports the UTF-8 character set (and also others if
|
||||
supported by the operating system). This is (mostly) handled transparently
|
||||
|
|
Loading…
Reference in a new issue