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: Tab bar tabs landed on master Date: Sun, 06 Oct 2019 00:55:33 +0300 Organization: LINKOV.NET Message-ID: <87tv8myi8m.fsf@mail.linkov.net> References: <8736gci5jn.fsf@mail.linkov.net> <87zhikp0ba.fsf@mail.linkov.net> <87lfu4jbbu.fsf@Ergus.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="11901"; 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: Juanma Barranquero , Emacs developers To: Ergus Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 05 23:58:49 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 1iGs4e-0002ul-EX for ged-emacs-devel@m.gmane.org; Sat, 05 Oct 2019 23:58:48 +0200 Original-Received: from localhost ([::1]:58964 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iGs4c-0004Z8-HS for ged-emacs-devel@m.gmane.org; Sat, 05 Oct 2019 17:58:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47713) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iGs4I-0004XC-SV for emacs-devel@gnu.org; Sat, 05 Oct 2019 17:58:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iGs4G-0003hy-C5 for emacs-devel@gnu.org; Sat, 05 Oct 2019 17:58:25 -0400 Original-Received: from chocolate.birch.relay.mailchannels.net ([23.83.209.35]:8220) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iGs4F-0003hK-Qb for emacs-devel@gnu.org; Sat, 05 Oct 2019 17:58:24 -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 4550C6A0F69; Sat, 5 Oct 2019 21:58:21 +0000 (UTC) Original-Received: from pdx1-sub0-mail-a36.g.dreamhost.com (100-96-45-148.trex.outbound.svc.cluster.local [100.96.45.148]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id A4C866A121F; Sat, 5 Oct 2019 21:58:20 +0000 (UTC) X-Sender-Id: dreamhost|x-authsender|jurta@jurta.org Original-Received: from pdx1-sub0-mail-a36.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.3); Sat, 05 Oct 2019 21:58:21 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|jurta@jurta.org X-MailChannels-Auth-Id: dreamhost X-Abortive-Ski: 04f68c200a0cbff4_1570312700936_3516088686 X-MC-Loop-Signature: 1570312700936:1412852401 X-MC-Ingress-Time: 1570312700935 Original-Received: from pdx1-sub0-mail-a36.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a36.g.dreamhost.com (Postfix) with ESMTP id 56D2881818; Sat, 5 Oct 2019 14:58:15 -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; s=linkov.net; bh=6nt9tuo4DZOAsyLkD2qRyg0YmZY=; b= j3ROOp4sVV8QWBzWGCPtz3FZLuUMmz2xMEAGqRF8027ISFL1zRWSz0GZD+f5O20/ s8NVIaOSPhAJ89wLKFoi6ATTLeEuwdDmaaPDJ/viWrOKXuJFU7FY0OsZlnQdzVEo 1ZrThMwJgPcBaJZwCg1audTYdzGRcPBSCqhTE1UJvos= Original-Received: from mail.jurta.org (m91-129-99-99.cust.tele2.ee [91.129.99.99]) (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-a36.g.dreamhost.com (Postfix) with ESMTPSA id 156A881817; Sat, 5 Oct 2019 14:58:12 -0700 (PDT) X-DH-BACKEND: pdx1-sub0-mail-a36 In-Reply-To: <87lfu4jbbu.fsf@Ergus.i-did-not-set--mail-host-address--so-tickle-me> (Ergus's message of "Wed, 2 Oct 2019 01:27:41 +0200") X-VR-OUT-STATUS: OK X-VR-OUT-SCORE: -100 X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedufedrheefgdduieekucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufhofhffjgfkfgggtgesthdtredttdertdenucfhrhhomheplfhurhhiucfnihhnkhhovhcuoehjuhhriheslhhinhhkohhvrdhnvghtqeenucfkphepledurdduvdelrdelledrleelnecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopehmrghilhdrjhhurhhtrgdrohhrghdpihhnvghtpeeluddruddvledrleelrdelledprhgvthhurhhnqdhprghthheplfhurhhiucfnihhnkhhovhcuoehjuhhriheslhhinhhkohhvrdhnvghtqedpmhgrihhlfhhrohhmpehjuhhriheslhhinhhkohhvrdhnvghtpdhnrhgtphhtthhopehsphgrtghisggsrgesrgholhdrtghomhenucevlhhushhtvghrufhiiigvpedt X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 23.83.209.35 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:240633 Archived-At: > I would like to ask you the possibility to make the tab-bar-switch-* > commands cyclic (after last go to first) even if not by default? The > problem is that in xterm (and related) it is not possible to sent > C-S-TAB, so in some cases (few tabs) it will be good enough to repeat > C-TAB. Even without this xterm issues it is easier to repeat C-TAB 2 or > 3 times than changing the hands to type C-S-TAB. Now cyclic switching implementation is pushed to master. Some examples of prefix arguments that support cycling: C-2 C-TAB switches to the second next tab C-- C-TAB switches to the previous tab These switching commands interpret their arg as relative offsets. If you want to select a tab by its absolute position, this is now possible with e.g. (dotimes (i 9) (global-set-key (vector (list 'super (+ i 1 ?0))) 'tab-bar-select-tab)) I don't know what prefix key or modifier could be used by default, but this example allows `s-1' to select the first tab in the tab bar, `s-2' the second, etc. A new option tab-bar-tab-hints shows absolute positions of tabs in the tab bar to help in selecting tabs by their numbers. The same way now the arg is interpreted by tab-close as the absolute position of tab to close, so e.g. C-2 C-x 6 0 closes the second tab (instead of the current tab by default) tab-new could support the prefix argument as well, but I don't know whether to interpret its numeric prefix argument as absolute or relative position because both ways are useful: C-2 C-x 6 2 - could create a new tab as the second tab in the tab-bar OR C-2 C-x 6 2 - create a new tab as the second next to the right from the current tab C-u -2 C-x 6 2 - create a new tab as the second previous to the left from the current tab Maybe to add a rule that if tab-bar-new-tab-to option has a relative value like 'right' then M-x tab-new should interpret its arg as relative, or if tab-bar-new-tab-to option has an absolute value like 'rightmost' then M-x tab-new should interpret arg as absolute? Or maybe to add a new command tab-add as a wrapper for tab-new to translate its relative arg to absolute number for tab-new?