From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.bugs Subject: bug#6755: 24.0.50; Customize buffer is too wide. Put doc string on separate line. Date: Sun, 22 Sep 2019 14:30:48 +0200 Message-ID: <87pnjswm13.fsf@gnus.org> References: <871rwgt32h.fsf@gnus.org> <87tv99loqr.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="101994"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: 6755@debbugs.gnu.org To: Mauro Aranda Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Sep 22 14:31:13 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1iC11D-000QOJ-4L for geb-bug-gnu-emacs@m.gmane.org; Sun, 22 Sep 2019 14:31:11 +0200 Original-Received: from localhost ([::1]:46596 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iC11C-0000JC-15 for geb-bug-gnu-emacs@m.gmane.org; Sun, 22 Sep 2019 08:31:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57810) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iC115-0000J4-A3 for bug-gnu-emacs@gnu.org; Sun, 22 Sep 2019 08:31:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iC114-0005Qe-6Q for bug-gnu-emacs@gnu.org; Sun, 22 Sep 2019 08:31:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:52883) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iC114-0005QY-37 for bug-gnu-emacs@gnu.org; Sun, 22 Sep 2019 08:31:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iC113-0003yU-UE for bug-gnu-emacs@gnu.org; Sun, 22 Sep 2019 08:31:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Lars Ingebrigtsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 22 Sep 2019 12:31:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 6755 X-GNU-PR-Package: emacs Original-Received: via spool by 6755-submit@debbugs.gnu.org id=B6755.156915545614972 (code B ref 6755); Sun, 22 Sep 2019 12:31:01 +0000 Original-Received: (at 6755) by debbugs.gnu.org; 22 Sep 2019 12:30:56 +0000 Original-Received: from localhost ([127.0.0.1]:33471 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iC10w-0003rF-7S for submit@debbugs.gnu.org; Sun, 22 Sep 2019 08:30:56 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:36810) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iC10u-0003pF-KI for 6755@debbugs.gnu.org; Sun, 22 Sep 2019 08:30:53 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=marnie) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iC10r-0003nn-50; Sun, 22 Sep 2019 14:30:51 +0200 In-Reply-To: (Mauro Aranda's message of "Sat, 21 Sep 2019 07:53:53 -0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:166900 Archived-At: Mauro Aranda writes: > As it stands now, yes, all widgets in customize would get its tag > filled, unless a different :create function is provided for that > widget. > > I didn't thought of the case of wanting one widget with its tag filled > and another one with its tag not filled, in a customize buffer. I didn't > see the need in that. When would that be a good thing? If we're adding a way to allow controlling whether to fill or not, then it should be flexible. > If it makes sense, a widget could have a :fill property set to t, for > example, and in the code that calls the widget creation functions (e.g., > widget-create), widget-fill-tag-string would be bound to t. This goes, > of course, for all other users of the widget library. Yes, adding a :fill property sounds better to me... -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no