From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "J.P." Newsgroups: gmane.emacs.bugs Subject: bug#70358: ERC not changing to buffers Date: Fri, 12 Apr 2024 19:54:44 -0700 Message-ID: <87mspy7z0r.fsf__29833.5668792546$1712976980$gmane$org@neverwas.me> References: <87y19inj4d.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28397"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-erc@gnu.org, 70358@debbugs.gnu.org To: Rahul Martim Juliato Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 13 04:56:12 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1rvTYo-00078S-6J for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 13 Apr 2024 04:56:10 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rvTYZ-0002ya-3U; Fri, 12 Apr 2024 22:55:55 -0400 Original-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 1rvTYX-0002yL-Pk for bug-gnu-emacs@gnu.org; Fri, 12 Apr 2024 22:55:53 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rvTYX-0002eh-Bk for bug-gnu-emacs@gnu.org; Fri, 12 Apr 2024 22:55:53 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rvTYh-0003Ap-7e for bug-gnu-emacs@gnu.org; Fri, 12 Apr 2024 22:56:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: "J.P." Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 13 Apr 2024 02:56:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 70358 X-GNU-PR-Package: emacs Original-Received: via spool by 70358-submit@debbugs.gnu.org id=B70358.171297690211499 (code B ref 70358); Sat, 13 Apr 2024 02:56:03 +0000 Original-Received: (at 70358) by debbugs.gnu.org; 13 Apr 2024 02:55:02 +0000 Original-Received: from localhost ([127.0.0.1]:59791 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rvTXi-0002zN-8K for submit@debbugs.gnu.org; Fri, 12 Apr 2024 22:55:02 -0400 Original-Received: from mail-108-mta227.mxroute.com ([136.175.108.227]:37657) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rvTXg-0002yh-25 for 70358@debbugs.gnu.org; Fri, 12 Apr 2024 22:55:01 -0400 Original-Received: from filter006.mxroute.com ([136.175.111.2] filter006.mxroute.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta227.mxroute.com (ZoneMTA) with ESMTPSA id 18ed560fee70003bea.001 for <70358@debbugs.gnu.org> (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Sat, 13 Apr 2024 02:54:47 +0000 X-Zone-Loop: c09523133d9dcdcc21838bb7b56dd93f7c5ec6d5f24f X-Originating-IP: [136.175.111.2] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=neverwas.me ; s=x; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date: References:In-Reply-To:Subject:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=2cL9NqBvIK3vdAHVtk1lMAa5wHnOkahLk0ocPSc51+I=; b=CwfGQgSakJDYvyqT3Yb1SL+aUX 9gM3KOrpxiLox8xgp9Mw7a4mSdv207fYkAy0rFMQ3+vlQGq4LSnKgysqUPF8txf57D+rkxHje6ssT 0Sy2Yj8Ukvv8SK/LsfSJjE9HThVR116VyEtNWBR84yBXe0pdvQ0Bm7F0OyYY7DVQGl96E1J+06uDY yMxC3auu+7tXMix8HXWBlUlsGbyogBtX2HrLaX3MkFFiv6Gu+DzGWJr9OiP5POpH7hN7cbqk7r1FT ohCD6vhCYG8FRIV/rXPjRDTPAgsxdCxdVx3hPvcQNHfevN+GtT1JqryjCNSAyeLuV1oj5XNgR0XOY WmlOBkGA==; In-Reply-To: <87y19inj4d.fsf@gmail.com> (Rahul Martim Juliato's message of "Fri, 12 Apr 2024 22:31:30 -0300") X-Authenticated-Id: masked@neverwas.me X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:283157 Archived-At: Hi Rahul, Rahul Martim Juliato writes: > Hello there! > > I am not completely sure this is a bug, but since some versions ago (I > am on emacs 29.3 for Linux), ERC stopped (what I use to remember) a > behaviour. Please see this post for context: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D62833#14 > If I call ERC with `M-x erc`, it connects, but keeps the buffer on the > background, and I have to manually switch to it. > > The same with `/join #channel` and other commands. On HEAD, a new option, `erc-interactive-display', supersedes `erc-join-buffer' (now called `erc-buffer-display') in interactive situations, like /JOIN and M-x erc RET. Quoting from etc/ERC-NEWS: ** Revised buffer-display handling. A point of friction for new users and one only just introduced with ERC 5.5 has been the lack of visual feedback when first connecting via M-x erc or when issuing a "/JOIN" command at the prompt. As explained below, in the news for 5.5, the discovery of a security issue led to most new ERC buffers being "buried" on creation. On further reflection, this was judged to have been an overcorrection in the case of interactive invocations, hence the borrowing of an old option, 'erc-query-display', and the bestowing of a new alias, 'erc-interactive-display', which better describes its expanded role as a more general buffer-display knob for interactive commands ("/QUERY" still among them). > I find it confusing and non-intuitive, it makes the user believe > something wrong happened. I come from the old school of iirc, Bitchx, > mIrc, and so on. I can=C2=B4t remember ever seen such behaviour for issui= ng > IRC commands (even on ERC). > > Is this a bug? A feature? Is there a custom variable to keep the old > behaviour? On 5.5, you can customize `erc-join-buffer' to `buffer'. On 5.6, you'll be able to do the same with `erc-interactive-display', as mentioned. > Strangelly if someone `/query me` it pops up a buffer (for that I know > there's a switch). So, two sides of the same coin I guess? Right, that's controlled by the option `erc-auto-query', now called `erc-receive-query-display'. Quoting from etc/ERC-NEWS: Accompanying this addition are "display"-suffixed aliases for related options 'erc-join-buffer' and 'erc-auto-query', which users have reported as being difficult to discover and remember. When the latter option (now known as 'erc-receive-query-display') is nil, ERC uses 'erc-join-buffer' in its place, much like it does for 'erc-interactive-display'. The old nil behavior can still be gotten via the new compatibility flag 'erc-receive-query-display-defer'. The relatively new option 'erc-reconnect-display' has likewise been renamed, this time for clarity, to 'erc-auto-reconnect-display'. > If anyone could help me, I'd be more than happy. The next release of ERC should be out "soon" (though we've been saying that for months). If you're both super desperate and unwilling to customize options, there's always the devel package on GNU ELPA [1]. For non-bug related questions, there's ERC's own mailing list (Cc'd), as well as the #erc channel on Libera.Chat. Thanks, J.P. P.S. In the future, please consider filing bugs with M-x erc-bug RET or adding the Emacs or ERC version number to the subject line. [1] https://emacs-erc.gitlab.io/bugs/archive/doc/erc.html#Upgrading