> Does anyone know if it is possible to automatically disable caps lock
> when I exit insert mode? I often enable it to type the name of
> variables, and then forget to disable it when I exit insert mode.
>
> Then pressing "j" joins lines, and to my frustration pressing "u" will
> not undo it back as expected. At this point I realize my stupidity in
> having left caps lock on, and after correcting the error and swearing at
> the monitor I return to my blissful state.

Sorry for the late reply, but
http://www.vim.org/scripts/script.php?script_id=1725
might be what you want.

Nico
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Fri, Aug 01, 2008 at 03:57:32AM -0700, Nico Weber wrote:

>> Does anyone know if it is possible to automatically disable caps lock
>> when I exit insert mode? I often enable it to type the name of
>> variables, and then forget to disable it when I exit insert mode.
>>
>> Then pressing "j" joins lines, and to my frustration pressing "u" will
>> not undo it back as expected. At this point I realize my stupidity in
>> having left caps lock on, and after correcting the error and swearing at
>> the monitor I return to my blissful state.
>
> Sorry for the late reply, but
> http://www.vim.org/scripts/script.php?script_id=1725 might be what you
> want.

That's *PERFECT*! Thanks,

GI

--
If life gives you llamas, make llamanade.

Hello Vim Developers,

Opening a file with full path name changes the directory.
For example:

     gvim -u NONE -N  \vim\vimfiles\myfile.vim

keeps my current directory.  However,

     gvim -u NONE -N  c:\vim\vimfiles\myfile.vim

changes the directory, in vim, to c:\vim\vimfiles.

--
Best regards,
Bill


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reading about omnicomplete and thereabouts in the docs, I found
out about the thesaurus facility.  I can see this could be quite useful
in breaking writing habits.  However, the text in the help file
(:he thesaurus) says

To obtain a file to be used here, check out the wordlist FAQ at
http://www.hyphenologist.co.uk .

I've tried that and there is a link to word lists.  This link is broken,
however.  So, I did my best to find another source for such a file so
I could send a helpful patch.  However, I can't find a free file of
this kind on the internet, and anything else would lead to copyright
issues.

