bug#5083: 23.1.50; Eshell | Invalid function: eshell-eval-using-options

bug#5083: 23.1.50; Eshell | Invalid function: eshell-eval-using-options

[Leo]

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug.  If you can, give
a recipe starting from `emacs -Q':

To reproduce

1. emacs -q and M-x eshell

2. mkdir test

"Invalid function: eshell-eval-using-options" will be printed in the
eshell buffer although 'test' is successfully created.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
For information about debugging Emacs, please read the file
/Applications/Emacs.app/Contents/Resources/etc/DEBUG.


In GNU Emacs 23.1.50.1 (i386-apple-darwin9.8.0, NS apple-appkit-949.54)
 of 2009-11-27 on victoria.local
Windowing system distributor `Apple', version 10.3.949
configured using `configure  '--with-ns''

bug#5083: 23.1.50; Eshell | Invalid function: eshell-eval-using-options

[Leo]

On 2009-11-30 19:20 +0000, Leo wrote:
> To reproduce
>
> 1. emacs -q and M-x eshell
>
> 2. mkdir test
>
> "Invalid function: eshell-eval-using-options" will be printed in the
> eshell buffer although 'test' is successfully created.

Additionally, 'rm somefile' generates

    Symbol's value as variable is void: interactive

and the file is not removed.

Leo

bug#5083: 23.1.50; Eshell | Invalid function: eshell-eval-using-options

[Michael Albinus]

Leo <sdl.web@gmail.com> writes:

> On 2009-11-30 19:20 +0000, Leo wrote:
>> To reproduce
>>
>> 1. emacs -q and M-x eshell
>>
>> 2. mkdir test
>>
>> "Invalid function: eshell-eval-using-options" will be printed in the
>> eshell buffer although 'test' is successfully created.
>
> Additionally, 'rm somefile' generates
>
>     Symbol's value as variable is void: interactive
>
> and the file is not removed.

I cannot reproduce it (anymore). I have seen a similar error wrt
eshell-eval-using-options some days ago; meanwhile it does not happen
anymore. Maybe you make a fresh checkout, and apply "make bootstrap"?

> Leo

Best regards, Michael.

bug#5083: marked as done (23.1.50; Eshell | Invalid function: eshell-eval-using-options)

[Emacs bug Tracking System]

[-- Attachment #1: Type: text/plain, Size: 914 bytes --]

Your message dated Tue, 01 Dec 2009 14:13:53 +0000
with message-id <m01vjebx3y.fsf@cam.ac.uk>
and subject line Re: bug#5083: 23.1.50; Eshell | Invalid function: eshell-eval-using-options
has caused the Emacs bug report #5083,
regarding 23.1.50; Eshell | Invalid function: eshell-eval-using-options
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
5083: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=5083
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 2994 bytes --]

From: Leo <sdl.web@gmail.com>
To: emacs-pretest-bug@gnu.org
Subject: 23.1.50; Eshell | Invalid function: eshell-eval-using-options
Date: Mon, 30 Nov 2009 19:20:14 +0000
Message-ID: <m0y6lnbz0x.fsf@cam.ac.uk>

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug.  If you can, give
a recipe starting from `emacs -Q':

To reproduce

1. emacs -q and M-x eshell

2. mkdir test

"Invalid function: eshell-eval-using-options" will be printed in the
eshell buffer although 'test' is successfully created.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
For information about debugging Emacs, please read the file
/Applications/Emacs.app/Contents/Resources/etc/DEBUG.


In GNU Emacs 23.1.50.1 (i386-apple-darwin9.8.0, NS apple-appkit-949.54)
 of 2009-11-27 on victoria.local
Windowing system distributor `Apple', version 10.3.949
configured using `configure  '--with-ns''


[-- Attachment #3: Type: message/rfc822, Size: 2652 bytes --]

From: Leo <sdl.web@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 5083-done@emacsbugs.donarmstrong.com
Subject: Re: bug#5083: 23.1.50; Eshell | Invalid function: eshell-eval-using-options
Date: Tue, 01 Dec 2009 14:13:53 +0000
Message-ID: <m01vjebx3y.fsf@cam.ac.uk>

On 2009-12-01 11:00 +0000, Michael Albinus wrote:
> Leo <sdl.web@gmail.com> writes:
>
>> On 2009-11-30 19:20 +0000, Leo wrote:
>>> To reproduce
>>>
>>> 1. emacs -q and M-x eshell
>>>
>>> 2. mkdir test
>>>
>>> "Invalid function: eshell-eval-using-options" will be printed in the
>>> eshell buffer although 'test' is successfully created.
>>
>> Additionally, 'rm somefile' generates
>>
>>     Symbol's value as variable is void: interactive
>>
>> and the file is not removed.
>
> I cannot reproduce it (anymore). I have seen a similar error wrt
> eshell-eval-using-options some days ago; meanwhile it does not happen
> anymore. Maybe you make a fresh checkout, and apply "make bootstrap"?

Indeed this is due to eshell-eval-using-options macro. `em-unix'
requires `esh-opt' to compile otherwise this error is borne. I have
close this bug. Sorry for the false report.

>
>> Leo
>
> Best regards, Michael.

Leo