From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Should tab-next cycle instead of stopping? Date: Sun, 13 Oct 2019 00:53:04 +0300 Organization: LINKOV.NET Message-ID: <87o8yl7hrz.fsf@mail.linkov.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="162953"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) Cc: emacs-devel@gnu.org To: Pankaj Jangid Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 12 23:57:35 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iJPOI-000gHh-Fy for ged-emacs-devel@m.gmane.org; Sat, 12 Oct 2019 23:57:35 +0200 Original-Received: from localhost ([::1]:36250 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iJPOG-00054B-0x for ged-emacs-devel@m.gmane.org; Sat, 12 Oct 2019 17:57:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37054) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iJPN8-0004Xg-D2 for emacs-devel@gnu.org; Sat, 12 Oct 2019 17:56:23 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iJPN7-0008Q2-1W for emacs-devel@gnu.org; Sat, 12 Oct 2019 17:56:22 -0400 Original-Received: from bumble.birch.relay.mailchannels.net ([23.83.209.25]:32053) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iJPN6-0008Pi-L5 for emacs-devel@gnu.org; Sat, 12 Oct 2019 17:56:20 -0400 X-Sender-Id: dreamhost|x-authsender|jurta@jurta.org Original-Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id B1BF2740D81; Sat, 12 Oct 2019 21:56:18 +0000 (UTC) Original-Received: from pdx1-sub0-mail-a3.g.dreamhost.com (100-96-91-110.trex.outbound.svc.cluster.local [100.96.91.110]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 2F33E740C82; Sat, 12 Oct 2019 21:56:18 +0000 (UTC) X-Sender-Id: dreamhost|x-authsender|jurta@jurta.org Original-Received: from pdx1-sub0-mail-a3.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.5); Sat, 12 Oct 2019 21:56:18 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|jurta@jurta.org X-MailChannels-Auth-Id: dreamhost X-Language-Cellar: 145d3e480c76d292_1570917378389_890201065 X-MC-Loop-Signature: 1570917378389:3642221070 X-MC-Ingress-Time: 1570917378388 Original-Received: from pdx1-sub0-mail-a3.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a3.g.dreamhost.com (Postfix) with ESMTP id F08EC84311; Sat, 12 Oct 2019 14:56:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=linkov.net; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type:content-transfer-encoding; s=linkov.net; bh=BOwSQW 3DXVggeh7GVpJbiBqvoME=; b=Fv19vrYV3/ejpH2No5nWM3996hcael/7FH8z+1 EWYRLMSIWKDXqKrgwQhc7oOZbhOsqxufGn6MIqktzU0ecfBN6TVQptEzm1C1WNgQ lMFRhecGdhhrdWyBJ6+U1fKVRm7hlxxeB9ju6txOzlxI8Zr9XRkOphBiWl9lIJtq y+owo= Original-Received: from mail.jurta.org (m91-129-105-34.cust.tele2.ee [91.129.105.34]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jurta@jurta.org) by pdx1-sub0-mail-a3.g.dreamhost.com (Postfix) with ESMTPSA id A2CAA842F8; Sat, 12 Oct 2019 14:56:11 -0700 (PDT) X-DH-BACKEND: pdx1-sub0-mail-a3 In-Reply-To: (Pankaj Jangid's message of "Fri, 11 Oct 2019 08:32:48 +0530") X-VR-OUT-STATUS: OK X-VR-OUT-SCORE: -100 X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedufedrieekgddthecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvffuohhfffgjkfgfgggtgfesthekredttderjeenucfhrhhomheplfhurhhiucfnihhnkhhovhcuoehjuhhriheslhhinhhkohhvrdhnvghtqeenucfkphepledurdduvdelrddutdehrdefgeenucfrrghrrghmpehmohguvgepshhmthhppdhhvghlohepmhgrihhlrdhjuhhrthgrrdhorhhgpdhinhgvthepledurdduvdelrddutdehrdefgedprhgvthhurhhnqdhprghthheplfhurhhiucfnihhnkhhovhcuoehjuhhriheslhhinhhkohhvrdhnvghtqedpmhgrihhlfhhrohhmpehjuhhriheslhhinhhkohhvrdhnvghtpdhnrhgtphhtthhopehprghnkhgrjhdrjhgrnhhgihgusehgmhgrihhlrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 23.83.209.25 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:240937 Archived-At: >> If you have two tabs in the current frame, and you're in the first tab= , >> C-tab moves to the second tab. At that pointthe next C-tab appears to = do >> nothing, a subsequent C-tab moves to the first tab. >> >> Is that a bug or a feature? >> >> Would be nice if C-tab just treated the tabs in the current frame as a >> ring that it cycles through ... > > I don't know if that is a feature or not but your email got me thinking= . > > It would be a good idea if C-tab beeps at the last tab and a subsequent > C-tab moves to the first tab. When there are lots of tabs open, this > will give an indication that the user has reached the last tab. IOW, should it be like isearch wrapping? This has one problem: when used with a numeric argument it stops at the end, e.g. =E2=80=98C-u 3 C-s=E2=80=99 doesn't jump to the third match from the begi= nning of the buffer. Instead, it stops at the end of the buffer and beeps. Currently =E2=80=98C-u 3 C-TAB=E2=80=99 silently wraps to the next third = tab even from the beginning of the tab-bar with predictable outcome. Signaling at the end of the tab-bar won't allow to visually calculate and predict on what tab =E2=80=98C-u 3 C-TAB=E2=80=99 will arrive. > And of course this is Emacs. This behaviour should be configurable. Maybe configurable like multi-isearch-pause? But before implementing this, I'd like to understand if such overshooting is a real problem. Isn't easy in this case to go back with C-S-TAB?