From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: help-gnu-emacs Digest, Vol 188, Issue 10
Date: Sat, 07 Jul 2018 10:29:19 +0300 [thread overview]
Message-ID: <83sh4vjygg.fsf@gnu.org> (raw)
In-Reply-To: <CAECeiF_jESm8z14EdroQsxgBZYWkkixyroS4vjO3urQzU3PsrA@mail.gmail.com> (message from Baldero Mendoza on Fri, 6 Jul 2018 21:43:24 -0400)
> From: Baldero Mendoza <bzy711@gmail.com>
> Date: Fri, 6 Jul 2018 21:43:24 -0400
>
> Ok. I'm nobody's guru in anything, but I have used - and continue to use -
> both of these utilities for years now.
Nothing wrong with that.
> Normally with each new update of emacs nothing much changes with these two
> in my usage of them.
> For org mode, 1) I open Emacs, 2) if I have a question with org mode I do "
> C h i" to go to info, 3) then "m", 4) then " org" followed by "tab" to fill
> it out, then " enter". This used to to take me to something of an org mode
> manual within info.
> Not any more. Now all I get is " [ no match ] ".
Please tell more about your current Emacs version and about your
upgrade process. What is the current Emacs version, and what was the
one you had before? How did you install the new version, and on what
OS?
Also, do you have the INFOPATH environment variable set, and if so,
what is its value? What is the value of the Info-directory-list
variable inside Emacs (you can show it using the "M-:" command)?
Finally, if you do "C-h i", what do you see in the node "dir" that
this displays? Please show its entire contents, and please also tell
what is the value of default-directory in the *Info* buffer showing
that node.
I presume that the manuals you cannot find are somewhere on your
system, but Info is misconfigured, and so doesn't see them. The
questions above are designed to find the reasons for that.
prev parent reply other threads:[~2018-07-07 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.19.1530892803.27295.help-gnu-emacs@gnu.org>
2018-07-07 1:43 ` help-gnu-emacs Digest, Vol 188, Issue 10 Baldero Mendoza
2018-07-07 7:29 ` Eli Zaretskii [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sh4vjygg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).