* Rename output buffer of `ibuffer-do-shell-command-pipe'
@ 2016-07-14 12:22 Tino Calancha
2016-07-14 12:32 ` Tino Calancha
0 siblings, 1 reply; 2+ messages in thread
From: Tino Calancha @ 2016-07-14 12:22 UTC (permalink / raw)
To: emacs-devel
`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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Rename output buffer of `ibuffer-do-shell-command-pipe'
2016-07-14 12:22 Rename output buffer of `ibuffer-do-shell-command-pipe' Tino Calancha
@ 2016-07-14 12:32 ` Tino Calancha
0 siblings, 0 replies; 2+ messages in thread
From: Tino Calancha @ 2016-07-14 12:32 UTC (permalink / raw)
To: emacs-devel
On Thu, 14 Jul 2016, Tino Calancha wrote:
>
> `ibuffer-do-shell-command-pipe' inserts the output in a buffer called
> as in `ibuffer-do-shell-command-file'.
By the way, you may notice when doing, for instance:
F1-f ibuffer-do-shell-command-pipe RET
That the button 'ibuf-ext.el' in buffer *Help* bring you
to the beginning of the source file.
Should `describe-function' be extended to show the
definition of such commands build with `define-ibuffer-op'?
Thanks,
Tino
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-07-14 12:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-07-14 12:22 Rename output buffer of `ibuffer-do-shell-command-pipe' Tino Calancha
2016-07-14 12:32 ` Tino Calancha
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).