Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in / Register
Toggle navigation
Menu
Open sidebar
adam.huang
Ohmyzsh
Commits
643bb25a
Commit
643bb25a
authored
Dec 13, 2014
by
Marc Cornellà
Browse files
Organize history.zsh file and improve comments
parent
94baa9ea
Changes
1
Hide whitespace changes
Inline
Side-by-side
lib/history.zsh
View file @
643bb25a
## Command history configuration
[
-z
"
$HISTFILE
"
]
&&
HISTFILE
=
"
$HOME
/.zsh_history"
HISTSIZE
=
10000
SAVEHIST
=
10000
## History wrapper
## History wrapper
function
omz_history
{
function
omz_history
{
# Delete the history file if `-c' argument provided.
# Delete the history file if `-c' argument provided.
...
@@ -23,11 +18,17 @@ case $HIST_STAMPS in
...
@@ -23,11 +18,17 @@ case $HIST_STAMPS in
*
)
alias history
=
'omz_history'
;;
*
)
alias history
=
'omz_history'
;;
esac
esac
setopt append_history
## History file configuration
setopt extended_history
[
-z
"
$HISTFILE
"
]
&&
HISTFILE
=
"
$HOME
/.zsh_history"
setopt hist_expire_dups_first
HISTSIZE
=
10000
setopt hist_ignore_dups
# ignore duplication command history list
SAVEHIST
=
10000
setopt hist_ignore_space
setopt hist_verify
## History command configuration
setopt inc_append_history
setopt append_history
# append history to HISTFILE on session exit
setopt share_history
# share command history data
setopt extended_history
# record timestamp of command in HISTFILE
setopt hist_expire_dups_first
# delete duplicates first when HISTFILE size exceeds HISTSIZE
setopt hist_ignore_dups
# ignore duplicated commands history list
setopt hist_ignore_space
# ignore commands that start with space
setopt hist_verify
# show command with history expansion to user before running it
setopt inc_append_history
# add commands to HISTFILE in order of execution
setopt share_history
# share command history data
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment