RE: Value menu value should be listed on a separate line

[Drew Adams]

>  > When a value menu is present, the current value should be on a
>  > separate line from the Value Menu button. Currently, the current value
>  > is listed next to the Value Menu button, which makes the Customize
>  > buffer far too wide.
>
> The author of an option is responsible for its appearance.

Uh, how is the author supposed to start a value that has a tag on a separate
line?

If you have a :tag, you have a :tag. Here's an example:

(defcustom foo 'foo1
  "*Whatever"
  :type `(choice
          (const :tag "This is a 70-char string describing this value" foo1)
          (const :tag "Another substantially long string" foo2))
  :group 'mygroup)

The :tag of the default value, foo1, is displayed to the right of the Value
Menu button, after a space. Tell me how to avoid that, and have it be
displayed on the next line, starting at column 1. Depending on the number of
chars in the option name, the column after the Value Menu button might
easily be near 70, just to start with. To that is added the length of the
:tag string.

Writers of defcustom's shouldn't need to concern themselves with the layout
of the Customize buffer, anyway. They should be able to define a :tag string
without the preoccupation of its starting position and the number of
characters already taken up by the option name and the button widths.

>  > Tags for menu items are generally less than 81
>  > characters wide. Putting the value (tag) on a separate line would mean
>  > that the entire buffer would generally be no more than 80 chars
>  > wide. Currently, a buffer with a 70-char value has a width of about
>  > 134.
>
> This should be decided for each option individually.

How? See above.