Le 28/02/2013 23:32, Rich Shepard a écrit :
I am curious why sometimes the Tab key moves the cursor from cell to
cell
in a table and other times appends (unwanted) text to the data in the cell.
Most of the time [Tab] moves the cursor to the next cell to the right
(or
the next row from the end of the row above) but sometimes it generates
unwanted text. For example, in a table cell I enter '10' and press [Tab];
the result is '10-years'. In another cell I entered 'June' and when the
[Tab] key is pressed the contents are changed to 'JuneJune'.
It is because Tab is a multi-bound key (I am not sure this terms means
anything) and one of these bindings is completion-accept..
\bind "Tab" "command-alternatives
completion-accept;cell-forward;tab-insert;depth-increment;outline-in"
"command-alternatives" means that all these possibilities are tried
one-by-one until one of them is enabled. If you look at the
possibilities, you see that everything is about moving, except
completion-accept and tab-insert. I would assume that tab-insert is OK
(it will work only in some cases of text-only insets IIRC), but
completion-accept is a different case.
The problem with completion accept in this setting is that it is totally
unpredictable. The user will not be able to know whether a completion is
going to happen or not (Hmm, or maybe the cursor style tells this?).
What would other people think about removing it from the Tab binding and
putting it somewhere else? The alternative would be to have it as last
choice.
Rich, the short answer is that, if you do not use completion, you can
just turn it off.
JMarc
