Timeline for The simplest way to start Vim in private mode
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 27, 2022 at 6:16 | comment | added | Sam Watkins |
I vote for the environmental variable / vimrc solution, with a wrapper vim-private that sets it and runs vim, and an alias or symlink vip for short, because 1. I can set the environment variable for a whole "private shell session" and don't need to remember to type vip instead of vi every time, and 2. If I'm doing something tricky in my vimrc that might compromise privacy, I can easily check the environment variable and not do it in that case.
|
|
| Mar 22, 2021 at 11:02 | answer | added | Mateen Ulhaq | timeline score: 1 | |
| Aug 31, 2019 at 13:18 | answer | added | mvanle | timeline score: 2 | |
| Apr 13, 2017 at 12:51 | history | edited | CommunityBot |
replaced http://vi.stackexchange.com/ with https://vi.stackexchange.com/
|
|
| Jul 20, 2016 at 17:44 | history | edited | Mateusz Piotrowski | CC BY-SA 3.0 |
fix grammar
|
| Apr 24, 2016 at 11:43 | history | edited | Mateusz Piotrowski | CC BY-SA 3.0 |
typo
|
| Feb 25, 2016 at 8:36 | answer | added | Martin Tournoij | timeline score: 11 | |
| Jan 20, 2016 at 22:31 | history | edited | Mateusz Piotrowski | CC BY-SA 3.0 |
updated #6
|
| Jan 20, 2016 at 18:54 | comment | added | Mateusz Piotrowski | @garyjohn. Your solution is really nice! Works like a charm :) | |
| Jan 20, 2016 at 17:00 | comment | added | garyjohn |
Another method is to symlink vim to another name such as vimp, then test v:progname == "vimp" and if true, execute your private-mode settings. See :help v:progname.
|
|
| Jan 20, 2016 at 16:04 | comment | added | Steve |
How about a combination of 4 and 1,2 or 3? alias vimprivate='vim -u .vimrcprivate' etc.
|
|
| Jan 20, 2016 at 6:08 | comment | added | romainl |
I vote for vim -Nu .vimrcprivate.
|
|
| Jan 20, 2016 at 2:39 | comment | added | saginaw |
Maybe you could define a custom command inside your vimrc, like this: command! Private set history=0 nobackup secure ..., and then call it from the shell with vim +'Private'. Concerning the last autocommand you mentioned, when a buffer is read, it tests whether the value of the 'cryptmethod' option, or 'cm' for the short version, is non empty. This option controls the encryption method used to encrypt the buffer when it's written to a file with the Ex command :X. If the option is not empty, then the autocommand sets up various options.
|
|
| Jan 20, 2016 at 1:03 | history | edited | Mateusz Piotrowski | CC BY-SA 3.0 |
added case 6
|
| Jan 20, 2016 at 0:48 | history | edited | Mateusz Piotrowski |
edited tags
|
|
| Jan 19, 2016 at 23:34 | history | undeleted | Mateusz Piotrowski | ||
| Jan 19, 2016 at 23:30 | history | deleted | Mateusz Piotrowski | via Vote | |
| Jan 19, 2016 at 23:27 | review | First posts | |||
| Jan 19, 2016 at 23:32 | |||||
| Jan 19, 2016 at 23:21 | history | asked | Mateusz Piotrowski | CC BY-SA 3.0 |