bug#69265: 30.0.50; eshell: ls wrong number of arguments

bug#69265: 30.0.50; eshell: ls wrong number of arguments

[Colin Baxter]

1. emacs -Q <RET>
2. Mx-eshell <RET>
3. ls <RET>
4. Wrong number of arguments: (5 . 5), 4

GNU Emacs 30.0.50 (build 1, i686-pc-linux-gnu, cairo version 1.14.8) of 2024-02-19

Best wishes,
Colin Baxter.


In GNU Emacs 30.0.50 (build 1, i686-pc-linux-gnu, cairo version
 1.14.8) of 2024-02-19 built on bluestar
Repository revision: 8f260bb93f534b24d9a93d3315804ffe0c1fec4f
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.11902000
System Description: Debian GNU/Linux 9 (stretch)

Configured using:
 'configure --prefix=/home/redknight/local/opt/emacs-dev
 --with-x-toolkit=no --with-mailutils --without-sqlite3
 --without-sound --with-cairo --with-imagemagick --without-xaw3d
 --with-native-compilation=no --without-toolkit-scroll-bars'

Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ
IMAGEMAGICK JPEG JSON LCMS2 LIBOTF LIBSELINUX LIBSYSTEMD LIBXML2
M17N_FLT MODULES NOTIFY INOTIFY OLDXMENU PDUMPER PNG RSVG SECCOMP
THREADS TIFF X11 XDBE XIM XINPUT2 XPM ZLIB

Important settings:
  value of $LANG: en_GB.UTF-8
  locale-coding-system: utf-8

Major mode: Eshell

Minor modes in effect:
  TeX-source-correlate-mode: t
  eshell-prompt-mode: t
  eshell-pred-mode: t
  eshell-hist-mode: t
  eshell-cmpl-mode: t
  auto-insert-mode: t
  global-atomic-chrome-edit-mode: t
  server-mode: t
  global-emojify-mode: t
  emojify-mode: t
  eshell-proc-mode: t
  eshell-arg-mode: t
  project-x-mode: t
  savehist-mode: t
  display-time-mode: t
  global-so-long-mode: t
  show-paren-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  minibuffer-regexp-mode: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t

bug#69265: 30.0.50; eshell: ls wrong number of arguments

[Jim Porter]

On 2/19/2024 12:59 AM, Colin Baxter wrote:
> 1. emacs -Q <RET>
> 2. Mx-eshell <RET>
> 3. ls <RET>
> 4. Wrong number of arguments: (5 . 5), 4

This looks like you have a stale .elc file. (Unfortunately, if a macro 
defined in another file is changed, files using that macro aren't 
automatically recompiled.) Try `rm lisp/eshell/*.elc && make` to do a 
full Eshell rebuild.

If that doesn't work, you can run `eshell-debug error` to make Eshell 
stop trapping errors, and then rerun this (possibly after calling 
`toggle-debug-on-error`). Then you could at least get a stack trace.

bug#69265: 30.0.50; eshell: ls wrong number of arguments

[Colin Baxter]

>>>>> Jim Porter <jporterbugs@gmail.com> writes:

    > On 2/19/2024 12:59 AM, Colin Baxter wrote:
    >> 1. emacs -Q <RET> 2. Mx-eshell <RET> 3. ls <RET> 4. Wrong number
    >> of arguments: (5 . 5), 4

    > This looks like you have a stale .elc file. (Unfortunately, if a
    > macro defined in another file is changed, files using that macro
    > aren't automatically recompiled.) Try `rm lisp/eshell/*.elc &&
    > make` to do a full Eshell rebuild.

That didn't work. However, a make bootstrap worked, which I really
should have done before sending a bug-report. I'm sorry, I feel I've
wasted your time.

Thanks.

Colin.

bug#69265: 30.0.50; eshell: ls wrong number of arguments

[Eli Zaretskii]

> Cc: 69265@debbugs.gnu.org
> From: Colin Baxter <m43cap@yandex.com>
> Date: Mon, 19 Feb 2024 20:25:08 +0000
> 
> >>>>> Jim Porter <jporterbugs@gmail.com> writes:
> 
>     > On 2/19/2024 12:59 AM, Colin Baxter wrote:
>     >> 1. emacs -Q <RET> 2. Mx-eshell <RET> 3. ls <RET> 4. Wrong number
>     >> of arguments: (5 . 5), 4
> 
>     > This looks like you have a stale .elc file. (Unfortunately, if a
>     > macro defined in another file is changed, files using that macro
>     > aren't automatically recompiled.) Try `rm lisp/eshell/*.elc &&
>     > make` to do a full Eshell rebuild.
> 
> That didn't work. However, a make bootstrap worked, which I really
> should have done before sending a bug-report.

Thanks, I'm therefore closing this bug.