From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, maurooaranda@gmail.com, 6755@debbugs.gnu.org
Subject: bug#6755: 24.0.50; Customize buffer is too wide. Put doc string on separate line.
Date: Sun, 22 Sep 2019 17:55:56 +0300 [thread overview]
Message-ID: <837e60qt1f.fsf@gnu.org> (raw)
In-Reply-To: <db8fbc61-0816-4750-a04f-62d7a2858849@default> (message from Drew Adams on Sat, 21 Sep 2019 22:36:23 +0000 (UTC))
> Date: Sat, 21 Sep 2019 22:36:23 +0000 (UTC)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 6755@debbugs.gnu.org
>
> The bug report just asks that the first line of a doc
> string be put on its own line, and likewise for :tag
> lines.
There's some kind of serious confusion in this bug report. The text
that is displayed to the right of the "Value Menu" button is not the
doc string, it's the textual description of the current value.
Therefore, it makes no sense at all to start that text on a new line.
I also don't see how filling of any kind can make the situation better
when the textual description is too long.
Reading the discussions, I think they were mostly based on the above
misunderstanding, so I think we should either close this bug, or maybe
start discussing it anew, after forgetting everything that was said
and suggested, because none of that makes sense to me.
next prev parent reply other threads:[~2019-09-22 14:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 16:29 bug#6755: 24.0.50; Customize buffer is too wide. Put doc string on separate line Drew Adams
2011-07-03 13:17 ` Lars Magne Ingebrigtsen
2011-07-03 14:13 ` Drew Adams
2011-07-03 14:51 ` Lars Magne Ingebrigtsen
2011-07-03 15:12 ` Drew Adams
2011-07-03 15:19 ` Lars Magne Ingebrigtsen
2011-07-04 4:48 ` Drew Adams
2011-07-04 12:24 ` Lars Magne Ingebrigtsen
2011-07-04 16:21 ` Drew Adams
2011-07-05 13:36 ` Lars Magne Ingebrigtsen
2011-07-03 15:25 ` Lars Magne Ingebrigtsen
2019-09-16 14:54 ` Mauro Aranda
2019-09-16 20:10 ` Lars Ingebrigtsen
2019-09-17 12:04 ` Mauro Aranda
2019-09-18 13:26 ` Lars Ingebrigtsen
2019-09-21 10:53 ` Mauro Aranda
2019-09-21 14:44 ` Drew Adams
2019-09-21 17:04 ` Mauro Aranda
2019-09-21 22:36 ` Drew Adams
2019-09-22 14:55 ` Eli Zaretskii [this message]
2019-09-22 17:24 ` Mauro Aranda
2019-09-22 19:11 ` Eli Zaretskii
2019-09-22 12:30 ` Lars Ingebrigtsen
[not found] <<CABczVwc9RpGvxYMTX8iSvhFqJ2eBZLvHvaWsZ4n2FZfYh_KZvg@mail.gmail.com>
[not found] ` <<871rwgt32h.fsf@gnus.org>
[not found] ` <<CABczVwd85QoEXfyRw-kskvSh_fB4GBdOC7HrTsM=0p8m8_JRnQ@mail.gmail.com>
[not found] ` <<87tv99loqr.fsf@gnus.org>
[not found] ` <<CABczVwe3QoPxeCAzNUdGFUgwE1YLTe6rDk73j-XH-_ppWp6=OA@mail.gmail.com>
[not found] ` <<780890ec-8e55-4829-942f-b9daf3513908@default>
[not found] ` <<CABczVwfyLe4wFKKd7gU-E8jgNEg_pAup=ymdrr1yGWbTZHTzCA@mail.gmail.com>
[not found] ` <<db8fbc61-0816-4750-a04f-62d7a2858849@default>
[not found] ` <<837e60qt1f.fsf@gnu.org>
2019-09-22 16:09 ` Drew Adams
2019-09-22 16:57 ` Eli Zaretskii
2019-09-23 10:10 ` Lars Ingebrigtsen
[not found] <<<CABczVwc9RpGvxYMTX8iSvhFqJ2eBZLvHvaWsZ4n2FZfYh_KZvg@mail.gmail.com>
[not found] ` <<<871rwgt32h.fsf@gnus.org>
[not found] ` <<<CABczVwd85QoEXfyRw-kskvSh_fB4GBdOC7HrTsM=0p8m8_JRnQ@mail.gmail.com>
[not found] ` <<<87tv99loqr.fsf@gnus.org>
[not found] ` <<<CABczVwe3QoPxeCAzNUdGFUgwE1YLTe6rDk73j-XH-_ppWp6=OA@mail.gmail.com>
[not found] ` <<<780890ec-8e55-4829-942f-b9daf3513908@default>
[not found] ` <<<CABczVwfyLe4wFKKd7gU-E8jgNEg_pAup=ymdrr1yGWbTZHTzCA@mail.gmail.com>
[not found] ` <<<db8fbc61-0816-4750-a04f-62d7a2858849@default>
[not found] ` <<<837e60qt1f.fsf@gnu.org>
[not found] ` <<8a2c1a21-5498-4e5d-a28c-88810ad7aa10@default>
[not found] ` <<83v9tkp8ui.fsf@gnu.org>
2019-09-22 22:56 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=837e60qt1f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6755@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=maurooaranda@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.