Hi James,
On 26/10/2019 21:26, James McCoy wrote:
> On Fri, Oct 25, 2019 at 09:54:33AM +0000, Sihera Andre wrote:
>> On 25/10/2019 18:24, Christian Brabandt wrote:
>>> On Fr, 25 Okt 2019, Sihera Andre wrote:
>>>> I think there should be another debate enabling .viminfo to be a symlink
>>>> and giving computer professionals the ability to manage their own security.
>>> Have you tried the 'viminfofile' option setting?
>> I didn't previously know about this option, but I have just tried it.
>>
>> It works for the "-i" command line invocation but a single line
>>
>> set viminfofile="...."
> " is Vim's comment character, so that command is effectively the same as
>
> set viminfofile=
>
> Do not quote the filename. If there's white space, then you need to
> escape it -- see “:help option-backslash”.
>
> Cheers,
Thanks for your suggestion. I did try it but to no avail.My .vimrc contains
the single line:
viminfofile=/home/andre/mnt/secure-home/.viminfo
However, regardless of the setting of "viminfofile", the file always
gets written
to "${HOME}/.viminfo"
Thanks for your input.
Cheers,
Andre.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/PS2P216MB027583905896DD443770332FC0670%40PS2P216MB0275.KORP216.PROD.OUTLOOK.COM.
