Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Poll: `C-u g' and `C-u C-u g' meanings
Date: Thu, 02 Dec 2010 21:20:46 +0100	[thread overview]
Message-ID: <87y6880vvl.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <smusjyg9yga.fsf@linuxpal.mit.edu> (Greg Troxel's message of "Thu, 02 Dec 2010 07:00:21 -0500")

On Thu, Dec 02 2010, Greg Troxel wrote:

> Once you go beyond "100% raw" and "100% cooked", there are a larger
> number of potential steps to be omitted.  So it probably makes sense to
> use numeric prefixes.  

The numerical prefix is already used for
`gnus-summary-show-article-charset-alist':

,----[ <f1> f gnus-summary-show-article RET (from an not up-to-date Gnus) ]
| gnus-summary-show-article is an interactive compiled Lisp function
| in `gnus-sum.el'.
| (gnus-summary-show-article &optional ARG)
| 
| Force redisplaying of the current article.
| If ARG (the prefix) is a number, show the article with the charset
| defined in `gnus-summary-show-article-charset-alist', or the charset
| input.
| If ARG (the prefix) is non-nil and not a number, show the raw article
| without any article massaging functions being run.  Normally, the key
| strokes are `C-u g'.
`----

> An alternative interface would be to have some
> keybinding following C-u g apply the processing steps one at a time.
> I don't really recommend space (haven't thought enough) but how about it
>
>   C-u g (fully raw) space (content-transfer) space (html/text select)
>   space (wash) ....
>
> and g when in incremental-cook mode got back to fully cooked and turned
> space back to normal?

Maybe (info "(gnus)Symbolic Prefixes") could be used?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



      reply	other threads:[~2010-12-02 20:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 17:16 Lars Magne Ingebrigtsen
2010-12-01 17:49 ` Adam Sjøgren
2010-12-01 18:13 ` Daniel Dehennin
2010-12-01 18:47 ` Steinar Bang
2010-12-01 19:36 ` Christoph Conrad
2010-12-01 21:40   ` Harry Putnam
2010-12-02  3:06     ` jidanni
2010-12-01 19:43 ` Frank Schmitt
2010-12-02 10:27 ` Łukasz Stelmach
2010-12-04 22:35   ` Lars Magne Ingebrigtsen
2010-12-14 23:40     ` Ted Zlatanov
2010-12-15 19:32       ` Lars Magne Ingebrigtsen
2010-12-15 21:06         ` Ted Zlatanov
2010-12-16 16:11           ` Lars Magne Ingebrigtsen
2010-12-16 17:22             ` Ted Zlatanov
2010-12-02 11:16 ` Ludovic Courtès
2010-12-02 12:00 ` Greg Troxel
2010-12-02 20:20   ` Reiner Steib [this message]

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=87y6880vvl.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).