unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Iñigo Serna" <inigoserna@gmx.com>
To: Jim Porter <jporterbugs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: eshell/addpath broken since commit dea24a0f7d
Date: Tue, 25 Jan 2022 20:50:41 +0100	[thread overview]
Message-ID: <87lez3wq3m.fsf@gmx.com> (raw)
In-Reply-To: <fcdfd0de-c2f1-b074-8aa8-772f803b73d0@gmail.com>

Hi Jim,

> Have you tried `make bootstrap' (or `touch lisp/eshell/*.el' if 
> you
> don't want to rebuild everything)? Commit dea24a0f7d changes the
> `eshell-eval-using-options' macro in a way that requires 
> recompiling
> files that use it.

Ouch. You're right, I missed this part.
Sorry everyone for the noise.

Thanks,
-- 
Iñigo Serna

On 25 January 2022 at 20:19 +01, Jim Porter 
<jporterbugs@gmail.com> wrote:

> On 1/25/2022 10:49 AM, Iñigo Serna wrote:
>> It looks `eshell/addpath' is broken in master since commit 
>> dea24a0f7d [1].
>> $ src/emacs --debug-init -Q --eval "(progn (require 'eshell)
>> (eshell/addpath \"~/bin\"))"
>> Debugger entered--Lisp error: (wrong-number-of-arguments (4 
>> . 4) 3)
>>   eshell--do-opts("addpath" ((98 "begin" nil prepend "add path
>>  element at beginning") (104 "help" nil nil "display this usage
>>  message") :usage "[-b] PATH\nAdds the given PATH to $PATH.")
>>  ("~/bin"))
>>   eshell/addpath("~/bin")
>
> Have you tried `make bootstrap' (or `touch lisp/eshell/*.el' if 
> you
> don't want to rebuild everything)? Commit dea24a0f7d changes the
> `eshell-eval-using-options' macro in a way that requires 
> recompiling
> files that use it.
>
> - Jim



      reply	other threads:[~2022-01-25 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 18:49 eshell/addpath broken since commit dea24a0f7d Iñigo Serna
2022-01-25 19:19 ` Jim Porter
2022-01-25 19:50   ` Iñigo Serna [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=87lez3wq3m.fsf@gmx.com \
    --to=inigoserna@gmx.com \
    --cc=emacs-devel@gnu.org \
    --cc=jporterbugs@gmail.com \
    /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).