Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: How to get multipart/alternative button to show plain text by default?
Date: Sun, 17 Jan 2016 16:30:34 -0800	[thread overview]
Message-ID: <m28u3nn2z9.fsf@boostpro.com> (raw)
In-Reply-To: <87h9im9922.fsf@nemi.mork.no>


on Sat Jan 09 2016, Bjørn Mork <bjorn-AT-mork.no> wrote:

> Dave Abrahams <dave@boostpro.com> writes:
>> on Wed Jan 06 2016, Bjørn Mork <bjorn-AT-mork.no> wrote:
>>
>>> I believe mm-discouraged-alternatives only affects the selection of
>>> which part to render when *not* buttonizing.  So you should drop the
>>> gnus-buttonized-mime-types customization.
>>
>> But sometimes I want to look at the HTML version, and the buttons are a
>> convenient way to switch back and forth that doesn't require remembering
>> an obscure key combination or rarely-used command. Can't I have it all?
>
> Yes, I sometimes want that as well.  You need to remember a single
> obscure key combination: "K b" will reenable the buttons for the article
> you are viewing.
>
> Ctrl + d is nice as well.  But I often want one of the actions from the
> button context menu.  E.g view the html part in an external browser.  So
> I use "K b" to be able to right click on the text/html button.

Thanks!  I knew that once...

It turns out that `W h' is a much more effective way for me to see the
HTML in most cases, but it's great to have a bag of tricks.

-Dave




  reply	other threads:[~2016-01-18  0:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 22:37 Dave Abrahams
2016-01-06 22:59 ` Adam Sjøgren
2016-01-07  9:51   ` Andreas Schwab
2016-01-06 23:04 ` Bjørn Mork
2016-01-08  7:18   ` Dave Abrahams
2016-01-08 12:19     ` Bjorn Solberg
2016-01-09  7:32     ` Steinar Bang
2016-01-09  9:51       ` Andreas Schwab
2016-01-09 13:28     ` Bjørn Mork
2016-01-18  0:30       ` Dave Abrahams [this message]
2016-01-08 12:00 ` Teemu Likonen

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=m28u3nn2z9.fsf@boostpro.com \
    --to=dave@boostpro.com \
    --cc=ding@gnus.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).