zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: Bug#190948: Violation against The Single UNIX ® Specification, Version 2
Date: Wed, 14 May 2003 13:40:35 +0100	[thread overview]
Message-ID: <21466.1052916035@csr.com> (raw)
In-Reply-To: "Oliver Kiddle"'s message of "Wed, 14 May 2003 13:07:03 +0200." <3014.1052910423@gmcs3.local>

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@csr.com>                  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 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


  parent reply	other threads:[~2003-05-14 12:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030427130703.GB12714@verso.st.jyu.fi>
2003-05-14 11:07 ` Oliver Kiddle
2003-05-14 11:46   ` Bug#190948: Violation against The Single UNIX R " Borzenkov Andrey
2003-05-14 12:40   ` Peter Stephenson [this message]
2003-05-14 12:57     ` Bug#190948: Violation against The Single UNIX ? " Zefram
2003-05-14 14:14       ` Peter Stephenson
2003-05-14 14:20         ` Peter Stephenson
2003-05-15  9:17         ` Peter Stephenson
2003-05-15  9:37           ` Zefram
2003-05-15  9:49             ` Peter Stephenson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21466.1052916035@csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).