From: Nafiz Islam <nafiz.islam1001@gmail.com>
To: 67972@debbugs.gnu.org
Subject: bug#67972: Use *command (&)* instead of shell-command-buffer-name(-async)
Date: Fri, 22 Dec 2023 12:31:24 -0500 [thread overview]
Message-ID: <CAKjtFcRRVPCixZbdgYmVkY_tOGQdFxAotD6iFi270Mk=Z2__Nw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
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.
@@ -4252,12 +4252,6 @@ undo-outer-limit-truncate
;;;; Shell commands
-(defconst shell-command-buffer-name "*Shell Command Output*"
- "Name of the output buffer for shell commands.")
-
-(defconst shell-command-buffer-name-async "*Async Shell Command*"
- "Name of the output buffer for asynchronous shell commands.")
-
(defvar shell-command-history nil
"History list for some commands that read shell commands.
@@ -4671,7 +4660,8 @@ shell-command
;; Output goes in a separate buffer.
(if (string-match "[ \t]*&[ \t]*\\'" command)
;; Command ending with ampersand means asynchronous.
- (let* ((buffer (get-buffer-create
+ (let* ((shell-command-buffer-name-async (concat "*" command
"*"))
+ (buffer (get-buffer-create
(or output-buffer
shell-command-buffer-name-async)))
(bname (buffer-name buffer))
(proc (get-buffer-process buffer))
@@ -4942,7 +4932,8 @@ shell-command-on-region
shell-command-default-error-buffer
t
(region-noncontiguous-p))))
- (let ((error-file
+ (let ((shell-command-buffer-name (concat "*" command "*"))
+ (error-file
(if error-buffer
(make-temp-file
(expand-file-name "scor"
[-- Attachment #2: Type: text/html, Size: 1949 bytes --]
next reply other threads:[~2023-12-22 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 17:31 Nafiz Islam [this message]
2023-12-22 19:18 ` bug#67972: Use *command (&)* instead of shell-command-buffer-name(-async) Eli Zaretskii
2023-12-22 19:39 ` Nafiz Islam
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='CAKjtFcRRVPCixZbdgYmVkY_tOGQdFxAotD6iFi270Mk=Z2__Nw@mail.gmail.com' \
--to=nafiz.islam1001@gmail.com \
--cc=67972@debbugs.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.