Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: unoder.spam@spam.jay.net (Martin Jørgensen)
Subject: Re: a couple of newbie questions with gnus
Date: Thu, 01 Jun 2006 00:56:27 +0200	[thread overview]
Message-ID: <rhj1l3-0t7.ln1@news.tdc.dk> (raw)
In-Reply-To: <v9bqtezk6h.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> On Wed, May 31 2006, Martin Jørgensen wrote:
>
>> How do I mark your message as "unread" so it'll automatically show
>> up when I have restarted gnus? 
>
> See (info "(gnus)Setting Marks").  Especially `!' and `M-u':

Oh, damn. I should have seen that and perhaps I did, but got confused by
this "Clear all readedness-marks". I should have read the last in that line.

> ,----[ (info "(gnus)Setting Marks") ]
> | `M c'
> | `M-u'
> |      Clear all readedness-marks from the current article
> |      (`gnus-summary-clear-mark-forward').  In other words, mark the
> |      article as unread.
> | 
> | `M t'
> | `!'
> |      Tick the current article (`gnus-summary-tick-article-forward').
> |      *Note Article Caching::.
> `----
>
>> I tried to look in the manual, but there was so much information.
>
> When I use `i mark' (lookup "mark" in the index) in the Gnus manual,
> the first match is (info "(gnus)Marking Articles") which contains an
> menu entry called "How to set and remove marks." pointing to the
> appropriate node:
>
> ,----[ (info "(gnus)Marking Articles") ]
> | * Setting Marks::               How to set and remove marks.
> `----

I think I looked there too, but now I can see it's pretty straight
forward, as you're also writing.

> If you tell us the keywords you (unsuccessfully) used to search in the
> manual, we might be able to improve the manual.

I didn't use them, because I forgot the difference between "apropos" and
all the other C-h things... So therefore I just got into those
"info"-pages somehow and manually navigated down to gnus with C-p +
C-n + enter... Then I navigated up with U, next with n and space and p
for previous... So I typed space a lot of times... But that ofcourse
also isn't the most efficient way of skimming the manual, but the good
thing is that next time I probably better regognize where something I'm
looking for is described...

For instance I was glad to find out what those letters meant: "O", "R",
"A".. etc, next to the name in the summary-view... I think I can find it
quicker and quicker, the more I practice looking in the manual - and it
actually looks like a good manual, like other people are telling too...


Best regards
Martin Jørgensen

-- 
---------------------------------------------------------------------------
Home of Martin Jørgensen - http://www.martinjoergensen.dk

  reply	other threads:[~2006-05-31 22:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-23 16:28 Martin Jørgensen
2006-05-23 16:57 ` David Z Maze
2006-05-24 23:05   ` Martin Jørgensen
2006-05-25  8:46     ` Alexander Ponomarenko
2006-05-25 15:03       ` Martin Jørgensen
2006-05-25 15:38         ` Malte Spiess
2006-05-25 23:06           ` Martin Jørgensen
2006-05-26  6:24             ` Malte Spiess
2006-05-26 15:20               ` Martin Jørgensen
2006-05-26 17:47                 ` Tassilo Horn
     [not found]                 ` <mailman.2324.1148665716.9609.info-gnus-english@gnu.org>
2006-05-26 18:29                   ` Karl Kleinpaste
2006-05-26 19:28                     ` Martin Jørgensen
2006-05-26 20:32                       ` Reiner Steib
2006-05-27  1:16                         ` Martin Jørgensen
2006-05-28  9:19                           ` Tassilo Horn
     [not found]                           ` <mailman.2366.1148808000.9609.info-gnus-english@gnu.org>
2006-05-28 15:22                             ` Martin Jørgensen
2006-05-28 16:16                               ` Tassilo Horn
2006-05-28 16:38                               ` Reiner Steib
2006-05-28 17:05                                 ` David Kastrup
2006-05-30 14:01                                   ` Reiner Steib
2006-05-30 15:33                                     ` David Kastrup
2006-05-31 22:35                                   ` Martin Jørgensen
2006-06-01  8:02                                     ` David Kastrup
2006-06-05 13:15                                     ` david.reitter
2006-06-15 13:55                                       ` Aking TIAN
2006-05-29  9:23                               ` Reiner Steib
     [not found]                               ` <mailman.2368.1148833009.9609.info-gnus-english@gnu.org>
2006-05-29 18:13                                 ` Martin Jørgensen
2006-05-29 22:22                                   ` Reiner Steib
2006-05-31  2:18                                     ` Martin Jørgensen
2006-05-31  8:13                                       ` Reiner Steib
2006-05-31 22:56                                         ` Martin Jørgensen [this message]
2006-05-30 17:45                                   ` Tassilo Horn
     [not found]                                   ` <mailman.2439.1149011220.9609.info-gnus-english@gnu.org>
2006-05-31  3:10                                     ` Martin Jørgensen
2006-05-23 22:02 ` Johan Bockgård
2006-05-24 23:08   ` Martin Jørgensen
2006-05-24 11:12 ` Alexander Ponomarenko

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=rhj1l3-0t7.ln1@news.tdc.dk \
    --to=unoder.spam@spam.jay.net \
    /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).