From: Eli Zaretskii <eliz@gnu.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 48072@debbugs.gnu.org, kevin.legouguec@gmail.com
Subject: bug#48072: 28.0.50: dired-read-shell-command: handle empty input properly [PATCH]
Date: Wed, 28 Apr 2021 18:13:11 +0300 [thread overview]
Message-ID: <83a6pifnnc.fsf@gnu.org> (raw)
In-Reply-To: <20210428150144.4uxrcguggkh7vrjx@E15-2016.optimum.net> (message from Boruch Baum on Wed, 28 Apr 2021 11:01:44 -0400)
> Date: Wed, 28 Apr 2021 11:01:44 -0400
> From: Boruch Baum <boruch_baum@gmx.com>
> Cc: kevin.legouguec@gmail.com, 48072@debbugs.gnu.org
>
> > > > I'm not sure I understand what you are suggesting. Do you mean set up
> > > > the completion candidates so that they would only include executable
> > > > files found on the system, but allow users also to type commands that
> > > > are not among the completion candidates? I think this could be
> > > > confusing, and I don't think we have a precedent for such a behavior
> > > > elsewhere.
>
> You had that idea correct in your prior paragraph, where your wrote:
>
> "set up the completion candidates so that they would only include
> executable files found on the system, but allow users also to type
> commands that are not among the completion candidates"
Then I already stated my opinion about this above. I wonder what do
others think about such a feature.
> 2.1.1) Try the following in a vanilla dired buffer: Navigate POINT to a file,
> let's say 'bar', and press '&' for the async command. Then type in some
> garbage command, let's say 'foo', and <RET>. The response I get is a
> message in the mini-buffer: "foo bar&wait: finished." (BTW, I haven't
> figured out where that message is being generated; anyone's help would be
> appreciated; I would like to see if it can report errors).
I think the message comes from process.c:status_notify, which is
called when the process is deleted after it exits.
next prev parent reply other threads:[~2021-04-28 15:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 19:02 bug#48072: 28.0.50: dired-read-shell-command: handle empty input properly [PATCH] Boruch Baum
2021-04-27 19:19 ` Eli Zaretskii
2021-04-27 19:32 ` Boruch Baum
2021-04-28 2:22 ` Eli Zaretskii
2021-04-28 3:00 ` Boruch Baum
2021-04-28 6:19 ` Kévin Le Gouguec
2021-04-28 9:33 ` Boruch Baum
2021-04-28 9:50 ` Boruch Baum
2021-04-28 11:58 ` Eli Zaretskii
2021-04-28 12:49 ` Boruch Baum
2021-04-28 13:03 ` Eli Zaretskii
2021-04-28 15:01 ` Boruch Baum
2021-04-28 15:13 ` Eli Zaretskii [this message]
2021-04-28 15:21 ` Boruch Baum
2021-04-28 15:52 ` Eli Zaretskii
2021-04-28 17:10 ` Michael Albinus
2021-04-28 15:16 ` Boruch Baum
2021-04-28 11:47 ` Eli Zaretskii
2021-04-28 11:03 ` Michael Albinus
2021-04-28 12:00 ` Boruch Baum
2021-04-28 12:13 ` Michael Albinus
2021-04-28 12:46 ` Boruch Baum
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a6pifnnc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=48072@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
--cc=kevin.legouguec@gmail.com \
/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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).