From: Alex Musolino <alex@musolino.id.au>
To: 9front@9front.org
Subject: Re: [9front] g
Date: Fri, 13 Aug 2021 12:13:44 +0930 [thread overview]
Message-ID: <9537C8A9A3C1A643998908E9CDDF9FE4@musolino.id.au> (raw)
In-Reply-To: <CABB-WO8CZcT5SVTj0E_BkNsh+uHYEt4MA3WZBi6RbQkZQX8jeQ@mail.gmail.com>
> I was about to solve this on my system with
>
> nfile -m $files | awk -F\t '$2 ~ /^text|application.x-sh/ { print $1 }'
>
> where nfile is a file(1) that actually uses a frog to separate,
You don't need to create a new program. Just specify the awk field
separator regex correctly, i.e. -F ': *'.
next prev parent reply other threads:[~2021-08-13 5:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 18:03 Stuart Morrow
2021-08-11 1:13 ` ori
2021-08-11 20:15 ` Stuart Morrow
2021-08-11 20:32 ` Stuart Morrow
2021-08-12 5:38 ` Alex Musolino
2021-08-13 2:43 ` Alex Musolino [this message]
2021-08-14 21:38 ` Stuart Morrow
2021-08-14 21:45 ` Stuart Morrow
2021-08-15 2:42 ` Alex Musolino
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=9537C8A9A3C1A643998908E9CDDF9FE4@musolino.id.au \
--to=alex@musolino.id.au \
--cc=9front@9front.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.
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).