All,
I was playing around with map and nested autocommands for splitting on buffers,
and noticed that when I actually do a split via a map, ie:
map ,, :split <cfile><CR>
it actually goes through the whole setup process via starting the shell,
loading the associated rc file, etc etc.
However, for me this process is exceedingly long because I have an involved rc
file that takes an order of seconds to execute and the commands were hanging as
a result. So when I tried to set it to:
export SHELL='/bin/tcsh -f'
to save on startup cost, I got a message from vim saying "Cannot execute shell
'/bin/tcsh -f'"
I ended up setting it to /bin/bash just to avoid the hassle.
So a couple of things:
1. why does vim need to spawn a shell just to open up a new buffer? The
command I used was "map ,, :split <cfile><CR>".
2. is it possible for vim to accept a SHELL with arguments, like the above,
to avoid startup cost?
3. is there a variable, say VIMSHELL that could be used to specify the
shell to use in the case that #2 is not possible?
Thanks much for any info,
Ed
--
--
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/543d4339-cd20-475c-8fef-11c7c4175c28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
