From: Lars Ingebrigtsen <larsi@gnus.org>
To: kobarity <kobarity@gmail.com>
Cc: 58565@debbugs.gnu.org
Subject: bug#58565: 29.0.50; ERTs for Python completion are not properly located
Date: Sun, 16 Oct 2022 15:26:45 +0200 [thread overview]
Message-ID: <87r0z7j3vu.fsf@gnus.org> (raw)
In-Reply-To: <eke78rlf6hg3.wl-kobarity@gmail.com> (kobarity@gmail.com's message of "Sun, 16 Oct 2022 22:12:12 +0900")
kobarity <kobarity@gmail.com> writes:
> I'm afraid ERTs for Python completion in my patches #58389, #58441,
> #58562, and #58548 were not properly located/named. Some of them
> should be located in "Symbol completion" section, instead of "Shell
> completion" section. Could you apply the attached patch?
Pushed to Emacs 29 now.
prev parent reply other threads:[~2022-10-16 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 13:12 bug#58565: 29.0.50; ERTs for Python completion are not properly located kobarity
2022-10-16 13:26 ` 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=87r0z7j3vu.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=58565@debbugs.gnu.org \
--cc=kobarity@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).