From unknown Fri Aug 15 04:03:50 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#68679 <68679@debbugs.gnu.org> To: bug#68679 <68679@debbugs.gnu.org> Subject: Status: 30.0.50; Burying a buffer shows an already displayed buffer Reply-To: bug#68679 <68679@debbugs.gnu.org> Date: Fri, 15 Aug 2025 11:03:50 +0000 retitle 68679 30.0.50; Burying a buffer shows an already displayed buffer reassign 68679 emacs submitter 68679 sds@gnu.org severity 68679 normal thanks From debbugs-submit-bounces@debbugs.gnu.org Tue Jan 23 19:12:14 2024 Received: (at submit) by debbugs.gnu.org; 24 Jan 2024 00:12:14 +0000 Received: from localhost ([127.0.0.1]:44162 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rSQsH-0007xn-Le for submit@debbugs.gnu.org; Tue, 23 Jan 2024 19:12:14 -0500 Received: from lists.gnu.org ([2001:470:142::17]:38406) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rSQsF-0007xX-Vt for submit@debbugs.gnu.org; Tue, 23 Jan 2024 19:12:12 -0500 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 1rSQs4-0000GK-KT for bug-gnu-emacs@gnu.org; Tue, 23 Jan 2024 19:12:00 -0500 Received: from mail-qk1-x72b.google.com ([2607:f8b0:4864:20::72b]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rSQs1-0008Jn-NL; Tue, 23 Jan 2024 19:12:00 -0500 Received: by mail-qk1-x72b.google.com with SMTP id af79cd13be357-7839ece697bso197455385a.0; Tue, 23 Jan 2024 16:11:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706055115; x=1706659915; darn=gnu.org; h=mime-version:message-id:date:reply-to:return-receipt-to:subject:to :from:sender:from:to:cc:subject:date:message-id:reply-to; bh=WOR0DK/krpdKkFtJqqMkjAiazqhTa83GYQ0sfnc77oA=; b=HLlbs6rSna7b4TRUdPY2EKKlg9dl/uWgkqqWjJou6PnG47rA6Z4blApxHthNbVRJBD pw3IpyT77zsDJbNkj9Xi6WBqwvRqtbMPnlqoniSl2x8tE8/RBxvVp/1rFwjx2ThBAgl4 DZal/VJN1k2KOzWBwjfS7acSK4wKhiH7AZhZO70kivhQgkQ9YWt7LkaBHHVV6WjXngFK qaJdW7OqeAV8+nXhWhPU7a7CR/gzXCd5ZUjKXX2afzgj8+b2JiJiNmibQfwyO/6pp9+h P6PAnPUwwDG9PAO4lx+nTTlTxKaQQ+eO+GQ5vX2wu4/UxJulKgtjWlUsvHv0lgkDRHO7 mDqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706055115; x=1706659915; h=mime-version:message-id:date:reply-to:return-receipt-to:subject:to :from:sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=WOR0DK/krpdKkFtJqqMkjAiazqhTa83GYQ0sfnc77oA=; b=YfrY6jUUOYDjNT0eVvSXqemlixAivuv7bBPLgZPJ4psMwvcuaVUxD6rhcj8LeV7368 afrtsKXxiWp8+rrQTkbjSRr3fPPaNF1lCvnnsv+cAigwArhmI6D2oeGDqQMKBgzmArgi TjWFej1CQDHI6hp0X6bz++/H2dHsrypdeGxFB7e8CxIkIg57FM0erO9ASFOWrKV9VxIB qB8NBD5GdeUMqYMttUiWY7rCr+P9Sc6cOdvx8lDsH9UeFLAW9NAS86C3nFQLBQ+fykMr IVNHiePpGQEKhmjO7vkKqrK0IHPTIxHQ/lqY19/uMXPYGeOqHzndELhGfSyAN7s4a5uf Vgsw== X-Gm-Message-State: AOJu0YzdlPwTSaRJ6ZhJyyTv2lZbQw1qIxFn7DN5WIoZBkIZVyNqVftp AjACtWQUaPu5Zpkz7sBNrQgFn64E21Q/eYJDAvaUruHO7/wu2TPKBnnJkWU= X-Google-Smtp-Source: AGHT+IGljEVe/bbPdszSi1JexrrDwEYWqaSOZKX/2hX/l7ZX2MDJpBgiRCOilCq2Cy2sewk6AObaQA== X-Received: by 2002:a05:620a:a0f:b0:783:3496:967a with SMTP id i15-20020a05620a0a0f00b007833496967amr576369qka.43.1706055115066; Tue, 23 Jan 2024 16:11:55 -0800 (PST) Received: from pop-os (pool-108-6-133-45.nycmny.fios.verizon.net. [108.6.133.45]) by smtp.gmail.com with ESMTPSA id p5-20020a05620a112500b0078397532e70sm3053227qkk.7.2024.01.23.16.11.53 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Tue, 23 Jan 2024 16:11:54 -0800 (PST) From: Sam Steingold To: bug-gnu-emacs@gnu.org Subject: 30.0.50; Burying a buffer shows an already displayed buffer X-Attribution: Sam X-Disclaimer: You should not expect anyone to agree with me. X-Debbugs-Cc: Date: Tue, 23 Jan 2024 19:11:53 -0500 Message-ID: <878r4fmvxy.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::72b; envelope-from=sam.steingold@gmail.com; helo=mail-qk1-x72b.google.com X-Spam_score_int: -14 X-Spam_score: -1.5 X-Spam_bar: - X-Spam_report: (-1.5 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, 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-Spam-Score: 1.5 (+) X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: ISTR that quit-window and bury-buffer made sure that the replacement/newly displayed buffer is not shown in any other window (at least that was my intention when I wrote quit-window many years ago). Right now I see that C-x b (switch-to-buffer) offers a good candidate (IOW, other-buffer returns a buffer that is not currently shown), but both quit-window and bury-buffer replace the current buffer [...] Content analysis details: (1.5 points, 10.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.2 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail domains are different -0.0 SPF_HELO_PASS SPF: HELO matches SPF record 1.0 SPF_SOFTFAIL SPF: sender does not match SPF record (softfail) 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (sam.steingold[at]gmail.com) -0.0 T_SCC_BODY_TEXT_LINE No description available. 0.2 FREEMAIL_FORGED_FROMDOMAIN 2nd level domains in From and EnvelopeFrom freemail headers are different X-Debbugs-Envelope-To: submit 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: , Reply-To: sds@gnu.org Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.5 (/) ISTR that quit-window and bury-buffer made sure that the replacement/newly displayed buffer is not shown in any other window (at least that was my intention when I wrote quit-window many years ago). Right now I see that C-x b (switch-to-buffer) offers a good candidate (IOW, other-buffer returns a buffer that is not currently shown), but both quit-window and bury-buffer replace the current buffer with one that is already displayed in another window in the current frame. Is there a way to restore the original behavior of never displaying an already visible buffer? Is this a (known) bug? Thank you! (https://emacs.stackexchange.com/q/80138/795) In GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.33, cairo version 1.16.0) of 2024-01-12 built on pop-os Repository revision: 8b7a6d7b6deca9346092501dbfa679e3e5ea5892 Repository branch: master Windowing system distributor 'The X.Org Foundation', version 11.0.12101004 System Description: Pop!_OS 22.04 LTS Configured using: 'configure --with-mailutils --with-native-compilation --with-imagemagick --with-native-image-api' Configured features: CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GSETTINGS HARFBUZZ IMAGEMAGICK JPEG JSON LCMS2 LIBSELINUX LIBXML2 MODULES NATIVE_COMP NOTIFY INOTIFY PDUMPER PNG RSVG SECCOMP SOUND SQLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS TREE_SITTER WEBP X11 XDBE XIM XINPUT2 XPM GTK3 ZLIB Important settings: value of $LC_COLLATE: C value of $LANG: C value of $XMODIFIERS: @im=ibus locale-coding-system: utf-8-unix Major mode: Shell Minor modes in effect: shell-dirtrack-mode: t pyvenv-mode: t comint-fontify-input-mode: t global-atomic-chrome-edit-mode: t global-edit-server-edit-mode: t server-mode: t winner-mode: t which-function-mode: t url-handler-mode: t desktop-save-mode: t tooltip-mode: t global-eldoc-mode: t show-paren-mode: t electric-indent-mode: t mouse-wheel-mode: t menu-bar-mode: t file-name-shadow-mode: t global-font-lock-mode: t font-lock-mode: t blink-cursor-mode: t minibuffer-regexp-mode: t column-number-mode: t line-number-mode: t auto-composition-mode: t auto-encryption-mode: t auto-compression-mode: t Memory information: ((conses 16 1179154 1747372) (symbols 48 45559 106) (strings 32 346009 122184) (string-bytes 1 11220588) (vectors 16 123283) (vector-slots 8 2866890 496408) (floats 8 1195 18070) (intervals 56 24806 20570) (buffers 984 73)) -- Sam Steingold (https://aphar.dreamwidth.org/) on Pop 22.04 (jammy) X 11.0.12101004 https://lastingimpactpsychology.com https://steingoldpsychology.com https://www.memritv.org https://www.dhimmitude.org https://ffii.org A year spent in artificial intelligence is enough to make one believe in God. From debbugs-submit-bounces@debbugs.gnu.org Wed Jan 24 07:28:44 2024 Received: (at 68679) by debbugs.gnu.org; 24 Jan 2024 12:28:44 +0000 Received: from localhost ([127.0.0.1]:44679 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rScN1-0000DU-TB for submit@debbugs.gnu.org; Wed, 24 Jan 2024 07:28:44 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:58410) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rScMz-0000DI-Ns for 68679@debbugs.gnu.org; Wed, 24 Jan 2024 07:28:42 -0500 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 1rScMo-0004ZX-C8; Wed, 24 Jan 2024 07:28:30 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=UO4YyYGs2hDxIiVv+hvfhFIeCD35gL8todW8LnragpQ=; b=DDS37TPtdmxp 0L/7vavVVCk2KijYpvwAaZGi2wZgyrVm4EiCdZ6tyNIwNQrfkM4KqgzEennDkLGzNFYcEzLochBOS P4BTVxIr7+V3+zZEupIcydeKBXWvIpAqFhXAAUuO0hucwcBqqM8bT6J9SJJbmthLVYt0nkWqP517q 2BBcZleK6I8EzZdeZacW00Wkcy6e7rQw2O2OLIiyQyitU6xtb3Regb7cLjHPQb6vG8ZtH5Gtmk1D8 O6+mXXnjaikWkkt+Ek8PV4akt3uXJIqoFr3JVKsiwcG/8FlZkBoeSEzu/qHbRJpiYoNEXSXvYg3V0 nZ1MW1JlAp+RMInq5jGaxA==; Date: Wed, 24 Jan 2024 14:28:26 +0200 Message-Id: <864jf26hlh.fsf@gnu.org> From: Eli Zaretskii To: sds@gnu.org, martin rudalics In-Reply-To: <878r4fmvxy.fsf@gnu.org> (message from Sam Steingold on Tue, 23 Jan 2024 19:11:53 -0500) Subject: Re: bug#68679: 30.0.50; Burying a buffer shows an already displayed buffer References: <878r4fmvxy.fsf@gnu.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 68679 Cc: 68679@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 (---) > From: Sam Steingold > Date: Tue, 23 Jan 2024 19:11:53 -0500 > > ISTR that quit-window and bury-buffer made sure that the > replacement/newly displayed buffer is not shown in any other window (at > least that was my intention when I wrote quit-window many years ago). > > Right now I see that C-x b (switch-to-buffer) offers a good candidate > (IOW, other-buffer returns a buffer that is not currently shown), but > both quit-window and bury-buffer replace the current buffer with one > that is already displayed in another window in the current frame. > > Is there a way to restore the original behavior of never displaying an > already visible buffer? > > Is this a (known) bug? Where did you see such promises from these two commands? Adding Martin, in case he has some comments and pointers. From debbugs-submit-bounces@debbugs.gnu.org Thu Jan 25 04:40:21 2024 Received: (at 68679) by debbugs.gnu.org; 25 Jan 2024 09:40:21 +0000 Received: from localhost ([127.0.0.1]:47362 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rSwDc-0007ps-Nt for submit@debbugs.gnu.org; Thu, 25 Jan 2024 04:40:20 -0500 Received: from mout.gmx.net ([212.227.15.19]:57489) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rSwDb-0007pf-5m for 68679@debbugs.gnu.org; Thu, 25 Jan 2024 04:40:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.at; s=s31663417; t=1706175607; x=1706780407; i=rudalics@gmx.at; bh=7gQaABHnSkTcqbr9sWtEHIzVzsvbDodVYkeskOK/nJ4=; h=X-UI-Sender-Class:Date:Subject:To:Cc:References:From: In-Reply-To; b=k18T+eDAieMLTHltOIq+yy4fc22Xn2tf/CPi0+fPTRfRIRUb431gs8uNuRLo6iER m0bM0rHWcUwoKt0mVWKExAccjZXqSPFUwrLGm+aaBCaimVxXbJkdK3OzuneuKMQGo O1U+J+hll3l/ZqNaDd4fCAJcMKRJxzQ8wY2vDMIek7xzQiC+RSjFYHOELl0heEtty 150Ggyi6nK466RqvcA3Th2mCgGIUS/ZaYlmNB7giydePTplLvDuP1iuG9P3dEUEAe 5T1n+35aByFz3k6eWk+xmRi9X1mMhHcyA3yGAgVgLBr9t4XtxirmgXu/HQBTE1JRL kPKrzhzSorA448ZinQ== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from [192.168.31.113] ([213.142.97.167]) by mail.gmx.net (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MYeQr-1rX7Jc2eKB-00Vcni; Thu, 25 Jan 2024 10:40:07 +0100 Message-ID: <73f77d65-9cb4-4d09-a80f-56aed7055732@gmx.at> Date: Thu, 25 Jan 2024 10:40:07 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: bug#68679: 30.0.50; Burying a buffer shows an already displayed buffer Content-Language: en-US To: Eli Zaretskii , sds@gnu.org References: <878r4fmvxy.fsf@gnu.org> <864jf26hlh.fsf@gnu.org> From: martin rudalics In-Reply-To: <864jf26hlh.fsf@gnu.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:K9Zra4XY87dZzHkgJav1Ancd6qNuzRK7Xt3m1eFQECuDNuv4rrf Xj8y/JNIuioAXWXQ92hl6IzLSohw7k5XAuX0YmC4KQQRvHLXcEeIfSeOeCbnSs46ojsHYdo 4fYP2M5U1S1Rmqe1i8oH3w2ZTyV5+mFNgvibZNLZRYQGjRaISIHJjigjARSb4e0D/3ivReg zX/T0L13hBvd4Dx6Q+VkA== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:MIOrzcM/X3w=;F+v7EP5mKJx4O6WTQvbj2MEOCNM mrKxgeCXGRqiHk5INUfasIZTsnf9flqdVjJc86Z4O3ftzeNzldiokjnG4woFU9gUln5QZgT3X 2Qil8lxhKY1jZ2/bleH6+/BlcWocXkZXb6bAodY1qbMl5R7z9oN7zNXw2+hXJUDXXaTv4egwb uWR+n26ZFZU+VeD2lR93iAj/avPJFdjhQJSwAWxKmNUnRXueLTw+MYznWdVsW938jGPGNEu1w XALs9Xz9oyT0HSHH+hYXVQoDMcgXRM7E9A4J+h92MvMfSlOkY0eVtKvOYBqt20tLwxd4ae12v yao/GPFyeMAE2EzeDMRZWplZsscvwEKAzeuPFHT6txmYpVlvLfuLCP0XtCGHBAqbrzz9QQct1 jCQGDxqAIm+RBIg7G0Uz0thaBLbYLlBw91AFIMNlSuVZYgcT7fCNfefPBxqWmUZqypqtTYE+4 FY2o1iLUBriXCi8a+KemE8A870bssRJ1HD9A9TmfhkK5S418fkhnHKskjCkNiIheGtoHqjH35 tmKhYhSPnFvDHWEMYd0DluTGLnKMQrIlOlMCPHM7btXr019heC6aPZOp4muRJResBQwTAwOo8 o6hj9nd4uAsedjSYm7d78dJkn6QEg3aO8BTyfa08+d2yrDN7XerwuF2CnbSBrSdnM9uaeRL87 57kPWl/N2IdLrfkcU8mccV2kVt4AiOBEHmzZ8/Ih6hUuCQg4gWqN0qWofudn5kyo2OCxwNN0Z Wk3zWDNE22/zrptdSPP3L9Luyjgfa63MIALckxnBd57/vGZB+IdIUH6wEQb4Rr2AWDXbgv1Bi DmVxWzw9R7elN3gzVjbOOArpsIZF3B4+rW82CpaeD1eXm/lMKHfalZd2z04qsiPJWYEKa6Ft+ bsrPH7vVMf0h9jT/NmpR4incrUmb7zZbS2g8YYAV1C35G+OgCWPJwP1w9lRx7lCAXvgk3Weqp RQEEQkH+qoxkovVIzZPgi6oR550= X-Spam-Score: 2.9 (++) X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: >> ISTR that quit-window and bury-buffer made sure that the >> replacement/newly displayed buffer is not shown in any other window (at >> least that was my intention when I wrote quit-window many yea [...] Content analysis details: (2.9 points, 10.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 3.6 RCVD_IN_SBL_CSS RBL: Received via a relay in Spamhaus SBL-CSS [213.142.97.167 listed in zen.spamhaus.org] 0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3) [212.227.15.19 listed in wl.mailspike.net] -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at https://www.dnswl.org/, low trust [212.227.15.19 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (rudalics[at]gmx.at) 0.0 RCVD_IN_MSPIKE_WL Mailspike good senders -0.0 T_SCC_BODY_TEXT_LINE No description available. X-Debbugs-Envelope-To: 68679 Cc: 68679@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: 1.9 (+) X-Spam-Report: Spam detection software, running on the system "debbugs.gnu.org", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: >> ISTR that quit-window and bury-buffer made sure that the >> replacement/newly displayed buffer is not shown in any other window (at >> least that was my intention when I wrote quit-window many yea [...] Content analysis details: (1.9 points, 10.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 3.6 RCVD_IN_SBL_CSS RBL: Received via a relay in Spamhaus SBL-CSS [213.142.97.167 listed in zen.spamhaus.org] 0.0 RCVD_IN_MSPIKE_H3 RBL: Good reputation (+3) [212.227.15.19 listed in wl.mailspike.net] -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at https://www.dnswl.org/, low trust [212.227.15.19 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (rudalics[at]gmx.at) 0.0 RCVD_IN_MSPIKE_WL Mailspike good senders -0.0 T_SCC_BODY_TEXT_LINE No description available. -1.0 MAILING_LIST_MULTI Multiple indicators imply a widely-seen list manager >> ISTR that quit-window and bury-buffer made sure that the >> replacement/newly displayed buffer is not shown in any other window (at >> least that was my intention when I wrote quit-window many years ago). >> >> Right now I see that C-x b (switch-to-buffer) offers a good candidate >> (IOW, other-buffer returns a buffer that is not currently shown), but >> both quit-window and bury-buffer replace the current buffer with one >> that is already displayed in another window in the current frame. More precisely "may replace". >> Is there a way to restore the original behavior of never displaying an >> already visible buffer? >> >> Is this a (known) bug? Can you try customizing 'switch-to-prev-buffer-skip'? martin From debbugs-submit-bounces@debbugs.gnu.org Thu Feb 01 04:50:12 2024 Received: (at 68679) by debbugs.gnu.org; 1 Feb 2024 09:50:12 +0000 Received: from localhost ([127.0.0.1]:40240 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rVThz-0004z8-Su for submit@debbugs.gnu.org; Thu, 01 Feb 2024 04:50:12 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:51802) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rVThx-0004yr-98 for 68679@debbugs.gnu.org; Thu, 01 Feb 2024 04:50:10 -0500 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 1rVThh-0004VL-DZ; Thu, 01 Feb 2024 04:49:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=zWMQjmoN7G8jyWovCPyVRbgxK8did+wfN8lvXo/lGDk=; b=a6zMoU0cVen8 fR1Ilt9bi0LJhN602erFf4AEeUhz5rPI8zNvSCUvzZ5ltU4CyVHIZbN2wkBxe8sda4X6F6zgj/bX8 jEJmY4LL09WmQ/CjEGTSnj+8pLE7JlQ3V2nPA1nLgCD/xUUIb2WLsX7IEuydnUldAUN0trO6Ttqis qksn1m6bLoUP1t0idag1kriLOjmLIg/ROsAeiytn1fkqUaTb58YZZsLzTHNSKb1vEgCDgCpEvJWtA m4OIdqdtgJTG0r+8vlzxmcshuFFqYLFBuB/RZs0Hmyl27kYHlrLGrJz8ogN++LqR2dJcjfgFEt/wo BCiyaNc9ZNOL/Yawb5W2qA==; Date: Thu, 01 Feb 2024 11:49:50 +0200 Message-Id: <867cjo1pkx.fsf@gnu.org> From: Eli Zaretskii To: martin rudalics In-Reply-To: <73f77d65-9cb4-4d09-a80f-56aed7055732@gmx.at> (message from martin rudalics on Thu, 25 Jan 2024 10:40:07 +0100) Subject: Re: bug#68679: 30.0.50; Burying a buffer shows an already displayed buffer References: <878r4fmvxy.fsf@gnu.org> <864jf26hlh.fsf@gnu.org> <73f77d65-9cb4-4d09-a80f-56aed7055732@gmx.at> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 68679 Cc: 68679@debbugs.gnu.org, sds@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 (---) > Date: Thu, 25 Jan 2024 10:40:07 +0100 > Cc: 68679@debbugs.gnu.org > From: martin rudalics > > >> ISTR that quit-window and bury-buffer made sure that the > >> replacement/newly displayed buffer is not shown in any other window (at > >> least that was my intention when I wrote quit-window many years ago). > >> > >> Right now I see that C-x b (switch-to-buffer) offers a good candidate > >> (IOW, other-buffer returns a buffer that is not currently shown), but > >> both quit-window and bury-buffer replace the current buffer with one > >> that is already displayed in another window in the current frame. > > More precisely "may replace". > > >> Is there a way to restore the original behavior of never displaying an > >> already visible buffer? > >> > >> Is this a (known) bug? > > Can you try customizing 'switch-to-prev-buffer-skip'? Ping! Sam, can you try Martin's suggestion and tell if it solves your problem? From debbugs-submit-bounces@debbugs.gnu.org Sat Feb 10 03:55:20 2024 Received: (at 68679) by debbugs.gnu.org; 10 Feb 2024 08:55:20 +0000 Received: from localhost ([127.0.0.1]:53633 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rYj8p-0007ry-UJ for submit@debbugs.gnu.org; Sat, 10 Feb 2024 03:55:20 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:57084) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rYj7f-0007mm-B0 for 68679@debbugs.gnu.org; Sat, 10 Feb 2024 03:54:07 -0500 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 1rYiie-0006tw-LC; Sat, 10 Feb 2024 03:28:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=F4WWRCd108kjnGcve1TPqzSlBj6o07cchpjGxowMDNM=; b=sGa14uF02NfL KgH9ns1J0jUy8Smm+LNBngWNNscuX3q4NBcbrOsUpM6k+AQ/SPOeoNHS3biOZbU5CR6gvYrpbE5BD alCFaJRI1deCo5o899RbWqZiErOnoOz6+KpUmsW/f2bePYYHc0gFTp+rLJVmHcR4al58Haa3meXDp oxH++U0qMG8+9Tm08xO13VUAKG0CNmZj2l0XkrxB+wVpFTayO5GvFCQV4ls09VYUgJMDSSyw5bXz8 DKW1kRoQ3XJdGjL5z3+VJ9ZjaCQ4A1VH+4hd/fmX7xvNPkwNeeAAxHDUBw/1TtMKnZJmpHewd9wxO LICSnCzo2+VVnZIcJ+uyYA==; Date: Sat, 10 Feb 2024 10:28:14 +0200 Message-Id: <868r3svi3l.fsf@gnu.org> From: Eli Zaretskii To: sds@gnu.org In-Reply-To: <867cjo1pkx.fsf@gnu.org> (message from Eli Zaretskii on Thu, 01 Feb 2024 11:49:50 +0200) Subject: Re: bug#68679: 30.0.50; Burying a buffer shows an already displayed buffer References: <878r4fmvxy.fsf@gnu.org> <864jf26hlh.fsf@gnu.org> <73f77d65-9cb4-4d09-a80f-56aed7055732@gmx.at> <867cjo1pkx.fsf@gnu.org> X-Spam-Score: -2.3 (--) X-Debbugs-Envelope-To: 68679 Cc: rudalics@gmx.at, 68679@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 (---) Ping! Ping! Sam, can you please try Martin's suggestion? > Cc: 68679@debbugs.gnu.org, sds@gnu.org > Date: Thu, 01 Feb 2024 11:49:50 +0200 > From: Eli Zaretskii > > > Date: Thu, 25 Jan 2024 10:40:07 +0100 > > Cc: 68679@debbugs.gnu.org > > From: martin rudalics > > > > >> ISTR that quit-window and bury-buffer made sure that the > > >> replacement/newly displayed buffer is not shown in any other window (at > > >> least that was my intention when I wrote quit-window many years ago). > > >> > > >> Right now I see that C-x b (switch-to-buffer) offers a good candidate > > >> (IOW, other-buffer returns a buffer that is not currently shown), but > > >> both quit-window and bury-buffer replace the current buffer with one > > >> that is already displayed in another window in the current frame. > > > > More precisely "may replace". > > > > >> Is there a way to restore the original behavior of never displaying an > > >> already visible buffer? > > >> > > >> Is this a (known) bug? > > > > Can you try customizing 'switch-to-prev-buffer-skip'? > > Ping! Sam, can you try Martin's suggestion and tell if it solves your > problem? > > > > From debbugs-submit-bounces@debbugs.gnu.org Sat Feb 17 03:27:02 2024 Received: (at 68679) by debbugs.gnu.org; 17 Feb 2024 08:27:03 +0000 Received: from localhost ([127.0.0.1]:60418 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rbG2I-0005Ti-8v for submit@debbugs.gnu.org; Sat, 17 Feb 2024 03:27:02 -0500 Received: from eggs.gnu.org ([209.51.188.92]:59372) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rbG2G-0005TJ-8O for 68679@debbugs.gnu.org; Sat, 17 Feb 2024 03:27:01 -0500 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 1rbG1q-0007H4-Db; Sat, 17 Feb 2024 03:26:34 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=FRONLmILKWjKro7WB611Mn3ppmv+O8WdZWWM1bD+slo=; b=Szva74q9sMyR 86Nb9kMb8o87GNoCUyXsPSfp2jwZSjRrvP7BZwpzaF9A1VfbSIPgYZuBJrdzWRnoOdspfB4FdTt45 APCOQYmJaGDEox8aOGZS9cA1Jzpd/KOrlJgZMuGLKE++t7oqiLIJkDOoCgUhVXJrtnp9qN/P0y8PJ Ap205eg4xs+VQ7eYp4jEDvL2hZH0sYYiASTN7dmAcLxa2Ahud0nFfZdVrs4vRKsCna6ccQq5RsKLD /0V7mg+yF8O5SKOCSeQkvSS2D4JIQlBva6/BydcHhd0B9OGhiiF5n27C6x4Hd00CrwlYKo0Cb3dJA b7P7OJJTVFiIUHwUW/NRQg==; Date: Sat, 17 Feb 2024 10:26:29 +0200 Message-Id: <86cysvv6mi.fsf@gnu.org> From: Eli Zaretskii To: sds@gnu.org In-Reply-To: <868r3svi3l.fsf@gnu.org> (message from Eli Zaretskii on Sat, 10 Feb 2024 10:28:14 +0200) Subject: Re: bug#68679: 30.0.50; Burying a buffer shows an already displayed buffer References: <878r4fmvxy.fsf@gnu.org> <864jf26hlh.fsf@gnu.org> <73f77d65-9cb4-4d09-a80f-56aed7055732@gmx.at> <867cjo1pkx.fsf@gnu.org> <868r3svi3l.fsf@gnu.org> X-Spam-Score: -4.2 (----) X-Debbugs-Envelope-To: 68679 Cc: rudalics@gmx.at, 68679@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: -5.2 (-----) Ping! Ping! Ping! Sam, any success in trying Martin's suggestion? > Cc: rudalics@gmx.at, 68679@debbugs.gnu.org > Date: Sat, 10 Feb 2024 10:28:14 +0200 > From: Eli Zaretskii > > Ping! Ping! Sam, can you please try Martin's suggestion? > > > Cc: 68679@debbugs.gnu.org, sds@gnu.org > > Date: Thu, 01 Feb 2024 11:49:50 +0200 > > From: Eli Zaretskii > > > > > Date: Thu, 25 Jan 2024 10:40:07 +0100 > > > Cc: 68679@debbugs.gnu.org > > > From: martin rudalics > > > > > > >> ISTR that quit-window and bury-buffer made sure that the > > > >> replacement/newly displayed buffer is not shown in any other window (at > > > >> least that was my intention when I wrote quit-window many years ago). > > > >> > > > >> Right now I see that C-x b (switch-to-buffer) offers a good candidate > > > >> (IOW, other-buffer returns a buffer that is not currently shown), but > > > >> both quit-window and bury-buffer replace the current buffer with one > > > >> that is already displayed in another window in the current frame. > > > > > > More precisely "may replace". > > > > > > >> Is there a way to restore the original behavior of never displaying an > > > >> already visible buffer? > > > >> > > > >> Is this a (known) bug? > > > > > > Can you try customizing 'switch-to-prev-buffer-skip'? > > > > Ping! Sam, can you try Martin's suggestion and tell if it solves your > > problem? > > > > > > > > > > > >