From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: Bug#99095: Process completion for gdb
Date: Thu, 31 May 2001 17:26:33 +0200 (MET DST) [thread overview]
Message-ID: <200105311526.RAA12705@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <20010531100751.A13076@dman.com>
Clint Adams wrote:
> ...
>
> We could do this to _gdb
>
> 50c50
> < _alternative 'files:: _files' "processes:: _pids -m ${w[1]:t}"
> ---
> > _alternative "core-files:: _files -g '*core'" 'files:: _files' "processes:: _pids -m ${w[1]:t}"
>
> and then you could set zstyle ':completion:*:complete:gdb:*' tag-order 'processes core-files'
>
> What do people think?
I thought about something like that when I wrote _gdb. The problem is
if there is no file matching *core. Then the first would complete all
files (or directories), too. And since they may be in different groups,
they would be shown twice.
Obviously, I didn't find a solution...
> > Or perhaps to have some portable and extensible mechanism for selecting
> > processes. I would say that at least these should be supported:
> >
> > - All of a user's processes (ps x, ps -u user), for most uses
> > - All of everyone's processes (ps ax, ps -e), for root
> > - Some formatting options (ps u, ps -f) for more verbosity
>
> The problem is accurately determining whether ps is SYSV- or BSD-style or
> something else entirely.
Indeed.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev parent reply other threads:[~2001-05-31 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010528201016.A16176@alcor.net>
[not found] ` <20010529104252.B403@dman.com>
[not found] ` <20010529134715.R27012@alcor.net>
[not found] ` <20010530104751.A28439@dman.com>
[not found] ` <20010530204009.C3810@alcor.net>
2001-05-31 14:07 ` Clint Adams
2001-05-31 15:26 ` Sven Wischnowsky [this message]
2001-05-31 17:58 ` Clint Adams
2001-06-01 7:30 ` Sven Wischnowsky
2001-06-01 12:13 ` PATCH: gdb corefile completion [was Re: Bug#99095: Process completion for gdb] Clint Adams
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=200105311526.RAA12705@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).