Re: Error with :.! commands

Thanks for the mkdir suggestion. Next time I face it, it will come in
handy.

-Chandra

On Jun 22, 2:40 pm, Gary Johnson <garyj...@spocom.com> wrote:
> On 2011-06-22, Christian Brabandt wrote:
>
>
>
>
>
>
>
>
>
> > Hi Gary!
>
> > On Mi, 22 Jun 2011, Gary Johnson wrote:
>
> > > On 2011-06-22, Ben Fritz wrote:
> > > > On Jun 22, 2:41 pm, Chandra wrote:
> > > > > Hello,
> > > > > I see the following error when I try to in-line execute a shell
> > > > > command something like
>
> > > > > :.!grep foo bar
>
> > > > > "/tmp/v454263/17" E212: Can't open file for writing
> > > > > E482: Can't create file /tmp/v454263/17
>
> > > > > It usually happens if the vim session has been on for a long time
> > > > > without ever closing and reopening vim.
> > > > > A fresh vim session does not give this error. Any idea what happens
> > > > > here?
>
> > > > Possibly the temp directory got deleted out from under you. I'm not
> > > > sure of a good way around this.
>
> > > When I've run into this I've just recreated the directory, e.g.,
>
> > >    :!mkdir /tmp/v454263
>
> > Yeah, that is the only way around it. Some time ago, I made a patch
> > (http://groups.google.com/group/vim_dev/browse_frm/thread/728829f95c9e...)
> > that would make Vim check first, whether the directory still exists and
> > would create a new one, if it doesn't, but Bram didn't want to include
> > it.
>
> That would be really useful.  It's a shame Bram rejected it.
>
> > Hm, I wonder whether one could catch E482 or E483 globally and try to
> > recreate the missing directory.
>
> Nice idea, but I didn't see any autocommand events that were
> triggered by errors or anything applicable under ":help
> ignore-errors".
>
> Regards,
> Gary

--
You received this message from the "vim_use" 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