From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Mauro Aranda Newsgroups: gmane.emacs.bugs Subject: bug#6755: 24.0.50; Customize buffer is too wide. Put doc string on separate line. Date: Sat, 21 Sep 2019 14:04:00 -0300 Message-ID: References: <871rwgt32h.fsf@gnus.org> <87tv99loqr.fsf@gnus.org> <780890ec-8e55-4829-942f-b9daf3513908@default> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000210da90593132dc9" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="136132"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Lars Ingebrigtsen , 6755@debbugs.gnu.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Sep 21 19:05: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 1iBioq-000ZIQ-4I for geb-bug-gnu-emacs@m.gmane.org; Sat, 21 Sep 2019 19:05:12 +0200 Original-Received: from localhost ([::1]:42986 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iBioo-0004rZ-Vx for geb-bug-gnu-emacs@m.gmane.org; Sat, 21 Sep 2019 13:05:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50138) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iBioh-0004qH-TR for bug-gnu-emacs@gnu.org; Sat, 21 Sep 2019 13:05:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iBiog-0007i1-Q4 for bug-gnu-emacs@gnu.org; Sat, 21 Sep 2019 13:05:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:52575) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iBiog-0007hP-MD for bug-gnu-emacs@gnu.org; Sat, 21 Sep 2019 13:05:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iBiog-0001m2-En for bug-gnu-emacs@gnu.org; Sat, 21 Sep 2019 13:05:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Mauro Aranda Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 21 Sep 2019 17:05:02 +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.15690854636751 (code B ref 6755); Sat, 21 Sep 2019 17:05:02 +0000 Original-Received: (at 6755) by debbugs.gnu.org; 21 Sep 2019 17:04:23 +0000 Original-Received: from localhost ([127.0.0.1]:33163 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iBio2-0001kp-Mg for submit@debbugs.gnu.org; Sat, 21 Sep 2019 13:04:23 -0400 Original-Received: from mail-lf1-f52.google.com ([209.85.167.52]:34806) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iBio0-0001kV-Bt for 6755@debbugs.gnu.org; Sat, 21 Sep 2019 13:04:20 -0400 Original-Received: by mail-lf1-f52.google.com with SMTP id r22so7186427lfm.1 for <6755@debbugs.gnu.org>; Sat, 21 Sep 2019 10:04:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=v/OsF+QeTu/QB6uH8vC9T18MZ2fpfzpwJGMLGORDCCI=; b=OcT9oju7gIrDpPc18yyauuIHH8llzlgdQkohJVj1zXPl1Woq4uxCpdgtZQhzZf8uDW AfC3UbYfl3pfWLx/Wr7lIWmGDE+FJ6rItHDIO/IKBV+w58y2FGhRQfX65iWtVx+qEfpK BXHIWbwvsUa1kFRes11ym0cyhgmCgZWfXtKUTZTVLgPvMVRC+0VkEj2fMXEA4uoTZAyD ixkTx18nykTTW4DF5nWpJn0bpsbU5AZmFX6vj18m+JrWFgwNx38yIvCu+sHOmjcPYCqa zAFTBFdzhAECSeo0o8moBlJiP8elqvhhaaq37pMRvY+DRM4fSNUT6j0z8O4qhPd/Pybw MNxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=v/OsF+QeTu/QB6uH8vC9T18MZ2fpfzpwJGMLGORDCCI=; b=NTOP/T+nWNf1ApKToJ4aolnXi8jgUqNAovDboBJM7m0Pb51iggh7VWQWT0g3Xfz3XO MxFwnoPYpg0uIwU1oJp5R9obJ6da13U3GbGLcO6n2kBBrJrCDbeeYikQ4Ef67edhFUN8 nHbyhA/E1MMSmDOdUUd3DngipeqeK2i11V4v6rP0iJElIMd6evFD+kj2ZlNIqOL+9NWu Gs+CDspqLgOyuO/0lwqLAUUfSu6fSfTeZMn7pfy1reOd5WHLqDqQVhJmt+DqQy/BRPe4 SUQVZqSksk/MKvaRVMLQT0FBvjYnHC3Df9dJCpIZAYEs3fue6yJt/JDcKp4odP2DoSjC BciA== X-Gm-Message-State: APjAAAWoTN27Gpb/H0qPacXuCj4RueuyGbnZTE6FYJxNN5340ddn2vDn Uqs4mQcG3YzZ0dzMWF6vBunpGX2RORdLGpNI9sI= X-Google-Smtp-Source: APXvYqx5clo8xj52edml7Mjc1BV2Gabh5Ij/8UU8JKJoqmUeH9sGCl1qxGJBchYyK3XoxNLgegqzXeOoIUrgD5P+aCs= X-Received: by 2002:a19:e204:: with SMTP id z4mr11735814lfg.157.1569085454354; Sat, 21 Sep 2019 10:04:14 -0700 (PDT) In-Reply-To: <780890ec-8e55-4829-942f-b9daf3513908@default> 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:166881 Archived-At: --000000000000210da90593132dc9 Content-Type: text/plain; charset="UTF-8" Drew Adams writes: > OP, here. Hello. > FWIW, this enhancement request (or bug report) > did not ask for the doc string to be filled. It > asked for it to be moved to its own line. Those > are not at all the same thing. I see. When I read the bug report, I thought it was just a suggestion to fix the problem of the customize buffer getting too wide. Perhaps I was wrong. > But that's not a fulfillment of _this_ enhancement > request (or bug fix). What's needed for this report > is to move the doc string to its own line. Can that > please be done, or at least considered? May I ask you then, what is the :format option missing for this situation? For example, if one of the const types of the defcustom you provided had the following format-string: (const :tag "Update `*Completions*' incrementally if already displayed" :format "\n%t\n%d" t) then the tag would go to its own line. And that avoids making the customize buffer too wide. > And if you _also_ want to consider filling the doc > string (that should be a separate enhancement > request), please do _not_ do so systematically. Let > users choose to do that (opt in), with a user option. I take all the points you raised about the filling option, but I think it might be better to at least postpone that discussion. --000000000000210da90593132dc9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Drew Adams <dr= ew.adams@oracle.com> writes:

> OP, here.

Hello.
=
> FWIW, this enhancement request (or bug report)
> did not ask= for the doc string to be filled.=C2=A0 It
> asked for it to be moved= to its own line.=C2=A0 Those
> are not at all the same thing.
I see.=C2=A0 When I read the bug report, I thought it was just a suggestio= n to
fix the problem of the customize buffer getting too wide.=C2=A0 Per= haps I was
wrong.

> But that's not a fulfillment of _this_= enhancement
> request (or bug fix).=C2=A0 What's needed for this= report
> is to move the doc string to its own line.=C2=A0 Can that> please be done, or at least considered?

May I ask you then, w= hat is the :format option missing for this situation?

For example, i= f one of the const types of the defcustom you provided
had the following= format-string:
(const
=C2=A0:tag
=C2=A0"Update `*Completion= s*' incrementally if already displayed"
=C2=A0:format "\n%= t\n%d"
=C2=A0t)

then the tag would go to its own line.=C2=A0= And that avoids making the
customize buffer too wide.

> And i= f you _also_ want to consider filling the doc
> string (that should b= e a separate enhancement
> request), please do _not_ do so systematic= ally.=C2=A0 Let
> users choose to do that (opt in), with a user optio= n.

I take all the points you raised about the filling option, but I = think
it might be better to at least postpone that discussion.
--000000000000210da90593132dc9--