From: Eli Zaretskii <eliz@gnu.org>
To: Daiki Ueno <ueno@gnu.org>
Cc: nyc4bos@aol.com, larsi@gnus.org, 13344@debbugs.gnu.org
Subject: bug#13344: 24.3.50; Gnus error c:/dev/fd/0
Date: Fri, 04 Jan 2013 09:48:09 +0200 [thread overview]
Message-ID: <83mwwpie2u.fsf@gnu.org> (raw)
In-Reply-To: <871ue1ddby.fsf-ueno@gnu.org>
> From: Daiki Ueno <ueno@gnu.org>
> Cc: Eli Zaretskii <eliz@gnu.org>, nyc4bos@aol.com, 13344-done@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.
next prev parent reply other threads:[~2013-01-04 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 0:14 bug#13344: 24.3.50; Gnus error c:/dev/fd/0 nyc4bos
2013-01-03 0:57 ` Lars Magne Ingebrigtsen
2013-01-03 22:16 ` nyc4bos
2013-01-03 17:29 ` Eli Zaretskii
2013-01-03 22:07 ` nyc4bos
2013-01-03 22:41 ` Lars Magne Ingebrigtsen
2013-01-04 0:03 ` Daiki Ueno
2013-01-04 7:48 ` Eli Zaretskii [this message]
2013-01-04 22:58 ` Daiki Ueno
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mwwpie2u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=13344@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=nyc4bos@aol.com \
--cc=ueno@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.