From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: Two missing completion functions that bug me
Date: Fri, 30 Mar 2001 16:11:02 +0000 [thread overview]
Message-ID: <1010330161103.ZM4360@candle.brasslantern.com> (raw)
In-Reply-To: <200103300821.KAA22411@beta.informatik.hu-berlin.de>
On Mar 30, 10:21am, Sven Wischnowsky wrote:
}
} > I was thinking it was needed to get other options to be completed in the
} > same word, because of:
} >
} > % vared -a<TAB>
} > % vared -a
} > ^cursor silently moves here
} >
} > [...] Is there a way *other than* adding a ->state
} > machine to get other options to complete in the same word but arguments
} > in the next for an option like -a?
}
} You could try the patch below, which does that (automatically) for
} me. I'll commit it if we don't find any nasty side effect (or should
} I apply it and take it back if we find problems? feel free to commit
} it if you like it...)
I haven't tried it yet, but what do you do if you *don't* want to allow
other single-letter options to be completed in the same word after one
that takes an argument (but do complete them in the same word *before*
the one that takes the argument)?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2001-03-30 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 8:21 Sven Wischnowsky
2001-03-30 16:11 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-02 9:15 Sven Wischnowsky
2001-04-02 12:04 ` Oliver Kiddle
2001-03-30 8:23 Sven Wischnowsky
2001-03-29 7:59 Bart Schaefer
2001-03-29 10:09 ` Oliver Kiddle
2001-03-29 16:24 ` Bart Schaefer
2001-03-30 9:16 ` Oliver Kiddle
2001-03-30 15:38 ` Bart Schaefer
2001-03-30 15:59 ` Bart Schaefer
2001-03-30 16:35 ` Oliver Kiddle
2001-03-30 16:53 ` Bart Schaefer
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=1010330161103.ZM4360@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.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).