INFOPATH and emacs

INFOPATH and emacs

[Ritesh]

i've installed a local repository of 'info' files in my home dir
....containing documentation of  the new emacs packages that i've
installed. I've written at appropriate 'dir' file which seems to be 
working fine. 
i've also set INFOPATH:$HOME/info/: in my .bash_profile...the trailing
':' appends the complied in path so that my files are prepended to the
already present files. info program is working fine, that is it displays
the entire info tree beginning with my files as expected. however, echo
$INFOPATH returns /home/ritesh/info: ; ie. it's not displaying the
compiled in path. this is a problem because emacs uses the INFOPATH
variable to look for info files, and now it's only seeing the files that
i've installed and not the compiled in files. 
How can i make emacs read the complete path?

Re: INFOPATH and emacs

[David Masterson]

>>>>> Ritesh  writes:

> i've installed a local repository of 'info' files in my home dir
> ....containing documentation of the new emacs packages that i've
> installed. I've written at appropriate 'dir' file which seems to be
> working fine.  i've also set INFOPATH:$HOME/info/: in my
> .bash_profile...the trailing ':' appends the complied in path so
> that my files are prepended to the already present files. info
> program is working fine, that is it displays the entire info tree
> beginning with my files as expected. however, echo $INFOPATH returns
> /home/ritesh/info: ; ie. it's not displaying the compiled in
> path. this is a problem because emacs uses the INFOPATH variable to
> look for info files, and now it's only seeing the files that i've
> installed and not the compiled in files.  How can i make emacs read
> the complete path?

Run that by again...

What are the commands you have in your .bash_profile to setup your
INFOPATH variable?  What does $INFOPATH look like after you login?

-- 
David Masterson                David DOT Masterson AT synopsys DOT com
Sr. R&D Engineer               Synopsys, Inc.
Software Engineering           Sunnyvale, CA

Re: INFOPATH and emacs

[Ritesh]

thanks for the prompt reply!!
my .bash_profile entry: 
INFOPATH=/home/ritesh/info:
export INFOPATH
(/home/ritesh is my HOME and ~/info is the directory where i've put my
new info files)
echo $INFOPATH returns:
/home/ritesh/info:

Re: INFOPATH and emacs

[Jeremy Gray]

Ritesh <sood@tenet.res.in> wrote:  
> thanks for the prompt reply!!
> my .bash_profile entry: 
> INFOPATH=/home/ritesh/info:
> export INFOPATH
> (/home/ritesh is my HOME and ~/info is the directory where i've put my
> new info files)
> echo $INFOPATH returns:
> /home/ritesh/info:

That means that info readers will only look in /home/ritesh/info for
info files.  You'll need something like:

/usr/info:/usr/local/info:/opt/gnome/info:/opt/teTeX/info:/home/gray/info

Which is my current INFOPATH.  Basically, INFOPATH should contain any
directory that has info files you are interested in reading.  

Also, please quote the relevant parts of the message you are following
up to so that people can see the context of the discussion.  

-- 
Jeremy A. Gray
gray@metacomet.net

"Remember the Pueblo." -- the Fourth Law of Marvin

Re: INFOPATH and emacs

[Kai Großjohann]

sood@tenet.res.in (Ritesh) writes:

> i've also set INFOPATH:$HOME/info/: in my .bash_profile...the trailing
> ':' appends the complied in path so that my files are prepended to the
> already present files.

Nifty feature.  I didn't know that info did this.

Maybe the best bet is this:

