As commands are entered they are stored in the history list and are retained across sessions.
Commands can be recalled with the ↑ key,
modified as if they had just been entered and executed (see readline)
When using command-line editing, search commands are available in each editing mode that provide access to the history list (see Commands For History).
history [n] †
history -ps args
history [-anrw] [filename]
history -c
history -d offset
Display the last n lines of the history list with line numbers, * indicates modified line.
Example:
> history 6 829 2016-02-17 16:03:39 vi diskUtilityDefaultsAll.html 830 2016-02-17 16:12:57 chmod 704 diskUtilityDefaultsAll.html 831 2016-02-17 16:13:15 vi defaults.1.html 832 2016-02-17 18:25:30 cd docs 833 2016-02-17 18:25:40 ls -l disk*
-p |
set -o history enables the history (default for interactive shells).
filename defaults to $HISTFILE usually .bash_history.
At login the history is initialized from $HISTFILE.
When an interactive shell exits, the last $HISTSIZE (default 1000) lines are copied from the history to
$HISTFILE (or appended based on $HISTAPPEND ) and then truncated to $HISTSIZE .
$HISTIGNORE supresses adding commands to list, prior to parameter a> and variable expansion but after history expansion.
For example:
HISTIGNORE=ls:head:tail:df:duThese commands, that don't (usually) modify anything are ignored .
$HISTCONTROL Don't save listed keywords causes some lines not to be saved (colon-separated list).
ignorespace space prefixed lines are not saved.ignoredups duplicate lines are not saved. ignoreboth ignorespace and ignoredups. erasedups duplicate lines removed . $HISTCONTROL is unset, or does not include a keyword, all lines are saved.$HISTTIMEFORMAT (default sometimes: %F %T i.e. YY-mm-dd HH:mm:ss ) format string for strftime to display time stamps
included with each entry, marked with the history comment character.#1718670469
are interpreted as timestamps.
shoptZ can be used to set :
cmdhist on|off each line of a multi-line command is put in the same history entry
lithist on|off (Literal History) causes the commands to be saved with embedded newlines
HISTCHARS='!^#' HISTCMD=1092 HISTFILE=/Volumes/DATA/duser/.zsh_sessions/0D6D1465-07C0-420A-A201-C09CB6BAE820.historynew HISTIGNORE=ls:lt:tail HISTORYymd_hms=/log/zsh_hist.0812_0809 HISTSIZE=2000 HISTTIMEFORMAT='%F %T ' SAVEHIST=1000 SHELL_SESSION_DID_HISTORY_CHECK=1 SHELL_SESSION_HISTFILE=/Volumes/DATA/duser/.zsh_sessions/0D6D1465-07C0-420A-A201-C09CB6BAE820.history SHELL_SESSION_HISTFILE_NEW=/Volumes/DATA/duser/.zsh_sessions/0D6D1465-07C0-420A-A201-C09CB6BAE820.historynew SHELL_SESSION_HISTFILE_SHARED=/Volumes/DATA/duser/.zsh_history SHELL_SESSION_HISTORY=1
Lists or edits and re-execute a portion of the history list.
fc [-e editor] [-lnr] [first] [last]
fc -s [pattern=replacment] [command]
first and last may be strings (to locate the most recent command beginning with that string) or
numbers, an index into the history list, a negative number is used as an offset from the current command number.
If first is not specified it is set to -1 i.e. the previous command for editing and -16 for listing.
If last is not specified it is set to first reulting in a range on one.
-l lists commands.
-n no command numbers .
-s substitute replacment for pattern
-r reverses the order of the listing. (without -l, results in commands being executed in the reverse order then when they were entered !)
editor or $FCEDIT or $EDITOR or vi is invoked on a file containing those commands.
When editing is complete, the edited commands are echoed and executed.
A useful alias is r='fc -s', so that typing r cc runs the last command beginning with cc and typing r re-executes the last command (see Aliases).
Introduced by the appearance of the history expansion character, default: !.
Enabled by default for interactive shells, and can be disabled using set +H .
History expansions introduce words from the history list into the input stream, making it easy to repeat commands, insert the arguments to a previous command into the current input line, or fix errors in previous commands quickly.
History expansion is performed immediately after a complete line is read, before the shell breaks it into words. It takes place in parts.
\ and' may be used to escape the history expansion character.
shopt may be used to tailor the behavior of history expansion.
If histverify is enabled, expanded line is loaded into the editing buffer for further modification.
If histreedit is enabled, a failed history expansion will be loaded into the editing buffer for correction.
The shell allows control of the various characters used by the history expansion mechanism with the histchars variable, as explained above (see Bash Variables). The shell uses the history comment character to mark history timestamps when writing the history file.
! |
A : separates the event specification from the word designator
and may be omitted if the word designator begins with a ^ ,
$ , * ,
-, or %.
If no event specification the previous command is used as the event.
Words are numbered from the beginning of the line, beginning with
Words are inserted into the current line separated by single spaces.
For example:
Preceding command. When you type this, the preceding command is repeated in toto.: !!
Last argument of the preceding command. !!:$ shortened to !$.
Second argument of the most recent command starting with the letters fi. !fi:2
|
:.
h |
: 1691944208:0;type echo -ptime EXTENDED_HISTORY
The second number is the duration of the command.
If either $INC_APPEND_HISTORY or $SHARE_HISTORY< is enabled
(setopt | grep -E '^(incappend|share)history$'),
To use of the duration metric while still saving the history to file during shell sessions, set $INC_APPEND_HISTORY_TIME ,
zsh waits for command completion before writing the entry.
Behaves like $INC_APPEND_HISTORY.
Only one of $INC_APPEND_HISTORY, $INC_APPEND_HISTORY_TIME and $SHARE_HISTORY should be active
bash timstamp is not present by default, $HISTTIMEFORMAT