So, are people known to be using this, and would the people who are
be willing to help someone (that will probably end up being me now
I've started this!) compile a file which could be distributed with Vim?

I've looked at Wordnet, and the output is designed to be read by
humans, and generating a comprehensive list of suitable thesaurus
entries would thus be nontrivial.  But if it is the only way I will try
that.

And I have one more question about the file format for the thesaurus:
I understand words follow the pattern of keywords.  Take the word
"chatter".  Wordnet turns up the following as thesaurus entries:

chew the fat, shoot the breeze, chat, confabulate, confab, chitchat,
chit-chat,
chatter, chaffer, natter, gossip, jaw, claver, visit

A significant number of these contain whitespace or hyphens.  Is the
thesaurus facility in Vim unable to cope with that, or have I missed a
way of composing the file so it could?  I wondered about some kind of
non-breaking space that one might use instead.  Failing that, one might
use "_" I suppose.

     Thank you
     Hugh


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 03/08/08 00:51, H. Sasse wrote:
> Reading about omnicomplete and thereabouts in the docs, I found
> out about the thesaurus facility.  I can see this could be quite useful
> in breaking writing habits.  However, the text in the help file
> (:he thesaurus) says
>
> To obtain a file to be used here, check out the wordlist FAQ at
> http://www.hyphenologist.co.uk .
>
> I've tried that and there is a link to word lists.  This link is broken,
> however.  So, I did my best to find another source for such a file so
> I could send a helpful patch.  However, I can't find a free file of
> this kind on the internet, and anything else would lead to copyright
> issues.

I don't see a broken link but a forbidden link:

*Forbidden*
You don't have permission to access /wordlist/ on this server.

Since anything ending in .co.uk means a British _commercial_ site, I
suppose you have to register (for £££) before you can get access to the
wordlists. This, of course, leaves whole the problem of how to get a
free thesaurus. Maybe there is none.

>
> So, are people known to be using this, and would the people who are
> be willing to help someone (that will probably end up being me now
> I've started this!) compile a file which could be distributed with Vim?
>
> I've looked at Wordnet, and the output is designed to be read by
> humans, and generating a comprehensive list of suitable thesaurus
> entries would thus be nontrivial.  But if it is the only way I will try
> that.
>
> And I have one more question about the file format for the thesaurus:
> I understand words follow the pattern of keywords.  Take the word
> "chatter".  Wordnet turns up the following as thesaurus entries:
>
> chew the fat, shoot the breeze, chat, confabulate, confab, chitchat,
> chit-chat,
> chatter, chaffer, natter, gossip, jaw, claver, visit
>
> A significant number of these contain whitespace or hyphens.  Is the
> thesaurus facility in Vim unable to cope with that, or have I missed a
> way of composing the file so it could?  I wondered about some kind of
> non-breaking space that one might use instead.  Failing that, one might
> use "_" I suppose.
>
>      Thank you
>      Hugh
>
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
93. New mail alarm on your palmtop annoys other churchgoers.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Sun, Aug 03, 2008 at 12:51:40 +0200, Tony Mechelynck wrote:
>
> On 03/08/08 00:51, H. Sasse wrote:
> > Reading about omnicomplete and thereabouts in the docs, I found
> > out about the thesaurus facility.  I can see this could be quite useful
> > in breaking writing habits.  However, the text in the help file
> > (:he thesaurus) says
> >
> > To obtain a file to be used here, check out the wordlist FAQ at
> > http://www.hyphenologist.co.uk .
> >
> > I've tried that and there is a link to word lists.  This link is broken,
> > however.  So, I did my best to find another source for such a file so
> > I could send a helpful patch.  However, I can't find a free file of
> > this kind on the internet, and anything else would lead to copyright
> > issues.
>
> I don't see a broken link but a forbidden link:
>
> *Forbidden*
> You don't have permission to access /wordlist/ on this server.

Looks like all the webpage files got deleted. The WayBack Machine shows
the site alive about a year ago and there is a link to some wordlists:
ftp://ftp.ox.ac.uk/pub/wordlists/

> Since anything ending in .co.uk means a British _commercial_ site, I
> suppose you have to register (for £££) before you can get access to the
> wordlists. This, of course, leaves whole the problem of how to get a
> free thesaurus. Maybe there is none.
>
> >
> > So, are people known to be using this, and would the people who are
> > be willing to help someone (that will probably end up being me now
> > I've started this!) compile a file which could be distributed with Vim?
> >
> > I've looked at Wordnet, and the output is designed to be read by
> > humans, and generating a comprehensive list of suitable thesaurus
> > entries would thus be nontrivial.  But if it is the only way I will try
> > that.

Well, Wordnet code is open source and there is also documentation for
the database files, so it should not be that complicated to extract just
the thesaurus part.

Regards,
Peter

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Sunday 03 August 2008 06:46, Peter Cech wrote:
>
> On Sun, Aug 03, 2008 at 12:51:40 +0200, Tony Mechelynck wrote:
> >
> > On 03/08/08 00:51, H. Sasse wrote:
> > > Reading about omnicomplete and thereabouts in the docs, I found
> > > out about the thesaurus facility.  I can see this could be quite useful
> > > in breaking writing habits.  However, the text in the help file
> > > (:he thesaurus) says
> > >
> > > To obtain a file to be used here, check out the wordlist FAQ at
> > > http://www.hyphenologist.co.uk .
> > >
> > > I've tried that and there is a link to word lists.  This link is broken,
> > > however.  So, I did my best to find another source for such a file so
> > > I could send a helpful patch.  However, I can't find a free file of
> > > this kind on the internet, and anything else would lead to copyright
> > > issues.
> >
> > I don't see a broken link but a forbidden link:
> >
> > *Forbidden*
> > You don't have permission to access /wordlist/ on this server.
>
> Looks like all the webpage files got deleted. The WayBack Machine shows
> the site alive about a year ago and there is a link to some wordlists:
> ftp://ftp.ox.ac.uk/pub/wordlists/
>
> > Since anything ending in .co.uk means a British _commercial_ site, I
> > suppose you have to register (for £££) before you can get access to the
> > wordlists. This, of course, leaves whole the problem of how to get a
> > free thesaurus. Maybe there is none.
> >
> > >
> > > So, are people known to be using this, and would the people who are
> > > be willing to help someone (that will probably end up being me now
> > > I've started this!) compile a file which could be distributed with Vim?
> > >
> > > I've looked at Wordnet, and the output is designed to be read by
> > > humans, and generating a comprehensive list of suitable thesaurus
> > > entries would thus be nontrivial.  But if it is the only way I will try
> > > that.
>
> Well, Wordnet code is open source and there is also documentation for
> the database files, so it should not be that complicated to extract just
> the thesaurus part.
>
> Regards,
> Peter

i can't say how good it is, but it appears there is a
downloadable thesaurus at

     http://www.translatum.gr/dictionaries/download-english.htm

sc



--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Andy Kittner wrote:

> While toying around with a few things I found a small memory leak
> with valgrind.
>
> In something like this:
> :python << END_PY
>       [...]
> END_PY
>
> The line containing the endmarker is not freed.
>
> The following patch should fix it:

Thanks for finding and fixing this!

--
Two cows are standing together in a field.  One asks the other:
"So what do you think about this Mad Cow Disease?"
The other replies: "That doesn't concern me. I'm a helicopter."

  /// Bram Moolenaar -- Bram@... -- 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    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Bill McCarthy wrote:

> Hello Vim Developers,
>
> Opening a file with full path name changes the directory.
> For example:
>
>     gvim -u NONE -N  \vim\vimfiles\myfile.vim
>
> keeps my current directory.  However,
>
>     gvim -u NONE -N  c:\vim\vimfiles\myfile.vim
>
> changes the directory, in vim, to c:\vim\vimfiles.

That is normal.

Reason is that when Vim sees the full path it assumes it is invoked by
the Explorer, possibly from the desktop.  There is no other way to
detect that.

--
ARTHUR:   Ni!
BEDEVERE: Nu!
ARTHUR:   No.  Ni!  More like this. "Ni"!
BEDEVERE: Ni, ni, ni!
                  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

  /// Bram Moolenaar -- Bram@... -- 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    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Patch 7.2b.026
Problem:    The GTK 2 file chooser causes the ~/.recently-used.xbel file to be
	     written over and over again.  This may cause a significant
	     slowdown. (Guido Berhoerster)
Solution:   Don't use the GTK 2 file chooser.
Files:     src/gui_gtk.c


*** ../vim-7.2b.025/src/gui_gtk.c Tue Jun 24 23:53:45 2008
--- src/gui_gtk.c Thu Jul 31 21:48:20 2008
***************
*** 1195,1201 ****
    * Implementation of the file selector related stuff
    */
   #if defined(HAVE_GTK2) && GTK_CHECK_VERSION(2,4,0)
! # define USE_FILE_CHOOSER
   #endif

   #ifndef USE_FILE_CHOOSER
--- 1195,1204 ----
    * Implementation of the file selector related stuff
    */
   #if defined(HAVE_GTK2) && GTK_CHECK_VERSION(2,4,0)
! /* This has been disabled, because the GTK library rewrites
!  * ~/.recently-used.xbel every time the main loop is quit.  For Vim that means
!  * on just about any event. */
! /* # define USE_FILE_CHOOSER */
   #endif

   #ifndef USE_FILE_CHOOSER
*** ../vim-7.2b.025/src/version.c Thu Jul 31 22:03:26 2008
--- src/version.c Thu Jul 31 22:28:33 2008
***************
*** 678,679 ****
--- 678,681 ----
   {   /* Add new patch number below this line */
+ /**/
+     26,
   /**/

--
Be nice to your kids...  they'll be the ones choosing your nursing home.

  /// Bram Moolenaar -- Bram@... -- 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    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Hi,

While toying around with a few things I found a small memory leak
with valgrind.

In something like this:
:python << END_PY
       [...]
END_PY

The line containing the endmarker is not freed.

The following patch should fix it:

diff --git a/src/ex_getln.c b/src/ex_getln.c
index 38e0fe8..624bf1c 100644
--- a/src/ex_getln.c
+++ b/src/ex_getln.c
@@ -6252,7 +6252,10 @@ script_get(eap, cmd)
 	     NUL, eap->cookie, 0);

 	 if (theline == NULL || STRCMP(end_pattern, theline) == 0)
+ {
+     vim_free(theline);
 	     break;
+ }

 	 ga_concat(&ga, theline);
 	 ga_append(&ga, '\n');

Best regards,
Andy

--
Magic is always the best solution -- especially reliable magic.

Hi,

This is my first attempt at modifying vim, so please bear with me.

I liked the idea of being able to display the word count for the
buffer on the status line. So I've made a patch which draws on code
from the g<CTRL-g> option and adds 'D' as a status line option for
showing the word count.

The patch involves making the line_count_info function from ops.c
non-static and using it in buffer.c.

As a disclaimer I'd say, whilst I'm an ok programmer, I don't use C
that much and so don't know the best practices nor all the
consequences of my actions!

My main concern is that it might be slow, but it seemed fine on the
59000+ words of spell.c so I hope it'll be acceptable. That said I'm
very happy for someone else to make it better or advise me on how to
make it better.

Cheers,
Michael

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

sc wrote:
> On Sunday 03 August 2008 06:46, Peter Cech wrote:
>
>> On Sun, Aug 03, 2008 at 12:51:40 +0200, Tony Mechelynck wrote:
>>
>>> On 03/08/08 00:51, H. Sasse wrote:
>>>
>>>> [...] in the help file
>>>> (:he thesaurus) says
>>>>
>>>> To obtain a file to be used here, check out the wordlist FAQ at
>>>> http://www.hyphenologist.co.uk .
>>>>
>>>> I've tried that and there is a link to word lists.  This link is broken,
>>>>
>>>>
>>> I don't see a broken link but a forbidden link:
>>>
>>> *Forbidden*
>>> You don't have permission to access /wordlist/ on this server.
>>>
OK, technically not broken, but as good as broken in that "it no longer
works".

>> Looks like all the webpage files got deleted. The WayBack Machine shows
>> the site alive about a year ago and there is a link to some wordlists:
>> ftp://ftp.ox.ac.uk/pub/wordlists/
>>
Those appear to be lists of words.  No thesaurus file.
>>
>>> Since anything ending in .co.uk means a British _commercial_ site, I
>>> suppose you have to register (for £££) before you can get access to the
>>>
No, I pruned the URL back to the main site and there is no way to do that.
Also, the assumption is false that it would be necessary to register on
a .co.uk
site:  *.demon.co.uk have been indivual sites provided by an ISP.  Also
bbc.co.uk
provides quite a lot of free content.  There are .co.uk mirrors, to keep
stuff local
[ or "for all the jackdaw reasons" :-)]
>>> wordlists. This, of course, leaves whole the problem of how to get a
>>> free thesaurus. Maybe there is none.
>>>
>>>
>>>> So, are people known to be using this, and would the people who are
>>>> be willing to help someone (that will probably end up being me now
>>>> I've started this!) compile a file which could be distributed with Vim?
>>>>
>>>> I've looked at Wordnet, and the output is designed to be read by
>>>> humans, and generating a comprehensive list of suitable thesaurus
>>>> entries would thus be nontrivial.  But if it is the only way I will try
>>>> that.
>>>>
>> Well, Wordnet code is open source and there is also documentation for
>> the database files, so it should not be that complicated to extract just
>> the thesaurus part.
>>
If people are using this feature in Vim, it shouldn't even be necessary.

>> Regards,
>> Peter
>>
>
> i can't say how good it is, but it appears there is a
> downloadable thesaurus at
>
>     http://www.translatum.gr/dictionaries/download-english.htm
>
>
That seems to be a list of software.  There is the Gutenburg Roget's
Thesaurus,
and provided the "Small Print" section is removed then I think we can
use that
instead, but it will need more work.

So, is anyone using this feature, is there a way to include spaces in a
word, and
is there any interest in providing a thesaurus file hosted at the vim site?

     Hugh


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

In non-gui vim the color of the visual selection is reverse instead of grey,
if t_Co > 8. It should only be reversed if t_Co <= 8.

":hi Visual" still contains cterm=reverse after setting t_Co to >8, so I think
this is used instead of ctermbg=7 (grey). After ":hi clear" it's cleaned up
and the color is shown as intended.

to reproduce it:
vim -u NONE

:set t_Co?
   t_Co=8 (for me)
:hi Visual
   Visual         xxx term=reverse cterm=reverse guibg=LightGrey
write some text and test visual mode, it's reversed (correct)

:set t_Co=16
:hi Visual
   Visual         xxx term=reverse cterm=reverse ctermbg=7 guibg=LightGrey
test visual mode, it's still reversed (wrong)

:hi clear
:hi Visual
   Visual         xxx term=reverse ctermbg=7 guibg=LightGrey
test visual mode, now it's grey (correct)

:set t_Co=8
:hi Visual
   Visual         xxx term=reverse cterm=reverse ctermbg=7 guibg=LightGrey
test visual mode, it's already (in contrast to t_Co=16) reversed (correct)

:hi clear
:hi Visual
   Visual         xxx term=reverse cterm=reverse guibg=LightGrey
test visual mode, it's still reversed (correct)


I have two solutions and think the first one is acceptable.


1st solution:

*** src/syntax.c (revision 1143)
--- src/syntax.c (working copy)
***************
*** 6461,6471 ****
        * With 8 colors brown is equal to yellow, need to use black for Search fg
        * to avoid Statement highlighted text disappears. */
       if (t_colors > 8)
!  do_highlight((char_u *)(*p_bg == 'l' ? "Visual ctermbg=LightGrey"
! 				   : "Visual ctermbg=DarkGrey"), FALSE, TRUE);
       else
       {
!  do_highlight((char_u *)"Visual cterm=reverse", FALSE, TRUE);
  	 if (*p_bg == 'l')
  	     do_highlight((char_u *)"Search ctermfg=black", FALSE, TRUE);
       }
--- 6461,6471 ----
        * With 8 colors brown is equal to yellow, need to use black for Search fg
        * to avoid Statement highlighted text disappears. */
       if (t_colors > 8)
!  do_highlight((char_u *)(*p_bg == 'l' ? "Visual cterm=NONE ctermbg=LightGrey"
! 				   : "Visual cterm=NONE ctermbg=DarkGrey"), FALSE, TRUE);
       else
       {
!  do_highlight((char_u *)"Visual cterm=reverse ctermbg=NONE", FALSE, TRUE);
  	 if (*p_bg == 'l')
  	     do_highlight((char_u *)"Search ctermfg=black", FALSE, TRUE);
       }


2nd solution:

*** src/option.c (revision 1143)
--- src/option.c (working copy)
***************
*** 5985,5991 ****
  		 T_CCO = empty_option;
  	     }
  	     /* We now have a different color setup, initialize it again. */
! 	    init_highlight(TRUE, FALSE);
  	 }
  	 ttest(FALSE);
  	 if (varp == &T_ME)
--- 5985,5991 ----
  		 T_CCO = empty_option;
  	     }
  	     /* We now have a different color setup, initialize it again. */
! 	    init_highlight(TRUE, TRUE);
  	 }
  	 ttest(FALSE);
  	 if (varp == &T_ME)


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Vim mostly doesn't find single-letter help tags even though they are in
$VIMRUNTIME/doc/tags (as found by looking under ":help help-tags")

