emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Re: Ringing the alarm bell in orgmode
Date: Tue, 06 Nov 2007 15:41:06 +0000	[thread overview]
Message-ID: <874pfz5qlp.fsf@bzg.ath.cx> (raw)
In-Reply-To: <wqejf3v5po.fsf@home.net> (Richard G. Riley's message of "Tue, 06 Nov 2007 14:55:31 +0100")

Richard G Riley <rileyrgdev@googlemail.com> writes:

>> One way to find information when browsing the manual in Info-mode is to
>> press `i' (M-x Info-index) and enter the index key to look for.
>
> Is it just me or are emacs info pages really a bit of a dog to search
> through?

It's not just you.  

Many people don't like to search through the Info pages and whether this
interface is the best one for Emacs documentation is always a hot topic
on the emacs-devel mailing list.

But `i' (M-x Info-index) will really make your life easier.

Personnally I do like Info pages and Info-mode very much.  In addition
to Info-index, I'm mostly using these:

  `l' Info-history-back
  `L' Info-history
  `]' Info-forward-node

Once you get used to these few commands, it's really quick to find and
fetch relevant information.

HTH,

-- 
Bastien

  reply	other threads:[~2007-11-06 14:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-06  8:23 Ringing the alarm bell in orgmode Uwe Jochum
2007-11-06  8:48 ` Stefan Kamphausen
2007-11-06 14:37   ` Bastien
2007-11-06  9:43 ` Bastien
2007-11-06 10:23   ` Uwe Jochum
2007-11-06 14:22     ` Bastien
2007-11-06 13:55       ` Richard G Riley
2007-11-06 15:41         ` Bastien [this message]
2007-11-06 15:16           ` William Henney
2007-11-06 15:34             ` Chris Leyon
2007-11-06 15:35             ` Richard G Riley
2007-11-06 16:43             ` Sivaram Neelakantan
2007-11-06 16:47             ` Bastien
2007-11-06 16:58               ` William Henney
     [not found]       ` <uzlxrfphs.fsf@uni-konstanz.de>
2007-11-06 15:31         ` Bastien

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874pfz5qlp.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).