GNU bug report logs - #26057
25.1; 'M-x eshell-source-file' fails

Previous Next

Package: emacs;

Reported by: Chunyang Xu <mail <at> xuchunyang.me>

Date: Sat, 11 Mar 2017 09:58:01 UTC

Severity: minor

Tags: fixed

Found in version 25.1

Fixed in version 27.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 26057 in the body.
You can then email your comments to 26057 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#26057; Package emacs. (Sat, 11 Mar 2017 09:58:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Chunyang Xu <mail <at> xuchunyang.me>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Sat, 11 Mar 2017 09:58:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Chunyang Xu <mail <at> xuchunyang.me>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.1; 'M-x eshell-source-file' fails
Date: Sat, 11 Mar 2017 17:57:24 +0800
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?






Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#26057; Package emacs. (Fri, 26 Jul 2019 12:16:01 GMT) Full text and rfc822 format available.

Message #8 received at 26057 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Chunyang Xu <mail <at> xuchunyang.me>
Cc: 26057 <at> debbugs.gnu.org
Subject: Re: bug#26057: 25.1; 'M-x eshell-source-file' fails
Date: Fri, 26 Jul 2019 14:15:24 +0200
Chunyang Xu <mail <at> xuchunyang.me> writes:

> 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

[...]

> it fails by showing the following in the echo area
>
>   eshell-source-file: No catch for tag: eshell-replace-command, (let

[...]

> I don't really sure about the purpose of making eshell-source-file
> interactive, maybe it is a bug?

It looks like the interactive spec has always been there (at least since
2000), but that function can't possibly work as an interactive command.
So, as you say, I think it's a bug, and I've now removed the interactive
spec from the function on the Emacs trunk.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




Added tag(s) fixed. Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Fri, 26 Jul 2019 12:16:02 GMT) Full text and rfc822 format available.

bug marked as fixed in version 27.1, send any further explanations to 26057 <at> debbugs.gnu.org and Chunyang Xu <mail <at> xuchunyang.me> Request was from Lars Ingebrigtsen <larsi <at> gnus.org> to control <at> debbugs.gnu.org. (Fri, 26 Jul 2019 12:16:02 GMT) Full text and rfc822 format available.

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sat, 24 Aug 2019 11:24:08 GMT) Full text and rfc822 format available.

This bug report was last modified 4 years and 218 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.