From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Installation via el-get: info not added correctly
Date: Fri, 27 Jul 2012 08:03:48 +0200 [thread overview]
Message-ID: <87wr1p7naz.fsf@Rainer.invalid> (raw)
In-Reply-To: CABo_DbByNq6ni46AVKEPQEzqJNO2JEa+F_oRtBqtk-x-CmJPcA@mail.gmail.com
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.
The ".info" suffix has actually only been added quite recently with
Emacs 24.1.50 and info continues to work correctly without any suffix,
so I don't understand why el-get seemingly insists on it.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2012-07-27 6:04 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 [this message]
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
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=87wr1p7naz.fsf@Rainer.invalid \
--to=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).