Re: Bug? :noh in a function doesn't work
AOYAMA Shotaro wrote: > hi, > > Using :noh in a user-defined function has no effect. > Is this a bug or intended? > > To reproduce: > > $ vim -u NONE -N > > function! Noh() > noh > endfunction > set hlsearch > > " search /foo > > :call Noh() > > " Now, the hilight doesn't turn off. > > > Regards, > Hmm... My guess is you've just found a helpfile bug rather than a Vim-C-code bug; but I'd like to read Bram's word on this. Best regards, Tony. -- hundred-and-one symptoms of being an internet addict: 175. You send yourself e-mail before you go to bed to remind you what to do when you wake up. --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Bug? :noh in a function doesn't work
hi, Using :noh in a user-defined function has no effect. Is this a bug or intended? To reproduce: $ vim -u NONE -N function! Noh() noh endfunction set hlsearch " search /foo :call Noh() " Now, the hilight doesn't turn off. Regards, -- AOYAMA Shotaro <[EMAIL PROTECTED]> --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Weird font issue
Jeff Lanzarotta wrote: > Hello, > > My version of Vim is the latest and greatest version from version > control which includes patches 1-175. This version was compiled using > Borland C++ 5.5 under Windows XP. > > The issue I am having is with the characters 'a' and 'e'... > > When I am in insert mode and I do: > 'a' then backspace, 'a' then backspace, 'a' then backspace, repeatively, > the character 'a' is replaced with 'å'. > > When I am in insert mode and I do: > 'e' then backspace then 'a', then 'e' then backspace then 'a', > repeatively, the character 'e' is replaced with 'æ'. > > This is weird. Has anyone else seen this? > > Thanks, > > Jeff > > > -Jef :set nodigraph see :help digraphs-use I suspect that you have a ":set digraph" line in your vimrc, which makes active (in addition to the always-available ) as an additional method of producing foreign characters by means of digraphs. If you have that line, remove it to disable the strange behaviour you've been seeing. You'll still be able to use the other (Ctrl-K prefix) method, which won't interfere with your use of the backspace key. (Note: aa is the digraph for the letter å, and ae for æ.) Best regards, Tony. -- "But don't you worry, its for a cause -- feeding global corporations paws." --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch to allow ctermfg or bg values as #rrggbb
On Dec 21, 2007 5:18 AM, Nico Weber <[EMAIL PROTECTED]> wrote: > > > 2) There is no algorithm available to programmatically judge the > > perceived differences between colors that suits our purposes. We do > > well with CIE L*a*b*, but not better than the stepping algorithm I > > proposed first, and in some places drastically worse. Unfortunately, > > CIE L*a*b* is only good at measuring the perceived differences between > > relatively similar colors, where the steps on our color cube are far > > enough apart that the colors are often not "similar" enough. > > Do you know about the Munsell color system ( > http://en.wikipedia.org/wiki/Munsell_color_system > )? It's a (the?) color system based on perceived colors, so perhaps > is coul be used for your purpose. No, I hadn't tried using the Munsell color system, but I had tried CIEXYZ, CIELAB, CIELUV, and gave a brief glance at CIECAM. All 4 of those color systems are designed based on scientific measurements of perceived colors. If there were more reasons to try it, I might be more motivated, but the only disadvantage to my stepping algorithm is that it can't work if the color palette doesn't follow the same general format as xterm's... and every color palette I've found so far does. ~Matt --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Weird font issue
Thanks.
I was messing around with my vimrc file and inadvertently added 'set digraph'...
I have now turned that feature off...
James Vega <[EMAIL PROTECTED]> wrote: On Fri, Dec 21, 2007 at 06:12:24AM -0800,
Jeff Lanzarotta wrote:
> When I am in insert mode and I do:
> 'a' then backspace, 'a' then backspace, 'a' then backspace, repeatively, the
> character 'a' is replaced with 'å'.
This is happening because you have the 'digraph' option enabled. When
this option is enabled, you can input unicode characters by typing
{char1} {char2} instead of using {char1}{char2}. This is
described at ":help 'digraphs'".
James
--
GPG Key: 1024D/61326D40 2003-09-02 James Vega
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
Re: Weird font issue
On Fri, Dec 21, 2007 at 06:12:24AM -0800, Jeff Lanzarotta wrote:
> When I am in insert mode and I do:
> 'a' then backspace, 'a' then backspace, 'a' then backspace, repeatively, the
> character 'a' is replaced with 'å'.
This is happening because you have the 'digraph' option enabled. When
this option is enabled, you can input unicode characters by typing
{char1} {char2} instead of using {char1}{char2}. This is
described at ":help 'digraphs'".
James
--
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
Weird font issue
Hello, My version of Vim is the latest and greatest version from version control which includes patches 1-175. This version was compiled using Borland C++ 5.5 under Windows XP. The issue I am having is with the characters 'a' and 'e'... When I am in insert mode and I do: 'a' then backspace, 'a' then backspace, 'a' then backspace, repeatively, the character 'a' is replaced with 'å'. When I am in insert mode and I do: 'e' then backspace then 'a', then 'e' then backspace then 'a', repeatively, the character 'e' is replaced with 'æ'. This is weird. Has anyone else seen this? Thanks, Jeff -Jeff --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: I care about vim rfc1345 switch
Philippe De Muyter wrote: > On Fri, Dec 21, 2007 at 03:02:15AM +0100, Tony Mechelynck wrote: >> Bram Moolenaar wrote: >>> Philippe de Muyter wrote: >>> On Sun, Oct 22, 2000 at 10:20:34PM +0200, Bram Moolenaar wrote: > [...] > The default digraphs now correspond to RFC1345. Most are different from > what was used in Vim 5.x. Do we care about this incompatibility? >>> Seems like only yesterday :-). > > I do not write french texts everyday :) > I only noticed that now, switching my linux distro to suse 10.3, and yes, I really care. I am a french-speaking programmer, so I use a qwerty-us keyboard beacause it is much easier for programming, but I need sometimes to produce french texts. Previously, I could use the CTRL-K combinations with ` (backquote or grave) to introduce grave accents, ^ (circumflex) for circumflex accents and " for diaeresis, juste like on a typing machine. RFC1345 recommends : ! instead of ` for grave accent > instead of ^ for circumflex accent : instead of " for diaeresis Frankly I do not understand why RFC1345 has choosen that. I know I can add digraphs in .exrc, but it seems to me more logical to add the french-writing typist combinations directly in the default digraphs of vim. Of course, I do not ask for removal of the !, > and : sequences, only their duplications with their `, ^ and " counterparts. >>> It seems that we can add these digraphs without breaking the existing >>> ones. Is there anything against adding something like a" for ä, which >>> you currently enter with a: ? >>> >> Currently, o" and u" are used for the doubly-acute-accented vowels of the >> Hungarian language (meaning long ö and long ü, i.e. vowels with both umlaut >> [for pitch change] and acute accent [for length]). >> >> Decimal codes 336, 337, 368, 369, or hexadecimal U+0150, U+0151, U+0170 and >> U+0171. > > I agree that " is not the best fit for diaeresis, but ` for grave and ^ > for circumflex are. So please re-introduct that in the defaults, just > like it was in older vim. > > A complementary suggestion : when one keys in an undefined CTRL-K > combination, let's vim show/point to the digraphs table. I, (and a colleague > independently) spent several hours to discover the combinations needed > to introduce e`. We are experienced vi and vim users, and we used CTRL-K > e' and CTRL-K e` before, so when e' works but e` does not work, the first > reaction is not to read vim documentation :), and moreover, there's of course > nothing in it about "grave" or about "accent". > > Best regards > > Philippe De Muyter > Why not read Vim documentation? If you are "experienced" Vim users, you should know that everything is in the help. :help digraphs-default :helpgrep grave :helpgrep accent Best regards, Tony. -- The difference between this school and a cactus plant is that the cactus has the pricks on the outside. --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: Patch to allow ctermfg or bg values as #rrggbb
> 2) There is no algorithm available to programmatically judge the > perceived differences between colors that suits our purposes. We do > well with CIE L*a*b*, but not better than the stepping algorithm I > proposed first, and in some places drastically worse. Unfortunately, > CIE L*a*b* is only good at measuring the perceived differences between > relatively similar colors, where the steps on our color cube are far > enough apart that the colors are often not "similar" enough. Do you know about the Munsell color system ( http://en.wikipedia.org/wiki/Munsell_color_system )? It's a (the?) color system based on perceived colors, so perhaps is coul be used for your purpose. Nico --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: I care about vim rfc1345 switch
On Fri, Dec 21, 2007 at 03:02:15AM +0100, Tony Mechelynck wrote: > Bram Moolenaar wrote: > > > >Philippe de Muyter wrote: > > > >>On Sun, Oct 22, 2000 at 10:20:34PM +0200, Bram Moolenaar wrote: > >>>[...] > >>>The default digraphs now correspond to RFC1345. Most are different from > >>>what was used in Vim 5.x. Do we care about this incompatibility? > > > >Seems like only yesterday :-). I do not write french texts everyday :) > > > >>I only noticed that now, switching my linux distro to suse 10.3, and yes, > >>I > >>really care. I am a french-speaking programmer, so I use a qwerty-us > >>keyboard > >>beacause it is much easier for programming, but I need sometimes to > >>produce french texts. > >> > >>Previously, I could use the CTRL-K combinations with ` (backquote or > >>grave) > >>to introduce grave accents, ^ (circumflex) for circumflex accents and " > >>for > >>diaeresis, juste like on a typing machine. > >> > >>RFC1345 recommends : > >> > >>! instead of ` for grave accent > >>> instead of ^ for circumflex accent > >>: instead of " for diaeresis > >> > >>Frankly I do not understand why RFC1345 has choosen that. > >> > >>I know I can add digraphs in .exrc, but it seems to me more logical to add > >>the french-writing typist combinations directly in the default digraphs > >>of vim. > >> > >>Of course, I do not ask for removal of the !, > and : sequences, only > >>their > >>duplications with their `, ^ and " counterparts. > > > >It seems that we can add these digraphs without breaking the existing > >ones. Is there anything against adding something like a" for ä, which > >you currently enter with a: ? > > > > Currently, o" and u" are used for the doubly-acute-accented vowels of the > Hungarian language (meaning long ö and long ü, i.e. vowels with both umlaut > [for pitch change] and acute accent [for length]). > > Decimal codes 336, 337, 368, 369, or hexadecimal U+0150, U+0151, U+0170 and > U+0171. I agree that " is not the best fit for diaeresis, but ` for grave and ^ for circumflex are. So please re-introduct that in the defaults, just like it was in older vim. A complementary suggestion : when one keys in an undefined CTRL-K combination, let's vim show/point to the digraphs table. I, (and a colleague independently) spent several hours to discover the combinations needed to introduce e`. We are experienced vi and vim users, and we used CTRL-K e' and CTRL-K e` before, so when e' works but e` does not work, the first reaction is not to read vim documentation :), and moreover, there's of course nothing in it about "grave" or about "accent". Best regards Philippe De Muyter --~--~-~--~~~---~--~~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~--~~~~--~~--~--~---
Re: I care about vim rfc1345 switch
On Thu, Dec 20, 2007 at 05:50:36PM +0100, Tony Mechelynck wrote:
> Philippe De Muyter wrote:
> >On Sun, Oct 22, 2000 at 10:20:34PM +0200, Bram Moolenaar wrote:
> >>[...]
> >>The default digraphs now correspond to RFC1345. Most are different from
> >>what was used in Vim 5.x. Do we care about this incompatibility?
> >>
> >
> >I only noticed that now, switching my linux distro to suse 10.3, and yes, I
> >really care. I am a french-speaking programmer, so I use a qwerty-us
> >keyboard
> >beacause it is much easier for programming, but I need sometimes to
> >produce french texts.
> >
> >Previously, I could use the CTRL-K combinations with ` (backquote or grave)
> >to introduce grave accents, ^ (circumflex) for circumflex accents and " for
> >diaeresis, juste like on a typing machine.
> >
> >RFC1345 recommends :
> >
> > ! instead of ` for grave accent
> > > instead of ^ for circumflex accent
> > : instead of " for diaeresis
> >
> >Frankly I do not understand why RFC1345 has choosen that.
>
> I guess: because more national keyboards have them, and/or they are more
> consistent with the rest, like ( for breve, < for caron (as on the initial
> C in the Czech version of the adjective "Czech"), etc.: in many cases, the
> 2nd part of the digraph moves 90° up to get above the first part, rotating
> all the while. One exception is - (macron) which doesn't rotate, but in
> this case it didn't strike me as weird when I first needed it.
>
> I don't understand why you believe that "a us-qwerty keyboard is much
> easier for programming", but, well, there's no reckoning with individual
> tastes.
The characters [ ] { } ~ | and \ are really more accessible on a qwerty-us
than on an azerty-be keyboard.
> (I have a Belgian AZERTY keyboard and I like the way it satisfies
> my needs, both for programming and for text writing in almost every
> Latin-alphabet language except Hungarian.)
Of course, you don't miss the "natural" combinations for e`, a`, u`, o^
and e^ then.
Best regards
Philippe De Muyter
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
