[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[RFC] A review of htags's options and config variables

From: Shigio YAMAGUCHI
Subject: [RFC] A review of htags's options and config variables
Date: Fri, 02 Apr 2010 18:00:18 +0900

Hi all,

I'm reviewing htags's options and config variables.
Some functions has both option and config variable, and others
has only the either. It seems random.  I want to arrange this again.

I made the following plan. What do you think?

Rough rules:
o Each value should have a config variable.
o Each function should have a option.

(1) An abolished option

an abolished option                     Config variable(remain)
--tabs number                           tabs(number)

(2) Abolished Config variables

abolished Config variables              Option(remain)
definition_header(position)             -h, --func-header[=position]
disable_grep                            --disable-grep
dynamic                                 -D, --dynamic
full_path                               --full-path
no_map_file                             --no-map-file
other_files                             -o, --other
show_position                           --show-position
table_flist                             -T, --table-flist[=rows]
flist_fields(number)                    -T, --table-flist[=rows]
enable_idutils                          --disable-idutils (*)
table_list                              --table-list (*)

Since some variables don't have corresponding option (*), I will make it. 
Though '--disable-idutils' is opposite to 'enable_idutils', I want to
adopt this option to the manner of '--disable-grep'.

These are incompatible changes. Users need to rewrite configuration file.
For example:
:htags_options=--func-header=before --full-path --other --table-flist=3 

Is there any problem?
Shigio YAMAGUCHI <address@hidden>
PGP fingerprint: D1CB 0B89 B346 4AB6 5663  C4B6 3CA5 BBB3 57BE DDA3

reply via email to

[Prev in Thread] Current Thread [Next in Thread]