Ben Fritz schrieb:
I posted this originally on vim_use but only got one response, from
someone who thinks it's a bug. The original thread is here:
http://groups.google.com/group/vim_use/browse_thread/thread/d93a0878b9a5bb91/8619edd9992fdd20
Basically, I have two tabs open, each with a
On May 12, 1:55 pm, Andy Wokula anw...@yahoo.de wrote:
Ben Fritz schrieb:
I posted this originally on vim_use but only got one response, from
someone who thinks it's a bug. The original thread is here:
http://groups.google.com/group/vim_use/browse_thread/thread/d93a0878b...
Basically,
Henrik Öhman schrieb:
On May 12, 1:55 pm, Andy Wokula anw...@yahoo.de wrote:
The 'wrap' option is local to the window. (Obviously) Vim does not
switch to the buffer's window when reloading a file - the option can be
set in the wrong window.
I also had some battles with window local
On May 12, 4:46 pm, Andy Wokula anw...@yahoo.de wrote:
Right: When a buffer is no longer displayed in any window, the old
window-local options are remembered together with other buffer data
and restored when the buffer is displayed again.
But these hidden window-local options are not
Hi:
Here's a small diff to bring gvim under photon up to date.
Regards,
-seanb
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
On May 12, 6:55 am, Andy Wokula anw...@yahoo.de wrote:
I found that :setf {ft-name} does nothing when auto-reloading a file
(intentionally I guess), so
:au FileType text setl wrap
works better for me. And it somehow looks better anyway ...
Of course you need to define the
On May 12, 11:40 am, Ben Fritz fritzophre...@gmail.com wrote:
When I remove the setlocal wrap from the ftplugin file, and add an
FileType autocmd to do the same, I get the same results.
I worded that a bit awkwardly. What I meant was, I removed the
setlocal wrap from the ftplugin file,
Well...I finally found some :help related to this. From :help ftplugin
(then scroll down or search for the OPTIONS section):
To make sure the filetype plugin only affects the current buffer use the
:setlocal
command to set options. And only set options which are local to a buffer
Will Kraytos wrote:
Steps to recreate:
- At the command line, create 4 Python files with minimal code, and launch
vim displaying them all:
echo 'def foo(): print bar # test' | tee {foo,bar,baz}.py qux.py
vim -c split foo.py -c split bar.py -c split baz.py qux.py
- Inside Vim: If
Sean Boudreau wrote:
Hi:
Here's a small diff to bring gvim under photon up to date.
Wow, that GUI hasn't be mentioned in ages.
For what version of photon does this make Vim work?
Does it break for an older version after the patch?
--
It is illegal for anyone to try and stop a child from
On 05/11/2009 03:25 PM, Bram Moolenaar wrote:
Michael Hordijk wrote:
On 05/05/2009 04:20 PM, Bram Moolenaar wrote:
The special characters in $HOME should indeed be escaped. I can only
think of a comma being special here.
Is this something that I can expect a future version of VIM to do?
11 matches
Mail list logo
