@Bram Although you qualified the problem as "tricky", I would like to push this issue again.
Having lots of source code in directories whose path contains a "#", I'm not able to open any of these files with --remote-silent (which I apply to use the same gvim server for all my edits). Not using --remote-silent works. Also, is there a possibility to avoid the error message when using --remote-silent w/o a file name (e.g. to open/create a "remote" instance of gvim)? Hope, you can give this problem a consideration... -- -- 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/d/optout.
