From unknown Thu Jun 19 14:08:35 2025 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailer: MIME-tools 5.509 (Entity 5.509) Content-Type: text/plain; charset=utf-8 From: bug#66285 <66285@debbugs.gnu.org> To: bug#66285 <66285@debbugs.gnu.org> Subject: Status: suggestion: change definition of hycontrol--blank-buffer to something more meaningful Reply-To: bug#66285 <66285@debbugs.gnu.org> Date: Thu, 19 Jun 2025 21:08:35 +0000 retitle 66285 suggestion: change definition of hycontrol--blank-buffer to s= omething more meaningful reassign 66285 hyperbole submitter 66285 Dan Drake severity 66285 normal thanks From debbugs-submit-bounces@debbugs.gnu.org Sat Sep 30 18:22:37 2023 Received: (at submit) by debbugs.gnu.org; 30 Sep 2023 22:22:37 +0000 Received: from localhost ([127.0.0.1]:59884 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qmiM7-0004bI-JK for submit@debbugs.gnu.org; Sat, 30 Sep 2023 18:22:37 -0400 Received: from lists.gnu.org ([2001:470:142::17]:38992) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qmfxz-0000Ki-HD for submit@debbugs.gnu.org; Sat, 30 Sep 2023 15:49:35 -0400 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 1qmfxd-0004tW-Kk for bug-hyperbole@gnu.org; Sat, 30 Sep 2023 15:49:10 -0400 Received: from mail-ej1-x62e.google.com ([2a00:1450:4864:20::62e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qmfxb-00030z-DT for bug-hyperbole@gnu.org; Sat, 30 Sep 2023 15:49:09 -0400 Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-9b2cee55056so394855166b.3 for ; Sat, 30 Sep 2023 12:49:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696103344; x=1696708144; darn=gnu.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=017gUpEdLw0qmASfVSQaK58XXPxT67Pl4J3wIGEXFQI=; b=NaAEBA7MFigXi6j/GMr8vB2/yh8LSoA1H1HPOySrvajRJ1frgcTyKmQLLEsQSUq+d4 8u/o9hqN6rs5wyafNfxdAUzJ+Ep2lOzMbh8F93KQzAm39Rz+lNrE/n0Z4D3nXnpcmfBq 2qdGKzX/sqATGjStDhsfmo3NHOO/+qyNxwHs0R1bdrZwaU8W76ayuUKmQCpMbhiwNgj6 kinwVBGpjS5z8Sgksx73OGw0zH2DKrAErsQm5OXpGKL91enUh+Kq8s8OouQStsYKXAQi XSfxLb0jq1TFHxAFmDqX8Y2xLUgFN0V9udpZql/SxBqSqQJBPfYv8sTBS7fP8TjKHDJ3 9LOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696103344; x=1696708144; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=017gUpEdLw0qmASfVSQaK58XXPxT67Pl4J3wIGEXFQI=; b=C6Pk9huBf1E4wzlvDas5MV3tHSxI+sReidc0ArwK8riOA9Ktq1QhfcCl1PtzGDVD9R h23LOQ+5uvtaNjbSG/H54F0/U1EGt8AzSDxm5tQdVpce6R59CGrITtenypMU1qeCZy5V ucLa2P4h2CdamuhfcjOzUApjKWpZ55z3xoxK52p7PkIBXSYqHsAYoe47gHkKYopDdcp+ P813Qf6TwoChgL+efUHjurCsi6XheAfD//gXtjv4vPXXWYTRS4IhIu3OeSLRHacBxvSF 3U7v1AD96p5syUsqskfpuiZ4UE0xC+m14Cy8JzH7pH6ZNdDPVQ+OazTJOxJMPOXbhHGt vd/Q== X-Gm-Message-State: AOJu0YxQqSl5PISonWUOdGxf/N9ykFkxjorLyrSQZ9pBt7EWhCOfB3+i WP/ApknWMnsVfioRKg8WjMIVp8yropHzQdz3ja2jEZzD+zc= X-Google-Smtp-Source: AGHT+IGX7rUAK92eC/FP1lt8PaSSsFh0mKIw6k1wcWUeMphcquUOWSLbAJidJ5BRj2vwYwN6tHs0ytSQjzbS+cj3DHc= X-Received: by 2002:a17:906:2cf:b0:9b2:b2f8:85dd with SMTP id 15-20020a17090602cf00b009b2b2f885ddmr7193750ejk.34.1696103343754; Sat, 30 Sep 2023 12:49:03 -0700 (PDT) MIME-Version: 1.0 From: Dan Drake Date: Sat, 30 Sep 2023 14:48:52 -0500 Message-ID: Subject: suggestion: change definition of hycontrol--blank-buffer to something more meaningful To: bug-hyperbole@gnu.org Content-Type: multipart/alternative; boundary="0000000000004e90cd060698d555" Received-SPF: pass client-ip=2a00:1450:4864:20::62e; envelope-from=dan.drake@gmail.com; helo=mail-ej1-x62e.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Score: 1.0 (+) X-Debbugs-Envelope-To: submit X-Mailman-Approved-At: Sat, 30 Sep 2023 18:22:34 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -0.0 (/) --0000000000004e90cd060698d555 Content-Type: text/plain; charset="UTF-8" Hello, A while back I posted this emacs.stackexchange question, about a mysterious buffer named BLANK which always appeared when I started emacs: https://emacs.stackexchange.com/q/78601/19526 Today I figured out the source: see my answer to that question. It's still not clear how this BLANK buffer was getting created on startup, since I have no idea how hycontrol-window-display-buffer was getting called, but I'd like to suggest that the name of that blank buffer be changed to something that makes its source and purpose more obvious. Perhaps (defvar hycontrol--blank-buffer (get-buffer-create " *hycontrol--blank-buffer*") ? Any user who does hycontrol-windows-grid and triggers that will see the extra buffers with that name, and if such buffers just show up in the buffer list, it'll be obvious that they can safely be killed. I don't have any strong feelings about the name, just something more helpful and meaningful -- and searchable! -- than "BLANK". Regards, Dan -- Ceci n'est pas une .signature. --0000000000004e90cd060698d555 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

