From: Ian Barton <lists@wilkesley.net>
To: emacs-orgmode@gnu.org
Subject: Re: documentation versions question
Date: Thu, 23 Jun 2011 15:42:33 +0100 [thread overview]
Message-ID: <4E0350D9.7030900@wilkesley.net> (raw)
In-Reply-To: <alpine.BSF.2.00.1106230549240.4770@freire1.furyyjbeyq.arg>
On 23/06/11 10:54, Jude DaShiell wrote:
> Once git pull has been run and the build of org and documentation have
> been done and installed, should info org provide the org version of 6.33x?
> Also, orgguide doesn't get added to my info files is it supposed to be
> held separate for some reason? orgguide has version of 7.50 on it and I
> expect that's correct too.
>
>
>
If you are running Linux, this depends on your distribution. The problem
is that Emacs is probably looking in a different place for the info file
to the place where the Makefile installed it.
My inelegant approach is to define a keyboard macro that points to the
place where the Makefile installed the info file:
(global-set-key (kbd "<f9> i") (lambda ()
(interactive)
(info
"~/dropbox/.emacs.d/src/org-mode/doc/org")))
A more subtle approach would be to edit the Makefile to put the info
file in the right place. However, on Ubuntu it's not all clear where
this should be.
Ian.
next prev parent reply other threads:[~2011-06-23 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 9:54 documentation versions question Jude DaShiell
2011-06-23 14:42 ` Ian Barton [this message]
2011-06-23 15:31 ` suvayu ali
2011-06-24 8:24 ` Sebastien Vauban
2011-06-24 20:49 ` suvayu ali
2011-06-23 16:15 ` install-info-debian on ubuntu? (was: documentation versions question) Memnon Anon
2011-06-24 3:18 ` documentation versions question Jude DaShiell
2011-06-23 15:06 ` Nick Dokos
-- strict thread matches above, loose matches on Subject: below --
2011-06-24 3:54 Rustom Mody
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=4E0350D9.7030900@wilkesley.net \
--to=lists@wilkesley.net \
--cc=emacs-orgmode@gnu.org \
--cc=lists@manor-farm.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.