Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: info-gnus-english@gnu.org
Subject: Re: Citation processing in HTML articles?
Date: Sun, 22 May 2016 11:37:21 -0700	[thread overview]
Message-ID: <m2futadjmm.fsf@eno.apple.com> (raw)
In-Reply-To: <86k2ip77c6.fsf@student.uu.se>


on Thu May 19 2016, Emanuel Berg <embe8573-AT-student.uu.se> wrote:

> Dave Abrahams <dave@boostpro.com> writes:
>
>> I can write a citation-coloring-and-hiding
>> postprocessor for Gnus myself if I have to
>> but I was hoping someone already solved
>> this problem.
>
> Isn't this achieved with:
>
>     (setq gnus-treat-hide-citation t)
>
> and then setting the faces:
>
>     gnus-cite-1
>     gnus-cite-2
>     gnus-cite-...
>     gnus-cite-attribution
>
> ?
>
>> No, I just don't want to have to go through
>> the process of hunting for the right
>> combination of mime buttons and article
>> washing necessary to make an article
>> readable.
>
> Gnus can to a certain extent make crappy
> messages look good. But if the messages are
> good to begin with, they'll look good in Gnus
> with no intervention to it.
>
> The hiding of citations, and replacing them
> with button so they can be expanded if need be,
> this is not washing but a convenient way of
> getting less text to bother you, while still
> have it readily available.
>
>> There are lots of reasons not to use a more
>> “traditional” mail client than Gnus, but at
>> least they tend to make more of the messages
>> quite readable without user intervention.
>
> Can you provide us with examples of messages
> that Gnus makes less readable? I don't think
> Gnus does that - more likely *the messages* are
> crappy beyond help to begin with, and with
> efforts Gnus can be made to make them look
> somewhat better.

That's not my experience.  If you read through the messages in
http://news.gmane.org/gmane.comp.lang.swift.evolution you'll see quite a
variety, and usually at least *one* way of looking at the message will
be pretty good, and furthermore usually a GUI client like Thunderbird
will do an excellent job at rendering it.  The most common problem I've
seen is that many messages with embedded code examples in HTML have the
code terribly misformatted in their plain text MIME segments.  So I have
to look at the HTML if I want to read the code.  However, I can't get
the overlong citations to be hidden, so it takes too long to figure out
which non-code I need to look at.

>> And I don't show the MIME buttons by
>> default, FWIW.
>
> Which are those? The attachment buttons?
> Why would you want to hide them?

I'm trying to eliminate visual clutter.  The more I can do that and have
Gnus get things right automatically, the better my life is.

-- 
-Dave


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2016-05-22 18:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16  6:23 Dave Abrahams
2016-05-16 19:05 ` Emanuel Berg
2016-05-17 15:07   ` Dave Abrahams
2016-05-17 20:05     ` Emanuel Berg
2016-05-19 22:41       ` Dave Abrahams
2016-05-20  3:10         ` Emanuel Berg
2016-05-22 18:37           ` Dave Abrahams [this message]
2016-05-22 21:36             ` Emanuel Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2futadjmm.fsf@eno.apple.com \
    --to=dave@boostpro.com \
    --cc=info-gnus-english@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).