as we have brand new lfun for alternative lfuns to be bound to
certain key
we should decide what to do with tab key:
to sum up for people not involved in lengthy discussions:
tab bindings:
1.5 state: used for tables and math arrays
rc2 state: used for completion (complete lfun)
new proposal on which we agreed with Richard was:
primary bind: complete-accept
secondary: cell-forward
(third from Vinc: make-tab-in-listings-lfun:)
(fourth from JM: depth-increment)
in this way
- when completion offers some proposal tab is always used to accept
such proposal.
- otherwise if we are in table or in math array we move one more cell
(- otherwise if we are in listings input the tab key)
(- otherwise if we are in some listing envi increment depth)
- otherwise do nothing
now the questions:
1. complete was replaced by complete-accept.
(complete is trying to complete in the way bash do after tab -
find the longest common prefix from the current on.)
is there some disagreement with it?
Fine with me if it feels more intuitive, especially now with multiple
bindings.
in case of no:
2. complete lfun has no binding, should we bind it (and where)?
Good luck to find a good key. I guess nearly every other combination
of modifiers and tab is somehow used by the OS. On Mac alt-tab would
be ok. But on Windows it's taken.
Stefan
