all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Running external info within Emacs
Date: Fri, 31 Mar 2023 20:09:40 +0200	[thread overview]
Message-ID: <86y1ncyeqj.fsf@gnu.org> (raw)
In-Reply-To: <83o7o92y6a.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 31 Mar 2023 10:10:53 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> What about shell-command? or if you invoke "info latex2e" from
> "M-x shell"? same error?

Yes, the same error with both of them.

> So the issue is that shell commands invoked from Emacs fail when the
> same shell commands invoked from the shell work?

Yes, but this is statement applies only to the directories I've added to
$INFOPATH. 'info dir' for example works as expected within Emacs in all
scenarios.

> And that it happens _only_ for this one Info file?  Then what is the
> difference between this Info file and the other ones?

Nope, I moved my Emacs directory, adjusted $INFOPATH and did in the
shell:

  $ info emacs
  $ info elisp
  $ info gnus

They all work. Within Emacs, no avail, no matter what I try.

Best, Arash



  reply	other threads:[~2023-03-31 18:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 10:56 Running external info within Emacs Arash Esbati
2023-03-30 13:17 ` Eli Zaretskii
2023-03-30 15:00   ` Arash Esbati
2023-03-30 15:56     ` Eli Zaretskii
2023-03-31  6:43       ` Arash Esbati
2023-03-31  7:10         ` Eli Zaretskii
2023-03-31 18:09           ` Arash Esbati [this message]
2023-03-31 19:07             ` Eli Zaretskii
2023-04-01 10:51               ` Arash Esbati
2023-04-01 11:37                 ` Eli Zaretskii
2023-04-01 14:45                   ` Arash Esbati
2023-04-01 15:34                     ` Eli Zaretskii
2023-04-02 17:04                       ` Arash Esbati
2023-04-02 17:14                         ` Eli Zaretskii

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=86y1ncyeqj.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 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.