From: YASUOKA Masahiko <yasuoka@yasuoka.net>
To: 42059@debbugs.gnu.org
Subject: bug#42059: 26.3; OpenBSD now has posix_openpt(3)
Date: Sat, 27 Jun 2020 12:56:42 +0900 (JST) [thread overview]
Message-ID: <20200627.125642.2094003492847014173.yasuoka@yasuoka.net> (raw)
In-Reply-To: <20200626.185255.1790338933470538786.yasuoka@yasuoka.net>
On Fri, 26 Jun 2020 18:52:55 +0900 (JST)
YASUOKA Masahiko <yasuoka@yasuoka.net> wrote:
> OpenBSD now has posix_openpt(3), emacs should use that.
> A diff is attached.
>
> Currently emacs uses an old way which actually causes a problem. I am
> using gnupg through Mew(*1) which run on emacs, Mew seems to create a
> process without a pty regardless it specifies "process-connection-type
> pty" properly. The pty is required to pass the passphrase.
>
> *1) http://mew.org/
The patch I sent previously was reversed. Let me update it.
--- configure.ac.orig Thu Aug 22 07:25:23 2019
+++ configure.ac Fri Jun 26 18:33:33 2020
@@ -4620,11 +4620,11 @@ case $opsys in
AC_DEFINE(PTY_TTY_NAME_SPRINTF, [])
;;
- gnu | openbsd | qnxnto )
+ gnu | qnxnto )
AC_DEFINE(FIRST_PTY_LETTER, ['p'])
;;
- gnu-linux | gnu-kfreebsd | dragonfly | freebsd | netbsd | darwin | nacl )
+ gnu-linux | gnu-kfreebsd | dragonfly | freebsd | openbsd | netbsd | darwin | nacl )
dnl if HAVE_GRANTPT
if test "x$ac_cv_func_grantpt" = xyes; then
AC_DEFINE(UNIX98_PTYS, 1, [Define if the system has Unix98 PTYs.])
next prev parent reply other threads:[~2020-06-27 3:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 9:52 bug#42059: 26.3; OpenBSD now has posix_openpt(3) YASUOKA Masahiko
2020-06-27 3:56 ` YASUOKA Masahiko [this message]
2020-06-30 11:52 ` Mattias Engdegård
2020-06-30 13:49 ` YASUOKA Masahiko
2020-06-30 14:24 ` Mattias Engdegård
2020-06-30 15:36 ` Eli Zaretskii
2020-06-30 14:32 ` Eli Zaretskii
2020-07-01 11:23 ` Jeremie Courreges-Anglas
2020-07-01 14:24 ` Eli Zaretskii
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=20200627.125642.2094003492847014173.yasuoka@yasuoka.net \
--to=yasuoka@yasuoka.net \
--cc=42059@debbugs.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.