GNU bug report logs - #13344
24.3.50; Gnus error c:/dev/fd/0

Previous Next

Full log

Message #28 received at 13344 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Daiki Ueno <ueno <at> gnu.org>
Cc: 13344 <at> debbugs.gnu.org, larsi <at> gnus.org, nyc4bos <at> aol.com
Subject: Re: bug#13344: 24.3.50; Gnus error c:/dev/fd/0
Date: Fri, 04 Jan 2013 09:48:09 +0200

> From: Daiki Ueno <ueno <at> gnu.org>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  nyc4bos <at> aol.com, 13344-done <at> debbugs.gnu.org
> Date: Fri, 04 Jan 2013 09:03:13 +0900
> 
> >>     ;; Set GPG_TTY and TERM for pinentry-curses.  Note that we can't
> >>     ;; use `terminal-name' here to get the real pty name for the child
> >>     ;; process, though /dev/fd/0" is not portable.
> >>     (with-temp-buffer
> >>       (when (= (call-process "tty" "/dev/fd/0" t) 0)
> >> 	(delete-backward-char 1)
> >> 	(setq terminal-name (buffer-string))))
> >>
> >> Obviously, this will never work on Windows.
> >
> > So perhaps that code should just be disabled for Windows?        
> 
> Oops.  Though I tend to revert the previous patch, I've just added error
> check around call-process for now.  Sorry for the inconvenience.

I don't think ignoring errors is TRT here.  You are invoking a command
that doesn't exist on Windows out of the box; however, if some user,
for some reason, does have that command somewhere on PATH, it _will_
be invoked, but the results could be unpredictable, because the
command by that name on MS-Windows can be unrelated to its Posix
namesake.

So it is best to avoid that call on Windows entirely.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.