From: Eli Zaretskii <eliz@gnu.org>
To: Mark Diekhans <markd@soe.ucsc.edu>
Cc: 13675@debbugs.gnu.org
Subject: bug#13675: Extremely slow redisplay when lines are very long
Date: Fri, 20 Oct 2017 19:10:32 +0300 [thread overview]
Message-ID: <83bml1dclj.fsf@gnu.org> (raw)
In-Reply-To: <23018.6971.899464.78569@kestrel.local> (message from Mark Diekhans on Fri, 20 Oct 2017 08:50:19 -0700)
> Date: Fri, 20 Oct 2017 08:50:19 -0700
> Cc: 13675@debbugs.gnu.org
> From: Mark Diekhans <markd@soe.ucsc.edu>
>
> I would be gladly work on a patch to ask a question or stop on
> files that might cripple emacs.
>
> However, before one dives into work, it's important to know the
> history and if there is existing work one can help with as opposed
> to start fresh. That leads to annoying questions like mine.
>
> The meta issue is not a user wanting something for nothing.
> It's that it's a lot of work for someone who is not a core
> developer to come up to speed on an issue since the discussions
> are not linked to bug reports and the mailing lists are very
> hard to search.
I don't think you have anything to fear, because AFAIR this particular
approach was never suggested or discussed.
So I'd start with a feature that read the first N bytes from the file,
and if no newlines were found in those N bytes, pop up the warning and
the question. A good place for this would be inside
insert-file-contents, which is where Emacs reads files into memory.
Let me know if I can help you further with making this happen.
Thanks.
prev parent reply other threads:[~2017-10-20 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 16:26 bug#13675: 24.2.93; Extremely slow redisplay when lines are very long Eli Zaretskii
2013-02-10 17:36 ` Eli Zaretskii
2017-10-20 1:45 ` bug#13675: " Mark Diekhans
2017-10-20 6:44 ` Eli Zaretskii
2017-10-20 11:57 ` Phil Sainty
2017-10-21 2:03 ` Phil Sainty
2017-10-20 15:50 ` Mark Diekhans
2017-10-20 16:10 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83bml1dclj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13675@debbugs.gnu.org \
--cc=markd@soe.ucsc.edu \
/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.