(require 'info)
(add-to-list 'Info-directory-list (expand-file-name "~/info/"))

I haven't tested it.  It's a hack.
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)

Re: INFOPATH and emacs

[Kevin Rodgers]

Jeremy Gray wrote:

> That means that info readers will only look in /home/ritesh/info for
> info files.


No.  Ritesh wrote:
 > > i've also set INFOPATH:$HOME/info/: in my .bash_profile...the trailing
 > > ':' appends the complied in path so that my files are prepended to the
 > > already present files. info program is working fine, that is it displays
 > > the entire info tree beginning with my files as expected.

So there is a discrepancy between the command line info program and Emacs'

M-x info command in how an empty INFOPATH component is interpreted.  I think
Emacs should emulate info as closely as possible; if the OP agrees, he should
use M-x report-emacs-bug to submit a bug report.


-- 
<a href="mailto:&lt;kevin.rodgers&#64;ihs.com&gt;">Kevin Rodgers</a>

Re: INFOPATH and emacs

[David Masterson]

>>>>> Kai Großjohann writes:

> sood@tenet.res.in (Ritesh) writes:

>> i've also set INFOPATH:$HOME/info/: in my .bash_profile...the
>> trailing ':' appends the complied in path so that my files are
>> prepended to the already present files.

> Nifty feature.  I didn't know that info did this.

> Maybe the best bet is this:

> (require 'info)
> (add-to-list 'Info-directory-list (expand-file-name "~/info/"))

> I haven't tested it.  It's a hack.

And still a problem because Info would preset the list based upon
INFOPATH and, thus, be messed up even before it gets to the
add-to-list.  What you're thinking means that you have to have two
INFOPATH settings -- one for 'info' and one for 'emacs'.

-- 
David Masterson                David DOT Masterson AT synopsys DOT com
Sr. R&D Engineer               Synopsys, Inc.
Software Engineering           Sunnyvale, CA

Re: INFOPATH and emacs

[Jeremy Gray]

Kevin Rodgers <ihs_4664@yahoo.com> wrote:  
> Jeremy Gray wrote:
>> 
>> That means that info readers will only look in /home/ritesh/info for
>> info files.
> 
> No.

Yep, your right.  I never heard of the info's trailing colon feature
before.  Plus I only found the info standalone node today (I always
wondered where that was), and the manpage doesn't mention it.  

> So there is a discrepancy between the command line info program and
> Emacs' M-x info command in how an empty INFOPATH component is
> interpreted.  I think Emacs should emulate info as closely as
> possible; if the OP agrees, he should use M-x report-emacs-bug to
> submit a bug report.

I think setting the entire path is easier in the long run since it
works for both info and info-mode.  But, I think this is a easily fixed
bug.  

-- 
Jeremy A. Gray
gray@metacomet.net

"Remember the Pueblo." -- the Fourth Law of Marvin

Re: INFOPATH and emacs

[David Masterson]

>>>>> Jeremy Gray writes:

> Jeremy Gray <gray@euthanasia.ath.cx> wrote:  
>> Kevin Rodgers <ihs_4664@yahoo.com> wrote:  

>>> So there is a discrepancy between the command line info program
>>> and Emacs' M-x info command in how an empty INFOPATH component is
>>> interpreted.  I think Emacs should emulate info as closely as
>>> possible; if the OP agrees, he should use M-x report-emacs-bug to
>>> submit a bug report.

>> I think setting the entire path is easier in the long run since it
>> works for both info and info-mode.  But, I think this is a easily
>> fixed bug.

> This appears to work, at least for me.  

> +		 (if (string-match ":$" path)

What if the INFOPATH include "::" in it?  In other words, what if he
wanted to append to Info-default-directory-list rather than prepend to
it?

Also, I think Info-default-directory-list is deprecated in XEmacs.

-- 
David Masterson                David DOT Masterson AT synopsys DOT com
Sr. R&D Engineer               Synopsys, Inc.
Software Engineering           Sunnyvale, CA

Re: INFOPATH and emacs

[Jeremy Gray]

Jeremy Gray <gray@euthanasia.ath.cx> wrote:  
> Kevin Rodgers <ihs_4664@yahoo.com> wrote:  
>> 
>> So there is a discrepancy between the command line info program and
>> Emacs' M-x info command in how an empty INFOPATH component is
>> interpreted.  I think Emacs should emulate info as closely as
>> possible; if the OP agrees, he should use M-x report-emacs-bug to
>> submit a bug report.
> 
> I think setting the entire path is easier in the long run since it
> works for both info and info-mode.  But, I think this is a easily fixed
> bug.  

This appears to work, at least for me.  

diff -Naur emacs-21.3/lisp/info.el emacs-21.3-jag/lisp/info.el
--- emacs-21.3/lisp/info.el	2001-12-21 13:08:17.000000000 -0600
+++ emacs-21.3-jag/lisp/info.el	2003-04-17 14:08:25.000000000 -0500
@@ -320,7 +320,8 @@
       (insert-file-contents fullname visit))))
 \f
 (defun info-initialize ()
-  "Initialize `Info-directory-list', if that hasn't been done yet."
+  "Initialize `Info-directory-list', respecting a final colon like
+info standalone, if that hasn't been done yet."
   (unless Info-directory-list
     (let ((path (getenv "INFOPATH"))
 	  (source (expand-file-name "info/" source-directory))
@@ -341,7 +342,10 @@
       (setq Info-directory-list
 	    (prune-directory-list
 	     (if path
-		 (split-string path (regexp-quote path-separator))
+		 (if (string-match ":$" path)
+                     (append (split-string path (regexp-quote path-separator))
+                             Info-default-directory-list)
+                   (split-string path (regexp-quote path-separator)))
 	       (if (and sibling (file-exists-p sibling))
 		   ;; Uninstalled, Emacs builddir != srcdir.
 		   (setq alternative sibling)

-- 
Jeremy A. Gray
gray@metacomet.net

"Remember the Pueblo." -- the Fourth Law of Marvin

Re: INFOPATH and emacs

[Kai Großjohann]

David Masterson <David.Masterson@synopsys.com> writes:

> And still a problem because Info would preset the list based upon
> INFOPATH and, thus, be messed up even before it gets to the
> add-to-list.  What you're thinking means that you have to have two
> INFOPATH settings -- one for 'info' and one for 'emacs'.

Thanks for catching this.  I completely missed this.
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)

Re: INFOPATH and emacs

[Jeremy Gray]

David Masterson <David.Masterson@synopsys.com> wrote:  
> Jeremy Gray writes:
> 
>> This appears to work, at least for me.  
> 
>> +		 (if (string-match ":$" path)
> 
> What if the INFOPATH include "::" in it?  In other words, what if he
> wanted to append to Info-default-directory-list rather than prepend to
> it?

You would have to set INFOPATH to the list of directories.  I just
implemented the ultimate colon behavior as it's documented for info
standalone.  So, any "::" parts of INFOPATH would be pruned (nil is not
a directory), with the ultimate colon behavior applicable if necessary.  

Of course casing on "^:" or "::" could also be done.  

> Also, I think Info-default-directory-list is deprecated in XEmacs.

Could be.  I exclusively use GNU emacs on unix-like machines.  So I tend
to say things like ":$" when I really mean (concat path-separator "$").
Or whatever.  

-- 
Jeremy A. Gray
gray@metacomet.net

"Remember the Pueblo." -- the Fourth Law of Marvin

Re: INFOPATH and emacs

[Ritesh]

Jeremy Gray <gray@euthanasia.ath.cx> wrote in message news:<slrnb9tse4.u3i.gray@euthanasia.ath.cx>...
> Kevin Rodgers <ihs_4664@yahoo.com> wrote:  
> > Jeremy Gray wrote:
> >> 
> >> That means that info readers will only look in /home/ritesh/info for
> >> info files.
> > 
> > No.
> 
> Yep, your right.  I never heard of the info's trailing colon feature
> before.  Plus I only found the info standalone node today (I always
> wondered where that was), and the manpage doesn't mention it.  
> 
> > So there is a discrepancy between the command line info program and
> > Emacs' M-x info command in how an empty INFOPATH component is
> > interpreted.  I think Emacs should emulate info as closely as
> > possible; if the OP agrees, he should use M-x report-emacs-bug to
> > submit a bug report.
> 
> I think setting the entire path is easier in the long run since it
> works for both info and info-mode.  But, I think this is a easily fixed
> bug.

that can be done, of-course, but that is hardly 'elegant'. Also, as
Jeremy
Gray says, emacs should emulate info as closely as possible. if info
is happy with the trailing ':', so should emacs be....

Re: INFOPATH and emacs

[Ritesh]

Jeremy Gray <gray@euthanasia.ath.cx> wrote in message news:<slrnb9tvbo.u3i.gray@euthanasia.ath.cx>...
> Jeremy Gray <gray@euthanasia.ath.cx> wrote:  
> > Kevin Rodgers <ihs_4664@yahoo.com> wrote:  
> >> 
> >> So there is a discrepancy between the command line info program and
> >> Emacs' M-x info command in how an empty INFOPATH component is
> >> interpreted.  I think Emacs should emulate info as closely as
> >> possible; if the OP agrees, he should use M-x report-emacs-bug to
> >> submit a bug report.
> > 
> > I think setting the entire path is easier in the long run since it
> > works for both info and info-mode.  But, I think this is a easily fixed
> > bug.  
> 
> This appears to work, at least for me.  
> 
> diff -Naur emacs-21.3/lisp/info.el emacs-21.3-jag/lisp/info.el
> --- emacs-21.3/lisp/info.el	2001-12-21 13:08:17.000000000 -0600
> +++ emacs-21.3-jag/lisp/info.el	2003-04-17 14:08:25.000000000 -0500

> @@ -320,7 +320,8 @@
>        (insert-file-contents fullname visit))))
>   
>  (defun info-initialize ()
> -  "Initialize `Info-directory-list', if that hasn't been done yet."
> +  "Initialize `Info-directory-list', respecting a final colon like
> +info standalone, if that hasn't been done yet."
>    (unless Info-directory-list
>      (let ((path (getenv "INFOPATH"))
>  	  (source (expand-file-name "info/" source-directory))
> @@ -341,7 +342,10 @@
>        (setq Info-directory-list
>  	    (prune-directory-list
>  	     (if path
> -		 (split-string path (regexp-quote path-separator))
> +		 (if (string-match ":$" path)
> +                     (append (split-string path (regexp-quote path-separator))
> +                             Info-default-directory-list)
> +                   (split-string path (regexp-quote path-separator)))
>  	       (if (and sibling (file-exists-p sibling))
>  		   ;; Uninstalled, Emacs builddir != srcdir.
>  		   (setq alternative sibling)

thanks!
can you please list out the steps? I've deleted/added the relevent
lines from above to my info.el file and also byte-compiled the file.
however, still the same behavior persists, that is the default info
path is not appended. I am running Red Hat Linux 7.3, emacs 21.2.1.

Re: INFOPATH and emacs

[Eli Zaretskii]

> From: sood@tenet.res.in (Ritesh)
> Newsgroups: gnu.emacs.help
> Date: 19 Apr 2003 02:34:57 -0700
> 
> can you please list out the steps? I've deleted/added the relevent
> lines from above to my info.el file and also byte-compiled the file.
> however, still the same behavior persists, that is the default info
> path is not appended. I am running Red Hat Linux 7.3, emacs 21.2.1.

That's because info.el is preloaded into Emacs.  You need to redump
Emacs, or manually load the newly-compiled info.elc.

Re: INFOPATH and emacs

[Stefan Monnier]

>>>>> "Eli" == Eli Zaretskii <eliz@elta.co.il> writes:
> That's because info.el is preloaded into Emacs.  You need to redump
> Emacs, or manually load the newly-compiled info.elc.

What were you smoking ?  Must be pretty good stuff !


        Stefan "who had to double check even though he remembered
                that Info-goto-node is not autoloaded."

Re: INFOPATH and emacs

[Ritesh]

"Stefan Monnier" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu> wrote in message news:<5ld6jil37r.fsf@rum.cs.yale.edu>...
> >>>>> "Eli" == Eli Zaretskii <eliz@elta.co.il> writes:
> > That's because info.el is preloaded into Emacs.  You need to redump
> > Emacs, or manually load the newly-compiled info.elc.
> 
> What were you smoking ?  Must be pretty good stuff !
> 
> 
>         Stefan "who had to double check even though he remembered
>                 that Info-goto-node is not autoloaded."


then i suppose only Jeremy Gray can clear the confusion. She/he seems
to have got it working alright.

Re: INFOPATH and emacs

[Ritesh]

sood@tenet.res.in (Ritesh) wrote in message news:<e910f684.0304192303.4833491f@posting.google.com>...
> "Stefan Monnier" <monnier+gnu.emacs.help/news/@flint.cs.yale.edu> wrote in message news:<5ld6jil37r.fsf@rum.cs.yale.edu>...
> > >>>>> "Eli" == Eli Zaretskii <eliz@elta.co.il> writes:
> > > That's because info.el is preloaded into Emacs.  You need to redump
> > > Emacs, or manually load the newly-compiled info.elc.
> > 
> > What were you smoking ?  Must be pretty good stuff !
> > 
> > 
> >         Stefan "who had to double check even though he remembered
> >                 that Info-goto-node is not autoloaded."
> 
> 
> then i suppose only Jeremy Gray can clear the confusion. She/he seems
> to have got it working alright.

it works!!
without having to manually load info.elc
just stared hard at the code provided by Jeremy Gray(I'm not familiar
with lisp) and figured what exactly the code was doing, and the error
i was making in copying the lines to info.el verbatim.
thanks a lot people!!