[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nano-devel] how should piping through an external command work?
From: |
Brand Huntsman |
Subject: |
Re: [Nano-devel] how should piping through an external command work? |
Date: |
Tue, 20 Feb 2018 18:12:32 -0700 |
On Mon, 19 Feb 2018 14:24:32 +0100
Benno Schulenberg <address@hidden> wrote:
> Op 18-02-18 om 14:42 schreef Marco Diego Aurélio Mesquita:
> > I have an Idea: if the first character of a command is a '|' (and
> > there is no text selected), nano should pipe the whole buffer to the
> > command. This is not very discoverable but would allow us to have
> > both possibilities without the need of new toggle.
>
> Not bad. But, as you say, this is not discoverable, and that is not
> nano's style. Nano's style is to show in the help lines the things
> that are possible.
What if ^| (or ^\ or M-| or M-\) was similar to comment/uncomment but it
prefixes/unprefixes the command in ^R^X with a '|'. The '|' can still be
manually typed but it gets a discoverable toggle and stays with the command in
history.
[Nano-devel] how should piping through an external command work?, Benno Schulenberg, 2018/02/18
Re: [Nano-devel] how should piping through an external command work?, Brand Huntsman, 2018/02/18
Re: [Nano-devel] how should piping through an external command work?, Benno Schulenberg, 2018/02/19
[Nano-devel] Fwd: Re: how should piping through an external command work?, Benno Schulenberg, 2018/02/19
Re: [Nano-devel] Fwd: Re: how should piping through an external command work?, Brand Huntsman, 2018/02/19
Re: [Nano-devel] Fwd: Re: how should piping through an external command work?, Benno Schulenberg, 2018/02/20