From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: completions for su and implicit fg/bg
Date: Fri, 9 Jul 1999 12:44:54 +0200 (MET DST) [thread overview]
Message-ID: <199907091044.MAA16294@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Peter Stephenson's message of Fri, 09 Jul 1999 12:04:15 +0200
Peter Stephenson wrote:
> Oliver Kiddle wrote:
> > First, is a patch to _first which completes jobs after an initial % on
> > the command line.
>
> I think the code in _first was deliberately left commented because it gets
> run every time, but the impact of this change is minimal.
Right. And since we only want it in command position, we should
probably put it in _command_names.
> > This is useful when foregrounding or backgrounding a
> > process without fg/bg. This feature seems to be undocumented actually.
>
> Hmm, I thought it was an option, but it seems it's run unconditionally at
> the top of execcmd(). What is an option is AUTO_RESUME.
It's in builtins.yo under `bg' and `fg'.
> > I've included a basic completion for the
> > common shells which just does the -c option.
>
> It really needs to be told to treat a (possibly quoted) word after -c as a
> complete command line. I've forgotten how to do that.
It's `compset -q' -- and with that I can repeat the question I asked
at the time when I sent the completion-quoting-patch: currently the
`-q' option only has an effect if the word on the command line is
quoted -- should we change it to work on unquoted strings, too?
And: nothing against giving _normal (an) optional argument(s) that
will be put at the front of $words. (_normal is one of the older
functions that survived (with changes) the transition from reporting
command line words as positional parameters to the $words array we
have now; that's why nobody made it accept arguments again, I think).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~1999-07-09 10:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-09 10:44 Sven Wischnowsky [this message]
1999-07-09 12:34 ` Peter Stephenson
[not found] ` <3785FAFB.3E9FDD41@thoth.u-net.com>
1999-07-09 13:53 ` Oliver Kiddle
1999-07-09 14:47 ` Peter Stephenson
1999-07-09 15:53 ` Oliver Kiddle
-- strict thread matches above, loose matches on Subject: below --
1999-07-19 13:58 Sven Wischnowsky
1999-07-19 13:38 ` Peter Stephenson
1999-07-13 9:02 Sven Wischnowsky
1999-07-12 12:11 Sven Wischnowsky
1999-07-12 14:29 ` Peter Stephenson
1999-07-12 10:39 Sven Wischnowsky
1999-07-12 11:27 ` Peter Stephenson
1999-07-09 13:47 Sven Wischnowsky
1999-07-09 10:23 Oliver Kiddle
1999-07-09 10:04 ` Peter Stephenson
1999-07-09 10:40 ` Andrej Borsenkow
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=199907091044.MAA16294@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).