unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lars Magne Ingebrigtsen'" <larsi@gnus.org>
Cc: 6755@debbugs.gnu.org
Subject: bug#6755: 24.0.50; Customize buffer is too wide. Put doc string on separate line.
Date: Mon, 4 Jul 2011 09:21:12 -0700	[thread overview]
Message-ID: <75CF15637AB140EB9125E7B88FCBD6A7@us.oracle.com> (raw)
In-Reply-To: <m3pqlqxmha.fsf@quimbies.gnus.org>

> Starting with a newline didn't look very nice.  Most of the option
> values are short, and moving them away from the button made the
> interface less understandable.
> 
> I think the right solution is to output the string where it 
> is now, but to fill it if it's too long.

Why not just start it on a new line if it would wrap?

IOW, instead of just filling, if it would wrap then start it on a new line.

(You could also then fill it, after starting on a new line, but I doubt that
:tag string will be more than 70 chars.  Still, it wouldn't hurt to do that.)






  reply	other threads:[~2011-07-04 16:21 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=75CF15637AB140EB9125E7B88FCBD6A7@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=6755@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).