• Last one..

    From Accession@46:1/100 to All on Sat Apr 16 08:58:18 2016
    Forgot I was using restricted mode from the BBS, while sharing the same .viminfo file. Testing using .pharcyde_viminfo instead so nothing else but the BBS shares/uses the file.

    Regards,
    Nick
    --- SBBSecho 3.00-Linux
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (46:1/100)
  • From Accession@46:1/100 to All on Sat Apr 16 08:59:59 2016
    Forgot I was using restricted mode from the BBS, while sharing the same .viminfo file. Testing using .pharcyde_viminfo instead so nothing else but the BBS shares/uses the file.

    Ok I lied about it being the last one. Trying '-i NONE' so that no .viminfo is used. Since in restricted mode, it can't write any files besides the one that's
    loaded (MSGTMP for editing a message only).

    Regards,
    Nick
    --- SBBSecho 3.00-Linux
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (46:1/100)
  • From Accession@46:1/100 to All on Sat Apr 16 09:00:54 2016
    Hello All,

    On 16 Apr 16 08:59, Accession wrote to All:

    Forgot I was using restricted mode from the BBS, while sharing
    the same .viminfo file. Testing using .pharcyde_viminfo instead
    so nothing else but the BBS shares/uses the file.

    Ok I lied about it being the last one. Trying '-i NONE' so that no .viminfo is used. Since in restricted mode, it can't write any files besides the one that's loaded (MSGTMP for editing a message only).

    We have a winner! Took long enough to find that one. Not in the --help or formal docs, but I found it in the man page.

    Regards,
    Nick

    --- GoldED+/LNX 1.1.5-b20160322
    * Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (46:1/100)