From: Lars Ingebrigtsen <larsi@gnus.org>
To: miha@kamnitnik.top
Cc: awrhygty@outlook.com, 53219@debbugs.gnu.org
Subject: bug#53219: 27.2; shell-mode output is stolen by python-eldoc
Date: Fri, 14 Jan 2022 08:34:11 +0100 [thread overview]
Message-ID: <87y23iu5xo.fsf@gnus.org> (raw)
In-Reply-To: <87a6fzmts0.fsf@miha-pc> (miha@kamnitnik.top's message of "Thu, 13 Jan 2022 18:26:23 +0100")
miha@kamnitnik.top writes:
> Please consider applying the following patch to fix this.
Thanks; applied to Emacs 29.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-01-14 7:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 17:54 bug#53219: 27.2; shell-mode output is stolen by python-eldoc awrhygty
2022-01-13 6:13 ` Lars Ingebrigtsen
2022-01-13 17:26 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-14 7:34 ` Lars Ingebrigtsen [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=87y23iu5xo.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=53219@debbugs.gnu.org \
--cc=awrhygty@outlook.com \
--cc=miha@kamnitnik.top \
/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).