unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: 37178@debbugs.gnu.org
Subject: bug#37178: 26.2; doc strings of `eshell' and `eshell-buffer-name'
Date: Sat, 19 Oct 2019 16:27:11 +0000 (UTC)	[thread overview]
Message-ID: <459d5cd4-d9fc-4f56-80f3-945d1fb5fb22@default> (raw)
In-Reply-To: <CADwFkmmtJ6uCfOB4S8=VrgJRGjyC40LkeVi1+QkAQREoEmpe6w@mail.gmail.com>

> Maybe it could be made more clear, but I don't see how if we also want
> to keep it sufficiently succinct.

If the behavior, when there is no such existing
buffer, is to just create a buffer with a new
number, maybe just say that, instead of saying
that we "create it", where "it" is a "session
with that number".

IOW, say what it does: you get a new buffer,
but we say nothing about the particular number
it gets.

Another possibility is to change the behavior,
to actually create a session with that number
(why not, if that's what the user really asked
for?): create the buffer with number <42>.

Anyway, I'm OK with what you have now.  Thx.
Mentioning these things mostly for completion.





  parent reply	other threads:[~2019-10-19 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-24 23:37 bug#37178: 26.2; doc strings of `eshell' and `eshell-buffer-name' Drew Adams
2019-10-19  1:00 ` 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 [this message]
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=459d5cd4-d9fc-4f56-80f3-945d1fb5fb22@default \
    --to=drew.adams@oracle.com \
    --cc=37178@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /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).