From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qemu-io: fix EOF Ctrl-D handling in qemu-io readline code
Date: Wed, 6 Dec 2017 08:30:27 -0600 [thread overview]
Message-ID: <f06a9a2f-2f4a-945f-739b-8be9333caf5e@redhat.com> (raw)
In-Reply-To: <20171206142513.GD18296@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On 12/06/2017 08:25 AM, Daniel P. Berrange wrote:
>> Should we instead be looking for a match against the current termios()
>> c_cc[VEOF] setting, in case the user prefers something other than ^D via
>> stty? Does readline provide any functionality for automating this?
>
> I was afraid someone was going to suggest doing that. I was being lazy by
> hardcoding Ctrl-D, but yes the real readline() library will honour the
> VEOF value. QEMU though is using a home-grown reimpl of readline...
I understand why we can't use modern libreadline (it is licensed GPLv3+,
making it impossible to use with our GPLv2-only code) - but doesn't BSD
have a readline-alike library with BSD licensing that we could use
instead of implementing readline ourselves? (Was it named libinput?)
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-12-06 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 11:57 [Qemu-devel] [PATCH] qemu-io: fix EOF Ctrl-D handling in qemu-io readline code Daniel P. Berrange
2017-12-06 14:22 ` Eric Blake
2017-12-06 14:25 ` Daniel P. Berrange
2017-12-06 14:30 ` Eric Blake [this message]
2017-12-06 16:14 ` Markus Armbruster
2017-12-08 12:15 ` Dr. David Alan Gilbert
2017-12-08 13:35 ` Daniel P. Berrange
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=f06a9a2f-2f4a-945f-739b-8be9333caf5e@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.
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 NNTP newsgroup(s).