Gnus development mailing list
 help / color / mirror / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Difference between M-C-k and d?
Date: Mon, 08 Feb 2016 12:51:18 +0100	[thread overview]
Message-ID: <m2d1s7fmix.fsf@krugs.de> (raw)
In-Reply-To: <87oabupdy0.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 06 Feb 2016 17:09:43 +1100")

[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Rainer M Krug <Rainer@krugs.de> writes:
>
>> I am using threaded view in my imap folders and I am wondering about the
>> topic commands:
>>
>> M-C-k (Mark Tread as Read) results in "K", while d
>> (gnus-summary-mark-as-read-forward) in "r".
>>
>> Killing is for me equivalent to deleting - is this also the case here?
>> Is "killing" and "mark as read" the semae for an imap mailbox?
>
> Yeah, all those marks just means "read".  But they can be used to
> distinguish different types of actions when using adaptive scoring.  For
> instance, you could score threads you kill harsher than other kinds of
> read articles.

Thanks - so I can safely use M-C-k to mark a thread as read.

Cheers,

Rainer
-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax :       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug

PGP: 0x0F52F982

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]

      reply	other threads:[~2016-02-08 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04  9:55 Rainer M Krug
2016-02-06  6:09 ` Lars Ingebrigtsen
2016-02-08 11:51   ` Rainer M Krug [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=m2d1s7fmix.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=ding@gnus.org \
    --cc=larsi@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).