From: Jeremy Gray <gray@euthanasia.ath.cx>
Subject: Re: INFOPATH and emacs
Date: Thu, 17 Apr 2003 19:22:29 GMT [thread overview]
Message-ID: <slrnb9tse4.u3i.gray@euthanasia.ath.cx> (raw)
In-Reply-To: 3E9EE2EE.5060709@yahoo.com
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
next prev parent reply other threads:[~2003-04-17 19:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 6:34 INFOPATH and emacs Ritesh
2003-04-16 17:54 ` David Masterson
2003-04-17 5:18 ` Ritesh
2003-04-17 6:52 ` Jeremy Gray
2003-04-17 17:22 ` Kevin Rodgers
2003-04-17 19:22 ` Jeremy Gray [this message]
2003-04-17 20:12 ` Jeremy Gray
2003-04-17 19:26 ` David Masterson
2003-04-17 20:46 ` Jeremy Gray
2003-04-19 9:34 ` Ritesh
2003-04-19 11:38 ` Eli Zaretskii
[not found] ` <mailman.4929.1050748877.21513.help-gnu-emacs@gnu.org>
2003-04-19 19:03 ` Stefan Monnier
2003-04-20 7:03 ` Ritesh
2003-04-22 13:44 ` Ritesh
2003-04-19 8:44 ` Ritesh
2003-04-17 16:52 ` Kai Großjohann
2003-04-17 18:55 ` David Masterson
2003-04-17 20:21 ` Kai Großjohann
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=slrnb9tse4.u3i.gray@euthanasia.ath.cx \
--to=gray@euthanasia.ath.cx \
--cc=gray@metacomet.net \
/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.