Timeline for Remove duplicates in file (without sorting!) leaving the _last_ of the occurences
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2024 at 17:36 | comment | added | tink | And another suggestion for keeping history clean ... I personally wouldn't use Ctrl-r for a cd .. and I use Ctrl-L for a clear, so having these in history ever seems unnecessary. I use HISTIGNORE= for things I see aspollutants, so your ~/.bashrc could have e.g. HISTIGNORE="cd:cd ..:pwd:exit:mc:clear:history *" ... | |
| Jul 10, 2024 at 9:03 | comment | added | Make42 | @spuck: I am not using the history for debugging or something like that. I only use it for fast access of commands I used in the past and which I use regularly. | |
| Jul 9, 2024 at 2:55 | answer | added | waltinator | timeline score: 2 | |
| Jul 8, 2024 at 22:08 | answer | added | Matthew | timeline score: 2 | |
| Jul 8, 2024 at 21:42 | comment | added | Matthew | @spuck, true, but if something's causing your history to be spammed with cd .., knowing "you" ran that recently, often, etc. is not actually useful information. | |
| Jul 8, 2024 at 19:03 | comment | added | spuck | Have you tried unset HISTFILE before launching the editor to disable history? | |
| Jul 8, 2024 at 18:47 | comment | added | spuck | @Matthew, thanks for the explanation. The awk code in the OP makes me think they are trying to remove successive repeats. This seems like an XY problem: removing commands like this seems to defeat the purpose of having a command history at all, IMHO. If all I can see is that I ran cd .., but no idea if I ran it once, twice, or 53 times, nor in what sequence it ran interspersed with other commands doesn't seem useful to me. To each his own. | |
| Jul 8, 2024 at 10:05 | vote | accept | Make42 | ||
| Jul 2, 2024 at 10:08 | comment | added | Make42 | @Mathew: No, I do not need (nor want) the history from Kile, but I do not know how to disable Kile's history recording (and I searched). If you know how to do that, that would be great. | |
| Jul 2, 2024 at 7:45 | answer | added | Kaz | timeline score: 2 | |
| Jul 1, 2024 at 22:37 | comment | added | Matthew | @spuck, say a certain command is issued regularly. Choosing the first instance means it's buried near the beginning of history. Choosing the last means it's recent. The difference is whether the first time or most recent time a command is used is preserved. If the purpose of history is to repeat recently used commands (usually the case), the latter is "better". | |
| Jul 1, 2024 at 22:34 | comment | added | Matthew | Do you even need history from Kile? If not, you could probably detect if Kile is the parent process in .bashrc and just disable history recording. | |
| Jul 1, 2024 at 22:18 | comment | added | spuck | Dumb question: In a list of duplicate lines, what difference does choosing either the first or last occurrence make in the end result? | |
| Jul 1, 2024 at 17:44 | history | became hot network question | |||
| Jul 1, 2024 at 9:51 | answer | added | Stephen Kitt | timeline score: 6 | |
| Jul 1, 2024 at 9:43 | history | asked | Make42 | CC BY-SA 4.0 |