Re: vim.vim organization

2012-11-01 Fir de Conversatie Tony Mechelynck

On 01/11/12 01:19, Kartik Agaram wrote:

I notice many keywords in runtime/syntax/vim.vim are split across
multiple lines. For example, I assume all the lines beginning with
syn keyword vimCommand could logically be assumed to be a single
(very long) command. Is that accurate?

If this is correct, I'm curious if there's some pattern to how they
are organized. It seems each line is in alphabetical order. But
there's a's in each line. Is there some way to decide which line each
keyword goes to?

Or am I just over-thinking things? :)

Kartik
http://akkartik.name



As Dr.Chip said, parts of the syntax/vim.vim script are generated 
automatically. When the interpreter sources the script, every line 
starts a new statement, except of course in the case of continuation 
lines, i.e. if (in 'nocompatible' mode) the first nonblank on the line 
is a backslash, in which case the interpreter disregards the backslash, 
all (zero or more) tabs or spaces preceding it, and the line break 
between that line and the one before it.


Best regards,
Tony.
--
Someone will try to honk your nose today.

--
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


Re: vim.vim organization

2012-11-01 Fir de Conversatie Kartik Agaram
 You're likely looking at the automatically generated keyword lists;
 vimCommands are generated automatically.  The keywords are sorted in the
 usual ascending alphabetical order with 100 keywords per line.

Yeah I see the comments now that these lines are auto-generated:

syn keyword vimCommand containedabc[lear] argdo argu[ment]
bel[owright] bN[ext] ...
syn keyword vimCommand containedabo[veleft] arge[dit] as[cii]
bf[irst] bo[tright] ...
syn keyword vimCommand containedal[l] argg[lobal] bad[d] bl[ast]
bp[revious] ...

Each of them is internally in alphabetical order. But how are the
boundaries between lines decided? They're all keyword vimCommand.

Also, is the generator in the repo?

-- 
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


vim.vim organization

2012-10-31 Fir de Conversatie Kartik Agaram
I notice many keywords in runtime/syntax/vim.vim are split across
multiple lines. For example, I assume all the lines beginning with
syn keyword vimCommand could logically be assumed to be a single
(very long) command. Is that accurate?

If this is correct, I'm curious if there's some pattern to how they
are organized. It seems each line is in alphabetical order. But
there's a's in each line. Is there some way to decide which line each
keyword goes to?

Or am I just over-thinking things? :)

Kartik
http://akkartik.name

-- 
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


Re: vim.vim organization

2012-10-31 Fir de Conversatie Charles E Campbell Jr

Kartik Agaram wrote:

I notice many keywords in runtime/syntax/vim.vim are split across
multiple lines. For example, I assume all the lines beginning with
syn keyword vimCommand could logically be assumed to be a single
(very long) command. Is that accurate?

If this is correct, I'm curious if there's some pattern to how they
are organized. It seems each line is in alphabetical order. But
there's a's in each line. Is there some way to decide which line each
keyword goes to?

Or am I just over-thinking things? :)

You're likely looking at the automatically generated keyword lists; 
vimCommands are generated automatically.  The keywords are sorted in the 
usual ascending alphabetical order with 100 keywords per line.


Regards,
C Campbell

--
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