[h-e-w] RE: Please test w32-shell-execute

[Raymond Zeitler]

Sorry for the late reply.  All five test cases work for me.

Win XP Pro SP3
GNU Emacs 22.0.50.1 (i386-mingw-nt5.1.2600) of 2006-03-21 on YAMALOK
(pre-compiled binary).
Firefox 3.5.5 is set as default browser.

I attached the export of HKEY_CLASSES_ROOT\.htm as a TXT document.  The
HKLM version contains identical info, and I have no .htm under the HKCU
path.

HTH!

- Ray

-----Original Message-----
Date: Thu, 19 Nov 2009 13:40:03 +0100
From: Lennart Borgman <address@hidden>
Subject: [h-e-w] Please test w32-shell-execute
To: address@hidden
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset=UTF-8

I have got a problem with w32-shell-execute and file:/// URLs. It
looks like Jason Rumney and I get different results and I do not know
why. I need the help of couple of persons to test if the below calls
works or not. Could perhaps you test?

Please replace the file argument to a valid file and try the calls
below. Just place the cursor after the ) char and press C-x C-e. I
want to know if it opens the file in the web browser or not.

 (w32-shell-execute "open" "c:/some/file.html") ;; OK
 (w32-shell-execute nil "file:c:/some/file.html") ;; OK
 (w32-shell-execute nil "file:///c:/some/file.html") ;; OK
 (w32-shell-execute "open" "file:///c:/some/file.html") ;; Doesn't work
 (w32-shell-execute "open" "file:c:/some/file.html") ;; Doesn't work


Date: Thu, 19 Nov 2009 16:14:56 +0100
From: Lennart Borgman <address@hidden>
Subject: Re: [h-e-w] Please test w32-shell-execute
To: Drew Adams <address@hidden>
Cc: address@hidden
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset=UTF-8

On Thu, Nov 19, 2009 at 3:52 PM, Drew Adams <address@hidden>
wrote:
>> I get the same as you, Lennart.
>>
>> The last two do not open the browser, and they do not raise
>> an error - they seem to do nothing.
>
> I should have added that that is with the 23.1 Emacs release on
Windows XP SP3,
> using `emacs -Q'.


Thanks for all responses. I think there must be some Registry entries
responsible for the difference. Does anyone know which those might be?

I guess the relavant entries are at

   HKEY_CURRENT_USER\Software\Classes\file
   HKEY_LOCAL_MACHINE\SOFTWARE\Classes\file
   HKEY_CLASSES_ROOT\file

Could someone for whom it worked in all cases export these keys and
send them here?

HCRdothtm.txt
Description: HCRdothtm.txt