From: Katsumi Yamaoka <yamaoka@jpl.org>
To: 45944@debbugs.gnu.org
Subject: bug#45944: 28.0.50; Mailabbrev sometimes hangs
Date: Tue, 19 Jan 2021 08:39:00 +0900 [thread overview]
Message-ID: <b4mlfcpzugb.fsf@jpl.org> (raw)
In-Reply-To: <b4m35yznlzc.fsf@jpl.org>
On Mon, 18 Jan 2021 09:10:31 +0900, Katsumi Yamaoka wrote:
> When expanding a mail abbrev in the message header of a message-
> mode buffer, it sometime hangs like it goes into an infinite loop.
[...]
> Though I haven't found out the cause of the problem so far,...
I found it. `(forward-word 1)' in the `abbrev--before-point'
function takes a very long time for a certain mail body contents
(`hang' I wrote first was my misregarding).
Here is a recipe to reproduce the problem in `emacs -Q':
1. Create the ~/.mailrc file, if it is absent.
The file needs to contain at least a line like this:
--8<---------------cut here---------------start------------->8---
foo foo@example.com.invalid
--8<---------------cut here---------------end--------------->8---
2. Eval this form in the *scratch* buffer.
--8<---------------cut here---------------start------------->8---
(with-current-buffer (get-buffer-create "*testing*")
(erase-buffer)
(insert "To: \n--text follows this line--\n\
________________________________________________________________\n")
(message-mode)
(mail-abbrevs-setup)
(goto-char (point-min))
(end-of-line)
(pop-to-buffer (current-buffer)))
--8<---------------cut here---------------end--------------->8---
3. In To: header, enter "foo" or something another and type ",".
As far as I can observe, the more "____" line is long, the more
it takes a long time.
Thanks.
next prev parent reply other threads:[~2021-01-18 23:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 0:10 bug#45944: 28.0.50; Mailabbrev sometimes hangs Katsumi Yamaoka
2021-01-18 23:39 ` Katsumi Yamaoka [this message]
2021-01-19 4:47 ` Lars Ingebrigtsen
2021-01-19 8:30 ` Andreas Schwab
2021-01-19 11:07 ` Katsumi Yamaoka
2021-01-19 15:09 ` Lars Ingebrigtsen
2021-01-19 21:50 ` Katsumi Yamaoka
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=b4mlfcpzugb.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=45944@debbugs.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 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.