zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: expand style `suffix' option
Date: Thu, 04 Oct 2001 14:33:23 +0100	[thread overview]
Message-ID: <22093.1002202403@csr.com> (raw)
In-Reply-To: "Sven Wischnowsky"'s message of "Thu, 04 Oct 2001 15:10:07 +0200." <15292.24495.82880.514083@gargle.gargle.HOWL>

Sven Wischnowsky wrote:
> > When it does seem to be on, I would expect
> >   ~/b/b<TAB>
> > to list or cycle through all files ~/b*/b* when menu completion is in use,
> > but it doesn't. 
> 
> Well, it says (or tries to say) that this suff-behaviour is only done
> when not using menu-completion. I think we either had a discussion or
> I thought that people using menu-completion wouldn't want to be
> bothered with looong lists.
>...
> Restoring those things would still not make it work with menu
> completion, though (the suffix thing), but that could be added. Should 
> we?

OK, I suppose the manual is saying it works if menu completion is started
afterwards, but not if it's already in effect.

Since the `suffix' behaviour is selectable completely separately from
anything else, I can't think of a good reason why the setting shouldn't
simply be respected.  If you don't want it with menu completion you can
simply not turn it on.

Tying settings together is really another problem entirely.  If we want
some more general way of grouping --- set a whole load of styles all
together - we can probably write a function suite that does it, e.g.
  % zselect -v my_menu_styles
  Turning on option `menuselect'
  Changing style `expand' from `prefix suffix' to `prefix'
However, it's not that trivial when you take contexts into account
(compinstall has basically side-stepped this issue and while it handles
contexts, you have to select them by hand).

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


**********************************************************************
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.
**********************************************************************


  reply	other threads:[~2001-10-04 13:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-02 11:41 Peter Stephenson
2001-10-02 14:52 ` Bart Schaefer
2001-10-04 13:10 ` Sven Wischnowsky
2001-10-04 13:33   ` Peter Stephenson [this message]
2001-10-05 11:17     ` Sven Wischnowsky
2001-10-05 16:10       ` PATCH: " Peter Stephenson
2001-10-08 12:33         ` Sven Wischnowsky
2001-10-09  9:48         ` Sven Wischnowsky
2001-10-09 10:35           ` 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=22093.1002202403@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).