From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Fix width tabs Date: Sat, 05 Nov 2022 19:28:43 +0200 Message-ID: <83iljt2tv8.fsf@gnu.org> References: <87wnhtfad7.fsf@gmail.com> <865ypcmx6s.fsf@mail.linkov.net> <87sfsgfd2b.fsf@gmail.com> <86mtimzt13.fsf@mail.linkov.net> <86fsock4f1.fsf@mail.linkov.net> <867d0lww7o.fsf@mail.linkov.net> <87k04h850x.fsf@gmail.com> <86tu3hxmkz.fsf@mail.linkov.net> <86tu3fnor9.fsf@mail.linkov.net> <83r0yj5ehy.fsf@gnu.org> <865yfts53l.fsf@mail.linkov.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21262"; mail-complaints-to="usenet@ciao.gmane.io" Cc: orontee@gmail.com, emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 05 18:48:39 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 1orNHa-0005Ks-Kp for ged-emacs-devel@m.gmane-mx.org; Sat, 05 Nov 2022 18:48:38 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1orMyV-0006f1-Oi; Sat, 05 Nov 2022 13:28:55 -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 1orMyU-0006ah-67 for emacs-devel@gnu.org; Sat, 05 Nov 2022 13:28:54 -0400 Original-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 1orMyT-0000kc-JD; Sat, 05 Nov 2022 13:28:53 -0400 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=TFEIYFGkYo+PWRc7XGi386W7bz/llmqwSC7cfV0oBbc=; b=RUxspspDA7VU eevjilU0MVewSbkcx4Y8E6uUXPT3OB7fopE3eHmjOzVNVRyWMFyKsO5EVCjuNrHrGMtOSdnRS2vMo +769yFmFmGLBwJdiSo1NBcN+1BYYM4Gbq1PJkR81rFCM+c9ePRXcxQxK37IlwEj+dYWGCmcbgMVv3 hMQQJIXtglDx00yZmoDaWm2Vq2oC1DCJyo5IyJ+ZDjOzYnQ5G+4czE2VYxTxTpPnjHMSXRzelUXTk vhioCH9ZuA1Rmo9YskIQhH2+Ba0br4tRJ1+BD3LCXgt4WZ8/7TYbjGyTz3UWnha23B9ZZWdSE+mBM EQYQMAWcvfjbupunTbilMw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1orMyR-0007ii-5H; Sat, 05 Nov 2022 13:28:52 -0400 In-Reply-To: <865yfts53l.fsf@mail.linkov.net> (message from Juri Linkov on Sat, 05 Nov 2022 19:12:54 +0200) 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: , Original-Sender: "Emacs-devel" Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:299225 Archived-At: > From: Juri Linkov > Cc: orontee@gmail.com, emacs-devel@gnu.org > Date: Sat, 05 Nov 2022 19:12:54 +0200 > > > This begs the question: what is the fixed width to which the tabs are > > resized? if it's "fixed", then the value is known in advance, right? > > Moreover, if the tab sizes are fixed, why does the doc string say > > "automatically resize"? "resizing" is the antithesis of "fixed width". > > Maybe a better name would be `tab-bar-auto-resize'? > But this name will be confused with the existing > `auto-resize-tab-bars' that resizes the tab-bar's height, > not width. We can think about a good name for the variable when we have a good understanding of the behavior it changes. > > Can you explain in plain words what this option does, when it is > > non-nil? (There's a hint to that in the doc string of > > tab-bar-fixed-width-max, but that's not the right place for this > > information.) Also, what does it do when it's nil? > > When tab-bar-fixed-width is non-nil, tabs are distributed evenly > across the tab-bar. When also tab-bar-fixed-width-max is a number, > then tab names are truncated to the defined width. > > In any case, short tab names are filled with spaces. > Currently there is no option to avoid filling with spaces. > Maybe tab-bar-fixed-width could also support a new value > 'shrink-only' for this. Ok, and what happens when tab-bar-fixed-width is nil? > > The style of the doc string is also problematic: we shouldn't describe > > in a doc string of user option what problems it solves. Instead, we > > should tell what is the behavior for each valid value of the option; > > the judgment of what is a "problem" and what isn't is left to the > > user, because the needs of users may differ, and what is a "problem" > > for some is a "solution" to others. That's why we have user options > > to begin with. > > > > The NEWS entry is also problematic, basically for the same reason. > > Maybe the description of problems should be moved from the doc string > to NEWS? No, I don't think so. I believe if we explain the behavior with both nil and non-nil values, users will understand what it does for them in various situations, and we won't need to qualify anything as a "problem". Thanks.