From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin-announce@cygwin.com
Subject: Updated: moreutils v0.65-1
Date: Sat, 16 Jan 2021 20:22:32 +0000 [thread overview]
Message-ID: <CA+kUOanKdcsMg1oHzTkBaaXxOF-qw+uoF7_w9CvTRgd_hRH-Gg@mail.gmail.com> (raw)
Version 0.65-1 of moreutils has been uploaded and should be coming
soon to a distribution server near you.
This is an update to the latest upstream release; it includes the
following changes:
- vipe: Added --suffix option. Thanks, Pål Grønås Drange.
- ifdata: fail when -ph is given but no hwaddr is available (Closes:
#386755) Thanks, Nicolas Schier
Moreutils is a "collection of the unix tools that nobody thought to
write long ago when unix was young."
From the upstream website, https://joeyh.name/code/moreutils/:
Probably the most general purpose tool in moreutils so far is sponge(1), which
lets you do things like this:
% sed "s/root/toor/" /etc/passwd | grep -v joey | sponge /etc/passwd
There are lots more listed below, and I'm always interested to add more to the
collection, as long as they're suitably general-purpose, and don't duplicate
other well-known tools.
- chronic: runs a command quietly unless it fails
- combine: combine the lines in two files using boolean operations
- errno: look up errno names and descriptions
- ifdata: get network interface info without parsing ifconfig output
- ifne: run a program if the standard input is not empty
- isutf8: check if a file or standard input is utf-8
- lckdo: execute a program with a lock held
- mispipe: pipe two commands, returning the exit status of the first
- parallel: run multiple jobs at once
- pee: tee standard input to pipes
- sponge: soak up standard input and write to a file
- ts: timestamp standard input
- vidir: edit a directory in your text editor
- vipe: insert a text editor into a pipe
- zrun: automatically uncompress arguments to command
reply other threads:[~2021-01-16 20:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CA+kUOanKdcsMg1oHzTkBaaXxOF-qw+uoF7_w9CvTRgd_hRH-Gg@mail.gmail.com \
--to=adam@dinwoodie.org \
--cc=cygwin-announce@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).