Examples:
	 :help A finds *'A* in motion.txt
		 instead of *A* in insert.txt
	 :help B finds *b:match_iniBR* in $VIM/vimfiles/doc/matchit.txt
		 instead of *B* in motion.txt
	 :help C finds *'t_CS'* in term.txt
		 instead of *C* in change.txt
	 etc.
	 :help x finds *-x* in starting.txt
		 instead of *x* in change.txt
	 :help y finds *-y* in starting.txt
		 instead of *y* in change.txt
	 :help z finds *z* in index.txt (OK)

Notes:
- I'm using 'ignorecase'
- The doc/tags file includes none of the following lines, which ctags
writes near the top of its output:
!_TAG_FILE_FORMAT 2 /extended format; --format=1 will not append ;" to
lines/
!_TAG_FILE_SORTED 1 /0=unsorted, 1=sorted, 2=foldcase/
!_TAG_PROGRAM_AUTHOR Darren Hiebert /dhiebert@.../
!_TAG_PROGRAM_NAME Exuberant Ctags //
!_TAG_PROGRAM_URL http://ctags.sourceforge.net /official site/
!_TAG_PROGRAM_VERSION 5.7 //

Looks to me as if Vim was using the first tag found with even a partial
match, instead of always preferring a full match.

After reading ":help {subject}" attentively, I still think this is a
bug, otherwise there's no way to match the helptags A B C ... x y
mentioned above.


