From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: u.s.reddy@cs.bham.ac.uk, 11037@debbugs.gnu.org
Subject: bug#11037: 24.0.94; gnutls-cli.exe program not found
Date: Thu, 22 Mar 2012 22:16:03 +0200 [thread overview]
Message-ID: <83ehskwfwc.fsf@gnu.org> (raw)
In-Reply-To: <m38visfptz.fsf@stories.gnus.org>
> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 22 Mar 2012 19:33:28 +0100
> Cc: 11037@debbugs.gnu.org
>
> But I wonder why, er, the following:
>
> > (signal-process (process-id process) 'SIGALRM)
>
> > does not work with Win32 Emacs, even with Cygwin also installed. But
> > one can mimic that with:
>
> > (call-process "c:\\cygwin\\bin\\kill.exe" nil nil nil
> > "-ALRM" (format "%d" (process-id process)))
>
> If this is the case, then why not do something along these lines under
> Windows? That is, define `signal-process' (under Windows) to call the
> external "kill.exe" program (if `signal-process' is broken under
> Windows, as claimed), or fix `signal-process' to do whatever the
> "kill.exe" program does?
Several reasons:
. kill.exe is part of Cygwin, and won't exist on a Windows machine,
unless Cygwin is installed.
. there's no SIGALRM on Windows, so the only way this kill.exe could
work is if it would send the signal to a Cygwin program (I guess
gnutls-cli.exe was meant in the message which you cited).
IOW, all this can only work, and as a kludge at that, if a complete
Cygwin installation, including a Cygwin-built GnuTLS, were available
on the target machine. Which is not really a good way of letting
users of the native Windows build of Emacs to have TLS. Especially
now, that a built-in TLS is available and working, without any need
for such kludges.
next prev parent reply other threads:[~2012-03-22 20:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 17:24 bug#11037: 24.0.94; gnutls-cli.exe program not found Uday S Reddy
2012-03-17 18:09 ` Eli Zaretskii
2012-03-17 20:14 ` Uday S Reddy
2012-03-27 0:11 ` Glenn Morris
2012-03-17 21:31 ` Uday S Reddy
2012-03-18 3:48 ` Eli Zaretskii
2012-03-22 18:33 ` Lars Magne Ingebrigtsen
2012-03-22 20:16 ` Eli Zaretskii [this message]
2012-03-22 20:45 ` Uday S Reddy
2012-03-23 8:01 ` Eli Zaretskii
2012-03-23 8:18 ` Uday S Reddy
2012-03-23 8:33 ` Eli Zaretskii
2012-03-23 12:30 ` Stefan Monnier
2012-03-22 21:05 ` Lars Magne Ingebrigtsen
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=83ehskwfwc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11037@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=u.s.reddy@cs.bham.ac.uk \
/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).