From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: Finding last *Async Shell Command* buffer?
Date: Thu, 25 Mar 2021 23:59:18 +0300 [thread overview]
Message-ID: <YFz5pmhZzW+2yigw@protected.localdomain> (raw)
In-Reply-To: <87h7kzm007.fsf@zoho.eu>
* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2021-03-25 23:55]:
> Jean Louis wrote:
>
> >> (defun switch-to-async-buffer ()
> >> (interactive)
> >> (switch-to-buffer-regexp "\*Async Shell Command\*") )
> >
> > Thanks for attempt. It is switching somewhere, true, but not
> > the last one, seem random or catching first buffers
> > among hundreds.
>
> Nope. Same order that they appear in *Buffer List*.
But you did get idea that order of creation of buffers is not really
numbered? When buffer 1 is created, 2 and 3, and buffer 2 deleted,
next buffer created becomes 2, and not 4, if you have 200 such
buffers, maybe 15, 18, 19, 112, and 113 were killed, and now populated
with recent buffers, but there is no way of knowing which one is
recent one to quickly look into standard output of the async command.
The last one is what is useful, or browsing through last few.
I am almost there, I just don't know how to assign it to command that
it works.
next prev parent reply other threads:[~2021-03-25 20:59 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 14:33 Finding last *Async Shell Command* buffer? Jean Louis
2021-03-25 15:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 15:08 ` Jean Louis
2021-03-25 20:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 20:36 ` Jean Louis
2021-03-25 20:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 20:59 ` Jean Louis [this message]
2021-03-25 21:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-25 21:12 ` Jean Louis
2021-03-26 5:52 ` Robert Thorpe
2021-03-26 6:47 ` Eli Zaretskii
2021-03-26 7:04 ` Jean Louis
2021-03-26 7:18 ` Eli Zaretskii
2021-03-26 7:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 7:38 ` Jean Louis
2021-03-26 7:52 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 8:43 ` Jean Louis
2021-03-26 13:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 20:08 ` Jean Louis
2021-03-26 21:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 7:17 ` Jean Louis
2021-03-26 7:47 ` Eli Zaretskii
2021-03-26 7:54 ` Jean Louis
2021-03-26 11:31 ` Eli Zaretskii
2021-03-26 14:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 20:11 ` Jean Louis
2021-03-26 22:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 23:28 ` Jean Louis
2021-03-26 23:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 7:01 ` Jean Louis
2021-03-26 7:09 ` Eli Zaretskii
2021-03-26 7:25 ` [solved]: " Jean Louis
2021-03-26 7:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 7:40 ` Jean Louis
2021-03-26 7:56 ` Eli Zaretskii
2021-03-26 8:55 ` Jean Louis
2021-03-26 11:18 ` Eli Zaretskii
2021-03-26 11:26 ` Jean Louis
2021-03-26 11:33 ` Eli Zaretskii
2021-03-26 11:48 ` Jean Louis
2021-03-26 12:37 ` Eli Zaretskii
2021-03-26 20:05 ` Jean Louis
2021-03-26 22:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 23:29 ` Jean Louis
2021-03-26 23:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 13:49 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 10:34 ` Jean Louis
2021-03-26 11:30 ` Eli Zaretskii
2021-03-25 15:18 ` Jean Louis
2021-03-25 15:54 ` Skip Montanaro
2021-03-25 19:31 ` Jean Louis
2021-03-25 18:10 ` Filipp Gunbin
2021-03-25 19:40 ` Jean Louis
2021-03-26 13:09 ` Filipp Gunbin
2021-03-26 13:40 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-26 20:06 ` Jean Louis
2021-03-26 21:17 ` Filipp Gunbin
2021-03-25 20:05 ` Jean Louis
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=YFz5pmhZzW+2yigw@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@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.