From: Tino Calancha <tino.calancha@gmail.com>
To: emacs-devel@gnu.org
Subject: Rename output buffer of `ibuffer-do-shell-command-pipe'
Date: Thu, 14 Jul 2016 21:22:22 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1607142120540.10620@calancha-pc> (raw)
`ibuffer-do-shell-command-pipe' inserts the output in a buffer called
"* ibuffer-shell-output*".
I would prefer calling it:
"*ibuffer-shell-output*"
(without space after '*').
Or even just:
"Shell Command Output*"
as in `ibuffer-do-shell-command-file'.
What do you think?
Tino
next reply other threads:[~2016-07-14 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 12:22 Tino Calancha [this message]
2016-07-14 12:32 ` Rename output buffer of `ibuffer-do-shell-command-pipe' Tino Calancha
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=alpine.DEB.2.20.1607142120540.10620@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=emacs-devel@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 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).