Re: matchparen tweak
On Wed, Sep 06, 2006 at 02:15:36AM +0200, A.J.Mechelynck wrote: Benji Fisher wrote: Now that the problem has been pointed out, I think the patch should be made in the official distribution. How about (simple but oh, so clever) let plist = split(matchpairs, '.\zs.') which removes every second character? Will that have trouble with multibyte characters? Are these even allowed in 'matchpairs'? The help for 'matchparen' mentions only single characters which must be different. You might try it with Arabic ornate parentheses, U+FD3E (left i.e. closing) and U+FD3F (right i.e.opening), which are obviously meant to pair with each other. I assume you mean the help for 'matchpairs', not 'matchparen'. I tried :let mps = \uFD3E:\uFD3F :set mps? and the value was not changed. I think the docs should be changed to mention that multi-byte characters are not allowed; as I read it, single characters does not rule out multi-byte characters. I also do not like the absence of an error message. I guess this is an issue with :let since I do get an E474 from :set mps=C-VuFD3E:C-VuFD3F (*not* typed literally). IIUC, a dot in a pattern matches one character, which may be one or more bytes, and which may occupy one screen cell, two for a wide CJK character, one to eight for a tab, etc. Yes, and :echo split(\uFD3E:\uFD3F, '.\zs.') returns ['﴾', '﴿'] as expected. So I think my proposal for matchparen.vim is safe even if 'matchpairs' is changed to allow multi-byte characters. HTH --Benji Fisher
Help non-functional in 7.0.90
In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Running :helptags in the doc/ subdirectories of all 'rtp' directories doesn't help. Best regards, Tony.
Re: using hidden unlisted buffer as transparently as possible
Bram,
In a thread started here [0] back in July I reported a problem I was
having with messages not being displayed in the right order. It was
determined during that thread that there was a difference of behavior
based on whether hidden was set or not. Buried in one of the later
messages, I asked you if this was intentional or a bug, but I haven't
heard back from you. You weren't active on the list at the time; I
assume you were on vacation/moving. I guess that my buried query didn't
catch your attention when you were catching up on mail.
Here is the summary:
-
vim -u NONE -U NONE somefile.txt
:e testbuf.vim
if testbuf.vim is new, paste the TestBuf function below and :w
:let g:testbuf = 2 the buffer number of testbuf.vim
:so %
:b #
we are now set up to demonstrate the problem
:call TestBuf()
this should display Done with TestBuf (found = 3)
:set hidden
:call TestBuf()
this displays somefile.txt line 1 of...
:set nohidden
:call TestBuf()
this still displays somefile.txt...
You must switch buffers at least once after :set nohidden before you
get the original (desired) behavior back.
- TestBuf
function! TestBuf()
let curbuf = bufnr(%)
exec b g:testbuf
let found = search('t.st')
exec b curbuf
echomsg 'Done with TestBuf (found = '.found.')'
endfunction
-
A separate problem is that changing both occurrences of exec b... to
silent exec b... does not change anything; that is, the output of
exec b... is not suppressed (when hidden is set).
I feel that both of these are bugs, but I wanted to know if there was
a reason that you thought these were the correct behaviors (or perhaps
it is simply impractical to change).
Thanks...Marvin
[0] http://groups.yahoo.com/group/vimdev/message/44273
Re: Re: Help non-functional in 7.0.90
On 06/09/06, Charles E Campbell Jr [EMAIL PROTECTED] wrote: A.J.Mechelynck wrote: In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Running :helptags in the doc/ subdirectories of all 'rtp' directories doesn't help. I tried both vim and gvim 7.0.90, and didn't have the problem you're having. ie. :help :help worked as expected. (using Fedora Core 5/linux). Works for me as well, on Mac OS X (Intel) Cheers Adam
Re: Help non-functional in 7.0.90
On Wed 6-Sep-06 8:01am -0600, A.J.Mechelynck wrote: In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Both work fine for (g)vim on WinXP from both my normal starting or from a pristine start (see below): vim -u NONE -i NONE -N --cmd se rtp=$VIMRUNTIME -- Best regards, Bill
Re: using hidden unlisted buffer as transparently as possible
Marvin Renich wrote:
In a thread started here [0] back in July I reported a problem I was
having with messages not being displayed in the right order. It was
determined during that thread that there was a difference of behavior
based on whether hidden was set or not. Buried in one of the later
messages, I asked you if this was intentional or a bug, but I haven't
heard back from you. You weren't active on the list at the time; I
assume you were on vacation/moving. I guess that my buried query didn't
catch your attention when you were catching up on mail.
Here is the summary:
-
vim -u NONE -U NONE somefile.txt
:e testbuf.vim
if testbuf.vim is new, paste the TestBuf function below and :w
:let g:testbuf = 2 the buffer number of testbuf.vim
:so %
:b #
we are now set up to demonstrate the problem
:call TestBuf()
this should display Done with TestBuf (found = 3)
:set hidden
:call TestBuf()
this displays somefile.txt line 1 of...
:set nohidden
:call TestBuf()
this still displays somefile.txt...
You must switch buffers at least once after :set nohidden before you
get the original (desired) behavior back.
- TestBuf
function! TestBuf()
let curbuf = bufnr(%)
exec b g:testbuf
let found = search('t.st')
exec b curbuf
echomsg 'Done with TestBuf (found = '.found.')'
endfunction
-
A separate problem is that changing both occurrences of exec b... to
silent exec b... does not change anything; that is, the output of
exec b... is not suppressed (when hidden is set).
I feel that both of these are bugs, but I wanted to know if there was
a reason that you thought these were the correct behaviors (or perhaps
it is simply impractical to change).
After you do :set nohidden there still is one hidden buffer. Thus the
first TestBuf() after that will work a bit different from the next ones.
I do see a problem: The info about the current buffer is displayed even
though you edited another buffer. Thus the message should be given for
the un-hidden file but it's given for the other file, for which a
message was already given. I'll fix that.
--
Have you heard about the new Barbie doll? It's called Divorce
Barbie. It comes with all of Ken's stuff.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\download, build and distribute -- http://www.A-A-P.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
Re: Help non-functional in 7.0.90
Charles E Campbell Jr wrote: A.J.Mechelynck wrote: In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Running :helptags in the doc/ subdirectories of all 'rtp' directories doesn't help. I tried both vim and gvim 7.0.90, and didn't have the problem you're having. ie. :help :help worked as expected. (using Fedora Core 5/linux). Regards, Chip Campbell Then I wonder what went wrong. I rebooted and still got it; recompiled (make reconfig) with --disable-nls (in configure) and -multi_lang (by commenting away #define FEAT_MULTI_LANG in feature.h) and still got it -- in both gvim and console vim. Best regards, Tony.
Re: Help non-functional in 7.0.90
A.J.Mechelynck wrote: In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Running :helptags in the doc/ subdirectories of all 'rtp' directories doesn't help. Best regards, Tony. Cleaned my ~/.vim and $VIM/vimfiles from a few obsolete and dubious files, compiled 7.0.091 (with make reconfig), it works again (as src/vim). More fear than harm. Next thing is make install. Best regards, Tony.
Re: Help non-functional in 7.0.90
On Thu, 2006-09-07 at 01:57 +0200, A.J.Mechelynck wrote: A.J.Mechelynck wrote: In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Running :helptags in the doc/ subdirectories of all 'rtp' directories doesn't help. Best regards, Tony. Cleaned my ~/.vim and $VIM/vimfiles from a few obsolete and dubious files, compiled 7.0.091 (with make reconfig), it works again (as src/vim). More fear than harm. Next thing is make install. Best regards, Tony. tony -- all this weirdness with your help -- as dependant as we are on whatever is insalled for 'ctags', i'd say you might spend some time looking at whatever shows up for 'which ctags' with a thought towards maybe fixing something there scott
Re: Help non-functional in 7.0.90
scott wrote: On Thu, 2006-09-07 at 01:57 +0200, A.J.Mechelynck wrote: A.J.Mechelynck wrote: In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Running :helptags in the doc/ subdirectories of all 'rtp' directories doesn't help. Best regards, Tony. Cleaned my ~/.vim and $VIM/vimfiles from a few obsolete and dubious files, compiled 7.0.091 (with make reconfig), it works again (as src/vim). More fear than harm. Next thing is make install. Best regards, Tony. tony -- all this weirdness with your help -- as dependant as we are on whatever is insalled for 'ctags', i'd say you might spend some time looking at whatever shows up for 'which ctags' with a thought towards maybe fixing something there scott IIUC it's the version of ctags that came with SuSE 9.3 rpm -qa |grep ctags ctags-2004.11.15-3 which -a ctags /usr/bin/ctags ls -l `which ctags` -rwxr-xr-x 1 root root 128852 Mar 19 2005 /usr/bin/ctags ctags --version Exuberant Ctags 5.5.4, Copyright (C) 1996-2003 Darren Hiebert Compiled: Mar 19 2005, 19:18:40 Addresses: [EMAIL PROTECTED], http://ctags.sourceforge.net Optional compiled features: +wildcards, +regex The wierdness appeared after installing the manpageview plugin from vim-online, and disappeared after removing it as well as versions of the netrw and vimball plugins which had become older than the default ones due to a runtime rsync. Don't know what _any_ of those had to do with not finding the help; and (I checked) my doc/tags files were OK -- anyway, regenerating them all using (internal) helptags changed nothing. Best regards, Tony.
indenting weirdness
help! i'm at 7.0.90, but i've noticed the indenting weirdness before, so i don't know when it really started i think the other time(s) too it was in my 'ai' module, which, although it has a .txt extenstion, comes up with 'filetype=' so weird ok -- no filetype is defined -- fine -- this still should not happen, in my opinion with tw=70, which i set with an f-key defined in my .vimrc, typing the following gives: an optimistic man might be tempted to celebrate -- we have proven, after see? what the @[EMAIL PROTECTED]@? kind of indenting rule says to create a hanging indent after the first word... dunno why filetype is undefined, but i have filetype indent off, i've gotten so frustrated with unexpected indenting behavior if it's relevant, i open my 'ai' modules with a script that sources a vim script that does (after the comments): let s:name = '~/documents/txt/ai_' . strftime(%Y%m) . '.txt' execute e + s:name which *may* help explain why filetype is undefined, but not in any way explains why 'an' is something that requires a hanging indent to be created on the next line i've got: filetype on filetype indent off filetype plugin on filetype plugin indent off in my .vimrc, which is an attempt on my part to get control over how indenting happens, yet i STILL get surprised with unexpected behavior any clues will be appreciated sc
Re: indenting weirdness
Hello scott, The 'filetype=' message is what happens when you use ':set filetype=' and don't specify any filetype. If you have 'cindent' turned on, Vim will add an indent after a line ending in a comma (,) and your sample sentence does. Use ':set cindent?' to check if it is turned on. regards, Peter --- scott [EMAIL PROTECTED] wrote: help! i'm at 7.0.90, but i've noticed the indenting weirdness before, so i don't know when it really started i think the other time(s) too it was in my 'ai' module, which, although it has a .txt extenstion, comes up with 'filetype=' so weird ok -- no filetype is defined -- fine -- this still should not happen, in my opinion with tw=70, which i set with an f-key defined in my .vimrc, typing the following gives: an optimistic man might be tempted to celebrate -- we have proven, after see? what the @[EMAIL PROTECTED]@? kind of indenting rule says to create a hanging indent after the first word... dunno why filetype is undefined, but i have filetype indent off, i've gotten so frustrated with unexpected indenting behavior if it's relevant, i open my 'ai' modules with a script that sources a vim script that does (after the comments): let s:name = '~/documents/txt/ai_' . strftime(%Y%m) . '.txt' execute e + s:name which *may* help explain why filetype is undefined, but not in any way explains why 'an' is something that requires a hanging indent to be created on the next line i've got: filetype on filetype indent off filetype plugin on filetype plugin indent off in my .vimrc, which is an attempt on my part to get control over how indenting happens, yet i STILL get surprised with unexpected behavior any clues will be appreciated sc On Yahoo!7 Messenger - Make free PC-to-PC calls to your friends overseas. http://au.messenger.yahoo.com
Re: indenting weirdness
scott wrote: help! i'm at 7.0.90, but i've noticed the indenting weirdness before, so i don't know when it really started i think the other time(s) too it was in my 'ai' module, which, although it has a .txt extenstion, comes up with 'filetype=' so weird ok -- no filetype is defined -- fine -- this still should not happen, in my opinion with tw=70, which i set with an f-key defined in my .vimrc, typing the following gives: an optimistic man might be tempted to celebrate -- we have proven, after see? what the @[EMAIL PROTECTED]@? kind of indenting rule says to create a hanging indent after the first word... dunno why filetype is undefined, but i have filetype indent off, i've gotten so frustrated with unexpected indenting behavior if it's relevant, i open my 'ai' modules with a script that sources a vim script that does (after the comments): let s:name = '~/documents/txt/ai_' . strftime(%Y%m) . '.txt' execute e + s:name which *may* help explain why filetype is undefined, but not in any way explains why 'an' is something that requires a hanging indent to be created on the next line i've got: filetype on filetype indent off filetype plugin on filetype plugin indent off in my .vimrc, which is an attempt on my part to get control over how indenting happens, yet i STILL get surprised with unexpected behavior any clues will be appreciated sc :verbose set autoindent? smartindent? cindent? cinoptions? :verbose set copyindent? preserveindent? indentkeys? cinkeys? (don't forget the question marks of course) Best regards, Tony.
Re: Help non-functional in 7.0.90
On Thu, 2006-09-07 at 05:58 +0200, A.J.Mechelynck wrote: scott wrote: On Thu, 2006-09-07 at 01:57 +0200, A.J.Mechelynck wrote: A.J.Mechelynck wrote: In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Running :helptags in the doc/ subdirectories of all 'rtp' directories doesn't help. Best regards, Tony. Cleaned my ~/.vim and $VIM/vimfiles from a few obsolete and dubious files, compiled 7.0.091 (with make reconfig), it works again (as src/vim). More fear than harm. Next thing is make install. Best regards, Tony. tony -- all this weirdness with your help -- as dependant as we are on whatever is insalled for 'ctags', i'd say you might spend some time looking at whatever shows up for 'which ctags' with a thought towards maybe fixing something there scott IIUC it's the version of ctags that came with SuSE 9.3 rpm -qa |grep ctags ctags-2004.11.15-3 which -a ctags /usr/bin/ctags ls -l `which ctags` -rwxr-xr-x 1 root root 128852 Mar 19 2005 /usr/bin/ctags ctags --version Exuberant Ctags 5.5.4, Copyright (C) 1996-2003 Darren Hiebert Compiled: Mar 19 2005, 19:18:40 Addresses: [EMAIL PROTECTED], http://ctags.sourceforge.net Optional compiled features: +wildcards, +regex The wierdness appeared after installing the manpageview plugin from vim-online, and disappeared after removing it as well as versions of the netrw and vimball plugins which had become older than the default ones due to a runtime rsync. Don't know what _any_ of those had to do with not finding the help; and (I checked) my doc/tags files were OK -- anyway, regenerating them all using (internal) helptags changed nothing. Best regards, Tony. hmmm what jumped out at me in your error messages was the '@en' -- makes me think whatever happened to you relates to something to do with the english language -- did manpageview have a lot of klunky language weirdness? sc
Re: indenting weirdness
peter-- that was the clue i needed -- after turning 'cindent' off i was able to type an optimistic man might be tempted to celebrate -- we have proven, after all, that life goes on after microsoft -- macros can be created in OOo basic, however bloody without the indenting weirdness as much java and C# as i work on, i hope i can live without cindent, but between you and me, i'm betting off is better thanx! sc On Thu, 2006-09-07 at 14:08 +1000, Peter Hodge wrote: Hello scott, The 'filetype=' message is what happens when you use ':set filetype=' and don't specify any filetype. If you have 'cindent' turned on, Vim will add an indent after a line ending in a comma (,) and your sample sentence does. Use ':set cindent?' to check if it is turned on. regards, Peter --- scott [EMAIL PROTECTED] wrote: help! i'm at 7.0.90, but i've noticed the indenting weirdness before, so i don't know when it really started i think the other time(s) too it was in my 'ai' module, which, although it has a .txt extenstion, comes up with 'filetype=' so weird ok -- no filetype is defined -- fine -- this still should not happen, in my opinion with tw=70, which i set with an f-key defined in my .vimrc, typing the following gives: an optimistic man might be tempted to celebrate -- we have proven, after see? what the @[EMAIL PROTECTED]@? kind of indenting rule says to create a hanging indent after the first word... dunno why filetype is undefined, but i have filetype indent off, i've gotten so frustrated with unexpected indenting behavior if it's relevant, i open my 'ai' modules with a script that sources a vim script that does (after the comments): let s:name = '~/documents/txt/ai_' . strftime(%Y%m) . '.txt' execute e + s:name which *may* help explain why filetype is undefined, but not in any way explains why 'an' is something that requires a hanging indent to be created on the next line i've got: filetype on filetype indent off filetype plugin on filetype plugin indent off in my .vimrc, which is an attempt on my part to get control over how indenting happens, yet i STILL get surprised with unexpected behavior any clues will be appreciated sc On Yahoo!7 Messenger - Make free PC-to-PC calls to your friends overseas. http://au.messenger.yahoo.com
text is gone
ok, so help me out here i've looked at filetype vim, and i see nothing that associates _.txt modules with ft=txt whether i enter my 'ai' modules with the script or by navigating to where they are and, with my bloody fingers typing 'gvim ai_200609.txt', still, inside the module, filetype is undefined are we only supposed to use vim for exotic languages? is 'text' deprecated? i thought it used to suffice to have an extension of .txt now the ground is shifting under my feet... sc
Re: Help non-functional in 7.0.90
On Thu, 2006-09-07 at 06:55 +0200, A.J.Mechelynck wrote: scott wrote: On Thu, 2006-09-07 at 05:58 +0200, A.J.Mechelynck wrote: scott wrote: On Thu, 2006-09-07 at 01:57 +0200, A.J.Mechelynck wrote: A.J.Mechelynck wrote: In (g)vim 7.0.90, when I try to invoke the help, let's say :help :help the program hangs; and when I finally hit Ctrl-C I get: E426: tag not found: :[EMAIL PROTECTED] Similarly for F1 E426: tag not found: [EMAIL PROTECTED] Running :helptags in the doc/ subdirectories of all 'rtp' directories doesn't help. Best regards, Tony. Cleaned my ~/.vim and $VIM/vimfiles from a few obsolete and dubious files, compiled 7.0.091 (with make reconfig), it works again (as src/vim). More fear than harm. Next thing is make install. Best regards, Tony. tony -- all this weirdness with your help -- as dependant as we are on whatever is insalled for 'ctags', i'd say you might spend some time looking at whatever shows up for 'which ctags' with a thought towards maybe fixing something there scott IIUC it's the version of ctags that came with SuSE 9.3 rpm -qa |grep ctags ctags-2004.11.15-3 which -a ctags /usr/bin/ctags ls -l `which ctags` -rwxr-xr-x 1 root root 128852 Mar 19 2005 /usr/bin/ctags ctags --version Exuberant Ctags 5.5.4, Copyright (C) 1996-2003 Darren Hiebert Compiled: Mar 19 2005, 19:18:40 Addresses: [EMAIL PROTECTED], http://ctags.sourceforge.net Optional compiled features: +wildcards, +regex The wierdness appeared after installing the manpageview plugin from vim-online, and disappeared after removing it as well as versions of the netrw and vimball plugins which had become older than the default ones due to a runtime rsync. Don't know what _any_ of those had to do with not finding the help; and (I checked) my doc/tags files were OK -- anyway, regenerating them all using (internal) helptags changed nothing. Best regards, Tony. hmmm what jumped out at me in your error messages was the '@en' -- makes me think whatever happened to you relates to something to do with the english language -- did manpageview have a lot of klunky language weirdness? sc I didn't check (and now it's gone thanks to rm -vf); but after recompiling (make reconfig but not make install) with (a) a define commented-out: /* # define FEAT_MULTI_LANG */ (b) an additional configure setting: export CONF_OPT_NLS='--disable-nls', and (c) renaming $VIMRUNTIME/lang to lanx (probably overkill but you never know...), I got the same error without the @en IIUC that @xx postfix is characteristic of multi-language help. My vimrc sets :language messages to C (on Unix) or en (on Windows) before sourcing the vimrc_example, to avoid French or Dutch menus and error messages regardless of the locale. Now I have undone all those changes, removed, as I said, the dubious plugins, re-made reconfig, and my 7.0.091 again shows any help with no noticeable lag. The only global plugins which I still have outside $VIMRUNTIME/plugin are matchit (runtime macros/matchit.vim) and a small plugin I wrote myself to display the splash screen (:intro) at the VimEnter event, even when Vim is started with one or more editfiles named on the command-line. Best regards, Tony. IIUC, your problem has been solved? no more goofy :help errors?
