From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id BD90C1F8C8;
	Sat, 18 Sep 2021 06:23:06 +0000 (UTC)
Date: Sat, 18 Sep 2021 06:23:05 +0000
From: Eric Wong <e@80x24.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: who runs commands from their $EDITOR?
Message-ID: <YUWFyW7JuVYXznQN@dcvr>
References: <20210917084425.GA29575@dcvr>
 <87czp6va65.fsf@kyleam.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <87czp6va65.fsf@kyleam.com>
List-Id: <meta.public-inbox.org>

Kyle Meyer <kyle@kyleam.com> wrote:
> Eric Wong writes:
> > -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.

Ah, good point, thanks.  Pushed w/o C<>.  I wonder if there's
other places where we over-use C<> (or any other POD markup)