Timeline for Why does bash still keep duplicate lines with erasedups?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 1, 2018 at 16:56 | comment | added | user232326 |
I believe that the question is about erasedups not ignoredups (please read the title). In any case, your answer does not explain such option
|
|
| Oct 25, 2017 at 2:26 | comment | added | phuclv | I constantly use Ctrl+R to find commands I've used and it shows many duplicates which is a bit annoying | |
| Oct 24, 2017 at 23:11 | comment | added | Wildcard |
@LưuVĩnhPhúc, I'm curious: are you trying to get a clean readable history list, or are you trying to easily re-execute commands you've run earlier? (If the latter, you might try using fc.
|
|
| Oct 18, 2017 at 3:43 | vote | accept | phuclv | ||
| Oct 18, 2017 at 3:43 | comment | added | phuclv |
ah, I thought that it will remove the previous duplicate entry. So it seems less useful than expected, because sometimes I run cmdA then cmdB then cmdA it still shows 2 cmdAs nearby
|
|
| Oct 18, 2017 at 3:27 | history | answered | Wildcard | CC BY-SA 3.0 |