Re: Quote emphasis

[Sudish Joseph <sudish@mindspring.com>]

In article <rjn2vzf79z.fsf@babbage.dina.kvl.dk>,
Per Abrahamsen <abraham@dina.kvl.dk> writes:
> Sudish Joseph <sudish@mindspring.com> writes:
>> I liked it, but I agree that it can cause havoc for certain messages.

> Which?  It works fine with the code snips I have seen.  The strings
> gets highlighted, as if the code was font-locked.  

Some messages with quotes spanning multiple lines.  A backtrace
buffer, for instance.  Not a big deal, it looks great for the common
case.  Smilies cause more problems, but they're sufferable, too.  

> But I agree it should be on a separate hook function.  What should it
> be called?  `highlight-quotes' would be "correct", but may be easy to
> confuse with `highlight-citation'.

highlight-quoted-strings?  Redundancy in the name might reduce the
confusion.

>> If all massagers provided two hook-safe functions, feature-foo-article
>> and un-feature-foo-article, we wouldn't need variables.  They could be
>> added to the appropriate hook and given bindings in the W keymap.

> Too difficult, not all display features can be undone.

I like the part I snipped out.  

Another thing we can do is to have all article buffer face
manipulation pass through one gnus-supplied function.  This function
(gnus-article-add-text-props?) could then add an extra property
alongside of the face proerty it's adding.  This property could be
used to unmassage the text back.

That's simplistic, there're all kinds of priority/sequencing
problems.  But it's still doable.

Not that it's useful for all article display features--face
manipulation is the most common case, and it's the easiest to handle.

-Sudish