From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Peter Newsgroups: gmane.emacs.help Subject: Re: The Menu is slow, how to find out why? Date: Tue, 24 Oct 2023 22:23:10 +0200 Message-ID: References: <875y33bqhq.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34234"; mail-complaints-to="usenet@ciao.gmane.io" Cc: help-gnu-emacs@gnu.org To: tpeplt Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Tue Oct 24 22:28:33 2023 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qvO0v-0008hK-Bd for geh-help-gnu-emacs@m.gmane-mx.org; Tue, 24 Oct 2023 22:28:33 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qvO0M-0001aM-5a; Tue, 24 Oct 2023 16:27:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qvO0I-0001Zn-Ki for help-gnu-emacs@gnu.org; Tue, 24 Oct 2023 16:27:55 -0400 Original-Received: from uucp.dinoex.org ([2a0b:f840::12]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qvO0E-0005S8-C2 for help-gnu-emacs@gnu.org; Tue, 24 Oct 2023 16:27:54 -0400 Original-Received: from uucp.dinoex.org (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]) by uucp.dinoex.org (8.17.2/8.17.2) with ESMTPS id 39OKR6cS060272 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 24 Oct 2023 22:27:06 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Original-Received: (from uucp@localhost) by uucp.dinoex.org (8.17.2/8.17.2/Submit) with UUCP id 39OKR6oG060269; Tue, 24 Oct 2023 22:27:06 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Original-Received: from disp.intra.daemon.contact (disp-e.intra.daemon.contact [IPv6:fd00:0:0:0:0:0:0:112]) by admn.intra.daemon.contact (8.17.1/8.17.1) with ESMTPS id 39OKO1FU085915 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=OK); Tue, 24 Oct 2023 22:24:01 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Original-Received: from disp.intra.daemon.contact (localhost [127.0.0.1]) by disp.intra.daemon.contact (8.17.1/8.17.1) with ESMTPS id 39OKNATR039487 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Tue, 24 Oct 2023 22:23:11 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Original-Received: (from pmc@localhost) by disp.intra.daemon.contact (8.17.1/8.17.1/Submit) id 39OKNA7Q039486; Tue, 24 Oct 2023 22:23:10 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) X-Authentication-Warning: disp.intra.daemon.contact: pmc set sender to pmc@citylink.dinoex.sub.org using -f Content-Disposition: inline In-Reply-To: <875y33bqhq.fsf@gmail.com> X-Milter: Spamilter (Reciever: uucp.dinoex.org; Sender-ip: 0:0:2a0b:f840::; Sender-helo: uucp.dinoex.org; ) X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (uucp.dinoex.org [IPv6:2a0b:f840:0:0:0:0:0:12]); Tue, 24 Oct 2023 22:27:09 +0200 (CEST) Received-SPF: pass client-ip=2a0b:f840::12; envelope-from=pmc@citylink.dinoex.sub.org; helo=uucp.dinoex.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:145379 Archived-At: On Wed, Oct 18, 2023 at 04:54:57PM -0400, tpeplt wrote: ! Peter writes: !=20 ! > Hi folks, ! > ! > I have a strange problem: the menu takes 1-2 seconds to open. ! > ! > I have read that one shouldn't use the menu, and I might agree, ! > but: my personal keybindungs have come a long way, and they are !=20 ! 1. One source of slow-down with Emacs is the toolbar and tool-tips. ! If you have these turned on, then turning them off might resolve ! your problem. (These are likely caused by slowness of the windowing ! system.) Thank You, these are good advice. But in this case the slowdown happens BEFORE the communication with X11 even starts. And in the end the solution was simple: I just needed to remove a line from keyboard.c that on my machine causes a pathologic loop. ! 2. A better rule than "Don=E2=80=99t use the menu" is "Use the menu when = you ! are using a mode that you don=E2=80=99t use often or don=E2=80=99t use fo= r long". ! In those cases, you won=E2=80=99t have learned the mode-specific keybindi= ngs ! and commands. That makes sense. When doing some continuous work during the last days, I found myself using only the Buffers menu. But that one is indeed useful: why should I bother myself with remembering the names of files I work on? Or why should I bother with an extra window for the buffer list when one is already present in the menu? Now I finally achieved something I probably should have tackled 30 years ago, and switched all systems-management to emacs. Lets see how it works. Currently it looks good, it can even display proper Devanagari when run via X11 (which firefox can't). Obviousely I can't read that, but it looks nice. ;) ! 3. If you do not use the toolbar or tool-tips, then to troubleshoot ! your problem, try to reproduce is by starting Emacs without any ! configuration customization (start with "emacs -Q") and see if the That was the first I did - I simply deleted the files to make sure. "emacs -Q" would also have worked? Cool, that will make things easier in the future. :) ! problem persists. If it does not persist, then start adding ! pieces of your customizations to the initialization file to see ! if you can isolate the source of the problem, which you can then ! ask about here on this mailing list. Yepp.