Loading ...
Sorry, an error occurred while loading the content.

54652RE: viminfo, args and --remote

Expand Messages
  • Keith Roberts
    Nov 1, 2004
    • 0 Attachment
      >-----Original Message-----
      >From: Antoine J. Mechelynck [mailto:antoine.mechelynck@...]
      >Sent: Thursday, October 28, 2004 1:13 PM
      >To: Keith Roberts; vim users' list; Antony Scriven
      >Subject: Re: viminfo, args and --remote
      >Keith Roberts <kroberts@...> wrote:
      >> IIUC, wasn't one of the reasons for avoiding the viminfo entirely
      >> (when filename(s) are specified in the command) so that the
      >> right-click "Edit with Vim" wouldn't interfere with an existing
      >> viminfo in that directory?
      >> Hmmm... Scanning thru starting.txt, under *startup-options* I see a
      >> command argument '-i', which looks like it was made for this purpose.
      >> So maybe a new argument '-I', which is identical to '-I',
      >except that
      >> any filenames specified are *merged* with the buffer list from the
      >> existing viminfo?
      >The default (with a default 'viminfo option, or whenever
      >'viminfo' is nonempty but doesn't include a viminfo file name)
      >is to use a viminfo file in $HOME; thus a viminfo in a
      >different directory won't normally be clobbered. I suppose you
      >can write your vimrc in such way as to place the viminfo file
      >in whatever directory is current at startup; but in that case,
      >of course, you're on your own.
      >Hmm. I suppose you mean "a new argument '-I', identical to
      >'-i'", etc. Let's run it up the flagpole and see if anyone salutes.

      Yes, that's exactly what I meant ... Another example of Outlook being
      entirely too %$&(*@ "helpful"! :(

    • Show all 12 messages in this topic