[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Value menu value should be listed on a separate line
From: |
Drew Adams |
Subject: |
RE: Value menu value should be listed on a separate line |
Date: |
Fri, 22 Dec 2006 16:31:24 -0800 |
> >> > 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?
>
> Usually with ":entry-format" and ":format".
No special formatting should be necessary, just to be able to use a simple
tag. I don't believe that was why :*format were introduced.
> > 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.
>
> I'm convinced that writers of defcustoms should care about the layout.
OK, you're convinced. I said that they should not *need* to concern
themselves with the layout of stuff, beyond their own creations. This is a
flaw in the basic layout, which should not be shoved off onto the definers
of individual values, to work around. It should be trivial to fix, no less -
why not fix the general case, instead of making writers of each value work
around it over and over?