From: Eli Zaretskii <eliz@gnu.org>
To: "J.P." <jp@neverwas.me>
Cc: emacs-erc@gnu.org, 62833@debbugs.gnu.org
Subject: bug#62833: 30.0.50; ERC 5.6: Rethink buffer-display options and behavior
Date: Sun, 04 Jun 2023 18:28:14 +0300 [thread overview]
Message-ID: <837csj5jsh.fsf__27106.133829669$1685892499$gmane$org@gnu.org> (raw)
In-Reply-To: <877csje0uz.fsf@neverwas.me> (jp@neverwas.me)
> From: "J.P." <jp@neverwas.me>
> Cc: emacs-erc@gnu.org, 62833@debbugs.gnu.org
> Date: Sun, 04 Jun 2023 07:52:20 -0700
>
> The solution to all this isn't straightforward, and we're making headway
> on it for ERC 5.6. In the meantime, I'm wondering if we might consider
> appeasing these disgruntled users somehow. Normally, I'd prefer just
> reverting back to `buffer', but because much has been made about its
> potential for causing mayhem via unintended sharing, I'm thinking we
> might change the default in Emacs 29 to `window-noselect'. This value
> tells ERC to show new buffers in a sibling window of the same vertical
> combination.
I don't use ERC, but how does it make sense to change the default so
close to a release? I could understand reverting back to 'buffer',
which was used for a long time, but switching to a new default that
had no real testing period? Are you absolutely sure this is a good
idea? And on top of that, change it only for Emacs 29?
next prev parent reply other threads:[~2023-06-04 15:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87leiuy3cv.fsf@neverwas.me>
2023-04-21 14:03 ` bug#62833: 30.0.50; ERC 5.6: Rethink buffer-display options and behavior J.P.
[not found] ` <87354tcoyk.fsf@neverwas.me>
2023-04-24 14:34 ` J.P.
2023-05-08 22:26 ` J.P.
[not found] ` <87jzxie9yf.fsf@neverwas.me>
2023-05-10 21:43 ` Corwin Brust
[not found] ` <CAJf-WoTk1vT3gVSHdO7MRs6Rfn4PRcs8UWM=mw_NbzeCGHDfvQ@mail.gmail.com>
2023-05-13 14:03 ` J.P.
[not found] ` <87sfc08h19.fsf@neverwas.me>
2023-06-02 14:06 ` J.P.
2023-05-16 14:37 ` Phillip Susi
2023-06-04 14:52 ` J.P.
[not found] ` <877csje0uz.fsf@neverwas.me>
2023-06-04 15:28 ` Eli Zaretskii [this message]
[not found] ` <837csj5jsh.fsf@gnu.org>
2023-06-04 21:36 ` J.P.
2023-06-09 13:50 ` J.P.
2023-06-22 13:48 ` J.P.
2023-07-08 14:19 ` J.P.
[not found] ` <87r0pi32po.fsf@neverwas.me>
2023-07-14 2:11 ` J.P.
2023-04-14 13:56 J.P.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='837csj5jsh.fsf__27106.133829669$1685892499$gmane$org@gnu.org' \
--to=eliz@gnu.org \
--cc=62833@debbugs.gnu.org \
--cc=emacs-erc@gnu.org \
--cc=jp@neverwas.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).