From: Nafiz Islam <nafiz.islam1001@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67972@debbugs.gnu.org
Subject: bug#67972: Use *command (&)* instead of shell-command-buffer-name(-async)
Date: Fri, 22 Dec 2023 14:39:55 -0500 [thread overview]
Message-ID: <CAKjtFcSnSFq8a3MW_XQ2esPtD5NgWg_i7qh8pcEmzHFsmbOSdw@mail.gmail.com> (raw)
In-Reply-To: <83a5q2f3ls.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
That is a good idea. They could take a string or a symbol with a default
string value.
The variables shell-command-buffer-name(-async) could be declared as
defcustom instead of defconst.
On Fri, Dec 22, 2023 at 2:18 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Nafiz Islam <nafiz.islam1001@gmail.com>
> > Date: Fri, 22 Dec 2023 12:31:24 -0500
> >
> > The buffer name for the shell-command or async-shell-command would be
> much more useful if they
> > were given the name of the command being executed.
> >
> > I started working a bit on a patch for that, but it's just code changes
> right now. Here's a preview of
> > what I mean.
>
> Instead of removing the default name, why not add one more possible
> value to async-shell-command-buffer, which will do what you want?
> Then users who are interested in this behavior could customize
> async-shell-command-buffer to that new value.
>
> Thanks.
>
[-- Attachment #2: Type: text/html, Size: 1349 bytes --]
prev parent reply other threads:[~2023-12-22 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 17:31 bug#67972: Use *command (&)* instead of shell-command-buffer-name(-async) Nafiz Islam
2023-12-22 19:18 ` Eli Zaretskii
2023-12-22 19:39 ` Nafiz Islam [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=CAKjtFcSnSFq8a3MW_XQ2esPtD5NgWg_i7qh8pcEmzHFsmbOSdw@mail.gmail.com \
--to=nafiz.islam1001@gmail.com \
--cc=67972@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.