From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Thuna Newsgroups: gmane.emacs.devel Subject: Re: Allow controlling the effect of visibility on buffer switching Date: Sat, 29 Jan 2022 10:48:08 +0300 Message-ID: <87mtjf0ypz.fsf@gmail.com> References: <87a6fi3lrl.fsf@gmail.com> <83a6fihbeb.fsf@gnu.org> <877dam38zr.fsf@gmail.com> <8335lah77y.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="8169"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jan 29 09:52:05 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 1nDjSn-0001xz-2X for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Jan 2022 09:52:05 +0100 Original-Received: from localhost ([::1]:58608 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nDjSl-0003Xf-TW for ged-emacs-devel@m.gmane-mx.org; Sat, 29 Jan 2022 03:52:03 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:57814) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nDiT3-0003G9-79 for emacs-devel@gnu.org; Sat, 29 Jan 2022 02:48:17 -0500 Original-Received: from [2a00:1450:4864:20::530] (port=37877 helo=mail-ed1-x530.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nDiT1-00022P-JW; Sat, 29 Jan 2022 02:48:16 -0500 Original-Received: by mail-ed1-x530.google.com with SMTP id c24so14959500edy.4; Fri, 28 Jan 2022 23:48:11 -0800 (PST) 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=Q6yRAuMlQ1Qfduvvj+1ucsD5kZx6j81DxVYJH4tnkw0=; b=YEOprWi5WEZkDU9QUPrWfgzGs6YugSeCokMH2W7zSTwu5h/b+g9K8pdfwVvmqEl7w6 EhO9aQpN8MZqSm5GcmC0axtC1u51MIUYGt1J4qvAtkhObNTT3drtPFKix5sAAvs4kp8W KmvrAtK+HGyFVBl03JOUkl7bQm0EQC8y+PGXmdVoiNeS/SLTOrOmQjTAKtegcrqfuFCC vFR/xbE+9z29WPAYPq/Ft//WT9ndI6OZpy5CjKuc5LJkKAo0F/taZIPHjUDHCZvs5Lac 03xNWhCU3J++Wg7MZnDjUQqMoNlfxmq7gvL95B0eeKcgO8br3T520yq9Qmh1HTGQErPi Dm7g== 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=Q6yRAuMlQ1Qfduvvj+1ucsD5kZx6j81DxVYJH4tnkw0=; b=nrFJ2S+/P+WPxKbT2GiUsvyCr0N8hULulrqAwZg7BtbEOhEc+UkFOev7mUaLX8Il9j TrIMN9Xcf40pQUjJE/v4K0MWUJrtz7/JxE48YldRTGuqDNko16Tn4G2uhhRfiNwM9Mnk O5LkCaAwmQoIdS1hCQMG/Fzi4f26PD72iEhYrpEC45A1VcarADJklDDTDbPhF8ksdvg9 UF7ubEZyy0F9klbG+UkS1SlYwVBezu+rO0w3o3qGjI2p2LHrYQdh/rEmOEb0bf8xFGR+ QNPor1WKjWrER8S3soLe8RN4dRyEQT5jv0VgeKPALDfL5EspLO3vJtBQNRBg39eT0AyY OZVg== X-Gm-Message-State: AOAM530QLM5XYk2dutF1jFRm8GNW27FIJgRVH3Sfs4bpytval4sY22Yu Kpvoh+FLpPoeAqWPm7O/BsmgrSgXah9tGA== X-Google-Smtp-Source: ABdhPJympu7upoT4mLWndzUg+a25L8FqzRJruJMDnPjfADxZoB+UynbTnLSicnwq6MKlasVfbKFfIA== X-Received: by 2002:a05:6402:51c9:: with SMTP id r9mr11711927edd.120.1643442490623; Fri, 28 Jan 2022 23:48:10 -0800 (PST) Original-Received: from Thuna ([78.161.73.233]) by smtp.gmail.com with ESMTPSA id g17sm9163333ejd.82.2022.01.28.23.48.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 28 Jan 2022 23:48:09 -0800 (PST) In-Reply-To: <8335lah77y.fsf@gnu.org> X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a00:1450:4864:20::530 (failed) Received-SPF: pass client-ip=2a00:1450:4864:20::530; envelope-from=thuna.cing@gmail.com; helo=mail-ed1-x530.google.com X-Spam_score_int: -12 X-Spam_score: -1.3 X-Spam_bar: - X-Spam_report: (-1.3 / 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, PDS_HP_HELO_NORDNS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Sat, 29 Jan 2022 03:48:29 -0500 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:285541 Archived-At: > Forcing users to learn too many options is also not a very good idea, > and we already have gobs of them. So much so that even the head > maintainers don't remember that many of them exist. If the proposal is rejected on this basis, I would like to revise it from "introducing an option to change the behavior of switch-to-buffer" to "changing the behavior of switch-to-buffer". It is extremely unlikely for someone to know what their last non-visible buffer is, especially after accounting for other frames and windows. People are better off typing the name of the buffer they want to visit. Compared to that, switching to the last buffer is considerably more manageable and useful.