zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Marko Myllynen <myllynen@redhat.com>, zsh workers <zsh-workers@zsh.org>
Subject: Re: zsh pid completion
Date: Thu, 19 May 2016 21:14:05 +0000	[thread overview]
Message-ID: <20160519211405.GA8007@tarsus.local2> (raw)
In-Reply-To: <CAHYJk3SDb5H9wQ8fmbwegTUYMS5xbQnqEQoVn0oWVBZr_UYJLA@mail.gmail.com>

Mikael Magnusson wrote on Tue, May 17, 2016 at 18:48:24 +0200:
> On Tue, May 17, 2016 at 12:50 PM, Marko Myllynen <myllynen@redhat.com> wrote:
> > Hi,
> >
> > I see that _pids completion offers only a very limited subset of the
> > running pids (even by the same user). For example, if I launch a command
> > on a terminal its PID is not included in completion alternatives on
> > another terminal. Also, when root, in some cases it might be beneficial
> > to offer also non-root PIDs (perhaps this could be configurable).
> >
> > Is there some reason for this limited approach? (I'm not sending any
> > patches yet, I'm afraid with ps(1) portability might be a bit tricky.)
> 
> No need for a patch, you can just set a style to run whatever ps
> command you like to generate the matches, i use:
> zstyle ':completion:*:processes' command 'ps ax -o
> user,pid,nice,%cpu,%mem,vsz,rss,tname,stat,start,time,command
> --sort=-%cpu'
> 
> These are also possible
> zstyle ':completion:*:processes' command 'ps aux'
> zstyle ':completion:*:processes' command 'ps --forest -A -o pid,user,cmd'

There's also a variant that allows cycling through user processes, all
user processes, and all processes:

http://www.zsh.org/cgi-bin/mla/redirect?USERNUMBER=20372

('_next_tags' is a widget that needs to be bindkey'd; I bind it to ^Xn)


  reply	other threads:[~2016-05-19 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 10:50 Marko Myllynen
2016-05-17 16:48 ` Mikael Magnusson
2016-05-19 21:14   ` Daniel Shahaf [this message]
2016-05-20  7:41     ` Marko Myllynen

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=20160519211405.GA8007@tarsus.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=mikachu@gmail.com \
    --cc=myllynen@redhat.com \
    --cc=zsh-workers@zsh.org \
    /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).