[doc][patch] Minor fixes for some documents

2018-12-17 Fir de Conversatie h_east
Hi Bram and list,

I atached a patch.

Below, explanation about correction contents.

eval.txt
- L6691: Fixes missing quote after `bufnr`
- L6702: s/or/nor/
- L6775: Remove extra whitespace at end of line.

map.txt
- L1282: Remove extra whitespace at end of line.
- L1410: Same as above

options.txt
- L4136-L4141: Fix to the actual value from `HIGHLIGHT_INIT` at src/option.c
- L4192-L4195: Adjust tab and space
- L4193: s/normal line/selected line/
 Because it is explanation of hl-PmenuSel.
- L7343: s/ASCII letter/ASCII alphabet/
 Adapted to implementation from src/option.c:L7826
 >if (!ASCII_ISALNUM(*p) && *p != '-')

repeat.txt
- L339: mentioned about `!`.

usr_41.txt
- L1062: Remove extra space between `program` and `being`.


Please check this.
--
Best regards,
Hirohito Higashi (h_east)

-- 
-- 
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 message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index 4e80f4a97..2e5bdff2b 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -6688,7 +6688,7 @@ prop_add({lnum}, {col}, {props})
 			"end_lnum" - line number for end of text
 			"end_col"  - column for end of text; not used when
  "length" is present
-			"bufnr	   - buffer to add the property to; when
+			"bufnr"	   - buffer to add the property to; when
  omitted the current buffer is used
 			"id"	   - user defined ID for the property; when
  omitted zero is used
@@ -6699,7 +6699,7 @@ prop_add({lnum}, {col}, {props})
 		are passed.  Either use "length" or "end_col" for a property
 		within one line, or use "end_lnum" and "end_col" for a
 		property that spans more than one line.
-		When neither "length" or "end_col" are passed the property
+		When neither "length" nor "end_col" are passed the property
 		will apply to one character.
 
 		"type" will first be looked up in the buffer the property is
@@ -6772,7 +6772,7 @@ prop_list({lnum} [, {props}]) *prop_list()*
 
 
 		*prop_remove()* *E968*
-prop_remove({props} [, {lnum} [, {lnum_end}]])	
+prop_remove({props} [, {lnum} [, {lnum_end}]])
 		Remove a matching text property from line {lnum}.  When
 		{lnum_end} is given, remove matching text properties from line
 		{lnum} to {lnum_end} (inclusive).
diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt
index d43afe9df..810df334f 100644
--- a/runtime/doc/map.txt
+++ b/runtime/doc/map.txt
@@ -1279,7 +1279,7 @@ intended!  Calling a function may be an alternative.
 
 
 Completion behavior ~
-*:command-completion* *E179* *E180* *E181* 
+*:command-completion* *E179* *E180* *E181*
 *:command-complete*
 By default, the arguments of user defined commands do not undergo completion.
 However, by specifying one or the other of the following attributes, argument
@@ -1407,7 +1407,7 @@ Possible values are:
 	-addr=loaded_buffers	Range for loaded buffers
 	-addr=windows		Range for windows
 	-addr=tabs		Range for tab pages
-	-addr=other		other kind of range 
+	-addr=other		other kind of range
 
 
 Special cases ~
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 177a5699c..e2506284b 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -4133,11 +4133,12 @@ A jump table for the options with a short description can be found at |Q_op|.
  l:Search,m:MoreMsg,M:ModeMsg,n:LineNr,
  N:CursorLineNr,r:Question,s:StatusLine,
  S:StatusLineNC,c:VertSplit,t:Title,
- v:Visual,w:WarningMsg,W:WildMenu,f:Folded,
- F:FoldColumn,A:DiffAdd,C:DiffChange,
- D:DiffDelete,T:DiffText,>:SignColumn,
+ v:Visual,V:VisualNOS,w:WarningMsg,
+ W:WildMenu,f:Folded,F:FoldColumn,
+ A:DiffAdd,C:DiffChange,D:DiffDelete,
+ T:DiffText,>:SignColumn,-:Conceal,
  B:SpellBad,P:SpellCap,R:SpellRare,
- L:SpellLocal,-:Conceal,+:Pmenu,=:PmenuSel,
+ L:SpellLocal,+:Pmenu,=:PmenuSel,
  x:PmenuSbar,X:PmenuThumb,*:TabLine,
  #:TabLineSel,_:TabLineFill,!:CursorColumn,
  .:CursorLine,o:ColorColumn,q:QuickFixLine,
@@ -4182,16 +4183,16 @@ A jump table for the options with a short description can be found at |Q_op|.
 	|hl-DiffDelete|	 D  deleted line in diff mode
 	|hl-DiffText|	 T  inserted text in diff mode
 	|hl-SignColumn|	 >  column used for |signs|
+	|hl-Conceal|	 -  the placeholders used for concealed characters
+			(see 'conceallevel')
 	|hl-SpellBad|	 B  misspelled word |spell|
 	|hl-SpellCap|	 P  word that should start with capital |spell|
 	|hl-SpellRare|	 R  rare word |spell|
 	|hl-SpellLocal|	 L  word from other 

