From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: emacs rendering comparisson between emacs23 and emacs26.3 Date: Fri, 27 Mar 2020 22:40:47 -0400 Message-ID: References: <86tv2h2vww.fsf@gmail.com> <20200322123818.GB32470@ACM> <87eetk5swm.fsf@gnu.org> <20200326193128.GC14092@ACM> <86d08y4zsx.fsf@gmail.com> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="58402"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, emacs-devel@gnu.org To: rrandresf@gmail.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Mar 28 03:43:17 2020 Return-path: Envelope-to: ged-emacs-devel@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 1jI1RM-000F5x-T4 for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Mar 2020 03:43:16 +0100 Original-Received: from localhost ([::1]:49458 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jI1RL-0005H3-UD for ged-emacs-devel@m.gmane-mx.org; Fri, 27 Mar 2020 22:43:15 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52278) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jI1P1-0003Km-13 for emacs-devel@gnu.org; Fri, 27 Mar 2020 22:40:52 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:55485) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jI1P0-0003yB-5l; Fri, 27 Mar 2020 22:40:50 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1jI1Ox-00043Q-IU; Fri, 27 Mar 2020 22:40:47 -0400 In-Reply-To: <86d08y4zsx.fsf@gmail.com> (rrandresf@gmail.com) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:245851 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] To tell the people with the strongest commitment to freedom to use an old version of Emacs is to choose failure. We need to re-optimize the Emacs master so it gives good performance on those machines. Suggesting that we disable certain features is ok. Perhaps there could be a command to select several of these modes together. > The only way at the moment (for CC Mode) is to change > font-lock-maximum-decoration from t to 2. That is ok as part of the solution. Regarding C++ indentation, I have two suggestions. * We could support a faster indentation mode for C code and for C++ files that use a limited repertoire of C++ constructs. * Maybe we can come up with additional tricks comparable to {-in-column-0 to optimize parsing. Emacs users would put these things into source files so as to get better peformance. > BTW. On my comparissons that variable was set no nil > as Doc says: > --8<---------------cut here---------------start------------->8--- > If nil, use the default decoration (typically the minimum available). > --8<---------------cut here---------------end--------------->8--- > Also xdisp.c. Just load c-mode not c++-mode What were the results of the comparisons you did with this setting? (I wasn't following this topic until yesterday.) > As Eli pointed out on another email on this same thread. It could be > BIDI. I would need to check on configure If it is possible to deactivate > BIDI support and see what difference it Does. Would you please try that? But don't limit yourself to existing configuration options -- try changing it at the C level if you can. If you find that this makes a big difference (a "bi di" ?), we can arrange to turn it on and off at run time. > With the help of Michael Albinus I have update the emacs23 builtin tramp > version to the latest one that supports GNU/Emacs23 The slash is not called for here. In "GNU Emacs", "GNU" acts as an adjectival modifying "Emacs", so it is correct to separate them with just a space. At least that is one problem that is easy to fix. (wellcome multihops and > adb). Has Tramp become a lot slower? Or is it only that the current Tramp doesn't work on Emacs 23? I think perhaps in the future I could upgrade org-mode to the last > version that supports GNU Emacs 23 (¿?). And I am going to stay with that setup on > low power machines. Has Org mode become a lot slower? Or is it only that the current Org mode doesn't work on Emacs 23? -- Dr Richard Stallman Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)