Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Jason Dufair <jase@dufair.org>
Subject: Re: increase number of posts
Date: Wed, 27 Jul 2005 16:52:44 -0500	[thread overview]
Message-ID: <7quiryv9as3.fsf@1078-ARIBA-004.central.purdue.lcl> (raw)
In-Reply-To: <42e7f14e$1_1@news.iprimus.com.au>

Baloff <vddr2u@bi.edu.gr> writes:

> Jason Dufair wrote:
>> Baloff <washdc@wash.edu> writes:
>>
>>>don't tell me to read the manual, if you do, tell me where
>> http://www.gnus.org/manual/gnus_71.html#SEC71
>>
>>>and make sure it is and clearly written.
>> It is.
>>
> thanks, how do you find something like this in the manual? I tried C-h a 
> number, post. I get nothing related, even if I thought about C-h a limit 
> it would not give me that place in the manual you provided the link for. 
> is there a better way to search and find thing in the manual in my box?

A few ideas:

Gnus' functions are often named after the buffer you want to do
something in.  So you can often do a C-h a summary, for example, to find
summary buffer fxns.

Also, C-h b will give you all the key bindings for the mode you're in.
You can poke around in there for interesting function names.

In the case above, I just went to the Gnus HTML manual online and looked
for summary buffer stuff.
-- 
Jason Dufair - jase@dufair.org
http://www.dufair.org/
"In matters of style, swim with the current; 
in matters of principle, stand like a rock."
-- Thomas Jefferson


  reply	other threads:[~2005-07-27 21:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27  7:43 Baloff
2005-07-27  9:22 ` Adam Sjøgren
2005-07-27 18:55 ` Jason Dufair
2005-07-28 13:52   ` Baloff
2005-07-27 21:52     ` Jason Dufair [this message]
2005-07-28 15:13     ` David Z Maze
2005-07-28  7:26 ` Koocy Ton

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=7quiryv9as3.fsf@1078-ARIBA-004.central.purdue.lcl \
    --to=jase@dufair.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).