Reply to message «optwin.vim - setlocal on global options ? ...»,
sent 10:13:02 30 January 2011, Sunday
by Marc Weber:
fun! SIDBinOptionL(name)
exe norm! \C-Wp
exe let val = . a:name
exe norm! \C-Wp
call append($, substitute(substitute( \tset . val . a:name . \t
. \!val
Hi Marc!
On So, 30 Jan 2011, Marc Weber wrote:
First of all: Why is setlocal aw allowed because its a global option
only.
setlocal will set the global option, if the option does not have a local
value.
I'd like to tidy up optwin.vim and change its output maybe adding core
funtions which
On 30/01/11 11:05 AM, Marc Weber wrote:
Does the current vim.sf.net page tell about existing repositories where
vim patches mature ?
If if they are never merged upstream it would be nice to have a local
place to share them.
I know about a git repository which collects many of them.
Mmm. But
Excerpts from Christian Brabandt's message of Sun Jan 30 13:41:09 +0100 2011:
because the functions are called a lot for all the options available.
I've counted them. They are called 35 times. Should be fast enough. A
noticeable delay occurs if you have 2.000 invokations.
It sounds like a
Dominique Pelle wrote:
Vim-7.3.107 crashes when I try to create the Esperanto
dictionary from OpenOffice-3.
Steps to reproduce:
$ wget http://extensions.services.openoffice.org/e-files/3377/1/1.0-dev.oxt
$ unzip 1.0-dev.oxt
$ vim -u NONE --noplugin -c 'set nomore' -c 'mkspell! /tmp/eo
Hi,
I was exploring the possibility to use cindent for JavaScript code
indentation, because all the indent plugins I've tried so far make me
unhappy. I've found that it works pretty well (except for array
literals spanning multiple lines, though I'll try to fix it using
indentexpr similar to how
Dominique Pelle wrote:
Attached is a minor patch which removes some useless
checks for NULL pointer before calling vim_free() since
vim_free() already checks for NULL pointer.
Thanks!
--
Hit any key to continue it said, but nothing happened after F sharp.
/// Bram Moolenaar --
Ben Schmidt wrote:
On 30/01/11 11:05 AM, Marc Weber wrote:
Does the current vim.sf.net page tell about existing repositories where
vim patches mature ?
If if they are never merged upstream it would be nice to have a local
place to share them.
I know about a git repository which
Marc Weber wrote:
First of all: Why is setlocal aw allowed because its a global option
only.
We can have a long discussion about using :setlocal for a global option
should fail or not.
I'd like to tidy up optwin.vim and change its output maybe adding core
funtions which can be used to
Excerpts from Bram Moolenaar's message of Sun Jan 30 22:07:55 +0100 2011:
If we allow uploading patches and mark them as such it's mainly a matter
of adding a new script type. It's easier to explain that a script can
also be a patch than to start a whole new section which would be mostly
the
Reply to message «Re: optwin.vim - setlocal on global options ? ...»,
sent 00:07:54 31 January 2011, Monday
by Bram Moolenaar:
That might find the option window for another window. We need to find
the option window that belongs to the current window.
I don't understand you.
:wincmd v
Reply to message «Re: optwin.vim - setlocal on global options ? ...»,
sent 00:28:57 31 January 2011, Monday
by ZyX:
I don't understand you.
:wincmd v
:options
:wincmd h
:options
will bring me to the first option window. If you meant option window on
other tab, then Marc's
Excerpts from Bram Moolenaar's message of Sun Jan 30 22:07:54 +0100 2011:
We can have a long discussion about using :setlocal for a global option
should fail or not.
I think it should because it strengthens the user awareness about cope of
options.
Anyway: Is there a way to view/set both:
Reply to message «Re: optwin.vim - setlocal on global options ? ...»,
sent 00:36:46 31 January 2011, Monday
by Marc Weber:
Do you have a rough estimate about how long it takes on such slow
machines? Maybe I can can benchmark alternative solutions to find out
how much slower they would be.
My
On Fri, Jan 28, 2011 at 4:18 PM, Benjamin R. Haskell v...@benizi.com wrote:
On Fri, 28 Jan 2011, Britton Kerin wrote:
There is some strange bug that causes line numbers in errors coming from
perl to come out wrong in some circumstances.
This code:
perl END_PERL
# line 3
For the source from the download page I get this and the latest stable perl
(5.12.3), I get this:
$ ./configure --prefix=$HOME/local --enable-perlinterp=dynamic
$ make
[snip]
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK -pthread
-I/home/bkerin/local/include/gtk-2.0
Bram, have you had a moment to ponder about this issue? Is one of the
approaches reasonable or is there anything else to be investigated?
On Thu, Jan 27, 2011 at 09:39, Gustavo Niemeyer gust...@niemeyer.net wrote:
Hi Bram,
That doesn't look like the right solution, since it restarts from the
Anyway: Is there a way to view/set both: local and global settings for those
options which are both?
:set sets both, but displays the value in effect. To display both, you
need to use :setlocal and :setglobal.
Ben.
--
You received this message from the vim_dev maillist.
Do not top-post!
Reply to message «Re: optwin.vim - setlocal on global options ? ...»,
sent 02:56:03 31 January 2011, Monday
by Ben Schmidt:
It is also possible to use l:option and g:option. They are better then
parsing
:set* output.
Original message:
Anyway: Is there a way to view/set both: local and
On Sun, 30 Jan 2011, Britton Kerin wrote:
On Fri, Jan 28, 2011 at 4:18 PM, Benjamin R. Haskell wrote:
On Fri, 28 Jan 2011, Britton Kerin wrote:
There is some strange bug that causes line numbers in errors coming
from perl to come out wrong in some circumstances.
[...]
The fact that it
20 matches
Mail list logo
