From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 22143@debbugs.gnu.org, gavenkoa@gmail.com
Subject: bug#22143: 24.5; Emacs blocked on long lines.
Date: Thu, 05 Apr 2018 18:00:12 +0300 [thread overview]
Message-ID: <83y3i11ywz.fsf@gnu.org> (raw)
In-Reply-To: <87muyh4swq.fsf@web.de> (message from Michael Heerdegen on Thu, 05 Apr 2018 16:41:41 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Thu, 05 Apr 2018 16:41:41 +0200
> Cc: 22143@debbugs.gnu.org
>
> (First, I don't think this is wishlist. Isn't it a bug when an editor
> can't open a file or freezes when doing so?)
This bug was marked wishlist because it asks for a new feature: a
warning about long lines when visiting a file.
The bug report about slow redisplay in this case and in similar cases
is bug#13675, and it is not marked wishlist.
> If we can't solve the issue with long lines in the display code, maybe
> we should do something like this by default?
Practical and detailed proposals, let alone patches, in that direction
will be most welcome.
But please don't forget that long lines could materialize not just
when a file is first visited, but also as result of its editing, or
more generally when some text is generated by editing, even if the
buffer doesn't visit any file. Bonus points for displaying such
warnings in those cases as well.
TIA
next prev parent reply other threads:[~2018-04-05 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 15:54 bug#22143: 24.5; Emacs blocked on long lines Oleksandr Gavenko
2018-04-05 14:41 ` Michael Heerdegen
2018-04-05 15:00 ` Eli Zaretskii [this message]
2018-04-05 15:20 ` Michael Heerdegen
2018-04-05 15:34 ` Eli Zaretskii
2020-08-21 13:53 ` Stefan Kangas
2020-08-21 14:01 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y3i11ywz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22143@debbugs.gnu.org \
--cc=gavenkoa@gmail.com \
--cc=michael_heerdegen@web.de \
/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.