Best regards,
Tony.
--
"Nuclear war would mean abolition of most comforts, and disruption of
normal routines, for children and adults alike."
		 -- Willard F. Libby, "You *Can* Survive Atomic Attack"

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Sunday 03 August 2008 19:29, Tony Mechelynck wrote:
>
> Vim mostly doesn't find single-letter help tags even though they are in
> $VIMRUNTIME/doc/tags (as found by looking under ":help help-tags")
>
> Examples:
>  :help A finds *'A* in motion.txt
> 	 instead of *A* in insert.txt
>  :help B finds *b:match_iniBR* in $VIM/vimfiles/doc/matchit.txt
> 	 instead of *B* in motion.txt
>  :help C finds *'t_CS'* in term.txt
> 	 instead of *C* in change.txt
>  etc.
>  :help x finds *-x* in starting.txt
> 	 instead of *x* in change.txt
>  :help y finds *-y* in starting.txt
> 	 instead of *y* in change.txt
>  :help z finds *z* in index.txt (OK)
>
> Notes:
> - I'm using 'ignorecase'
> - The doc/tags file includes none of the following lines, which ctags
> writes near the top of its output:
> !_TAG_FILE_FORMAT 2 /extended format; --format=1 will not append ;" to
> lines/
> !_TAG_FILE_SORTED 1 /0=unsorted, 1=sorted, 2=foldcase/
> !_TAG_PROGRAM_AUTHOR Darren Hiebert /dhiebert@.../
> !_TAG_PROGRAM_NAME Exuberant Ctags //
> !_TAG_PROGRAM_URL http://ctags.sourceforge.net /official site/
> !_TAG_PROGRAM_VERSION 5.7 //
>
> Looks to me as if Vim was using the first tag found with even a partial
> match, instead of always preferring a full match.
>
> After reading ":help {subject}" attentively, I still think this is a
> bug, otherwise there's no way to match the helptags A B C ... x y
> mentioned above.
>
>
> Best regards,
> Tony.

i see the same thing, and i am _not_ ignoring case

sc



--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Tony Mechelynck wrote:
> Vim mostly doesn't find single-letter help tags even though they are in
> $VIMRUNTIME/doc/tags (as found by looking under ":help help-tags")
>
> Examples:

I get buggy but different behaviour!

> Looks to me as if Vim was using the first tag found with even a partial
> match, instead of always preferring a full match.
>
> After reading ":help {subject}" attentively, I still think this is a
> bug, otherwise there's no way to match the helptags A B C ... x y
> mentioned above.

It's a newly introduced bug too.

I'll see if I can find it...

Yep. It was introduced with Vim 7.2b. The following patch introduces it,
consequently reversing the patch fixes it. It's pretty obvious what the
problem is, and simple to fix, but I'll leave it to Bram to decide
exactly how he wants to fix it.

Ben.



diff -r e6e5d578b132 -r 0b95aebcd055 runtime/doc/cmdline.txt
--- a/runtime/doc/cmdline.txt Mon Jul 14 04:36:41 2008 +1000
+++ b/runtime/doc/cmdline.txt Mon Jul 14 04:46:54 2008 +1000
@@ -369,7 +369,9 @@
   - Variable and function names: Only after a ":if", ":call" or similar command.

   When Vim was compiled with the |+cmdline_compl| feature disabled, only file
-names, directories and help items can be completed.
+names, directories and help items can be completed.  The number of help item
+matches is limited (currently to 300) to avoid a long delay when there are
+very many matches.

   These are the commands that can be used:

diff -r e6e5d578b132 -r 0b95aebcd055 src/ex_cmds.c
--- a/src/ex_cmds.c Mon Jul 14 04:36:41 2008 +1000
+++ b/src/ex_cmds.c Mon Jul 14 04:46:54 2008 +1000
@@ -5892,7 +5892,7 @@
       flags = TAG_HELP | TAG_REGEXP | TAG_NAMES | TAG_VERBOSE;
       if (keep_lang)
  	 flags |= TAG_KEEP_LANG;
