MIME-Version: 1.0
References: <CAKK-TZV+cXwTOepvzBuPWikayKTh_2ve5UfDKnX7EopNVd3PEA@mail.gmail.com>
 <20200314031348.a239331e515fd8a15927b0ef@nifty.ne.jp>
In-Reply-To: <20200314031348.a239331e515fd8a15927b0ef@nifty.ne.jp>
Date: Fri, 13 Mar 2020 21:49:05 +0300
Message-ID: <CAKK-TZXz9KZyu=Wc7-UWm9NQCdtG5bF0wb8JGCW+GBrXu3f8Qg@mail.gmail.com>
Subject: Re: rlwrap no longer works with windows console apps
To: cygwin@cygwin.com
From: Kostya Altukhov via Cygwin <cygwin@cygwin.com>
Reply-To: Kostya Altukhov <kacygwinlist@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

On Fri, Mar 13, 2020 at 9:14 PM Takashi Yano wrote:

> Why do you use rlwrap for cmd.exe? History and command line
> edit are working in cmd without rlwrap in new cygwin.
>

cmd.exe is just an example. I use rlwrap for other Windows command line
tools like Oracle's sqlplus and others. But even in stuff like cmd.exe,
only basic history and editing is available natively, rlwrap provides
additional benefits like history search, persistence of history between
sessions, more sophisticated editing commands, etc. I have a lot of aliases
wrapping all windows tools with rlwrap.
--
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