From: Richard G Riley <rileyrgdev@googlemail.com>
To: William Henney <whenney@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Ringing the alarm bell in orgmode
Date: Tue, 06 Nov 2007 16:35:29 +0100 [thread overview]
Message-ID: <86sl3jtmim.fsf@home.net> (raw)
In-Reply-To: <41c818190711060716p795fb91v9a3b899624a8a21d@mail.gmail.com> (William Henney's message of "Tue\, 6 Nov 2007 09\:16\:21 -0600")
"William Henney" <whenney@gmail.com> writes:
> On 11/6/07, Bastien <bzg@altern.org> wrote:
>> Richard G Riley <rileyrgdev@googlemail.com> writes:
>> > 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 info relevant information.
>>
>
> I use "l" a lot, but I didn't know about "L" - thanks!
>
> The commands I use most are "spacebar", which just chugs through an
> entire manual, and "s", which does a regexp search.
>
> I do like info pages when I can actually get the right ones to load.
> The big problem I have with info is in setting it up so that it finds
> the right files. For instance, I have totally failed to work out how I
> can tell it where my org info files are, with the result that it
> always shows me the old version that comes with my emacs (currently
> 4.67). I have tried setting Info-default-directory-list and
> Info-directory-list, but all to no avail. Has anyone else had this
> problem?
Yes.
On linux i ran (sudo) make install-info and then insured
/usr/local/info was on my info-directory-list
I also deleted any old org files lying around. I dont know, info files
and their set up is just damn confusing IMO, especially with plenty of
makefiles updating the wrong dir file. - its always worth checking which
define they use for their destination infopath.
>
> Cheers
>
> Will
>
>> HTH,
next prev parent reply other threads:[~2007-11-06 15:35 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
2007-11-06 15:16 ` William Henney
2007-11-06 15:34 ` Chris Leyon
2007-11-06 15:35 ` Richard G Riley [this message]
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=86sl3jtmim.fsf@home.net \
--to=rileyrgdev@googlemail.com \
--cc=emacs-orgmode@gnu.org \
--cc=whenney@gmail.com \
/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).