From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Larger GC thresholds for non-interactive Emacs Date: Thu, 23 Jun 2022 11:24:40 +0300 Message-ID: <83y1xneqif.fsf@gnu.org> References: <83bkutqb3z.fsf@gnu.org> <9778F176-E724-4E61-B0FB-327BCDD316C0@acm.org> <87sfo4epeo.fsf@localhost> <87bkurrc5e.fsf@localhost> <87bkur72b7.fsf@gnus.org> <874k0j40e7.fsf@gnus.org> <871qvm16he.fsf@gnus.org> <83a6aanm5j.fsf@gnu.org> <87o7yozzj0.fsf@gnus.org> <83k098kg6c.fsf@gnu.org> <8335fvg8kz.fsf@gnu.org> <87pmizrgoi.fsf@localhost> <83zgi3espf.fsf@gnu.org> <87pmizajtv.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7469"; mail-complaints-to="usenet@ciao.gmane.io" Cc: owinebar@gmail.com, larsi@gnus.org, monnier@iro.umontreal.ca, mattiase@acm.org, theophilusx@gmail.com, rms@gnu.org, acm@muc.de, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jun 23 10:26:26 2022 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 1o4IAU-0001lk-7r for ged-emacs-devel@m.gmane-mx.org; Thu, 23 Jun 2022 10:26:26 +0200 Original-Received: from localhost ([::1]:51366 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o4IAT-0005vP-8l for ged-emacs-devel@m.gmane-mx.org; Thu, 23 Jun 2022 04:26:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33076) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o4I91-0004op-CO for emacs-devel@gnu.org; Thu, 23 Jun 2022 04:24:55 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:38664) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o4I90-0003dI-6c; Thu, 23 Jun 2022 04:24:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=vKIaOVJ6NSV1zvta6YCSnZg0yDlZNCrLEpe/3wr/VnI=; b=HOtnFZxFVI3H hyO7Ck4gtDjg3uZFTp5Qsjh/N42ERT+Y2CA1k+s8h4tbyGCSEu+6civ4Z0o6dyzpIElgeScANbRLS NgoxaJYC4LnBtIGw9YoJ7IkRFbUCY0pLUf1FSjJTln8d1TszpSvWcMt28RKAdkwricjljv61ZUUZO L0UH+HtIIryWtHxDoP3vAnaxN9Tu1dqpxVha2nBamSLOUuJhAlyoVNNV0+XXaZkV+VBVP/aPj8ADm 3L55xNsH5by8vfcwXETPSdS2v2PG9ys6OlMtloiTOdxLUOqcYHVeFBx73meLsJMVhS5p5DDauxGQd z3ztunsIqEYtjPRaQX6qJw==; Original-Received: from [87.69.77.57] (port=2688 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o4I8w-0002Qv-IO; Thu, 23 Jun 2022 04:24:50 -0400 In-Reply-To: <87pmizajtv.fsf@localhost> (message from Ihor Radchenko on Thu, 23 Jun 2022 16:02:36 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:291530 Archived-At: > From: Ihor Radchenko > Cc: owinebar@gmail.com, larsi@gnus.org, monnier@iro.umontreal.ca, > mattiase@acm.org, theophilusx@gmail.com, rms@gnu.org, acm@muc.de, > emacs-devel@gnu.org > Date: Thu, 23 Jun 2022 16:02:36 +0800 > > > And that won't help with past discussions whose commits are in the > > tree for many years. > > Can't the past discussions be directly updated by sending an extra email > that links back to the new commit? You mean, rely on search engines to find an addition to a discussion made many years later? My experience with searching the archives is that it many times fails when the discussion crosses the year mark. For starters, display of the archives by thread doesn't work in that case as expected: you are given the illusion that the thread ends. Searching the archives also has the disadvantage that in many cases it's hard to know what are the keywords that would find the discussion efficiently (i.e. without drowning it in thousands of irrelevant messages). Otherwise, I don't see how sending a message to a thread long dead would help in this matter. Am I missing something? > > But yes, using such links is definitely helpful, and I'd encourage > > people to use that more. (That's one reason why changes should > > preferably be discussed on the bug tracker: the bug number -- if not > > forgotten to be mentioned in the log message -- serves as a pointer to > > the discussions.) > > What about the message ID? It should also be unique enough to link to > the relevant ML thread. (it is a bit annoying that lists.gnu.org does > not support easy search via link id, unlike e.g. > https://yhetil.org/emacs-devel/87r13n5muk.fsf@gnus.org/). That's okay, but is it really better than a URL of a message in the archives? It isn't much shorter. The basic problem is to remember to mention a discussion, in any form. Even just a date and the name of the forum are usually enough to quickly find the relevant thread.