From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Mark Diekhans Newsgroups: gmane.emacs.bugs Subject: bug#13675: Extremely slow redisplay when lines are very long Date: Fri, 20 Oct 2017 08:50:19 -0700 Message-ID: <23018.6971.899464.78569@kestrel.local> References: <83sj545e55.fsf@gnu.org> <23017.21788.768005.940877@eduroam-169-233-201-230.ucsc.edu> <831slye2sx.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1508514682 432 195.159.176.226 (20 Oct 2017 15:51:22 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 20 Oct 2017 15:51:22 +0000 (UTC) Cc: 13675@debbugs.gnu.org Bcc: Mark Diekhans , To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Oct 20 17:51:17 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e5ZZh-0006nv-N4 for geb-bug-gnu-emacs@m.gmane.org; Fri, 20 Oct 2017 17:51:05 +0200 Original-Received: from localhost ([::1]:54590 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e5ZZo-0006et-G5 for geb-bug-gnu-emacs@m.gmane.org; Fri, 20 Oct 2017 11:51:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42627) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e5ZZi-0006em-GK for bug-gnu-emacs@gnu.org; Fri, 20 Oct 2017 11:51:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e5ZZe-0000Eg-K4 for bug-gnu-emacs@gnu.org; Fri, 20 Oct 2017 11:51:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:43864) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e5ZZe-0000Ec-Fe for bug-gnu-emacs@gnu.org; Fri, 20 Oct 2017 11:51:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e5ZZd-0007kk-RY for bug-gnu-emacs@gnu.org; Fri, 20 Oct 2017 11:51:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Mark Diekhans Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 20 Oct 2017 15:51:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 13675 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 13675-submit@debbugs.gnu.org id=B13675.150851463229762 (code B ref 13675); Fri, 20 Oct 2017 15:51:01 +0000 Original-Received: (at 13675) by debbugs.gnu.org; 20 Oct 2017 15:50:32 +0000 Original-Received: from localhost ([127.0.0.1]:52545 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e5ZZA-0007jy-Ed for submit@debbugs.gnu.org; Fri, 20 Oct 2017 11:50:32 -0400 Original-Received: from mail-pf0-f175.google.com ([209.85.192.175]:51880) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e5ZZ8-0007ji-Jm for 13675@debbugs.gnu.org; Fri, 20 Oct 2017 11:50:31 -0400 Original-Received: by mail-pf0-f175.google.com with SMTP id n14so11611739pfh.8 for <13675@debbugs.gnu.org>; Fri, 20 Oct 2017 08:50:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=soe-ucsc-edu.20150623.gappssmtp.com; s=20150623; h=mime-version:content-transfer-encoding:message-id:date:to:cc :subject:in-reply-to:references:from; bh=+QRmbp6j8djtkIYwkkDinYs0fMbwOsnAlu/Qo4ZdH2E=; b=nmcb70LIv9AHrw+38kbdTFrWU+BeG5h43HhcpCSZMOgYuJGg0aRm8vWJ/t6UKpbsRJ P0LwO1IOKymKNAIsVO/D4nT9ruYlPwRKLPDQAc0DKWHaarK+4vOrrkegXFTqGsZ3yfCq 8oQTv5pDOnUA0+b7cKXXLIEFGh/yzFdwOI5fCT5WYtI5rn0s7Vs3yTu5w4+kfkmqc/T3 3EgvjG4s+QC4403MZxPU9pRgbKSEIctd1vwKn0b9yg4+FLcUevxJPBgfjGnCKqZwy7t2 18tfVGvHqSW/63RKV+w0Y06Dcsst5bYZJ9ldiMfnPFo2C/5nja+L/clbe/gCCCB7QzeR Kahg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:content-transfer-encoding :message-id:date:to:cc:subject:in-reply-to:references:from; bh=+QRmbp6j8djtkIYwkkDinYs0fMbwOsnAlu/Qo4ZdH2E=; b=BnC1eyFatnsocGdEwKzg3/muK/0kcWlAhAMgAiwvcB5fEVnx4NLkKVcvbvic65J/94 hAISzocOQ75SL7bZclLLrgq8OxuAJyWHZa2SM3RBtu8YiY74hgmYvueMjK6kHA7Cht9c huWUlQnjwaNx70uhuTs9V0Fj9xLfDervN9zp4ekZjLlpllA97ZHTOB4mbs+Wk72Bx3mp kyFFp4cYgubI/5g/zKJXbap+iOd+r69Y+fuYelMKESt9S/lAjjBoxr/JNfcJLg7jjNMM P/yBUqvurwM2iBjfB1tSu+4BXFYxYAuYEexM+vtanpEZQibtEFgb5ACYggxY9Ms6YLkN 2FVg== X-Gm-Message-State: AMCzsaX5pM44V+JBDEKYte+2qU3Hnyflcjpv0bJ++JBn8I+yhObq9KU8 6vL3jCdhed6Hjq/EBNdo66UXAQ== X-Google-Smtp-Source: ABhQp+R2SGbkdyw4azK8kdvR55MfSZ6em9MWFclYMsfWplkZaml3xPx25RQ/zkn/TNyFWDXswWxvXQ== X-Received: by 10.84.128.97 with SMTP id 88mr703038pla.161.1508514624442; Fri, 20 Oct 2017 08:50:24 -0700 (PDT) Original-Received: from localhost ([2601:647:c803:2f30:420:ec7a:c1cb:371f]) by smtp.gmail.com with ESMTPSA id l1sm2220379pff.77.2017.10.20.08.50.20 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 20 Oct 2017 08:50:22 -0700 (PDT) In-Reply-To: <831slye2sx.fsf@gnu.org> X-Mailer: VM 8.2.0b under 25.2.1 (x86_64-apple-darwin16.4.0) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:138771 Archived-At: Hi Eli, The issue really isn't needed to edit these kind of files, so much as not locking up emacs when one doesn't know a file has really long lines. In the past week, it's been an sql file that had long insert commands and a large json file create without line breaks. Both of these modes have font lock mode by default. 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. Mark Eli Zaretskii writes: > > From: Mark Diekhans > > Date: Thu, 19 Oct 2017 18:45:00 -0700 > > > > Is there anyone working on the long-line display speed issue? > > Not that I know of. I don't even have an idea for how to speed it up, > and I don't think anyone's come up with such ideas. > > > It is especially bad with font lock mode. > > What mode/kind of file needs font lock and has such long lines? > > In general, if you must handle such files, my advice is to use M-x > find-file-literally for them, it might make Emacs just barely > bearable, if you are lucky. But then you lose any font locking and > text encoding support, so this is only feasible for plain-ASCII files > that basically present some text. > > > If the fix is really complex, it would be much better emacs > > refuse to display the file than force killing it. > > Patches for presenting a warning for such files, like we do with very > large files, are welcome.