From: "Rainer J.H. Brandt" <rjhb@bb-c.de>
To: Emanuel Berg <incal@dataswamp.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: eshell bug? extra TAB after prompt
Date: Tue, 22 Aug 2023 19:51:41 +0200 (CEST) [thread overview]
Message-ID: <25828.62893.309601.468316@mail.bb-c.de> (raw)
In-Reply-To: <878ra6d4lp.fsf@dataswamp.org>
Emanuel Berg writes:
> > BTW: Is this the right place for questions about eshell?
>
> Absolutely, but you are not getting any replies :)
I might count your comment as a reply. But seriously, I'm surprised that
nobody except you cared to comment. That probably means that I have to go
straight to bug-gnu-emacs after verifying that the problem still occurs
with the latest release. I'd like to fix it, but expect that I'd need much
time, since my Elisp experience is rather limited.
Regards, Rainer
next prev parent reply other threads:[~2023-08-22 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 11:48 eshell bug? extra TAB after prompt Rainer J.H. Brandt
2023-08-19 22:55 ` Emanuel Berg
2023-08-22 17:51 ` Rainer J.H. Brandt [this message]
2023-08-22 18:10 ` Yuri Khan
2023-08-22 18:14 ` Yuri Khan
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=25828.62893.309601.468316@mail.bb-c.de \
--to=rjhb@bb-c.de \
--cc=help-gnu-emacs@gnu.org \
--cc=incal@dataswamp.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.
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).