On Wed, Aug 14, 2013 at 12:02 PM, Ben Fritz <[email protected]> wrote:
[snip]
> Otherwise, I think --remote commands internally use the :drop command to edit
> a file. You can see whether you can reproduce your problem using that.
I did narrow down the problem, but I'm not sure where to take it. Vim
ends up building this as the command to the server (sorry for the
wrapping):
<<<<<<<<
<C-\\><C-N>:cd /path/to/somewhere<CR>:if exists('*inputsave')|call
inputsave()|endif|drop filename|if exists('*inputrestore')|call
inputrestore()|endif<CR><C-\\><C-N>:if !exists('+acd')||!&acd|cd
-|endif<CR>:cal foreground()|if &im|star|en|redr|f<CR>
>>>>>>>>
If I reduce that command to just the following, I can reproduce the
problem in a running session:
<<<<<<<<
if exists('*inputsave')|call inputsave()|endif|drop filename|if
exists('*inputrestore')|call inputrestore()|endif
>>>>>>>>
I'm not sure what exactly is happening (I'm not too familiar with the
Vim code base just yet), but removing the inputsave/inputrestore does
allows it to work. There's a comment near inputsave() saying:
/* Call inputsave() so that a prompt for an encryption key works. */
Any ideas on where to go from here? I'd really like this to work, if
at all possible.
-John
--
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
