Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: Bug#190948: Violation against The Single UNIX ® Specification, Version 2

Oliver Kiddle wrote:
> On 27 Apr, Juhapekka Tolvanen wrote:
> > 
> > http://www.opengroup.org/onlinepubs/007908799/xcu/chap2.html#tag_001_014_01
> 1
> > 
> > juhtolv@heresy:/home/juhtolv % set -o vi
> > set: no such option: vi
> Being an interactive related feature, this isn't so critical but it would
> be better if we can handle this. Adding a special case in bin_set()
> instead of actually adding an option might perhaps be sufficient to
> satisfy the specification. However, on the basis that zle is a separate
> module and may not even be loaded and you can't just call selectkeymap(),
> I have no idea how to get this to work. And which keymap should set +o
> vi select?

Exactly, it's completely meaningless in zsh.  It is ridiculous for the
standard to specify how the shell handles line editing, it implies far
too much about the architecture, and I would suggest it actively
encourages poor component design.  Who says a shell *has* to have a
version of vi built into it, for goodness sake?

Although in principle we could handle it I would be quite happy to make
a point of it being a dummy or printing an error message, with a
rationale in the documentation.

Peter Stephenson <pws@xxxxxxx>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070

The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
If you received this in error, please contact the sender and 
delete the material from any computer.

Messages sorted by: Reverse Date, Date, Thread, Author