Hi Arnaud!

On Mi, 05 Aug 2015, Arnaud Decara wrote:

> > I have the same difficulties with this topic, thus would appreciate
> > proposed improvements too.

Thank you. In general looks good for me. I'll add some remarks inline to 
your new option.txt file.

- Some helptags got lost, e.g. *boolean*, *toggle*

> *options.txt* For Vim version 7.4.  Last change: 2015 Aug 05
> 
> 
>                 VIM REFERENCE MANUAL    by Bram Moolenaar
> 
> 
> Options                                                       *options*
> 
> 1. Types and scopes of options                |option-presentation|
> 2. Initialization of options          |option-initialization|
> 3. Displaying and setting options     |set-option|
> 4. Automatically setting options      |auto-setting|
> 5. Options summary                    |option-summary|
> 
> 
> Options provide an interface to change the values of some variables
> internal to Vim in order to alter its behaviour.
> For an overview of available options see |option-list|.
> 
> ==============================================================================
> 1. Types and scopes of options                                
> *option-presentation*
> 
>                                                       *option-types*
> Options come in three categories depending on the type of the variables they
> grant access to: boolean, numeric and string options.

Perhaps add from the current help text:

        boolean {bool.opt}      can only be on or off           *boolean* 
*toggle*
        number  {num.opt}       has a numeric value
        string  {str.opt}       has a string value

[…]
> They are disabled by default.  In a given buffer or window-buffer pair the
> value used to define the behaviour is the global one unless the local variable
> has been voluntarily enabled.

perhaps use explicit instead of voluntarily? (also in the other places 
that use it)

[…]
> On startup the variables global to Vim or to the first window must be
> initialized.  Roughly put, the global variables for which you haven't
> specified any initial values (see |auto-setting|) will be initialized to:
> - the Vim default values if Vim finds a user vimrc file or a user gvimrc file

    or has been started in no-compatible mode |-N|

> - the Vi default values otherwise.
> For the exact inialization mechanism on startup, see 'compatible' and
> |initialization|.
> 
> When a buffer B is edited for the first time in the Vim session, the new
> variables local to B and to (current window, B) must be initialized:

current window, W

[…]
> You can also display values of several options at once by using the "all"
> argument or by calling :set, :setlocal or :setglobal without argument.
>                                                               *:set-all*
> :setglobal all    displays the current global value of each local and
>                 global-local options (nothing displayed for global options).

:setg[lobal] all
> 
> :setlocal all           displays the current local value of each local and
>                 global-local options (nothing displayed for global options).

:setl[ocal] all
> 
> :set all        displays a value for each option:

:se[t]

[…]
>                   - the global         value  if the option is global
>                   - the current local  value  if the option is local
>                   - the currently used value  if the option is global-local.
>                                                               *:set*
> :set            Without any argument :set, :setlocal and :setglobal work
> :setlocal       respecively like :set all, :setlocal all and :setglobal all
> :setglobal      but only values differing from the default values (the Vi
>                 default values if 'compatible' is True; the Vim ones
>                 otherwise) are displayed.

Again, :se[t], :setl[ocal], :setg[lobal]

[…]
> 
> ----------------------------------------------------------------------------
> Table 4 - Arguments to change values of one option at a time

With {opt} any option, {bool.opt} being a boolean option, {str.opt} 
being a string option and {num.opt} being a numeric option value.

[…]
>                                                   *:set^=* *:set+=* *:set-=*
> {num.opt}^={val}      {val} multiplied by its current value    {not in Vi}
> {num.opt}+={val}      {val} added to its current value         {not in Vi}
> {num.opt}-={val}      {val} substracted from its current value {not in Vi}
> {str.opt}^={val}      its current value prepended with {val}   {not in Vi}
> {str.opt}+={val}      its current value appended  with {val}   {not in Vi}
> {str.opt}-={val}      its current value from which was removed {not in Vi}
>                         an eventual occurrence of {val}

Some aligning issues. Also I think this might be a little bit too terse. 
Perhaps keep the old description. (Especially I find the str./num.opt 
hard to understand.


Best,
Christian
-- 
Wer am Gipfel des Baumes Früchte sehen will, der nähre seine Wurzel.
                -- Johann Gottfried Herder

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

Raspunde prin e-mail lui