From: Michael Albinus <michael.albinus@gmx.de>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 55236@debbugs.gnu.org
Subject: bug#55236: 29.0.50; Surprising behaviors with Eshell expansions
Date: Tue, 03 May 2022 11:32:07 +0200 [thread overview]
Message-ID: <871qxbhsh4.fsf@gmx.de> (raw)
In-Reply-To: <026eb87e-1880-2200-934f-58d2296a94f9@gmail.com> (Jim Porter's message of "Mon, 2 May 2022 20:41:04 -0700")
Jim Porter <jporterbugs@gmail.com> writes:
Hi Jim,
> From "emacs -Q --eval '(eshell)'":
Unrelated to this bug, but convenient in general: The same can be done by
emacs -Q -f eshell
Best regards, Michael (always lazy).
prev parent reply other threads:[~2022-05-03 9:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 3:41 bug#55236: 29.0.50; Surprising behaviors with Eshell expansions Jim Porter
2022-05-03 3:45 ` bug#55236: [PATCH] " Jim Porter
2022-05-03 4:20 ` bug#55236: [PATCH v2] " Jim Porter
2022-05-03 16:24 ` bug#55236: " Lars Ingebrigtsen
2022-05-03 9:32 ` Michael Albinus [this message]
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=871qxbhsh4.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=55236@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
/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).