Filename completion relative to current buffer's location, not current working directory

2007-10-29 Fir de Conversatie Nikolai Weibull
Ctrl-X Ctrl-F does filename completion rooted at the current working directory. I would think that one probably wants to complete filenames rooted at the current buffer's location. Is this something for the TODO perhaps? --~--~-~--~~~---~--~~ You received this

Re: Filename completion relative to current buffer's location, not current working directory

2007-10-29 Fir de Conversatie Dominique Pelle
On 10/29/07, Ben Schmidt [EMAIL PROTECTED] wrote: Nah. Current directory makes more sense. But you may like to find yourself a nice vim script that changes the current directory to that of the buffer as you change buffers, etc. I believe there is such a thing on the Vim website. If not, I

Re: (2) Filename completion relative to current buffer's location, not current working directory

2007-10-29 Fir de Conversatie Nikolai Weibull
On 10/29/07, Ben Schmidt [EMAIL PROTECTED] wrote: Nikolai Weibull wrote: Ctrl-X Ctrl-F does filename completion rooted at the current working directory. I would think that one probably wants to complete filenames rooted at the current buffer's location. Is this something for the TODO

Re: Filename completion relative to current buffer's location, not current working directory

2007-10-29 Fir de Conversatie Matt Wozniski
On 10/29/07, Dominique Pelle [EMAIL PROTECTED] wrote: I have the following line in my .vimrc which does exactly what you're looking for, and I find it very useful: autocmd BufEnter * exe 'cd ' . substitute(expand(%:p:h), , , g) You might prefer this line: au BufEnter * if ft != 'help' |

Re: Trial patch for variable tabstops

2007-10-29 Fir de Conversatie Mark Waggoner
On 10/27/07, Mark Waggoner [EMAIL PROTECTED] wrote: On 10/27/07, Matthew Winn [EMAIL PROTECTED] wrote: On Sat, 27 Oct 2007 13:45:46 +1000, Ben Schmidt [EMAIL PROTECTED] wrote: Here's another version of the variable tabstop patch. I've made it a feature (FEAT_VARTABS) that

Re: MacVim bug

2007-10-29 Fir de Conversatie björn
On 28/10/2007, Bram Moolenaar [EMAIL PROTECTED] wrote: Bjorn Winckler wrote: This problem was brought up on the vim_mac list a while back but it turns out not to be mac specific so I am posting to the vim_dev list as well. On 12/09/2007, Nico Weber [EMAIL PROTECTED] wrote:

Re: Filename completion relative to current buffer's location, not current working directory

2007-10-29 Fir de Conversatie ap
On Oct 29, 5:49 pm, Nikolai Weibull [EMAIL PROTECTED] wrote: On 10/29/07, Ben Schmidt [EMAIL PROTECTED] wrote: Nikolai Weibull wrote: Ctrl-X Ctrl-F does filename completion rooted at the current working directory. I would think that one probably wants to complete filenames rooted

Patch 7.1.146 (extra)

2007-10-29 Fir de Conversatie Bram Moolenaar
Patch 7.1.146 (extra) Problem:VMS: Files with a very rare record organization (VFC) cannot be properly written by Vim. On older VAX systems mms runs into a syntax error. Solution: Check for this special situation. Do not wrap a comment, make it one long

Re: gvim problem with

2007-10-29 Fir de Conversatie Ben Schmidt
!xdvi -hushstdout -s 5 -geometry 1024x900+416+0 -expert %.dvi which works fine from vim, but not from gvim. I think what is happening is that Vim is creating a pseudo-terminal, running the command, and then killing the pseudo terminal (and consequently all commands attached to it) as

Re: gvim problem with

2007-10-29 Fir de Conversatie Gautam Iyer
On Tue, Oct 30, 2007 at 10:15:08AM +1100, Ben Schmidt wrote: !xdvi -hushstdout -s 5 -geometry 1024x900+416+0 -expert %.dvi which works fine from vim, but not from gvim. I think what is happening is that Vim is creating a pseudo-terminal, running the command, and then killing the