Re: Some abbreviations work only as imaps

On Thu, 25 Sep 2014 07:44:15 +0200
Tony Mechelynck <antoine.mechelynck@gmail.com> wrote:

> On 24/09/14 08:49, Gevisz wrote:
> > On Wed, 24 Sep 2014 07:55:33 +0200
> > Christian Brabandt <cblists@256bit.org> wrote:
> >
> >> Am 2014-09-24 07:13, schrieb Gevisz:
> >>> I have noticed that some abbreviations I define never
> >>> expand but they do if I redefine them via imaps.
> >>>
> >>> Does anybody can guess a possible reason for that?
> >>
> >> Have you checked, that the constraints given below (:h
> >> Abbreviations, look for the paragraph: "There are three types of
> >> abbreviations:") do apply? Abbreviations actually might become
> >> invalid, if you mess with the 'iskeyword' setting later on (after
> >> they have been defined).
> >
> > That explanation is unclear for me because I cannot understand which
> > symbols iskeyword in my settings. The command
> > :set iskeywords
> > returns
> > iskeyword=!-~,^*,^|,^",192-255
> > in my case.
> >
> > But I guess that my abbreviations should not mix with anything else
> > as they consist only from cyrillic letters.
> >
> > I used to set
> > langmap=ФИСВУАПРШОЛДЬТЩЗЙКЫЕГМЦЧНЯ;ABCDEFGHIJKLMNOPQRSTUVWXYZ,фисвуапршолдьтщзйкыегмцчня;abcdefghijklmnopqrstuvwxyz
> > but nothing changed (to the better :) when I commented it out.
> >
>
> 'iskeyword' resends to 'isfame' where the symbols used for both are
> defined; but if the {lhs} of your abbreviations is always made up of
> only Cyrillic letters, the relevant sentence is "Multi-byte
> characters 256 and above are always included, only the characters up
> to 255 are specified with this option." which would lead me to
> conclude that Cyrillic letters are always regarded as "word"
> characters. Yours would then fall under "full-id" abbreviations. A
> few examples (of what doesn't work, and, if you have any, of what
> does) would be useful though.

As we have already established, any abbreviation containing one or more
cyrillic letters "р" does not expands as expected for the reason that
is so far beyond my understanding.

Nevertheless, this problem has hopefully already been solved by the
patch from Christian Brabandt. ("Hopefully" because I have not applied
it. :)

> Best regards,
> Tony.

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.