-    if (find_tags(IObuff, num_matches, matches, flags, (int)MAXCOL, NULL) == OK
+    if (find_tags(IObuff, num_matches, matches, flags, TAG_MANY, NULL) == OK
  	     && *num_matches > 0)
  	 /* Sort the matches found on the heuristic number that is after the
  	  * tag name. */



--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On Sun 3-Aug-08 3:17pm -0600, Bram Moolenaar wrote:
> Bill McCarthy wrote:

>> Opening a file with full path name changes the directory.
>> For example:
>>
>>     gvim -u NONE -N  \vim\vimfiles\myfile.vim
>>
>> keeps my current directory.  However,
>>
>>     gvim -u NONE -N  c:\vim\vimfiles\myfile.vim
>>
>> changes the directory, in vim, to c:\vim\vimfiles.

> That is normal.
>
> Reason is that when Vim sees the full path it assumes it is invoked by
> the Explorer, possibly from the desktop.  There is no other way to
> detect that.

If you mean Windows Explorer, won't that set the current
directory to "C:\Documents and Settings\Bill\Desktop"?

What wrong with that?  I would much rather that behavior
than have Vim change directories on its own.

--
Best regards,
Bill


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

I wrote the patch that introduced the bug and I will be happy to fix
it. It was
written to solve the problem that doing :h <ctrl-d> would take a long
time to
show every help tag. It could be changed so that it only limits it in
that
specific case. Do you have any other ideas? If not, I will do that
one.

- Ian Kelling

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

When vim is in diff mode and a BufWrite autocommand containing a
"<range>g" is executed, the g command appears to ignore the range
and act on the entire buffer.

Here's an example.

Create a file containing the integers from 1 to 1000, each on a
separate line:

    $ seq 1000 > seq1

Create the following vim script and name it "test1.vim":

    au BufWrite * 1,100g/50$/s/$/\tchanged here/

When that autocommand is triggered by writing the buffer, it should
append "\tchanged here" to every line in the range 1 to 100 ending
in "50".  That is, it should change line 50 and only line 50.

Now edit seq1 with vim, source the script, open a new buffer, and
read seq1 into that buffer:

    $ vim -N -u NONE -i NONE -c 'so test1.vim' -c 'vnew|r seq1|normal ggdd' seq1

There's nothing magic about doing that on the command line--I just
got tired of typing all those vim commands as I worked on making the
example smaller.

Now move the cursor to the right window (^W^W) and write the buffer
to the seq1 file by executing:

    :w

Note that line 50 and only line 50 has changed to:

    50      changed here

This is as it should be.

Now diff the two buffers:

    :windo diffthis

and write the right buffer again:

    :w

Note now that every line in the file ending in "50" (i.e., 150, 250,
350, 450, 550, 650, 750, 850 and 950) has been appended with
"changed here".  This appears to be a bug.


I am using vim-7.2b (no patches) on a machine running Red Hat
Enterprise Linux WS release 4 (Nahant Update 5).  The output of "vim
--version" is:

VIM - Vi IMproved 7.2b BETA (2008 Jul 13, compiled Jul 15 2008 13:42:47)
Compiled by garyjohn@...
Normal version with GTK2 GUI.  Features included (+) or not (-):
-arabic +autocmd +balloon_eval +browse +builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs +dnd -ebcdic
-emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path +find_in_path
+float +folding -footer +fork() +gettext -hangul_input +iconv +insert_expand
+jumplist -keymap -langmap +libcall +linebreak +lispindent +listcmds +localmap
+menu +mksession +modify_fname +mouse +mouseshape -mouse_dec +mouse_gpm
-mouse_jsbterm -mouse_netterm -mouse_sysmouse +mouse_xterm +multi_byte
+multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra -perl +postscript
+printer -profile -python +quickfix +reltime -rightleft -ruby +scrollbind
+signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title
  +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
+vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim
+xsmp_interact +xterm_clipboard -xterm_save
    system vimrc file: "$VIM/vimrc"
      user vimrc file: "$HOME/.vimrc"
       user exrc file: "$HOME/.exrc"
   system gvimrc file: "$VIM/gvimrc"
     user gvimrc file: "$HOME/.gvimrc"
     system menu file: "$VIMRUNTIME/menu.vim"
   fall-back for $VIM: "/home/garyjohn/src/Linux/vim-7.2b/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -DXTHREADS
-D_REENTRANT -DXUSE_MTSAFE_API -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
-I/usr/X11R6/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0
-I/usr/include/freetype2 -I/usr/include/freetype2/config -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include     -g -O2  -I/usr/X11R6/include
Linking: gcc  -L/usr/X11R6/lib   -L/usr/local/lib -o vim   -Wl,--export-dynamic
-lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangoxft-1.0
-lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -lglib-2.0   -lXt -lm
-lncurses -lselinux -lacl -lgpm


Regards,
Gary


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Ben Schmidt wrote:

> Tony Mechelynck wrote:
> > Vim mostly doesn't find single-letter help tags even though they are in
> > $VIMRUNTIME/doc/tags (as found by looking under ":help help-tags")
> >
> > Examples:
>
> I get buggy but different behaviour!
>
> > Looks to me as if Vim was using the first tag found with even a partial
> > match, instead of always preferring a full match.
> >
> > After reading ":help {subject}" attentively, I still think this is a
> > bug, otherwise there's no way to match the helptags A B C ... x y
> > mentioned above.
>
> It's a newly introduced bug too.
>
> I'll see if I can find it...
>
> Yep. It was introduced with Vim 7.2b. The following patch introduces it,
> consequently reversing the patch fixes it. It's pretty obvious what the
> problem is, and simple to fix, but I'll leave it to Bram to decide
> exactly how he wants to fix it.

Yeah, the problem is that the number of tags is restricted before
sorting them on relevance.  Try the patch below.


*** ../vim-7.2b.026/src/ex_cmds.c Thu Jul 24 21:30:10 2008
--- src/ex_cmds.c Mon Aug  4 21:15:00 2008
***************
*** 5897,5908 ****
       flags = TAG_HELP | TAG_REGEXP | TAG_NAMES | TAG_VERBOSE;
       if (keep_lang)
  	 flags |= TAG_KEEP_LANG;
!     if (find_tags(IObuff, num_matches, matches, flags, TAG_MANY, NULL) == OK
  	     && *num_matches > 0)
  	 /* Sort the matches found on the heuristic number that is after the
  	  * tag name. */
  	 qsort((void *)*matches, (size_t)*num_matches,
  					       sizeof(char_u *), help_compare);
       return OK;
   }

--- 5897,5913 ----
       flags = TAG_HELP | TAG_REGEXP | TAG_NAMES | TAG_VERBOSE;
       if (keep_lang)
  	 flags |= TAG_KEEP_LANG;
!     if (find_tags(IObuff, num_matches, matches, flags, (int)MAXCOL, NULL) ==
OK
  	     && *num_matches > 0)
+     {
  	 /* Sort the matches found on the heuristic number that is after the
  	  * tag name. */
  	 qsort((void *)*matches, (size_t)*num_matches,
  					       sizeof(char_u *), help_compare);
+  /* Delete more than TAG_MANY to reduce the size of the listing. */
+  while (*num_matches > TAG_MANY)
+ 	    vim_free((*matches)[--*num_matches]);
+     }
       return OK;
   }



