From: Jude DaShiell <jdashiel@shellworld.net>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to update "Info Documentation"?
Date: Fri, 29 Jul 2011 06:25:36 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.00.1107290623220.37988@freire1.furyyjbeyq.arg> (raw)
In-Reply-To: <CAMXnza3z=Y-y4WiwNag5J92Q9g9xf0TQ476TcGwhvMPGe93EFw@mail.gmail.com>
1) make sure prefix on line 16 of Makefile is set correctly, if your real
prefix is /usr, that line shouldn't read /usr/local, 2) do make
info-install and then do info org and see if the documentation doesn't
suddenly update itself. hth.On Fri, 29 Jul 2011, suvayu ali wrote:
> On Fri, Jul 29, 2011 at 11:34 AM, Johan Ekh <ekh.johan@gmail.com> wrote:
> > Hi all,
> > I keep up to date with org-mode using:
> >
> > git pull && make clean && make && make doc && make install
> >
> > It works very well except that my "Info Documentation" is not updated.
> > It is still some old version.
> >
> > What do I have to do to get it updated?
> >
>
> 3 options:
>
> 1. Set this variable to the appropriate path in your init file
>
> ;; Info directory
> (add-to-list 'Info-default-directory-list
> (expand-file-name "/opt/emacs-lisp/share/info"))
>
> 2. Add to the INFOPATH variable in your shell profile file:
>
> e.g. (bash)
> ~/.bash_profile
> ..
> export INFOPATH=/opt/emacs-lisp/share/info:$INFOPATH
>
> 3. Edit your Makefile to reflect the proper infopath
>
> # Where local software is found
> prefix=/opt/emacs-lisp
>
> ..
>
> # Where info files go.
> infodir = $(prefix)/share/info
>
>
> > BR / Johan
> >
>
> Hope this helps.
>
>
next prev parent reply other threads:[~2011-07-29 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 9:34 How to update "Info Documentation"? Johan Ekh
2011-07-29 9:43 ` Walter Franzini
2011-07-29 9:47 ` suvayu ali
2011-07-29 10:25 ` Jude DaShiell [this message]
2011-07-29 10:26 ` suvayu ali
2011-07-29 16:54 ` Dave Abrahams
2011-07-29 17:33 ` suvayu ali
2011-07-29 19:56 ` Dave Abrahams
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=alpine.BSF.2.00.1107290623220.37988@freire1.furyyjbeyq.arg \
--to=jdashiel@shellworld.net \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@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).