Received: (at 66285) by debbugs.gnu.org; 1 Oct 2023 12:48:28 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Sun Oct 01 08:48:28 2023
Received: from localhost ([127.0.0.1]:60838 helo=debbugs.gnu.org)
by debbugs.gnu.org with esmtp (Exim 4.84_2)
(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
id 1qmvs2-0004jb-Sk
for submit <at> 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 <dan.drake@HIDDEN>) id 1qmv2x-0000X0-FB
for 66285 <at> 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 <at> 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: <CAKqbAeHZ9G96jcc9Ex=1O3D=of8s=X6g6g=Tyijh62oQeBzBQw@HIDDEN>
In-Reply-To: <CAKqbAeHZ9G96jcc9Ex=1O3D=of8s=X6g6g=Tyijh62oQeBzBQw@HIDDEN>
From: Dan Drake <dan.drake@HIDDEN>
Date: Sun, 1 Oct 2023 06:55:05 -0500
Message-ID: <CAKqbAeHE=PJaW1Z2TiDuZCRrBh2UcPs2RDVXAbeGGO-Rr4a==w@HIDDEN>
Subject: Re: bug#66285: suggestion: change definition of
hycontrol--blank-buffer to something more meaningful
To: 66285 <at> 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 <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>,
<mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>,
<mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
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 <dan.drake@HIDDEN> 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@HIDDEN
> 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
<div dir=3D"ltr"><div>Here's an alternative suggestion: juse use the sc=
ratch buffer.</div><div><br></div><div>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. <br></div><div><br></div><div>S=
o, in addition to a more useful name, I propose the following snippet for h=
ycontrol-window-display-buffer:</div><div><br></div><div>=C2=A0 =C2=A0 (set=
-window-buffer window<br> =C2=A0 =C2=A0 =C2=A0 (or buf<br> =C2=A0 ;; O=
ut of buffers to display, display scratch buffer if it exists...<br>=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*")<br>=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:<br> =C2=A0 hycontrol--blank-buffer))=
))</div><div><br></div><div>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.<br></div></div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Sep 30, 2023 at =
5:35=E2=80=AFPM Dan Drake <<a href=3D"mailto:dan.drake@HIDDEN">dan.dr=
ake@HIDDEN</a>> wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div dir=3D"ltr"><div>Hello,</div><div><br></div><div>A while =
back I posted this emacs.stackexchange question, about a mysterious buffer =
named BLANK which always appeared when I started emacs: <a href=3D"https://=
emacs.stackexchange.com/q/78601/19526" target=3D"_blank">https://emacs.stac=
kexchange.com/q/78601/19526</a></div><div><br></div><div>Today I figured ou=
t the source: see my answer to that question.</div><div><span class=3D"gmai=
l_signature_prefix"><br></span></div><div><span class=3D"gmail_signature_pr=
efix">It's still not clear how this BLANK buffer was getting created on=
startup, since I have no idea how </span>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</div><div><br></div><div>(defvar hycontrol--blank-buffer (get-b=
uffer-create " *hycontrol--blank-buffer*")</div><div><br></div><d=
iv>? 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.</div><div><b=
r></div><div>I don't have any strong feelings about the name, just some=
thing more helpful and meaningful -- and searchable! -- than "BLANK&qu=
ot;.</div><div><br></div><div>Regards,</div><div><br></div><div>Dan<br></di=
v><div><span class=3D"gmail_signature_prefix"><br></span></div><div><span c=
lass=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gma=
il_signature">Ceci n'est pas une .signature.</div></div></div>
_______________________________________________<br>
Bug-hyperbole mailing list<br>
<a href=3D"mailto:Bug-hyperbole@HIDDEN" target=3D"_blank">Bug-hyperbole@gn=
u.org</a><br>
<a href=3D"https://lists.gnu.org/mailman/listinfo/bug-hyperbole" rel=3D"nor=
eferrer" target=3D"_blank">https://lists.gnu.org/mailman/listinfo/bug-hyper=
bole</a><br>
</blockquote></div><br clear=3D"all"><br><span class=3D"gmail_signature_pre=
fix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">Ceci n'es=
t pas une .signature.</div>
--000000000000c8e0ab0606a6548d--
bug-hyperbole@HIDDEN:bug#66285; Package hyperbole.
Full text available.Received: (at submit) by debbugs.gnu.org; 30 Sep 2023 22:22:37 +0000 From debbugs-submit-bounces <at> debbugs.gnu.org Sat Sep 30 18:22:37 2023 Received: from localhost ([127.0.0.1]:59884 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>) id 1qmiM7-0004bI-JK for submit <at> 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 <dan.drake@HIDDEN>) id 1qmfxz-0000Ki-HD for submit <at> 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 <dan.drake@HIDDEN>) id 1qmfxd-0004tW-Kk for bug-hyperbole@HIDDEN; 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 <dan.drake@HIDDEN>) id 1qmfxb-00030z-DT for bug-hyperbole@HIDDEN; Sat, 30 Sep 2023 15:49:09 -0400 Received: by mail-ej1-x62e.google.com with SMTP id a640c23a62f3a-9b2cee55056so394855166b.3 for <bug-hyperbole@HIDDEN>; 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 <dan.drake@HIDDEN> Date: Sat, 30 Sep 2023 14:48:52 -0500 Message-ID: <CAKqbAeHZ9G96jcc9Ex=1O3D=of8s=X6g6g=Tyijh62oQeBzBQw@HIDDEN> Subject: suggestion: change definition of hycontrol--blank-buffer to something more meaningful To: bug-hyperbole@HIDDEN Content-Type: multipart/alternative; boundary="0000000000004e90cd060698d555" Received-SPF: pass client-ip=2a00:1450:4864:20::62e; envelope-from=dan.drake@HIDDEN; 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 <at> debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: <debbugs-submit.debbugs.gnu.org> List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe> List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/> List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org> List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help> List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe> Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org> 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 <div dir=3D"ltr"><div>Hello,</div><div><br></div><div>A while back I posted= this emacs.stackexchange question, about a mysterious buffer named BLANK w= hich always appeared when I started emacs: <a href=3D"https://emacs.stackex= change.com/q/78601/19526">https://emacs.stackexchange.com/q/78601/19526</a>= </div><div><br></div><div>Today I figured out the source: see my answer to = that question.</div><div><span class=3D"gmail_signature_prefix"><br></span>= </div><div><span class=3D"gmail_signature_prefix">It's still not clear = how this BLANK buffer was getting created on startup, since I have no idea = how </span>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</div><div><br></div= ><div>(defvar hycontrol--blank-buffer (get-buffer-create " *hycontrol-= -blank-buffer*")</div><div><br></div><div>? 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.</div><div><br></div><div>I don't have a= ny strong feelings about the name, just something more helpful and meaningf= ul -- and searchable! -- than "BLANK".</div><div><br></div><div>R= egards,</div><div><br></div><div>Dan<br></div><div><span class=3D"gmail_sig= nature_prefix"><br></span></div><div><span class=3D"gmail_signature_prefix"= >-- </span><br><div dir=3D"ltr" class=3D"gmail_signature" data-smartmail=3D= "gmail_signature">Ceci n'est pas une .signature.</div></div></div> --0000000000004e90cd060698d555--
Dan Drake <dan.drake@HIDDEN>:bug-hyperbole@HIDDEN.
Full text available.bug-hyperbole@HIDDEN:bug#66285; Package hyperbole.
Full text available.
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997 nCipher Corporation Ltd,
1994-97 Ian Jackson.