From: Patrick Brennan via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 62507@debbugs.gnu.org
Subject: bug#62507: 28.2; Crash when editing TODO line with malformed tag
Date: Thu, 30 Mar 2023 08:22:14 -0700 [thread overview]
Message-ID: <CADN4T5LfFhi9yq7qa9vfMeKer3Od11rSBi7NfpBrEn-yLE9wMw@mail.gmail.com> (raw)
In-Reply-To: <e246266e9f3cd4b5b713@heytings.org>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
Sure thing.
On Thu, Mar 30, 2023 at 8:21 AM Gregory Heytings <gregory@heytings.org>
wrote:
>
> >
> > I can't reproduce the bug using that same recipe either. So now I think
> > I may have made a mistake in exactly how the recipe is to be followed.
> > However, I am fairly sure that there is some way to make emax crash
> > using malformed tags using approximately the same procedure. As far as I
> > know, emax at Google is stock.
> >
>
> Thanks. Can we close this bug? If you find a better recipe, you can
> always file another bug report.
>
>
[-- Attachment #2: Type: text/html, Size: 907 bytes --]
next prev parent reply other threads:[~2023-03-30 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 17:54 bug#62507: 28.2; Crash when editing TODO line with malformed tag Patrick Brennan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-29 10:57 ` Eli Zaretskii
2023-03-29 12:28 ` Gregory Heytings
2023-03-29 16:11 ` Patrick Brennan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-29 16:12 ` Patrick Brennan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-30 15:21 ` Gregory Heytings
2023-03-30 15:22 ` Patrick Brennan via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-03-30 15:23 ` Gregory Heytings
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADN4T5LfFhi9yq7qa9vfMeKer3Od11rSBi7NfpBrEn-yLE9wMw@mail.gmail.com \
--to=bug-gnu-emacs@gnu.org \
--cc=62507@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=patrickbrennan@google.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.