Timeline for Prevent commands from populating command-line history
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 12:07 | vote | accept | Biggybi | ||
| Jun 15, 2020 at 21:08 | comment | added | Biggybi | @ChristianBrabandt Indeed, it looks to be the only way -- I was hoping for a way to prevent the history file population rather than having to manipulate it afterwards. | |
| Jun 15, 2020 at 12:22 | answer | added | statox | timeline score: 3 | |
| Jun 15, 2020 at 7:52 | comment | added | Christian Brabandt |
See :h histdel()
|
|
| Jun 15, 2020 at 6:58 | comment | added | d.k | just close vim, and do it in another editor. It shouldn't be present in the history then | |
| Jun 15, 2020 at 6:58 | comment | added | d.k | you can manually edit the vimhistory file (or how is it called), but it could leave other traces like file modification/access etc. | |
| Jun 15, 2020 at 6:48 | history | asked | Biggybi | CC BY-SA 4.0 |