From: Christophe Troestler <Christophe.Troestler@umons.ac.be>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24109@debbugs.gnu.org, djcb@djcbsoftware.nl
Subject: bug#24109: 24.5; Long lines in message mode make Emacs irresponsive
Date: Sat, 30 Jul 2016 13:38:53 +0100 [thread overview]
Message-ID: <87y44j8fmq.fsf@umons.ac.be> (raw)
In-Reply-To: <83y44jppsy.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 288 bytes --]
Eli Zaretskii writes:
>> https://github.com/djcb/mu/issues/880
>
> Thanks, but I don't think I understand what kind of display
> corruption did you see,
The corruption is not with the display but with the presentation of the headers (should be aligned left). See the attached image.
[-- Attachment #2: Emacs2.png --]
[-- Type: image/png, Size: 191959 bytes --]
[-- Attachment #3: Type: text/plain, Size: 555 bytes --]
> and I see nothing wrong in the backtrace posted there.
> So more details are required to understand what's going on here.
The problem is that, when moving the point to the headers view and, say,
pressing C-a, Emacs becomes *unresponsive*, even C-g does not work — I
have to kill it.
/CC Dirk-Jan C. Binnema, the author of mu4e, who may be able to give
more details.
> Also, would you mind trying the 25.1 release candidate, to see if the
> problem still exists there?
I compiled Emacs from the Git repository and the problem still exists.
next prev parent reply other threads:[~2016-07-30 12:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 11:36 bug#24109: 24.5; Long lines in message mode make Emacs irresponsive Christophe Troestler
2016-07-30 7:07 ` Eli Zaretskii
2016-07-30 12:38 ` Christophe Troestler [this message]
2016-07-30 14:52 ` Clément Pit--Claudel
2016-07-30 15:55 ` Eli Zaretskii
2016-07-30 17:01 ` martin rudalics
2016-07-30 17:13 ` Eli Zaretskii
2016-07-30 17:30 ` martin rudalics
2016-07-30 18:02 ` Eli Zaretskii
2016-07-30 18:30 ` John Mastro
2016-07-30 18:48 ` Eli Zaretskii
2016-07-30 19:22 ` Dirk-Jan C. Binnema
2016-08-30 12:38 ` Yuri D'Elia
2016-08-30 12:45 ` Yuri D'Elia
2016-08-30 15:29 ` Eli Zaretskii
2016-08-30 15:51 ` Yuri D'Elia
2016-08-30 16:25 ` Eli Zaretskii
2016-08-31 9:15 ` Yuri D'Elia
2016-08-31 14:37 ` Eli Zaretskii
2016-08-31 15:51 ` Yuri D'Elia
2016-08-31 16:12 ` Eli Zaretskii
2016-08-31 16:49 ` Yuri D'Elia
2016-09-01 2:35 ` Eli Zaretskii
2016-09-01 14:30 ` Eli Zaretskii
2016-09-01 14:39 ` Yuri D'Elia
2016-09-01 14:48 ` Yuri D'Elia
2016-09-01 15:18 ` Eli Zaretskii
2016-09-01 15:37 ` Yuri D'Elia
2016-09-01 16:00 ` Eli Zaretskii
2016-09-03 13:25 ` Eli Zaretskii
[not found] ` <28e7ddc58bcfeec0@fake-msgid>
2016-10-01 17:10 ` Yuri D'Elia
2016-10-01 17:47 ` Eli Zaretskii
2016-10-01 18:25 ` Yuri D'Elia
2016-10-02 7:09 ` Eli Zaretskii
2016-10-04 7:16 ` Yuri D'Elia
2016-10-04 7:56 ` Eli Zaretskii
2016-10-08 7:55 ` Eli Zaretskii
2016-10-08 15:27 ` Yuri D'Elia
2016-10-08 15:38 ` Eli Zaretskii
2016-10-08 15:42 ` Yuri D'Elia
2016-10-09 19:21 ` Christophe Troestler
2016-10-10 6:08 ` Eli Zaretskii
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=87y44j8fmq.fsf@umons.ac.be \
--to=christophe.troestler@umons.ac.be \
--cc=24109@debbugs.gnu.org \
--cc=djcb@djcbsoftware.nl \
--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).