--
TALL KNIGHT:   Firstly.  You must get us another shrubbery!
OTHER KNIGHTS: More shrubberies!  More shrubberies for the ex-Knights of Ni!
ARTHUR:        Not another shrubbery -
                  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

  /// Bram Moolenaar -- Bram@... -- 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    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Tony Mechelynck wrote:

Note that you used windows-1252 encoding for this message, some
characters don't appear right for me.

>  From doc/spell.txt, lines 298 sqq:
>
> > Exceptions:
> > - Vim uses "latin1" when 'encoding' is "iso-8859-15".  The euro sign doesn't
> >   matter for spelling.
>
> Indeed, the euro sign doesn't, but some other characters do. For
> instance, the French œ Œ (oe OE) digraph, or the capital Y with
> diaeresis, and maybe others, exist in Latin9 (iso-8859-15) but not in
> Latin1 (iso-8859-1). The œ digraph exists in such common French
> words as cœur (heart), sœur (sister), œil (eye), œuf
> (egg), bœuf (ox, beef), vœu (wish), etc.; even œil-de-bœuf
> (Engl. oeil-de-boeuf) with two of them; these digraphs are also used
> for transliteration of some Latin and Greek words, e.g. in Œdipe
> (Oedipus), œsophage (oesophagus), etc.
>
> These characters have the following values:
> Π(Latin9 0xBC) U+0152 LATIN CAPITAL LETTER OE
> œ (Latin9 0xBD) U+0153 LATIN SMALL LETTER OE
> Ÿ (Latin9 0xBE) U+0178 LATIN CAPITAL LETTER Y WITH DIAERESIS
>
> When a Latin9 file containing them is read by mistake in Latin1, here is
> what we get:
> U+00BC ¼ VULGAR FRACTION ONE-QUARTER
> U+00BD ½ VULGAR FRACTION ONE-HALF
> U+00BE ¾ VULGAR FRACTION THREE-QUARTERS
>
> So, what should be done? Use one-half to represent œ (etc.) in the
> Latin1 spelling dictionary for any language using it?

It's close to impossible to recognize the difference between latin1 and
latin9.  For the languages where it matters the latin9 characters can be
used in the latin1 spell files.  The only problem is that when the text
actually is latin1 some obscure spelling mistakes won't be highlighted.
I don't think this is worth making two separate spell files for, they
are quite big.

--
Q: How do you tell the difference between a female cat and a male cat?
A: You ask it a question and if HE answers, it's a male but, if SHE
    answers, it's a female.

  /// Bram Moolenaar -- Bram@... -- 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    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Markus Heidelberg wrote:

> In non-gui vim the color of the visual selection is reverse instead of grey,
> if t_Co > 8. It should only be reversed if t_Co <= 8.
>
> ":hi Visual" still contains cterm=reverse after setting t_Co to >8, so I think
> this is used instead of ctermbg=7 (grey). After ":hi clear" it's cleaned up
> and the color is shown as intended.
>
> to reproduce it:
> vim -u NONE
>
> :set t_Co?
>   t_Co=8 (for me)
> :hi Visual
>   Visual         xxx term=reverse cterm=reverse guibg=LightGrey
> write some text and test visual mode, it's reversed (correct)
>
> :set t_Co=16
> :hi Visual
>   Visual         xxx term=reverse cterm=reverse ctermbg=7 guibg=LightGrey
> test visual mode, it's still reversed (wrong)
>
> :hi clear
> :hi Visual
>   Visual         xxx term=reverse ctermbg=7 guibg=LightGrey
> test visual mode, now it's grey (correct)
>
> :set t_Co=8
> :hi Visual
>   Visual         xxx term=reverse cterm=reverse ctermbg=7 guibg=LightGrey
> test visual mode, it's already (in contrast to t_Co=16) reversed (correct)
>
> :hi clear
> :hi Visual
>   Visual         xxx term=reverse cterm=reverse guibg=LightGrey
> test visual mode, it's still reversed (correct)
>
>
> I have two solutions and think the first one is acceptable.

I think the first solution should work.  Clearing all the settings is
drastic, it might have unexpected side effects.

I suppose that when switching from 16 to 8 colors then ctermbg value
should be cleared.


*** ../vim-7.2b.026/src/syntax.c Wed Jun 25 00:17:00 2008
--- src/syntax.c Mon Aug  4 23:07:11 2008
***************
*** 6459,6471 ****
       /* Reverse looks ugly, but grey may not work for 8 colors.  Thus let it
        * depend on the number of colors available.
        * With 8 colors brown is equal to yellow, need to use black for Search fg
!      * to avoid Statement highlighted text disappears. */
       if (t_colors > 8)
!  do_highlight((char_u *)(*p_bg == 'l' ? "Visual ctermbg=LightGrey"
! 				   : "Visual ctermbg=DarkGrey"), FALSE, TRUE);
       else
       {
!  do_highlight((char_u *)"Visual cterm=reverse", FALSE, TRUE);
  	 if (*p_bg == 'l')
  	     do_highlight((char_u *)"Search ctermfg=black", FALSE, TRUE);
       }
--- 6459,6474 ----
       /* Reverse looks ugly, but grey may not work for 8 colors.  Thus let it
        * depend on the number of colors available.
        * With 8 colors brown is equal to yellow, need to use black for Search fg
!      * to avoid Statement highlighted text disappears.
!      * Clear the attributes, needed when changing the t_Co value. */
       if (t_colors > 8)
!  do_highlight((char_u *)(*p_bg == 'l'
! 		    ? "Visual cterm=NONE ctermbg=LightGrey"
! 		    : "Visual cterm=NONE ctermbg=DarkGrey"), FALSE, TRUE);
       else
       {
!  do_highlight((char_u *)"Visual cterm=reverse ctermbg=NONE",
! 								 FALSE, TRUE);
  	 if (*p_bg == 'l')
  	     do_highlight((char_u *)"Search ctermfg=black", FALSE, TRUE);
       }


--
TIM: To the north there lies a cave,  the cave of Caerbannog, wherein, carved
      in mystic runes, upon the very living rock, the last words of Olfin
      Bedwere of Rheged make plain the last resting place of the most Holy
      Grail.
                  "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

  /// Bram Moolenaar -- Bram@... -- 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    ///

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Bram Moolenaar, 04.08.2008:
>
> Markus Heidelberg wrote:
>
> > In non-gui vim the color of the visual selection is reverse instead of grey,
> > if t_Co > 8. It should only be reversed if t_Co <= 8.
> >
> >
> > I have two solutions and think the first one is acceptable.
>
> I think the first solution should work.  Clearing all the settings is
> drastic, it might have unexpected side effects.