A while back I posted= this emacs.stackexchange question, about a mysterious buffer named BLANK w= hich always appeared when I started emacs: https://emacs.stackexchange.com/q/78601/19526=

Today I figured out the source: see my answer to = that question.

=
It's still not clear = how this BLANK buffer was getting created on startup, since I have no idea = how hycontrol-window-display-buffer was getting called, but I'd = like to suggest that the name of that blank buffer be changed to something = that makes its source and purpose more obvious. Perhaps

(defvar hycontrol--blank-buffer (get-buffer-create " *hycontrol-= -blank-buffer*")

? Any user who does hycontro= l-windows-grid and triggers that will see the extra buffers with that name,= and if such buffers just show up in the buffer list, it'll be obvious = that they can safely be killed.

I don't have a= ny strong feelings about the name, just something more helpful and meaningf= ul -- and searchable! -- than "BLANK".

R= egards,

Dan

--
Ceci n'est pas une .signature.
--0000000000004e90cd060698d555-- From debbugs-submit-bounces@debbugs.gnu.org Sun Oct 01 08:48:28 2023 Received: (at 66285) by debbugs.gnu.org; 1 Oct 2023 12:48:28 +0000 Received: from localhost ([127.0.0.1]:60838 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qmvs2-0004jb-Sk for submit@debbugs.gnu.org; Sun, 01 Oct 2023 08:48:27 -0400 Received: from mail-ej1-x633.google.com ([2a00:1450:4864:20::633]:59487) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qmv2x-0000X0-FB for 66285@debbugs.gnu.org; Sun, 01 Oct 2023 07:55:40 -0400 Received: by mail-ej1-x633.google.com with SMTP id a640c23a62f3a-9ad810be221so2177549266b.2 for <66285@debbugs.gnu.org>; Sun, 01 Oct 2023 04:55:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696161317; x=1696766117; darn=debbugs.gnu.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=UWmHYdEtsdmKpV35kRjG6i/uFihDD5joTVp9g3EEOvs=; b=jc/UBlfqB+vJE96gAP+nMfgHvyMaxSYooxTTO3lpqzjaMfdVOwPN07imArQR9LmjB3 95YfcW6ohBW8Wsce+2avi59IVMv+RsZTnBzqpM/h5cQ76RNLGWLQM1svwYRgqLpRNQVM QwF1vGi/FRnBw9nGRYeqnRqd61jIs9SmTdmP43brfkTCfNVfwxfjxKs5CjqC4xIGCEn4 PCTuSjQOr8wexm8jWQUrZMmbMu2k+ebQI27nPt1324aM4KNp9GVd2prFJzRUc9/Oxg9M ptEj/1+HAxi/0QreVQR4o/NCaQzC6H7tgl2hQPfGx0UrDolt/Tnd0b3iuXUmOe++/hOR KUMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696161317; x=1696766117; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=UWmHYdEtsdmKpV35kRjG6i/uFihDD5joTVp9g3EEOvs=; b=N6uciat33W8TVUzNbYQdnM77s4sd97HQ4t4iexqJQ8Wak/c6POWX/arUU243H2DFvL CZLXTbSNwsjGqWJet5NQqNZfIL04+G6wNU3t346p7LAUtrwwxWgI6DGxpNB4KxwADRq8 WkdZGPu54JqSAor7WtB9j3IdQiht5OCHY/bQRIlWjhDQnq+yZY9iE5HNMN1sYPy4OK/u 8drZfdJCDvQ5xCPdVVtn4aNp+VNgQZvadlO0u+aSzGnaz+nFMN3KaoF+wC2XM88zl2r6 TEPpf0BsmWUpxfqFMHSdjAA1NUSYpTagSORy+l8g4w+11MkeOtMbtXVnD+M8jWf30cyZ PSAw== X-Gm-Message-State: AOJu0YwE/T+2ShHD9P9GSpfZXhpY8wEvJ2O5D1Aolg+SOVD6VYoN5Y+1 VR0nNBzO2JRoikyz0UtEXKhedix85Y28pxxUj6mWZ9iZb2s= X-Google-Smtp-Source: AGHT+IGBIHFFwj8tJSKW5+mvCL7sQzm29eRbhak6iyudxvwg7h+k4/HyKIOMlub4YObFI9fzoHlRVdHQ/tm7+59N8Pg= X-Received: by 2002:a17:907:762d:b0:9a1:c357:c743 with SMTP id jy13-20020a170907762d00b009a1c357c743mr7720490ejc.52.1696161317050; Sun, 01 Oct 2023 04:55:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Dan Drake Date: Sun, 1 Oct 2023 06:55:05 -0500 Message-ID: Subject: Re: bug#66285: suggestion: change definition of hycontrol--blank-buffer to something more meaningful To: 66285@debbugs.gnu.org Content-Type: multipart/alternative; boundary="000000000000c8e0ab0606a6548d" X-Spam-Score: 0.0 (/) X-Debbugs-Envelope-To: 66285 X-Mailman-Approved-At: Sun, 01 Oct 2023 08:48:22 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -1.0 (-) --000000000000c8e0ab0606a6548d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Here's an alternative suggestion: juse use the scratch buffer. Many users, I think, always have a scratch buffer open. If hycontrol-window-display-buffer runs out of buffers to display, instead of creating new, empty, useless buffers, it seems reasonable to default to displaying the scratch buffer. And if there's no such buffer, then fall back to the blank one. So, in addition to a more useful name, I propose the following snippet for hycontrol-window-display-buffer: (set-window-buffer window (or buf ;; Out of buffers to display, display scratch buffer if it exists... (get-buffer "*scratch*") ;; ...otherwise, a blank buffer: hycontrol--blank-buffer)))) It just adds the single condition to the "or" to get the scratch buffer, and gracefully falls back to existing behavior if there's no scratch buffer= . On Sat, Sep 30, 2023 at 5:35=E2=80=AFPM Dan Drake wro= te: > Hello, > > A while back I posted this emacs.stackexchange question, about a > mysterious buffer named BLANK which always appeared when I started emacs: > https://emacs.stackexchange.com/q/78601/19526 > > Today I figured out the source: see my answer to that question. > > It's still not clear how this BLANK buffer was getting created on startup= , > since I have no idea how hycontrol-window-display-buffer was getting > called, but I'd like to suggest that the name of that blank buffer be > changed to something that makes its source and purpose more obvious. Perh= aps > > (defvar hycontrol--blank-buffer (get-buffer-create " > *hycontrol--blank-buffer*") > > ? Any user who does hycontrol-windows-grid and triggers that will see the > extra buffers with that name, and if such buffers just show up in the > buffer list, it'll be obvious that they can safely be killed. > > I don't have any strong feelings about the name, just something more > helpful and meaningful -- and searchable! -- than "BLANK". > > Regards, > > Dan > > -- > Ceci n'est pas une .signature. > _______________________________________________ > Bug-hyperbole mailing list > Bug-hyperbole@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-hyperbole > --=20 Ceci n'est pas une .signature. --000000000000c8e0ab0606a6548d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Here's an alternative suggestion: juse use the sc= ratch buffer.

Many users, I think, always have a s= cratch buffer open. If hycontrol-window-display-buffer runs out of buffers = to display, instead of creating new, empty, useless buffers, it seems reaso= nable to default to displaying the scratch buffer. And if there's no su= ch buffer, then fall back to the blank one.

S= o, in addition to a more useful name, I propose the following snippet for h= ycontrol-window-display-buffer:

=C2=A0 =C2=A0 (set= -window-buffer window
=C2=A0 =C2=A0 =C2=A0 (or buf
=C2=A0 ;; O= ut of buffers to display, display scratch buffer if it exists...
=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0(get-buffer "*scratch*")
=C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0;; ...otherwise, a blank buffer:
=C2=A0 hycontrol--blank-buffer))= ))

