public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Wayne Davison <wayne@opencoder.net>
To: cygwin <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] mysql 10.1.19-1
Date: Sun, 13 Nov 2016 23:23:00 -0000	[thread overview]
Message-ID: <CAHSx_Svc6ovmJS-sMTOFDPcYpJKJ2ZbhfLs_ME1P1J1UxEbcTQ@mail.gmail.com> (raw)

On Sun, Nov 13, 2016 at 12:36 PM, Yaakov Selkowitz
<yselkowitz@cygwin.com> wrote:
> The following packages have been uploaded to the Cygwin distribution:
> * mysql-10.1.19-1
> * [...]

Would you consider a change in the mysql packages back to using
readline? It should hopefully be as simple as:

CYGCONF_ARGS="--with-readline"

I tried doing a cygport prep with that set, but the mysql package's
patches aren't applying successfully, so I couldn't easily give it a
try.

The reason for the switch back is that the current line-editing lib is
severely crippled compared to readline. There's no search (and the
suggestions I saw for how to enable Ctrl-R don't work), there's no
undo (or redo), there's no Esc-. arg references, there's no word
delete, etc. Also, its save format is quite unreadable (not to mention
that it blew-away my mysql command history in ~/.mysql_history, which
was really quite rude of it).

I know that RHEL/CentOS still uses readline in their mariadb packages,
so hopefully it will be an easy change.

..wayne..

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2016-11-13 22:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-13 23:23 Wayne Davison [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-11-13 21:11 Yaakov Selkowitz

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=CAHSx_Svc6ovmJS-sMTOFDPcYpJKJ2ZbhfLs_ME1P1J1UxEbcTQ@mail.gmail.com \
    --to=wayne@opencoder.net \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).