I am a packrat, but I do like a bit of order. This makes maintaining my bash history difficult. There are some commands that I use frequently that seem to fill up my history file making it hard to keep some of the lesser used, yet very important commands in the history. Finally sick of the problem, I poured over the manpage for bash and found the section on HISTCONTROL. From the description there, I found that this along with HISTIGNORE, I can almost eliminate my problem of my bash history getting too full of stupid common commands.<\/p>\n
I added this to my ~\/.bash_profile:<\/p>\n
Here is the snippet from the bash manual that corresponds to these controls:<\/p>\n I am a packrat, but I do like a bit of order. This makes maintaining my bash history difficult. There are some commands that I use frequently that seem to fill up my history file making it hard to keep some of the lesser used, yet very important commands in the history. Finally sick of … Continue reading Tame your bash history<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5],"tags":[11,42],"class_list":["post-135","post","type-post","status-publish","format-standard","hentry","category-hobbies","tag-software","tag-tips-and-tricks"],"_links":{"self":[{"href":"https:\/\/vernon.mauery.com\/content\/wp-json\/wp\/v2\/posts\/135","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/vernon.mauery.com\/content\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vernon.mauery.com\/content\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vernon.mauery.com\/content\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/vernon.mauery.com\/content\/wp-json\/wp\/v2\/comments?post=135"}],"version-history":[{"count":0,"href":"https:\/\/vernon.mauery.com\/content\/wp-json\/wp\/v2\/posts\/135\/revisions"}],"wp:attachment":[{"href":"https:\/\/vernon.mauery.com\/content\/wp-json\/wp\/v2\/media?parent=135"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vernon.mauery.com\/content\/wp-json\/wp\/v2\/categories?post=135"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vernon.mauery.com\/content\/wp-json\/wp\/v2\/tags?post=135"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nexport HISTIGNORE=\"&:ls:[bf]g:disown:cd:cd[ ]-:exit:^[ t]*\"
\nexport HISTCONTROL=ignoredups:ignorespace:erasedups
\nexport HISTFILESIZE=2000
\n<\/code><\/p>\n\n HISTCONTROL
\n A colon-separated list of values controlling how commands are saved on the history
\n list. If the list of values includes ignorespace, lines which begin with a space
\n character are not saved in the history list. A value of ignoredups causes lines
\n matching the previous history entry to not be saved. A value of ignoreboth is
\n shorthand for ignorespace and ignoredups. A value of erasedups causes all previous
\n lines matching the current line to be removed from the history list before that
\n line is saved. Any value not in the above list is ignored. If HISTCONTROL is
\n unset, or does not include a valid value, all lines read by the shell parser are
\n saved on the history list, subject to the value of HISTIGNORE. The second and sub-
\n sequent lines of a multi-line compound command are not tested, and are added to the
\n history regardless of the value of HISTCONTROL.
\n HISTFILESIZE
\n The maximum number of lines contained in the history file. When this variable is
\n assigned a value, the history file is truncated, if necessary, by removing the old-
\n est entries, to contain no more than that number of lines. The default value is
\n 500. The history file is also truncated to this size after writing it when an
\n interactive shell exits.
\n HISTIGNORE
\n A colon-separated list of patterns used to decide which command lines should be
\n saved on the history list. Each pattern is anchored at the beginning of the line
\n and must match the complete line (no implicit `*' is appended). Each pattern is
\n tested against the line after the checks specified by HISTCONTROL are applied. In
\n addition to the normal shell pattern matching characters, `&' matches the previous
\n history line. `&' may be escaped using a backslash; the backslash is removed
\n before attempting a match. The second and subsequent lines of a multi-line com-
\n pound command are not tested, and are added to the history regardless of the value
\n of HISTIGNORE.<\/p>\n","protected":false},"excerpt":{"rendered":"