From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Larger GC thresholds for non-interactive Emacs Date: Thu, 23 Jun 2022 17:03:35 +0800 Message-ID: <87mte3ah08.fsf@localhost> References: <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> <83y1xneqif.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34628"; 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: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jun 23 11:11:41 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 1o4IsH-0008uf-Fi for ged-emacs-devel@m.gmane-mx.org; Thu, 23 Jun 2022 11:11:41 +0200 Original-Received: from localhost ([::1]:46078 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o4IsC-0008KI-N5 for ged-emacs-devel@m.gmane-mx.org; Thu, 23 Jun 2022 05:11:38 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39878) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o4IjR-000689-6f for emacs-devel@gnu.org; Thu, 23 Jun 2022 05:02:33 -0400 Original-Received: from mail-oa1-x35.google.com ([2001:4860:4864:20::35]:33556) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o4IjK-0000rB-PS; Thu, 23 Jun 2022 05:02:32 -0400 Original-Received: by mail-oa1-x35.google.com with SMTP id 586e51a60fabf-101d2e81bceso17020986fac.0; Thu, 23 Jun 2022 02:02:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version; bh=lfuF76RbCOf1oSxrgubGJ2aCJixaoBNHTFEEzA8Wejk=; b=NDDEYLYGzVbJ2iZEkuyPjzImXLQoc/v/hNsoSMpf2fmTqduXgT1VuLmrnrOYB5tCSr mms3yHJpnf5qfdxAxd7TggfXzu2jiCC80IyL5g+Xw3Nkn15XTOa0/5tIhQhRal4piq/L As3eCJ3uK9sPnsxU/9bGVCOp1Yh9kQLYo2n8M8iaryFa9LneTnIulQ8amH9zzIQ+xyzh ce0Adx6Z+U3tKPkWbgLq4VgXYenj/nophU6W64SWjvkbBxXSLAZcmNZlaFwbTd+TYR1D TBM7fl7PMQoCn6B5D6ZQ9PNZtu0UQiDZhUBEFk2lk8FLJwJHc/lZgbdQQTeJHl55hHH+ pQmg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=lfuF76RbCOf1oSxrgubGJ2aCJixaoBNHTFEEzA8Wejk=; b=B6VyQYI7ctbYVSSGrRS/Jbju2DXnDvsAZZS5c+nlWNO1BIq176dSzD304R+fEuHlbq 8SZ1/E7x2uRoxhIIUmLqEzzl0UOCVXmRp54xE6c2rKGUVgGXnUAq5Fo6SIU/Vi2Z3akG BoZFvJcOroqW43EhBYd1ug4N+yzozdyLNHTLYmfUfZNQxoOhsmJ3OUgTyR+wVCgsdpdv TLL54YTBqviObwJBGyWu2GxO8LH77w12b18/oMiyUVz/Wmw/QOuW+czRzc+lOHKA16pg fRVUvTpp38TctvT5Z32ETnWyivTo9T5OYzJlXpHG11P7ltmBcoOBt0FQgPXAXsXQZ5/K /f1g== X-Gm-Message-State: AJIora+tSlVwCFj4v7LfMs68Sl7yA/JCcub3qSbkAbO10L7WXURTkhgw GqfajwOKL6GAQYNyY/yW+vjmovfHxzrYLxso X-Google-Smtp-Source: AGRyM1tuA93j6KcBYbqo2hDqHVm4SC7yyLZtqaVApJh8sESMcnQUJbJdN5nu33U5C4vXTi71yXvWYQ== X-Received: by 2002:a05:6870:ad07:b0:106:919c:80e9 with SMTP id nt7-20020a056870ad0700b00106919c80e9mr1852490oab.67.1655974944585; Thu, 23 Jun 2022 02:02:24 -0700 (PDT) Original-Received: from localhost ([207.126.88.10]) by smtp.gmail.com with ESMTPSA id t21-20020a056808159500b003264a325ecdsm12380989oiw.5.2022.06.23.02.02.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 23 Jun 2022 02:02:23 -0700 (PDT) In-Reply-To: <83y1xneqif.fsf@gnu.org> Received-SPF: pass client-ip=2001:4860:4864:20::35; envelope-from=yantar92@gmail.com; helo=mail-oa1-x35.google.com 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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action 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:291531 Archived-At: Eli Zaretskii writes: >> 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. Are you referring to lists.gnu.org thread display interface? If it is as buggy as you are describing, why don't you file a bug report the relevant ML and get the problem fixed? There are alternatives. I personally prefer to search using local maildir copy via notmuch. I believe that gnus should also be able to search across the maildir. Also, there is https://yhetil.org/ with somewhat better search and display interface (IMHO). See https://yhetil.org/emacs-devel/_/text/help/ > 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). When I was saying "links back to the new commit", I was referring to the unique commit number. Searching exact match will not give false positives then. Best, Ihor