In article <[EMAIL PROTECTED]>, Ben Bucksch
<[EMAIL PROTECTED]> wrote:
> J.B. Moreno wrote:
>
> > I don't think that's as important as the display being "correct".
>
> huh? The display is correct. (We are talking about format=flowed.) Using
> ">"s would only *add* ambiguity. (That doesn't mean, we shouldn't offer
> the option, since some users seems to want it.)
I put "correct" into quotes because what I really meant was "correct
according to what the user expects/wants".
> >> Why a pref, if you can do it with a few CSS lines in your user
> >> stylesheet?
> >
> > Because I haven't a clue as to how or where to edit the user stylesheet
> > and I probably never will, and I don't think I am that unusual in this
> > respect.
>
> I don't think, there will ever be pref UI for it, unless we couple it
> with disabling the bars for normal plaintext.
What would be wrong about that?
> If there is no UI, editing prefs.js or userContent.css is not very
> different.
prefs.js would (IMO) be better than userContent.css (particularly if
you can include comments around the option so that the user can easily
know what the available options are and how to get them).
--
J.B. Moreno
