From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: ndame Newsgroups: gmane.emacs.help Subject: Re: Why doesn't emacs yield more? Date: Thu, 29 Aug 2019 17:39:20 +0200 (CEST) Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="113223"; mail-complaints-to="usenet@blaine.gmane.org" To: "help-gnu-emacs@gnu.org" Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Aug 29 17:39:41 2019 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1i3MWS-000TKb-A6 for geh-help-gnu-emacs@m.gmane.org; Thu, 29 Aug 2019 17:39:40 +0200 Original-Received: from localhost ([::1]:51244 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i3MWQ-00023q-Ur for geh-help-gnu-emacs@m.gmane.org; Thu, 29 Aug 2019 11:39:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57662) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i3MWD-00023X-9a for help-gnu-emacs@gnu.org; Thu, 29 Aug 2019 11:39:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i3MWC-0006eT-20 for help-gnu-emacs@gnu.org; Thu, 29 Aug 2019 11:39:25 -0400 Original-Received: from fmfe30.onbox.hu ([46.107.16.235]:35954 helo=web-out.onbox.hu) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1i3MWB-0006cc-CD for help-gnu-emacs@gnu.org; Thu, 29 Aug 2019 11:39:23 -0400 X-fm-smtp-source: yes Original-Received: from localhost (localhost [85.238.93.204]) by web-out.onbox.hu (Postfix) with SMTP id 46K6Gw3wbYzgjX for ; Thu, 29 Aug 2019 17:39:20 +0200 (CEST) X-AccountId: 57978162 X-Originating-Ip: 85.238.93.204 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduvddrudeivddgkeejucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpucfhtffggffotefknfenuceurghilhhouhhtmecufedttdenucenucfjughrpefhkffugggtvfhiffesrgdtregstddtudenucfhrhhomhepnhgurghmvgcuoegvmhgrtghsuhhsvghrsehfrhgvvghmrghilhdrhhhuqeenucfkphepkeehrddvfeekrdelfedrvddtgeenucfrrghrrghmpehhvghloheppdhinhgvthepkeehrddvfeekrdelfedrvddtgedpmhgrihhlfhhrohhmpegvmhgrtghsuhhsvghrsehfrhgvvghmrghilhdrhhhupdhrtghpthhtohephhgvlhhpqdhgnhhuqdgvmhgrtghssehgnhhurdhorhhgnecuvehluhhsthgvrhfuihiivgeptd DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=simple/relaxed; t=1567093160; s=20181004; d=freemail.hu; h=From:Message-ID:Subject:MIME-Version:Content-Type:To:Date; l=3264; bh=+qgn9mCXxcR4U8iGbzur3dht9IZ08zYDNHzJjP9YeZU=; b=hT68ggSnaGqvCAP+/yE41Jhc4inDYVLwRAFHmm1S3dZLKmfzyWu3Ec+RttwZRRee +a4DVJMEyR0v8pXVfQkD/Mr3dYZSLcwH6vCUI+e9pDwrFyovzehbmw5xedY3y0ZT7+N oJZm5EigCLOAMjT2m8fYyzJWEl5gq5GAH2kiVWhGEbFclWLO2r+lnXev6dK4WwiKe1u rNrpTmcSUnC648cinqaU6D+9fkk6BYIFa3stKCAOWct+Ja6QiO6Y9jZob8Tx6mQBLB5 26meCgyDWAfMXN+7Yypu3GXquNwQX/qjDXQ5iw9dDVVvnRp3GFZcXYHMMKPqJbziv3A LXneK5S7EA== X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x [fuzzy] X-Received-From: 46.107.16.235 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:121396 Archived-At: >=C2=A0 > Assuming it was redisplay that took most of the time: you cannot > interrupt it, not by default. =C2=A0What would be the purpose of that? > Emacs cannot allow the display to be left in a state that is > inconsistent with the contents of the buffer, so it will immediately > reenter another redisplay cycle. If I e.g. do a C-y and consquently emacs starts a long operation then if I interrupt then emacs could simply restore the buffer/display state from before the C-y state. I didn't see my C-y operation finish because of the redisplay, so I wouldn't mind if a C-g would cancel that too. I don't know if a snapshot can be made of the current buffer/display state, but if emacs can do that then it could simply restore the previous snapshot instantly, so there would be no issue of inconsistent buffer/display after interrupting. > What you can do is type M-< to go to the beginning of the buffer. =C2=A0I= f > the problematic portion of the buffer will then be off-screen, you > should be able to stop waiting. Interesting. I'll try it next time. > >=C2=A0 > > Would it be a big performance hit? I don't know if the check > > could be inlined somehow. Was something like this discussed > > before? >=C2=A0 > We already do all that when running Lisp code. Thanks. I didn't know that.