From: Drew Adams <drew.adams@oracle.com>
To: 37178@debbugs.gnu.org
Subject: bug#37178: 26.2; doc strings of `eshell' and `eshell-buffer-name'
Date: Sat, 24 Aug 2019 16:37:50 -0700 (PDT) [thread overview]
Message-ID: <f1ae31ff-7fa3-44b4-b03c-77855c8eb2b6@default> (raw)
This is the `eshell' doc string:
Create an interactive Eshell buffer.
The buffer used for Eshell sessions is determined by the value of
'eshell-buffer-name'. If there is already an Eshell session active in
that buffer, Emacs will simply switch to it. Otherwise, a new session
will begin. A numeric prefix arg (as in 'C-u 42 M-x eshell RET')
switches to the session with that number, creating it if necessary. A
nonnumeric prefix arg means to create a new session. Returns the
buffer selected (or created).
That's a wall of text. But the problem to report here is that the
_number_ of a session is unclear. What is it and, especially, what, if
anything, does it have to do with `eshell-buffer-name'.
Experimenting a bit, a guess is that the names of Eshell buffers use
`eshell-buffer-name' followed, by all but the first, by "<N>", where N =
2,3,4... as additional sessions are created. And with a numeric prefix
arg M, `eshell' tries to find a session with buffer name ending in <M>.
E.g., I tried `M-x eshell' followed by `C-u M-x eshell'. The first
created buffer `*eshell*', and the second created buffer `*eshell<2>*'
(not `*eshell<4>*', BTW).
This naming convention should be described in the doc string, in order
to make clear (1) how `eshell-buffer-name' is used as a "base name" and
(2) how the prefix arg relates to the buffer-name convention.
Also, the doc string for variable `eshell-buffer-name' is poor. That's
really where the use of the value as a "base name" needs to be described
(i.e., make clear what is mean by "base name" and how multiple eshell
buffers are named).
In GNU Emacs 26.2 (build 1, x86_64-w64-mingw32)
of 2019-04-13
Repository revision: fd1b34bfba8f3f6298df47c8e10b61530426f749
Windowing system distributor `Microsoft Corp.', version 10.0.17763
Configured using:
`configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
next reply other threads:[~2019-08-24 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 23:37 Drew Adams [this message]
2019-10-19 1:00 ` bug#37178: 26.2; doc strings of `eshell' and `eshell-buffer-name' Stefan Kangas
2019-10-19 5:21 ` Drew Adams
2019-10-19 12:22 ` Stefan Kangas
2019-10-19 12:47 ` Eli Zaretskii
2019-10-19 16:27 ` Drew Adams
2019-10-20 13:16 ` Stefan Kangas
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=f1ae31ff-7fa3-44b4-b03c-77855c8eb2b6@default \
--to=drew.adams@oracle.com \
--cc=37178@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 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).