Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: $KEYMAP in command, isearch and menuselect
- X-seq: zsh-workers 28192
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: "Zsh Hackers' List" <zsh-workers@xxxxxxx>
- Subject: Re: $KEYMAP in command, isearch and menuselect
- Date: Mon, 23 Aug 2010 06:43:07 -0700
- In-reply-to: <20100823110127.7566d360@xxxxxxx>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <op.vg6lcz2hvocxtk@tabole> <20100823103638.2fb7e695@xxxxxxx> <20100823110127.7566d360@xxxxxxx>
On Aug 23, 11:01am, Peter Stephenson wrote:
}
} I'm now scratching my head over this in the isearch doc:
}
} Any multi-character string that is not bound to one of the above
} functions will beep and interrupt the search, leaving the last found
} line in the buffer. Any single character that is not bound to one of
} the above functions, or tt(self-insert) or tt(self-insert-unmeta),
} will have the same effect but the function will be executed.
}
} I don't think this distinction exists --- I think any unrecognised
} binding will have the same effect, of leaving isearch and executing
} that command.
I think this is a leftover from a previous generation of handling of
multi-character bindings, and probably should have changed years ago
had anyone thought to pay attention.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author