I included the second patch, only because it was my first solution (similar to
:hi clear).

> I suppose that when switching from 16 to 8 colors then ctermbg value
> should be cleared.

Yes, I did so in my patch.

Markus


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 04/08/08 22:08, Bram Moolenaar wrote:
[...]
> Yeah, the problem is that the number of tags is restricted before
> sorting them on relevance.  Try the patch below.
>
>
> *** ../vim-7.2b.026/src/ex_cmds.c Thu Jul 24 21:30:10 2008
> --- src/ex_cmds.c Mon Aug  4 21:15:00 2008
[...]

Single-letter help tags are found again; and my computer is faster than
me by a big enough margin that I don't notice any delay on ":h A" etc.
;-) On ":h A<Ctrl-D>" I wait about one second (which is acceptable) then
I get one full screen plus one line of matches (with lines=48
columns=142). As expected, the "full match" is now first.

With the "tiny" console-only version Ctrl-D seems to go slightly faster
but of course there are fewer matches per screen (lines=43 columns=80).

Here are the "version" listings and the executable sizes (before and
after strip) for both builds:

========================================================================
VIM - Vi IMproved 7.2b BETA (2008 Jul 13, compiled Aug  4 2008 23:59:06)
Included patches: 1-26
Modified by Bill McCarthy (float), Bram Moolenaar (helptags)
Compiled by antoine.mechelynck@...
Huge version with GTK2-GNOME GUI.  Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent +clientserver +clipboard +cmdline_compl +cmdline_hist
+cmdline_info +comments +cryptv +cscope +cursorshape +dialog_con_gui
+diff +digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search
+farsi +file_in_path +find_in_path +float +folding -footer +fork()
+gettext -hangul_input +iconv +insert_expand +jumplist +keymap +langmap
+libcall +linebreak +lispindent +listcmds +localmap +menu +mksession
+modify_fname +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm
+mouse_netterm -mouse_sysmouse +mouse_xterm +multi_byte +multi_lang
-mzscheme +netbeans_intg -osfiletype +path_extra +perl +postscript
+printer +profile +python +quickfix +reltime +rightleft +ruby
+scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax
+tag_binary -tag_old_static -tag_any_white +tcl +terminfo +termresponse
+textobjects +title +toolbar +user_commands +vertsplit +virtualedit
+visual +visualextra +viminfo +vreplace +wildignore +wildmenu +windows
+writebackup +X11 -xfontset +xim +xsmp_interact +xterm_clipboard
+xterm_save
     system vimrc file: "$VIM/vimrc"
       user vimrc file: "$HOME/.vimrc"
        user exrc file: "$HOME/.exrc"
    system gvimrc file: "$VIM/gvimrc"
      user gvimrc file: "$HOME/.gvimrc"
      system menu file: "$VIMRUNTIME/menu.vim"
    fall-back for $VIM: "/usr/local/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/freetype2
-I/usr/include/libpng12   -DORBIT2=1 -pthread
-I/usr/include/libgnomeui-2.0 -I/usr/include/libart-2.0
-I/usr/include/gconf/2 -I/usr/include/gnome-keyring-1
-I/usr/include/libgnome-2.0 -I/usr/include/libbonoboui-2.0
-I/usr/include/libgnomecanvas-2.0 -I/usr/include/gtk-2.0
-I/usr/include/gnome-vfs-2.0 -I/usr/lib/gnome-vfs-2.0/include
-I/usr/include/orbit-2.0 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/include/libbonobo-2.0
-I/usr/include/bonobo-activation-2.0 -I/usr/include/libxml2
-I/usr/include/pango-1.0 -I/usr/include/gail-1.0
-I/usr/include/freetype2 -I/usr/include/atk-1.0
-I/usr/lib/gtk-2.0/include -I/usr/include/cairo -I/usr/include/libpng12
      -O2 -fno-strength-reduce -Wall    -D_REENTRANT -D_GNU_SOURCE
-DPERL_USE_SAFE_PUTENV -DDEBUGGING  -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64
-I/usr/lib/perl5/5.10.0/i586-linux-thread-multi/CORE
-I/usr/include/python2.5 -pthread -I/usr/include
-D_LARGEFILE64_SOURCE=1  -I/usr/lib/ruby/1.8/i586-linux
Linking: gcc   -L.  -rdynamic -Wl,-export-dynamic  -Wl,-E
-Wl,-rpath,/usr/lib/perl5/5.10.0/i586-linux-thread-multi/CORE
-L/usr/local/lib -o vim   -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0
-lgdk_pixbuf-2.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0
-lgmodule-2.0 -lglib-2.0     -lgnomeui-2 -lbonoboui-2 -lgnomevfs-2
-lgnomecanvas-2 -lgnome-2 -lpopt -lbonobo-2 -lbonobo-activation
-lORBit-2 -lart_lgpl_2 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0
-lgdk_pixbuf-2.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgconf-2
-lgthread-2.0 -lrt -lgmodule-2.0 -lgobject-2.0 -lglib-2.0   -lXt
-lncurses -lacl -lgpm   -Wl,-E
-Wl,-rpath,/usr/lib/perl5/5.10.0/i586-linux-thread-multi/CORE
-L/usr/lib/perl5/5.10.0/i586-linux-thread-multi/CORE -lperl -lutil -lc
-L/usr/lib/python2.5/config -lpython2.5 -lutil -Xlinker -export-dynamic
-L/usr/lib -ltcl8.5 -lieee -Wl,-R -Wl,/usr/lib -L/usr/lib -lruby -lm
========================================================================
VIM - Vi IMproved 7.2b BETA (2008 Jul 13, compiled Aug  4 2008 23:52:51)
Included patches: 1-26
Modified by Bram Moolenaar (helptags)
Compiled by antoine.mechelynck@...
Tiny version without GUI.  Features included (+) or not (-):
-arabic -autocmd -balloon_eval -browse +builtin_terms -byte_offset -cindent
-clientserver -clipboard -cmdline_compl -cmdline_hist -cmdline_info
-comments
-cryptv -cscope -cursorshape -dialog -diff -digraphs -dnd -ebcdic
-emacs_tags
-eval -ex_extra -extra_search -farsi -file_in_path -find_in_path -float
-folding -footer +fork() -gettext -hangul_input -iconv -insert_expand
-jumplist
   -keymap -langmap -libcall -linebreak -lispindent -listcmds -localmap -menu
