[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New behavior
From: |
Eli Zaretskii |
Subject: |
Re: New behavior |
Date: |
Sun, 16 Sep 2018 20:01:50 +0300 |
> Date: Sun, 16 Sep 2018 09:29:53 -0700 (PDT)
> From: Drew Adams <address@hidden>
> Cc: address@hidden
>
> > The Customize UI is for users who are not necessarily Lisp
> > programmers, so the Value Menu should show the human-readable
> > description of what each choice will do; it doesn't have to say
> > anything about the Lisp value which stands for that choice.
>
> "Doesn't have to"? Sure. But it is generally more helpful for users
> if the corresponding Lisp values are also cited in the doc string.
I don't think I agreer, not in general.
> That users should not, and generally do not, need to know Lisp
> to customize a user option is not a reason that the doc for that
> option should not mention the Lisp values. It's true that there
> is no obligation for the doc to mention the Lisp values, but it
> generally helps users to do so - so it typically _should_.
There's also no catastrophe if users will read the source to find that
out. Especially those who want to know and use Lisp.
- Re: New behavior, (continued)
- Re: New behavior, Stephen Berman, 2018/09/13
- Re: New behavior, Eli Zaretskii, 2018/09/13
- Re: New behavior, Bruce Korb, 2018/09/13
- Re: New behavior, Van L, 2018/09/14
- Re: New behavior, Phil Sainty, 2018/09/14
- Re: New behavior, Eli Zaretskii, 2018/09/14
- Re: New behavior, Van L, 2018/09/16
- Re: New behavior, Eli Zaretskii, 2018/09/16
- RE: New behavior, Drew Adams, 2018/09/16
- Re: New behavior,
Eli Zaretskii <=
- RE: New behavior, Drew Adams, 2018/09/16
- Re: New behavior, Van L, 2018/09/16
- Re: New behavior, Eli Zaretskii, 2018/09/16
- Re: New behavior, Van L, 2018/09/17
- Re: New behavior, Eli Zaretskii, 2018/09/18
- Re: New behavior, Bingo, 2018/09/19
- Re: New behavior, Davis Herring, 2018/09/19
- Re: New behavior, Bingo, 2018/09/19
- Re: New behavior, Van L, 2018/09/20