bug#17225: 24.4.50; emacs -Q "d:\some\dir": "Symbol's function definition is void: dired-noselect"

bug#17225: 24.4.50; emacs -Q "d:\some\dir": "Symbol's function definition is void: dired-noselect"

[Drew Adams]

I started Emacs using a Windows shortcut with this Target:
D:\MY-EMACS-LOCATION\bin\runemacs.exe -Q --debug-init "d:\SOME\DIR"

I immediately got this error:

run-hook-with-args-until-success: Symbol's function definition is void: dired-noselect

In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
 of 2014-04-06 on ODIEONE
Bzr revision: 116947 lekktu@gmail.com-20140407005152-3ep5fsp53mgxh67m
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/snapshot/trunk
 --enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
 LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
 -Ic:/Devel/emacs/include''

bug#17225: 24.4.50; emacs -Q "d:\some\dir": "Symbol's function definition is void: dired-noselect"

[Eli Zaretskii]

> Date: Tue, 8 Apr 2014 08:45:54 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> 
> I started Emacs using a Windows shortcut with this Target:
> D:\MY-EMACS-LOCATION\bin\runemacs.exe -Q --debug-init "d:\SOME\DIR"
> 
> I immediately got this error:
> 
> run-hook-with-args-until-success: Symbol's function definition is void: dired-noselect
> 
> In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
>  of 2014-04-06 on ODIEONE
> Bzr revision: 116947 lekktu@gmail.com-20140407005152-3ep5fsp53mgxh67m

I cannot reproduce this here (with a trunk revision only slightly
newer than yours: 116956).  Please see if some local configuration
could be the cause.

bug#17225: 24.4.50; emacs -Q "d:\some\dir": "Symbol's function definition is void: dired-noselect"

[Juanma Barranquero]

On Tue, Apr 8, 2014 at 6:27 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> Please see if some local configuration could be the cause.

No, this isn't a local configuration issue. I can reproduce it with
the same snapshot that Drew is using, but the bug is gone with the
current trunk, though I have no idea which commit fixed it...

Anyway, I'm building a snapshot from today's trunk, it should be
available shortly.

    J

bug#17225: 24.4.50; emacs -Q "d:\some\dir": "Symbol's function definition is void: dired-noselect"

[Juanma Barranquero]

Version: 24.5

On Tue, Apr 8, 2014 at 6:38 PM, Juanma Barranquero <lekktu@gmail.com> wrote:

> Anyway, I'm building a snapshot from today's trunk, it should be
> available shortly.

On its way. Closing.

bug#17225: 24.4.50; emacs -Q "d:\some\dir": "Symbol's function definition is void: dired-noselect"

[Drew Adams]

> the bug is gone with the current trunk...
> 
> Anyway, I'm building a snapshot from today's trunk, it should be
> available shortly.

Thank you. Feel free to close the bug in that case.

bug#17225: 24.4.50; emacs -Q "d:\some\dir": "Symbol's function definition is void: dired-noselect"

[Drew Adams]

> I cannot reproduce this here (with a trunk revision only slightly
> newer than yours: 116956).  Please see if some local configuration
> could be the cause.

Try using the exact same build, perhaps?  It is from Juanma.

I don't know of any local configuration.  What did you have in mind?

As I said in the recipe, I started Emacs from a Windows shortcut,
with the shortcut as described.  The only things I left out of the
info about the shortcut are these:

1. The exact absolute file names ("paths") for runemacs.exe and
the directory visited by Dired.

2. The fact that I have the "Start in:" field pointing to that
same diretory (that is used for Dired).  So Emacs should start
in that directory, showing Dired for it.

bug#17225: 24.4.50; emacs -Q "d:\some\dir": "Symbol's function definition is void: dired-noselect"

[Juanma Barranquero]

On Tue, Apr 8, 2014 at 8:25 PM, Drew Adams <drew.adams@oracle.com> wrote:

> As I said in the recipe, I started Emacs from a Windows shortcut,
> with the shortcut as described.  The only things I left out of the
> info about the shortcut are these:

FWIW, the shortcut wasn't necessary. I could reproduce it with

 emacs -Q --debug-init "C:\devel\emacs"

bug#17225: 24.4.50; emacs -Q "d:\some\dir": "Symbol's function definition is void: dired-noselect"

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Tue, 8 Apr 2014 21:31:09 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>, 17225@debbugs.gnu.org
> 
> On Tue, Apr 8, 2014 at 8:25 PM, Drew Adams <drew.adams@oracle.com> wrote:
> 
> > As I said in the recipe, I started Emacs from a Windows shortcut,
> > with the shortcut as described.  The only things I left out of the
> > info about the shortcut are these:
> 
> FWIW, the shortcut wasn't necessary. I could reproduce it with
> 
>  emacs -Q --debug-init "C:\devel\emacs"

FWIW, I tried both methods.

bug#17225: 24.4.50; emacs -Q "d:\some\dir": "Symbol's function definition is void: dired-noselect"

[Juanma Barranquero]

On Wed, Apr 9, 2014 at 4:47 AM, Eli Zaretskii <eliz@gnu.org> wrote:

> FWIW, I tried both methods.

Sure. I think the bug appeared on

  116945: Stefan Monnier 2014-04-06 * lisp/dired-aux.el
(dired-file-set-difference): Use lexical-scoping.

and likely disappeared with

  116948: Glenn Morris 2014-04-07 Auto-commit of loaddefs files.

so the window to hit the bug was short indeed. But certainly, it is
perfectly repeatable with my emacs-trunk-20140407-r116947-bin-i386.zip
snapshot.

    J