On 16/04/11 12:45 AM, Paul LeoNerd Evans wrote:
Having recently dredged this topic up again - what is the current state
of plan? Are we happy we have a working model of how things will work
and are just awaiting time to write some code, or are there still
questions lingering about?
I think
Q1. Need to change the input queue structure?
A1. Changing this requires many other changes, and it's not clear that
there's a whole lot to be gained for doing (very) much work. The
current queue isn't so terrible, it's just not a nicely-packaged
struct.
Q2. Can current queue structure encode
For backward compatibility reasons, existing -notation should be
considered ambiguous, but we should come up with an extension of this
notation to be considered specific. Perhaps just adding an extra
character after the opening ''--for instance !Enter could mean
Enter, specifically. When
On Sun, 17 Apr 2011, Ben Schmidt wrote:
On 16/04/11 12:45 AM, Paul LeoNerd Evans wrote:
Having recently dredged this topic up again - what is the current
state of plan? Are we happy we have a working model of how things
will work and are just awaiting time to write some code, or are there
On 17/04/11 15:23, Ben Schmidt wrote:
On 16/04/11 12:45 AM, Paul LeoNerd Evans wrote:
Having recently dredged this topic up again - what is the current state
of plan? Are we happy we have a working model of how things will work
and are just awaiting time to write some code, or are there still
On 17/04/11 16:19, Benjamin R. Haskell wrote:
[...]
Err, if you're using the 7-bit Control Sequence Introducer (\e[ = Esc
+ [ = \033 \133), then CSI sequences are virtually always valid UTF-8.
The 8-bit single-character variant does avoid UTF-8, though. In a
properly formed stream of bytes, 0x9b
Raghavendra D Prabhu wrote:
Currently when using cscope with vim and being several levels deep from
project root directory (with cscope.out located in this directory), the
cscope queries fail because of lack of prefix. Using a cscope prefix on
a per-project basis is hard. So, this patch
- It sounds like changing the internal Vim byte-stream representation for
keypresses to actually be CSI could be a good idea. By making careful use of the
private area we could ensure Vim can represent everything it needs to, plus
almost by definition it can represent all the keys/modifiers
On 18/04/11 02:31, Ben Schmidt wrote:
- It sounds like changing the internal Vim byte-stream representation
for
keypresses to actually be CSI could be a good idea. By making careful
use of the
private area we could ensure Vim can represent everything it needs
to, plus
almost by definition it can
APPROACH 2:
- -notation LHS defines specific and ambiguous maps
- C-M defines ^M and CSI-Ctrl-M
- Enter defines ^M and CSI-Enter
APPROACH 3:
- Ambiguous LHS defines ambiguous and specific maps
- ^M defines ^M, CSI-Ctrl-M and CSI-Enter
- -notation LHS defines specific and ambiguous maps
- C-M
10 matches
Mail list logo
