GNU bug report logs - #13675
24.2.93; Extremely slow redisplay when lines are very long

Previous Next

Full log

Message #35 received at 13675 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Mark Diekhans <markd <at> soe.ucsc.edu>
Cc: 13675 <at> debbugs.gnu.org
Subject: Re: bug#13675: Extremely slow redisplay when lines are very long
Date: Fri, 20 Oct 2017 19:10:32 +0300

> Date: Fri, 20 Oct 2017 08:50:19 -0700
> Cc: 13675 <at> debbugs.gnu.org
> From: Mark Diekhans <markd <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.