From: Stephen Berman <stephen.berman@gmx.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63811-done@debbugs.gnu.org
Subject: bug#63811: 29.0.91; todo-mode item editing bugs
Date: Wed, 31 May 2023 16:25:14 +0200 [thread overview]
Message-ID: <87v8g88to5.fsf@gmx.net> (raw)
In-Reply-To: <83fs7cfzsk.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 31 May 2023 15:31:07 +0300")
On Wed, 31 May 2023 15:31:07 +0300 Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Stephen Berman <stephen.berman@gmx.net>
>> Date: Wed, 31 May 2023 11:12:32 +0200
>>
>> I have encountered several bugs in todo-mode when creating and editing
>> todo items. I have fixes for them and since I'm the todo-mode
>> maintainer I intend to push them to the Savannah repo when I get a bug
>> number and clearance for which branch to push to. The bugs are
>> long-standing, at least since Emacs 28 and probably earlier. The fixes
>> touch no code outside of todo-mode.el and seem low-risk; in my testing
>> they work as expected. I've attached a diff against emacs-29 below (the
>> todo-mode.el files in current emacs-29 and master are identical).
>
> Assuming all the tests still pass after these changes, please go ahead
> and install on emacs-29, and thanks.
All todo-mode tests passed `make check'. I did get some unexpected
failures in a few other tests and a hang in epg-tests, but the same
thing happened when I ran `make check' on my master branch, which does
not have the todo-mode changes, so these are not responsible for the
test problems, and I went ahead and pushed the changes to emacs-29 and
am closing the bug report. Thanks.
Steve Berman
prev parent reply other threads:[~2023-05-31 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 9:12 bug#63811: 29.0.91; todo-mode item editing bugs Stephen Berman
2023-05-31 12:31 ` Eli Zaretskii
2023-05-31 14:25 ` Stephen Berman [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=87v8g88to5.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=63811-done@debbugs.gnu.org \
--cc=eliz@gnu.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.
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).