* bug#16252: 24.3.50; `report-emacs-bug' is now broken: (error "ShellExecute failed: The system cannot find the file specified.")
@ 2013-12-25 6:01 Drew Adams
2013-12-25 17:32 ` Eli Zaretskii
0 siblings, 1 reply; 4+ messages in thread
From: Drew Adams @ 2013-12-25 6:01 UTC (permalink / raw)
To: 16252
[Note: The build noted below is the one regarding this bug report. I'm
using an older build to report the bug, which is about the fact that I
can no longer use `report-emacs-bug'.]
This is the backtrace I got for `report-emacs-bug' (using my setup, not
emacs -Q):
Debugger entered--Lisp error: (error "ShellExecute failed: The system cannot find the file specified.")
w32-shell-execute("open" "mailto:bug-gnu-emacs@gnu.org?subject=24.3.50%3b%20%60icomplete-mode%27%20breaks%20my%20file%20opening&body=%2a%2a%2a%20E-Mail%20body%20has%20been%20placed%20on%20clipboard%2c%20please%20paste%20it%20here%21%20%2a%2a%2a")
browse-url-default-windows-browser("mailto:bug-gnu-emacs@gnu.org?subject=24.3.50%3b%20%60icomplete-mode%27%20breaks%20my%20file%20opening&body=%2a%2a%2a%20E-Mail%20body%20has%20been%20placed%20on%20clipboard%2c%20please%20paste%20it%20here%21%20%2a%2a%2a" nil)
apply(browse-url-default-windows-browser "mailto:bug-gnu-emacs@gnu.org?subject=24.3.50%3b%20%60icomplete-mode%27%20breaks%20my%20file%20opening&body=%2a%2a%2a%20E-Mail%20body%20has%20been%20placed%20on%20clipboard%2c%20please%20paste%20it%20here%21%20%2a%2a%2a" nil)
browse-url-default-browser("mailto:bug-gnu-emacs@gnu.org?subject=24.3.50%3b%20%60icomplete-mode%27%20breaks%20my%20file%20opening&body=%2a%2a%2a%20E-Mail%20body%20has%20been%20placed%20on%20clipboard%2c%20please%20paste%20it%20here%21%20%2a%2a%2a" nil)
apply(browse-url-default-browser "mailto:bug-gnu-emacs@gnu.org?subject=24.3.50%3b%20%60icomplete-mode%27%20breaks%20my%20file%20opening&body=%2a%2a%2a%20E-Mail%20body%20has%20been%20placed%20on%20clipboard%2c%20please%20paste%20it%20here%21%20%2a%2a%2a" nil)
browse-url("mailto:bug-gnu-emacs@gnu.org?subject=24.3.50%3b%20%60icomplete-mode%27%20breaks%20my%20file%20opening&body=%2a%2a%2a%20E-Mail%20body%20has%20been%20placed%20on%20clipboard%2c%20please%20paste%20it%20here%21%20%2a%2a%2a")
mailclient-send-it()
message-send-mail-with-mailclient()
message-multi-smtp-send-mail()
message-send-mail(nil)
message-send-via-mail(nil)
message-send(nil)
message-send-and-exit(nil)
call-interactively(message-send-and-exit nil nil)
command-execute(message-send-and-exit)
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2013-12-24 on ODIEONE
Bzr revision: 115738 cyd@gnu.org-20131225030511-ru56hhc243pxja04
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
CPPFLAGS=-Ic:/Devel/emacs/include'
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#16252: 24.3.50; `report-emacs-bug' is now broken: (error "ShellExecute failed: The system cannot find the file specified.")
2013-12-25 6:01 bug#16252: 24.3.50; `report-emacs-bug' is now broken: (error "ShellExecute failed: The system cannot find the file specified.") Drew Adams
@ 2013-12-25 17:32 ` Eli Zaretskii
2013-12-25 19:36 ` Eli Zaretskii
[not found] ` <<83eh5067ue.fsf@gnu.org>
0 siblings, 2 replies; 4+ messages in thread
From: Eli Zaretskii @ 2013-12-25 17:32 UTC (permalink / raw)
To: Drew Adams; +Cc: 16252
> Date: Tue, 24 Dec 2013 22:01:38 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
>
> This is the backtrace I got for `report-emacs-bug' (using my setup, not
> emacs -Q):
>
> Debugger entered--Lisp error: (error "ShellExecute failed: The system cannot find the file specified.")
> w32-shell-execute("open" "mailto:bug-gnu-emacs@gnu.org?subject=24.3.50%3b%20%60icomplete-mode%27%20breaks%20my%20file%20opening&body=%2a%2a%2a%20E-Mail%20body%20has%20been%20placed%20on%20clipboard%2c%20please%20paste%20it%20here%21%20%2a%2a%2a")
Sorry, my bad. I fixed a bug in one use case for w32-shell-execute,
but the fix screwed up another. Now fixed in trunk revision 115742.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#16252: 24.3.50; `report-emacs-bug' is now broken: (error "ShellExecute failed: The system cannot find the file specified.")
2013-12-25 17:32 ` Eli Zaretskii
@ 2013-12-25 19:36 ` Eli Zaretskii
[not found] ` <<83eh5067ue.fsf@gnu.org>
1 sibling, 0 replies; 4+ messages in thread
From: Eli Zaretskii @ 2013-12-25 19:36 UTC (permalink / raw)
To: 16252-done
> Date: Wed, 25 Dec 2013 19:32:26 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 16252@debbugs.gnu.org
>
> > Date: Tue, 24 Dec 2013 22:01:38 -0800 (PST)
> > From: Drew Adams <drew.adams@oracle.com>
> >
> > This is the backtrace I got for `report-emacs-bug' (using my setup, not
> > emacs -Q):
> >
> > Debugger entered--Lisp error: (error "ShellExecute failed: The system cannot find the file specified.")
> > w32-shell-execute("open" "mailto:bug-gnu-emacs@gnu.org?subject=24.3.50%3b%20%60icomplete-mode%27%20breaks%20my%20file%20opening&body=%2a%2a%2a%20E-Mail%20body%20has%20been%20placed%20on%20clipboard%2c%20please%20paste%20it%20here%21%20%2a%2a%2a")
>
> Sorry, my bad. I fixed a bug in one use case for w32-shell-execute,
> but the fix screwed up another. Now fixed in trunk revision 115742.
Closing.
^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <<83eh5067ue.fsf@gnu.org>]
end of thread, other threads:[~2013-12-28 4:41 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-25 6:01 bug#16252: 24.3.50; `report-emacs-bug' is now broken: (error "ShellExecute failed: The system cannot find the file specified.") Drew Adams
2013-12-25 17:32 ` Eli Zaretskii
2013-12-25 19:36 ` Eli Zaretskii
[not found] ` <<83eh5067ue.fsf@gnu.org>
2013-12-28 4:41 ` Drew Adams
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).