From: Aki <please@ignore.pl>
To: Jakub Slepecki <jakub.slepecki@intel.com>, patches@ignore.pl
Subject: Re: [PATCH] what: use pl.lapp for what command
Date: Fri, 15 May 2026 23:12:02 +0200 [thread overview]
Message-ID: <88fd1d60-4633-425b-8293-8697bd197002@ignore.pl> (raw)
In-Reply-To: <20260515124539.477794-1-jakub.slepecki@intel.com>
On 15/05/2026 14:45, Jakub Slepecki wrote:
> Penlight's pl.lapp has a very nice interface for users that want to
> do `which what` being somewhat self-documenting. It has some minor
> problems, it misses some *nix or GNU traditions (e.g., lack of - with
> file type that's addressed here) and some quirks like useless newlines.
> These sound solvable upstream, but for now we need to wrap them.
>
> No functional changes are done to the command interface. All calls that
> were correct are intended to continue being correct.
>
> Remove io.stdin check before closing the input stream. Lua has an
> internal check that fails the io.close() returning error message.
> We can just ignore it.
>
> Signed-off-by: Jakub Slepecki <jakub.slepecki@intel.com>
Merged as 96b9b70d6415.
Corrected a small type "User (...) themselves" -> "Users (...) themselves.
prev parent reply other threads:[~2026-05-15 21:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 12:45 Jakub Slepecki
2026-05-15 21:12 ` Aki [this message]
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=88fd1d60-4633-425b-8293-8697bd197002@ignore.pl \
--to=please@ignore.pl \
--cc=jakub.slepecki@intel.com \
--cc=patches@ignore.pl \
/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