From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#69993: Wrap window buffers while cycling Date: Fri, 29 Mar 2024 09:45:24 +0100 Message-ID: References: <86h6gug41x.fsf@mail.linkov.net> <3419df35-1b96-4a64-8ed7-722a05c58742@gmx.at> <86le66ckhj.fsf@mail.linkov.net> <86h6gs2lk7.fsf@mail.linkov.net> <5c71ea64-0f97-4b90-af61-1156fe33f1ea@gmx.at> <86cyreu78w.fsf@mail.linkov.net> <463c9242-56ef-4c99-9fe6-4b70be2071b2@gmx.at> <86sf0abeg3.fsf@mail.linkov.net> Reply-To: martin rudalics Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36882"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla Thunderbird Cc: 69993@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Mar 29 09:46:25 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 1rq7sX-0009Q0-Ad for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 29 Mar 2024 09:46:25 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rq7sB-000176-Rr; Fri, 29 Mar 2024 04:46:03 -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 1rq7s9-00015x-GI for bug-gnu-emacs@gnu.org; Fri, 29 Mar 2024 04:46:01 -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 1rq7s9-0000Qd-8I for bug-gnu-emacs@gnu.org; Fri, 29 Mar 2024 04:46:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rq7sA-0005Wg-Co for bug-gnu-emacs@gnu.org; Fri, 29 Mar 2024 04:46:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 29 Mar 2024 08:46:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 69993 X-GNU-PR-Package: emacs Original-Received: via spool by 69993-submit@debbugs.gnu.org id=B69993.171170193621095 (code B ref 69993); Fri, 29 Mar 2024 08:46:02 +0000 Original-Received: (at 69993) by debbugs.gnu.org; 29 Mar 2024 08:45:36 +0000 Original-Received: from localhost ([127.0.0.1]:41678 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rq7rk-0005U7-0G for submit@debbugs.gnu.org; Fri, 29 Mar 2024 04:45:36 -0400 Original-Received: from mout.gmx.net ([212.227.15.19]:50391) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rq7rg-0005TA-ND for 69993@debbugs.gnu.org; Fri, 29 Mar 2024 04:45:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.at; s=s31663417; t=1711701925; x=1712306725; i=rudalics@gmx.at; bh=dtecStb3F/mhO7e85VZLjEsEE1ThDNBcZfGJlau4noM=; h=X-UI-Sender-Class:Date:Subject:To:Cc:References:From: In-Reply-To; b=Tdvttyxdsn7sTy39Lpy0pRKUbo/BpahQCKXDS5lInkptR6TXWsblhdpYlpToMYlD 7IFhfdJlYCly7adkFTuLMpfzcQFYsUIIJ+IfN12lC3tXnR0G4r7fLD7e8ojfAxMRX aSy/YchEFNsJroJWpu8zNwVEB6q5YTzmkE9hz0rZ3NYBsgDRsruKBVFjRaA1AA8lD Y3+PM9uVGLTx5GdtezEJHqknfgpABRi65C/EjSA+Us8WpPTFPrsXDJUlBKaCDNmTk /2dfsKlRrR7Z8vsFfCW2qoG5fj3zEdB5iffSl2Afg/qYiMt+J2DUa04t/5B/aaarB lyRK1FBC2YyHcO0Rvg== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Original-Received: from [192.168.31.113] ([46.125.249.18]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MV67o-1sElTn07cM-00SB2q; Fri, 29 Mar 2024 09:45:25 +0100 Content-Language: en-US In-Reply-To: <86sf0abeg3.fsf@mail.linkov.net> X-Provags-ID: V03:K1:smI0BphHrDLF06vOm5+zKlx/8ax9lMcsST6wzMvzMujUNTpWWCa /y1aCR1DkLclVjSDLEqlsoWZ7tS//u4m3w/T02mSkUbEfZTdc0gsW0UPUdqYk47HWL7Zkjj iaay4RCNc3sp+EL5NLeee/vAvtUW4XwtP4CBiQR+4bSQoCZ6hdrJd8HlZD50+pt6nlN3Yfo JaUiWWKeD88iaDjUWNLbQ== UI-OutboundReport: notjunk:1;M01:P0:8Wu9XaUraUk=;XJUwIZs50EEMKRmx/kyz1ZSINMB nKOpuVExkM2HyIpkgO3UgVyKzg52Qc5w+HmhWMnV80DwJEGKVDfnzsEdBf31ny2vC1GUnj6my DrsLK6ywCK2PCBO8nODJgjmBXmlFA9ALVzGJlnDGv/+Ei91grdqK8LD0Ln6kE1KU1IkECcj+V 0+ER2n0fFYevZjWDpi2SkVkDSlUfboVByHMrW6JtloieFYD/kX2cLNmyzVzZIYlq+X5C8hVqG sRVaIzxn4tcsldL7S25dyv2pHB5nPZK6rIZxAZtzD6+QLHSG1tDiqaDxZaDOJtmybTLPWx6LR hF2LNJmJWuURyBLU+lhe2LKwdYzfjMBzYD5/nkbuDJVFIePb01x230FgLJyqOhsvzHLuu0hl7 jrt779zSimlOQQjqjrA9Rj9mrUbEtdD2Ei/EKqq6fMwktuwgmtI3vK77Cf5sRDza4ErhlkY0t R5yECRGJjtYqBjBT+7hb+xytnznK+MlmWjt6MvcEx/iCZqCVTHEWJBbaZMTCldvAMNkSIRYwr cXMkWuiXnwJ4KzKzMDyvsQyhKpV/XaXGWyr7bBvUFc1k5SGI5jmUghKgJ0rNzANT1GYVH7EJ8 BtWhCGBB0IoPBkaNxzxkfvGuJSFZvN5p8eXeUnebQwmje8cv7u13iTSUjf+0eP28O41LEDCAk /E1B/CLfWYl++OIHxOb9s6aFhgJzBsXqsA5QK+aCl2nyQeIeo9nWt6q/NA242HvprD6y9hYlc uyTPX2wM5K/FURBTzTfZnDRtHy17NB9uSupNII9PwUsX26YIVzg94bl711BuMe42zBRqLxGC 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:282277 Archived-At: >> (1) The classic behavior where switching may show a buffer never shown >> in the window before. I suppose you mean that >> 'switch-to-prev-buffer-wrap' does not affect it. If that's the >> case, please say so. > > Indeed, 'switch-to-prev-buffer-wrap' does not affect it. > Switching to a buffer that was never shown in the window > should still reset the list of next-buffers to nil. > >> (2) The new behavior where switching may only show buffers shown in that >> window before. For this you want to either wrap or not. So the >> option 'switch-to-prev-buffer-wrap' will affect (2) only. Right? > > 'switch-to-prev-buffer-wrap' will affect only 'C-x C-left' and 'C-x C-right' > cycling buffers shown in that window before. I'm still confused. Do you mean that C-x b, when it switches to a buffer previously shown in that window, should not change the ordering of buffers previously shown in that window? And behave so if and only if 'switch-to-prev-buffer-wrap' is non-nil? Then what would users do if they (1) want to use your new option but (2) still want C-x b or C-x C-left make that buffer the most previously used one in that window? martin