It just adds the single condition to the "= or" to get the scratch buffer, and gracefully falls back to existing b= ehavior if there's no scratch buffer.

On Sat, Sep 30, 2023 at = 5:35=E2=80=AFPM Dan Drake <dan.dr= ake@gmail.com> wrote:
Hello,

A while = back I posted this emacs.stackexchange question, about a mysterious buffer = named BLANK which always appeared when I started emacs: https://emacs.stac= kexchange.com/q/78601/19526

Today I figured ou= t the source: see my answer to that question.

It's still not clear how this BLANK buffer was getting created on= startup, since I have no idea how hycontrol-window-display-buffer w= as getting called, but I'd like to suggest that the name of that blank = buffer be changed to something that makes its source and purpose more obvio= us. Perhaps

(defvar hycontrol--blank-buffer (get-b= uffer-create " *hycontrol--blank-buffer*")

? Any user who does hycontrol-windows-grid and triggers that will see th= e extra buffers with that name, and if such buffers just show up in the buf= fer list, it'll be obvious that they can safely be killed.
I don't have any strong feelings about the name, just some= thing more helpful and meaningful -- and searchable! -- than "BLANK&qu= ot;.

Regards,

Dan

--
Ceci n'est pas une .signature.
_______________________________________________
Bug-hyperbole mailing list
Bug-hyperbole@gn= u.org
https://lists.gnu.org/mailman/listinfo/bug-hyper= bole


--
Ceci n'es= t pas une .signature.
--000000000000c8e0ab0606a6548d-- From debbugs-submit-bounces@debbugs.gnu.org Thu Mar 21 18:58:17 2024 Received: (at 66285) by debbugs.gnu.org; 21 Mar 2024 22:58:17 +0000 Received: from localhost ([127.0.0.1]:43660 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rnRMX-0000BC-0I for submit@debbugs.gnu.org; Thu, 21 Mar 2024 18:58:17 -0400 Received: from eggs.gnu.org ([209.51.188.92]:40030) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rnRMV-0000Ah-2l for 66285@debbugs.gnu.org; Thu, 21 Mar 2024 18:58:16 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rnRJf-0008QL-1u; Thu, 21 Mar 2024 18:55:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=6f2yoJWq59PPYWSVQ849zHvTJkhiQUsaJAdokCH98o8=; b=mIZW0tI4qzI9aI7akHs7 w8ugQexl1aEd8EcVNQw3s/2xF3K2qIyiNYrKIYe7jcZpCc4XtiwP8f2tuV/OGbDQQxc7p3HRZdgcv iz92NKA4h/vp2/ToZLZOvRfv/A80nsnziAYoGlarCF6qM/VV/a3SvSugG6qq1LtLzXXvD38+4vkAz kLbhIxdO0OJE8uhpVz/Cazf2iuCt/xUs3T73bFwKRGLCM/0pa7ujwy5kiFiqfM1L1vR64Jo+zkOIB s25PX7UG5XOolWIRNMtbfDU8gm9GubzBHgTK27bxFLX2zbM7D3tiqdGbfhkYU7tKX3ipf6uMPPeEU H1MDfsV001UNYg==; From: Mats Lidell To: Dan Drake Subject: Re: bug#66285: suggestion: change definition of hycontrol--blank-buffer to something more meaningful In-Reply-To: (Dan Drake's message of "Sat, 30 Sep 2023 14:48:52 -0500") References: Date: Thu, 21 Mar 2024 23:55:15 +0100 Message-ID: <874jczci0c.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 66285 Cc: 66285@debbugs.gnu.org X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) > Dan Drake writes: > Hello, > > A while back I posted this emacs.stackexchange question, about a mysterious buffer named BLANK which always appeared when I started emacs: > https://emacs.stackexchange.com/q/78601/19526 > > Today I figured out the source: see my answer to that question. > > It's still not clear how this BLANK buffer was getting created on startup, since I have no idea how hycontrol-window-display-buffer was getting called, > but I'd like to suggest that the name of that blank buffer be changed to something that makes its source and purpose more obvious. Perhaps > > (defvar hycontrol--blank-buffer (get-buffer-create " *hycontrol--blank-buffer*") > > ? Any user who does hycontrol-windows-grid and triggers that will see the extra buffers with that name, and if such buffers just show up in the buffer > list, it'll be obvious that they can safely be killed. > > I don't have any strong feelings about the name, just something more helpful and meaningful -- and searchable! -- than "BLANK". > > Regards, > > Dan > > -- > Ceci n'est pas une .signature. Thanks for the suggestion. The variable `hycontrol-blank-buffer-name' has been introduced with commit 31d4095. Is is customizable and defaults to " BLANK". It will be part of the next release of Hyperbole and is available from elpa-devel archive. Yours -- %% Mats From debbugs-submit-bounces@debbugs.gnu.org Fri Mar 22 18:17:36 2024 Received: (at control) by debbugs.gnu.org; 22 Mar 2024 22:17:36 +0000 Received: from localhost ([127.0.0.1]:53291 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rnnCi-0006il-DS for submit@debbugs.gnu.org; Fri, 22 Mar 2024 18:17:36 -0400 Received: from eggs.gnu.org ([209.51.188.92]:46802) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rnnCg-0006iU-Eq for control@debbugs.gnu.org; Fri, 22 Mar 2024 18:17:35 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rnnBw-0007yd-8u for control@debbugs.gnu.org; Fri, 22 Mar 2024 18:16:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Subject:From:To:Date:mime-version:in-reply-to: references; bh=npb/WgqsQ/natnMc9u/RKidiwf2bZxDCPcbtaUeNfwA=; b=JRLHqe3YvsG2wV 7CvFOzpi0syXfvMIWyr6pMpED4tYNvwn3L6aX/SkIYcPE9lgqdIBf5IqkF4U6Ns30l3VRrXaV67/6 D38Og+u44SEXKl1tymK+mn+sXNzFZ3VAWHTKrYhHCrCQg1AuXHvnkB4ipqvC2W8H/kO1IbZLtpak4 2k6QuEApOAkbRad8JhmcnpJ+Pgohm71rMIo6LjVDFm4KKk5JHwoegoo4XA67yMwws58mpiAs9tcGV AFbS1pNqnxhhWxy6X+tparoiEszkViE9kyA1EfBafXTcoO3RrKU/qTSJqJZCaJv+BnS9A8pNrWA/u 8yEstaE7LFiPd9riLq/A==; Date: Fri, 22 Mar 2024 23:16:41 +0100 Message-Id: <87o7b552uu.fsf@gnu.org> To: control@debbugs.gnu.org From: Mats Lidell Subject: control message for bug #66285 X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: control X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: -3.3 (---) close 66285 quit From unknown Thu Jun 19 14:08:35 2025 Received: (at fakecontrol) by fakecontrolmessage; To: internal_control@debbugs.gnu.org From: Debbugs Internal Request Subject: Internal Control Message-Id: bug archived. Date: Sat, 20 Apr 2024 11:24:15 +0000 User-Agent: Fakemail v42.6.9 # This is a fake control message. # # The action: # bug archived. thanks # This fakemail brought to you by your local debbugs # administrator