From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH: fix a few problems of "_pids -m pattern"
Date: Wed, 19 Aug 2015 07:59:12 -0700 [thread overview]
Message-ID: <150819075912.ZM27667@torch.brasslantern.com> (raw)
In-Reply-To: <2C7B5A5B-EF10-4474-94A7-34BF531D2D28@kba.biglobe.ne.jp>
On Aug 19, 10:39pm, Jun T. wrote:
}
} (3) The patch also replaces the '${2}*' by '${2}([[:blank:]]*|)'
} so that, for example,
}
} % gdb /path/to/ex <TAB>
}
} does not completes the PIDs of running 'expect' (or 'expand').
This seems fine to me. "ex" is the word on the line, it's what should
be used to (as precisely as possible) match the process name in ps.
prev parent reply other threads:[~2015-08-19 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 13:39 Jun T.
2015-08-19 14:59 ` Bart Schaefer [this message]
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=150819075912.ZM27667@torch.brasslantern.com \
--to=schaefer@brasslantern.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).