Re: [vim/vim] Add support for changing the current index in a quickfix/location list (#3701)

2018-12-17 Fir de Conversatie Yegappan Lakshmanan
Hi Bram,

On Mon, Dec 17, 2018 at 11:43 AM Bram Moolenaar
 wrote:
>
> We keep adding more features and complexity, making it difficult for
> someone who reads the help to understand what it's all for. In many
> cases it would help to add tags and tag references, so that the reader
> can find the relevant explanation.
>

I will add the additional tags and see whether we can enhance the help
text for the getqflist() and setqflist() functions.

Most of the recently added quickfix functionality is targeted at getting
and setting the  various quickfix stack/list properties using the getqflist()
and setqflist() functions. Same for the location lists/stacks using the
getloclist() and setloclist() functions.

>
> > Add the 'idx' item to the {what} argument for the setqflist() and
> > setloclist() functions to set the current index.
>
> This uses the term "file window id". There currently is one place where
> 'filewinid' is mentioned, and the explanation is hard to understand.
> I think this deserves some more words to explain what it is and how to
> use it.
>

The "filewinid" is not related to this change and was introduced in 8.1.0345.
I forgot to add an example for showing how to get it in that patch.
I am adding an example in this patch.

>
> + idx index of the current entry in the list
>
> In what list? This is also unclear.
>

The setqflist() is modifying a particular quickfix list specified either by an
identifier (id) or by a number in the stack (nr). All the other attributes in
the {what} argument are applied to this list. In this case, the 'idx' changes
the index of the current selection in the list specified by {id} or {nr}.

Regards,
Yegappan

-- 
-- 
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 message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [patch] change runtime/syntax/help.vim

2018-12-17 Fir de Conversatie Bram Moolenaar


Hirohito Higashi wrote:

> "_" was used for the argument name for the first time in
> doc/textprop.txt. It is not highlighted at present. It is necessary to
> change runtime/syntax/help.vim.  Is it OK with the attached patch?

Well, another way of looking at it is that using lnum_end is not
consistent with what's used so far.  Changing it to lnum-end works.
It's not a valid variable name, but I suppose that isn't needed here.


-- 
How To Keep A Healthy Level Of Insanity:
6. In the memo field of all your checks, write "for sexual favors".

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
-- 
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 message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[patch] change runtime/syntax/help.vim

2018-12-17 Fir de Conversatie h_east
Hi Bram and dev,

"_" was used for the argument name for the first time in doc/textprop.txt. It 
is not highlighted at present. It is necessary to change 
runtime/syntax/help.vim.
Is it OK with the attached patch?

--
Best regards,
Hirohito Higashi (h_east)

-- 
-- 
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 message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff --git a/runtime/syntax/help.vim b/runtime/syntax/help.vim
index 693a11373..8803db590 100644
--- a/runtime/syntax/help.vim
+++ b/runtime/syntax/help.vim
@@ -66,7 +66,7 @@ syn match helpSpecial		"\[N]"
 syn match helpSpecial		"N  N"he=s+1
 syn match helpSpecial		"Nth"me=e-2
 syn match helpSpecial		"N-1"me=e-2
-syn match helpSpecial		"{[-a-zA-Z0-9'"*+/:%#=[\]<>.,]\+}"
+syn match helpSpecial		"{[-a-zA-Z0-9_'"*+/:%#=[\]<>.,]\+}"
 syn match helpSpecial		"\s\[[-a-z^A-Z0-9_]\{2,}]"ms=s+1
 syn match helpSpecial		"<[-a-zA-Z0-9_]\+>"
 syn match helpSpecial		"<[SCM]-.>"


Re: [vim/vim] Update menu_it_it.latin1.vim (#3693)

2018-12-17 Fir de Conversatie Antonio Giovanni Colombo
I prefer something univocal... Actually there are corrections to do to make
them so.

On Mon, Dec 17, 2018 at 11:38 AM Diego Marino 
wrote:

> The convention is to have the shortcut keys in upper case. How they are
> displayed is different per system.
>
> Fair enough. Then why not making the first letter of a word the shortcut?
> Even if there's another with the same letter, I'd prefer to cycle through
> them than to have uppercase letters in the middle of words.
>

-- 
-- 
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 message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Patch 8.1.0586

2018-12-17 Fir de Conversatie Christian Brabandt


On Sa, 15 Dez 2018, Bram Moolenaar wrote:

> 
> Christian wrote:
> 
> > On Fr, 14 Dez 2018, Bram Moolenaar wrote:
> > 
> > > Patch 8.1.0586
> > > Problem::digraph output is not easy to read.
> > > Solution:   Add highlighting for :digraphs. (Marcin Szamotulski, closes 
> > > #3572)
> > > Also add section headers for :digraphs!.
> > > Files:src/ex_docmd.c, src/digraph.c, src/proto/digraph.pro,
> > > src/ex_cmds.h, runtime/doc/digraph.txt
> > […]
> > > + } header_table[] = {
> > > + {DG_START_OTHER1, N_("Other")},
> > […]
> > > + {DG_START_OTHER2, N_("Other")},
> > […]
> > > + {DG_START_OTHER3, N_("Other")},
> > 
> > Does having 3 Other sections make sense?
> > 
> > Shouldn't those be better (according to Unicode):
> > 
> > Letterlike (U+2100-U+214F)
> > Optical Character Recognition (U+2440-U+245F)
> > Enclosed CJK Letters (U+3200-U+32FF)
> > Alphabetic Presentation Forms (U+FB00-U+FB4F)
> 
> Well, if we want to.  These sections will become rather short.
> The names are also not very meaningful, how many users would be looking
> for "Alphabetic Presentation Forms", unless you already know where they
> are.

I just found it confusing to have "Other" appear 3 times with different 
characters and thought since we kind of used the official Unicode names, 
it would make sense to use them for the "Others" as well.

I don't have a strong opinion about it however.

Best,
Christian
-- 
Das Programm neigt sich seinem Anfang zu.
-- Heinz Erhardt

-- 
-- 
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 message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.