From: Chunyang Xu <mail@xuchunyang.me>
To: 26057@debbugs.gnu.org
Subject: bug#26057: 25.1; 'M-x eshell-source-file' fails
Date: Sat, 11 Mar 2017 17:57:24 +0800 [thread overview]
Message-ID: <m2lgsc16gr.fsf@xuchunyang.me> (raw)
After I open Eshell, the eshell-source-file is available as an
interactive command and in (info "(eshell) Scripts") it says
Scripts are invoked from Eshell with ‘source’, or from anywhere in Emacs
with ‘eshell-source-file’.
so it looks like to me I can run
M-x eshell-source-file RET /tmp/foo.esh RET
the content of the file (which should not matter)
~ $ cat /tmp/foo.esh
pwd
~ $
it fails by showing the following in the echo area
eshell-source-file: No catch for tag: eshell-replace-command, (let ((eshell-command-name (quote "/tmp/foo.esh")) (eshell-command-arguments (quote nil))) (eshell-trap-errors (eshell-named-command "pwd")))
the backtrace is
Debugger entered--Lisp error: (no-catch eshell-replace-command (let ((eshell-command-name (quote "/tmp/foo.esh")) (eshell-command-arguments (quote nil))) (eshell-trap-errors (eshell-named-command "pwd"))))
throw(eshell-replace-command (let ((eshell-command-name (quote "/tmp/foo.esh")) (eshell-command-arguments (quote nil))) (eshell-trap-errors (eshell-named-command "pwd"))))
eshell-source-file("/tmp/foo.esh")
funcall-interactively(eshell-source-file "/tmp/foo.esh")
call-interactively(eshell-source-file record nil)
command-execute(eshell-source-file record)
execute-extended-command(nil "eshell-source-file" nil)
funcall-interactively(execute-extended-command nil "eshell-source-file" nil)
call-interactively(execute-extended-command nil nil)
command-execute(execute-extended-command)
I don't really sure about the purpose of making eshell-source-file
interactive, maybe it is a bug?
next reply other threads:[~2017-03-11 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 9:57 Chunyang Xu [this message]
2019-07-26 12:15 ` bug#26057: 25.1; 'M-x eshell-source-file' fails Lars Ingebrigtsen
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=m2lgsc16gr.fsf@xuchunyang.me \
--to=mail@xuchunyang.me \
--cc=26057@debbugs.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.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).