Gnus development mailing list
 help / color / mirror / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: ding@gnus.org
Subject: Difference between M-C-k and d?
Date: Mon, 04 Jan 2016 10:55:24 +0100	[thread overview]
Message-ID: <m2r3hx654j.fsf@Rainers-MBP.fritz.box> (raw)

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

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?

Thanks,

Rainer

-- 
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982

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

             reply	other threads:[~2016-01-04  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04  9:55 Rainer M Krug [this message]
2016-02-06  6:09 ` Lars Ingebrigtsen
2016-02-08 11:51   ` Rainer M Krug

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=m2r3hx654j.fsf@Rainers-MBP.fritz.box \
    --to=rainer@krugs.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).