emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mike McLean <mike.mclean@pobox.com>
To: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Cc: Achim Gratz <Stromeko@nexgo.de>
Subject: Re: Installation via el-get: info not added correctly
Date: Sun, 29 Jul 2012 15:43:26 -0400	[thread overview]
Message-ID: <A97003A1-F2A1-41B4-B6BA-548982759BEE@pobox.com> (raw)
In-Reply-To: <CANid5Q56AHHDdKG_QD=+xPRLYCOqHJdBTkDrBHPWdGm-CdkJ0g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2670 bytes --]


On Jul 28, 2012, at 2:13 PM, Mike McLean wrote:

> On Fri, Jul 27, 2012 at 2:03 AM, Achim Gratz <Stromeko@nexgo.de> wrote:
> Markus Baden writes:
> > I just installed org-mode via the recipe provided with the current
> > development version of el-get [1]. Org-Mode is installed correctly
> > into emacs.d/el-get/org-mode and the docs can be found in the doc
> > subfolder. The recipe [2] adds the doc to the info via the :info "doc"
> > property. However, when going to the info browser with C-h i the
> > org-mode docs cannot be found. In the doc subfolder there is a file
> > called "org" (no filename extension), which looks like the info file.
> > After doing a "cp org org.info" the org-mode info shows up in the info
> > browser.
> 
> El-get for whatever reason seems to think that all info files have a
> ".info" suffix, but they appear to never check if that assumption is
> true.  I don't understand how they set up the info tree further on from
> looking at the sources.  File a bug report for el-get I'd say.
> 
> Looking at this a bit this morning, I'm not sure that it is el-get (at least alone) that is insisting on the .info suffix. The portion of elisp in el-get that adds the .info suffix:
> 
> #+begin_src emacs-lisp
> (if (string= (substring infofile -5) ".info")
>     infofile
>     (concat infofile ".info"))
> #+end_src
> 
> (Side note, I did try a work around, https://github.com/SkydiveMike/el-get/commit/88920c84bbe4d814bae1e79cdda163315d8d8d24 that doesn't work).
> 
> Is only called if the ~dir~' file does not exist (and other conditions) and as part of creating a command string for ~/usr/bin/install-info~. Since an non-built (no execution of ~make~) Org mode Git clone has a ~dir~ file, this code is never called.
> 
> I also don't believe that ~cp org org.info~ in ~$HOME/.emacs.d/el-get/org-mode/~ fixes things (I currently can't get the correct info to display using that).

After some more investigation, I don't think this is a bug with either Org or el-get. I had other issues with my Info path setups in my specific configuration (Emacs on OS X from http://emacsformacosx.com) that included an invalid build-directory artifact and more significantly always put the Emacs ``info'' directory as the first item in my ``Info-directory-list''. This meant that the built-in Org info would always supersede the info for my current version of Org (installed by el-get). 

Once I resolved all of that, my Emacs Info now sees the correct version of Org info from el-get without needing to ``cp org org.info''. 

More gory details at: https://github.com/dimitri/el-get/issues/821

Sorry for the noise.

[-- Attachment #2: Type: text/html, Size: 3973 bytes --]

  parent reply	other threads:[~2012-07-29 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27  4:06 Installation via el-get: info not added correctly Markus Baden
2012-07-27  6:03 ` Achim Gratz
2012-07-27  6:21   ` Markus Baden
2012-07-28 18:13   ` Mike McLean
     [not found]   ` <CANid5Q56AHHDdKG_QD=+xPRLYCOqHJdBTkDrBHPWdGm-CdkJ0g@mail.gmail.com>
2012-07-29 19:43     ` Mike McLean [this message]
2012-07-29 20:07       ` Jude DaShiell

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=A97003A1-F2A1-41B4-B6BA-548982759BEE@pobox.com \
    --to=mike.mclean@pobox.com \
    --cc=Stromeko@nexgo.de \
    --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).