From: Jeremy Sowden <jeremy@azazel.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>,
Sebastian Priebe <sebastian.priebe@de.sii.group>
Subject: Re: [PATCH nftables 0/3] Add Linenoise support to the CLI.
Date: Tue, 24 Sep 2019 08:42:13 +0100 [thread overview]
Message-ID: <20190924074212.GB4859@azazel.net> (raw)
In-Reply-To: <20190924074034.4099-1-jeremy@azazel.net>
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
On 2019-09-24, at 08:40:31 +0100, Jeremy Sowden wrote:
> Sebastian Priebe [0] requested Linenoise support for the CLI as an
> alternative to Readline, so I thought I'd have a go at providing it.
> Linenoise is a minimal, zero-config, BSD licensed, Readline replacement
> used in Redis, MongoDB, and Android [1].
>
> 0 - https://lore.kernel.org/netfilter-devel/4df20614cd10434b9f91080d0862dd0c@de.sii.group/
> 1 - https://github.com/antirez/linenoise/
>
> The upstream repo doesn't contain the infrastructure for building or
> installing libraries. I've taken a look at how Redis and MongoDB handle
> this, and they both include the upstream sources in their trees (MongoDB
> actually uses a C++ fork, Linenoise NG [2]), so I've done the same.
>
> 2 - https://github.com/arangodb/linenoise-ng
>
> By default, the CLI continues to be build using Readline, but passing
> `--with-cli=linenoise` instead causes Linenoise to be used instead.
>
> `nft -v` has been extended to display what CLI implementation was built
> and whether mini-gmp was used.
>
> Changes since RFC:
>
> * two tidy-up patches dropped because they have already been applied;
> * source now added to include/ and src/;
> * tests/build/run-tests.sh updated to test `--with-cli=linenoise`;
> * `nft -v` extended.
>
> Jeremy Sowden (3):
> src, include: add upstream linenoise source.
> cli: add linenoise CLI implementation.
> main: add more information to `nft -v`.
>
> configure.ac | 14 +-
> include/Makefile.am | 1 +
> include/cli.h | 2 +-
> include/linenoise.h | 73 +++
> src/Makefile.am | 12 +
> src/cli.c | 64 +-
> src/linenoise.c | 1201 ++++++++++++++++++++++++++++++++++++++
> src/main.c | 28 +-
> tests/build/run-tests.sh | 4 +-
> 9 files changed, 1381 insertions(+), 18 deletions(-)
> create mode 100644 include/linenoise.h
> create mode 100644 src/linenoise.c
Whoops! Sent the old version out again by mistake. v2 to follow.
J.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-09-24 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 7:40 [PATCH nftables 0/3] Add Linenoise support to the CLI Jeremy Sowden
2019-09-24 7:40 ` [PATCH nftables 1/3] src, include: add upstream linenoise source Jeremy Sowden
2019-09-24 7:40 ` [PATCH nftables 2/3] cli: add linenoise CLI implementation Jeremy Sowden
2019-09-24 7:40 ` [PATCH nftables 3/3] main: add more information to `nft -v` Jeremy Sowden
2019-09-24 7:42 ` Jeremy Sowden [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-21 12:20 [PATCH nftables 0/3] Add Linenoise support to the CLI Jeremy Sowden
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=20190924074212.GB4859@azazel.net \
--to=jeremy@azazel.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=sebastian.priebe@de.sii.group \
/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).