Hi
Attached patch fixes a few typos in Vim-7.4.355 doc.
Regards
Dominique
--
--
You received this message from the "vim_dev" 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 messag
> I agree 100% that it's broken. They still do it.
>
> For what it's worth, I had to look at the sources at many of said
> compilers to get syntastic to understand their output, and using virtual
> columns isn't *that* far fetched. Most of the time they just expand
> tabs while parsing a
Given recent discussion around matchaddpos() and the fact that converting
virtual column to byte offset has a larger variety of use cases (I personally
needed this to get -selected block without altering marks, registers,
cursor position, etc) I propose the new function colnr():
colnr :: (s
On 4 July 2014, Павлов Николай Александрович
wrote:
> On July 1, 2014 9:54:00 PM GMT+03:00, LCD 47 wrote:
> >On 1 July 2014, Bram Moolenaar wrote:
> >> The main thing was to highlight one or a few characters at a fixed
> >> position in the text. Such as a parenthesis. Text is usually
> >> loca
> I was thinking just about the focus related events.
More precisely, about the focus related events >triggered by the
particular implementation of the autocomplete mechanism<, not by the
user or other plugins or parts of vim where they could arguably be of
interest.
--
--
You received this mes
>> You can selectively supress autocommands at vimscript level with noautocmd
>> and eventignore. Can you do that at the C level? Do you think it's
>> undesirable to do so? I'm not able to think of a listener interested in this
>> particular buffer switch as it's more of a subproduct of a partic
On Friday, July 4, 2014 6:41:53 AM UTC-5, Carlos Pita wrote:
> You can selectively supress autocommands at vimscript level with noautocmd
> and eventignore. Can you do that at the C level? Do you think it's
> undesirable to do so? I'm not able to think of a listener interested in this
> particul
On 4 July 2014, Alexey Radkov wrote:
> 2014-07-04 18:22 GMT+04:00 Павлов Николай Александрович :
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > Are you sure you need exactly screen cells? There are the following
> > possible ways to identify position inside a string:
> >
> > 1.
On 4 July 2014, Павлов Николай Александрович wrote:
> Are you sure you need exactly screen cells? There are the following
> possible ways to identify position inside a string:
>
> 1. Byte offset.
> 2. Unicode codepoints offset.
> 3. Composed characters offset (one "composed character" is "one
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On July 1, 2014 9:54:00 PM GMT+03:00, LCD 47 wrote:
>On 1 July 2014, Bram Moolenaar wrote:
>> lcd wrote:
>[...]
>> > First, the interface:
>> >
>> >matchaddpos({group}, {pos}[, {priority}[, {id}]])
>> >
>> > Here, {pos} is a list of lists.
Daniel Hahler wrote:
> I am using Vim's source via a Git mirror
> (https://github.com/vim-jp/vim) and it would be useful to use a
> symlink ".gitignore -> .hgignore", instead of a modified copy.
>
> While git picks up the patterns from ".hgignore" in general, it
> appears to be sensible to trail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On July 4, 2014 6:55:28 PM GMT+03:00, Alexey Radkov
wrote:
>2014-07-04 18:22 GMT+04:00 Павлов Николай Александрович
>:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> Are you sure you need exactly screen cells? There are the following
2014-07-04 18:22 GMT+04:00 Павлов Николай Александрович :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Are you sure you need exactly screen cells? There are the following
> possible ways to identify position inside a string:
>
> 1. Byte offset.
> 2. Unicode codepoints offset.
> 3. Compo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Are you sure you need exactly screen cells? There are the following possible
ways to identify position inside a string:
1. Byte offset.
2. Unicode codepoints offset.
3. Composed characters offset (one "composed character" is "one Unicode
codepoint
Ok, probably so. If script is able to calculate the end in bytes itself,
then the current solution is good. But if it knows how many screen cells it
must highlight it is getting almost not feasible to calculate the end col.
if case 1 is more common than 2 then current solution is better :)
2014-0
When looking at the help of ':h briopt', I've noticed that the "tab" setting
for "listchars" influences the indent of hanging paragraphs, if "linebreak" is
enabled (but no lines are wrapped) and listchars are not displayed.
TEST CASE:
1. vim -u NONE
2. :h 'briopt'
3. :set linebreak listchars=tab
You can selectively supress autocommands at vimscript level with noautocmd
and eventignore. Can you do that at the C level? Do you think it's
undesirable to do so? I'm not able to think of a listener interested in
this particular buffer switch as it's more of a subproduct of a particular
implementa
Please find attached a patch with two small fixes to the djangohtml related
runtime files:
1. improve filetype detection of "htmldjango", by also looking for "load"
block tags
2. allow optional block tag content with the opening "{% comment %}" tag.
Branch on Github: https://github.com/bluey
I am using Vim's source via a Git mirror (https://github.com/vim-jp/vim) and it
would be useful to use a symlink ".gitignore -> .hgignore", instead of a
modified copy.
While git picks up the patterns from ".hgignore" in general, it appears to be
sensible to trailing whitespace in the patterns,
Hi Bram,
2014/7/4(Fri) 19:05:30 UTC+9 Bram Moolenaar:
> Hirohito Higashi wrote:
>
>
>
> > Hi Carlos,
>
> >
>
> > 2014/7/3(Thu) 5:04:10 UTC+9 Carlos Pita:
>
> > > When the omnifunc provides extra info to be shown in the preview window
> > > (in case preview is included in completeopt) there
Am Samstag, 15. Februar 2014 22:48:15 UTC+1 schrieb Christian Brabandt:
> On Fr, 14 Feb 2014, Daniel Hahler wrote:
> > > Another update, that fixes failure of test10.
> > This patch changes the default title (?) from ":setloclist()" to
> > "setloclist()".
> The reason for leaving out the colon wa
Alexey Radkov wrote:
> Now it accepts len in screen cells.
Hmm, that's confusing. Suppose a script isolates a word that it wants
to highlight. Then it's easy to locate the start of the word and the
length with various methods, e.g. using getline(), match() and
matchend(). Then you have the po
Hirohito Higashi wrote:
> Hi Carlos,
>
> 2014/7/3(Thu) 5:04:10 UTC+9 Carlos Pita:
> > When the omnifunc provides extra info to be shown in the preview window (in
> > case preview is included in completeopt) there is a permanent focus
> > switching back and forth between the current window and
23 matches
Mail list logo
