Browse Source

Try and fixe Bash history

Turns out what also breaks it is what might be a bug in Bash causing
HIST* vars in Debian's .bashrc trim the history immediately, before wwe
get a chance to set it to a huge number.

The workaround -- which cannot be done safely within bashum -- is to
comment any HIST* variables in your .bashrc.
Alois Mahdal 8 months ago
parent
commit
cd9f64f8ca
1 changed files with 6 additions and 7 deletions
  1. 6
    7
      dotfiles/config/bashum/main.bashrc

+ 6
- 7
dotfiles/config/bashum/main.bashrc View File

@@ -617,18 +617,17 @@ cal() {
617 617
 ### '''' ###
618 618
 
619 619
 HISTCONTROL=ignoredups:erasedups
620
-shopt -s histappend
621
-PROMPT_COMMAND="history -n; history -w; history -c; history -r; $PROMPT_COMMAND"
620
+# shopt -s histappend
621
+# PROMPT_COMMAND="history -n; history -w; history -c; history -r; $PROMPT_COMMAND"
622 622
 
623 623
 HISTIGNORE="$HISTIGNORE:ls:ll:la:cd"
624
-HISTIGNORE="$HISTIGNORE:git dc:git st"
625
-HISTIGNORE="$HISTIGNORE:reset"
624
+HISTIGNORE="$HISTIGNORE:git st"
626 625
 HISTIGNORE="$HISTIGNORE:se *:sc *"
627
-HISTSIZE=-1
628
-HISTFILESIZE=100000
626
+HISTSIZE=33333
627
+HISTFILESIZE=33333
629 628
 HISTTIMEFORMAT='%F %T '
630 629
 GLOBIGNORE=.:..
631
-shopt -s histverify
630
+# shopt -s histverify
632 631
 
633 632
 # some more aliases
634 633
 alias cls='clear'