-mksession -modify_fname -mouse -mouse_dec -mouse_gpm -mouse_jsbterm
-mouse_netterm -mouse_sysmouse -mouse_xterm -multi_byte -multi_lang
-mzscheme
-netbeans_intg -osfiletype -path_extra -perl -printer -profile -python
-quickfix -reltime -rightleft -ruby -scrollbind -signs -smartindent -sniff
-statusline -sun_workshop -syntax -tag_binary -tag_old_static -tag_any_white
-tcl +terminfo -termresponse -textobjects -title -toolbar -user_commands
-vertsplit -virtualedit -visual -viminfo -vreplace +wildignore -wildmenu
-windows +writebackup -X11 -xfontset -xim -xsmp -xterm_clipboard -xterm_save
     system vimrc file: "$VIM/vimrc"
       user vimrc file: "$HOME/.vimrc"
        user exrc file: "$HOME/.exrc"
    fall-back for $VIM: "/usr/local/share/vim"
Compilation:
gcc -c -I. -Iproto -DHAVE_CONFIG_H     -O2 -fno-strength-reduce -Wall
Linking: gcc   -L/usr/local/lib -o vi       -lm -lncurses
========================================================================
linux:~/.build/vim/vim72b # ls -l src/vim src/tiny/vi `which vim` `which vi`
-rwxr-xr-x 1 root root  504960 Aug  4 23:58 /usr/local/bin/vi*
-rwxr-xr-x 1 root root 3114216 Aug  5 00:11 /usr/local/bin/vim*
-rwxr-xr-x 1 root root  567673 Aug  4 23:53 src/tiny/vi*
-rwxr-xr-x 1 root root 3471156 Aug  5 00:02 src/vim*


Best regards,
Tony.
--
All wars are civil wars, because all men are brothers ... Each one owes
infinitely more to the human race than to the particular country in
which he was born.
		 -- Francois Fenelon

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

On 04/08/08 23:37, Bram Moolenaar wrote:
> Tony Mechelynck wrote:
>
> Note that you used windows-1252 encoding for this message, some
> characters don't appear right for me.

Next time I'll pay more attention. The strange thing is that although
your message's headers say ISO-8859-1 8bit, the "non-Latin-1" characters
in my quoted post display correctly in SeaMonkey (version 2.0a1pre for
Linux). Saving the message source as an .eml file then examining it with
Vim shows that they were indeed encoded in Windows-1252. (Maybe
SeaMonkey will silently accept "invalid" Latin1 characters and assume
they came from a b0rken Windows sender such as Word, and that it sent
Windows-1252 text under a Latin1 label?)

FYI (and that of any lurkers), here they are again in UTF-8:

>> Indeed, the euro sign doesn't, but some other characters do. For
>> instance, the French Å“ Å’ (oe OE) digraph, or the capital Y with
>> diaeresis, and maybe others, exist in Latin9 (iso-8859-15) but not in
>> Latin1 (iso-8859-1). The Å“ digraph exists in such common French
>> words as cœur (heart), sœur (sister), œil (eye), œuf
>> (egg), bœuf (ox, beef), vœu (wish), etc.; even œil-de-bœuf
>> (Engl. oeil-de-boeuf) with two of them; these digraphs are also used
>> for transliteration of some Latin and Greek words, e.g. in Å’dipe
>> (Oedipus), Å“sophage (oesophagus), etc.
>>
>> These characters have the following values:
>> Å’ (Latin9 0xBC) U+0152 LATIN CAPITAL LETTER OE
>> Å“ (Latin9 0xBD) U+0153 LATIN SMALL LETTER OE
>> Ÿ (Latin9 0xBE) U+0178 LATIN CAPITAL LETTER Y WITH DIAERESIS
>>
>> When a Latin9 file containing them is read by mistake in Latin1, here is
>> what we get:
>> U+00BC ¼ VULGAR FRACTION ONE-QUARTER
>> U+00BD ½ VULGAR FRACTION ONE-HALF
>> U+00BE ¾ VULGAR FRACTION THREE-QUARTERS

Best regards,
Tony.
--
There was a plane crash over mid-ocean, and only three survivors were
left in the life-raft: the Pope, the President, and Mayor Daley.
Unfortunately, it was a one-man life-raft, and quickly sinking, so they
started debating who should be allowed to stay.

The Pope pointed out that he was the spiritual leader of millions all
over the world, the President explained that if he died then America
would be stuck with the Vice-President, and so forth.  Then Mayor Daley
said, "Look!  We're not solving anything like this!  The only fair
thing to do is to vote on it."  So they did, and Mayor Daley won by 97
votes.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Does anyone know if there is a good reason that the distributed
perl.vim syntax file only supports //, ##, {}, and [] style regex
delimiters? A huge host of delimiters is supported by perl itself,
just like in Vim, such as:

++
--
()
))
@@
""
''

And more.

I can certainly understand if it fails to catch a few of the less-used
ones, but why check explicitly for only 4 patterns?
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Ian Kelling wrote:
> I wrote the patch that introduced the bug and I will be happy to fix
> it. It was written to solve the problem that doing :h <ctrl-d> would
> take a long time to show every help tag. It could be changed so that
> it only limits it in that specific case. Do you have any other ideas?
> If not, I will do that one.
>
> - Ian Kelling

I question the usefulness of this behaviour, actually. What's the point
of having a list of completions if there's only a 30% chance or
something that it will contain the entry you actually want, because it's
a random selection of the possible completions? If anything, this will
lead you to deduce that Vim doesn't have help on a particular topic
because CTRL-D presents you with a list that doesn't include that topic.
Why would you do :he CTRL-D anyway? The only reason I can think of is if
you have no idea what tag you are looking for, and so you want to look
through the entire list in the hope that you will recognise it. Deleting
items from the list makes this impossible.

If you think people absent-mindedly type CTRL-D (or whatever completion
key) so often that speed really is an issue for this, I'd sooner have
completion completely disabled for short words, or common words (that
produce a list above a certain size) rather than an incomplete and
therefore misleading list. But I'd sooner just have the old behaviour:
some operations do take a long time; we might not like to wait, but
breaking the feature isn't a good fix, and sometimes the wait is worth
it.

Ben.



--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---