user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: who runs commands from their $EDITOR?
Date: Fri, 17 Sep 2021 23:23:46 -0400	[thread overview]
Message-ID: <87czp6va65.fsf@kyleam.com> (raw)
In-Reply-To: <20210917084425.GA29575@dcvr>

Eric Wong writes:

> Just wondering, is this a common thing for other *nix users?
> It's been second nature to me for decades, now.  Even nvi
> supports it (not just vim), so it's not new...

Feeding text to arbitrary shell commands would feel pretty natural to
most Emacs users, I think.  This can be done with
shell-command-on-region (bound to M-| by default).

> Subject: [PATCH] doc: lei-lcat: document --stdin behavior
>
> This is another feature I've found immensely useful,
> but I also wonder if I'm the only one who uses it.

This is a nice feature to call out.

> diff --git a/Documentation/lei-lcat.pod b/Documentation/lei-lcat.pod
> index b7887b6c..ea883e65 100644
> --- a/Documentation/lei-lcat.pod
> +++ b/Documentation/lei-lcat.pod
> @@ -13,7 +13,7 @@ lei lcat [OPTIONS] (--stdin|-)
>  lcat (local cat) is a wrapper around L<lei-q(1)> that displays local
>  messages by Message-ID.  It is able to extract Message-IDs from URLs
>  as well as from common formats such as C<E<lt>$MSGIDE<gt>> and
> -C<id:$MSGID>.  When reading from stdin, input that isn't understood is
> +C<id:$MSGID>.  When reading from C<stdin>, input that isn't understood is

Fwiw I went in the opposite direction with ee308223 (doc: lei-import:
drop markup of "stdin", 2021-02-27), removing the only C<stdin> in the
docs.

  reply	other threads:[~2021-09-18  3:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17  8:44 who runs commands from their $EDITOR? Eric Wong
2021-09-18  3:23 ` Kyle Meyer [this message]
2021-09-18  6:23   ` Eric Wong

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87czp6va65.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).