Gnus development mailing list
 help / color / mirror / Atom feed
From: Emanuel Berg <moasenwood@zoho.eu>
To: help-gnu-emacs@gnu.org
Cc: ding@gnus.org
Subject: Re: a mysterious star on the Gnus firmament
Date: Sat, 23 Mar 2019 19:41:32 +0100	[thread overview]
Message-ID: <86mullcu1v.fsf@zoho.eu> (raw)
In-Reply-To: <m2va0aknx1.fsf@linux-m68k.org>

Andreas Schwab wrote:

>> Second, what does the `*' char mean, how did
>> it get there (except for me falling asleep),
>> and how do I remove it?
>
> * runs the command gnus-cache-enter-article
> (found in gnus-summary-mode-map), which is an
> interactive autoloaded compiled Lisp function
> in ‘gnus-cache.el’.

Thank you. You remove it with the default `M-*'
for `gnus-cache-remove-article'.

-- 
underground experts united
http://user.it.uu.se/~embe8573




      parent reply	other threads:[~2019-03-23 18:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 21:20 Emanuel Berg
     [not found] ` <m2va0aknx1.fsf@linux-m68k.org>
2019-03-23 18:41   ` Emanuel Berg [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=86mullcu1v.fsf@zoho.eu \
    --to=moasenwood@zoho.eu \
    --cc=ding@gnus.org \
    --cc=help-gnu-emacs@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).