From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] split(1): -e vs. -n, -f
Date: Mon, 30 Dec 2013 11:10:45 +0100 [thread overview]
Message-ID: <462816165.fiyU6ZYvxS@coil> (raw)
hi list,
both behavior and code indicate that split(1)'s `-e' (split by regular
expression) doesn't play along with either `-n' (line count) or `-f' (output
file prefix). the former is somewhat understandable, but the later is strange
in lieu of `-s' (output file suffix) working just fine.
that by accident or is there some rationale?
--
dexen deVries
[[[↓][→]]]
next reply other threads:[~2013-12-30 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 10:10 dexen deVries [this message]
2013-12-30 13:50 ` [9fans] split(1): -e vs. -n, -f [patch] dexen deVries
2013-12-30 16:12 ` [9fans] split(1): -e vs. -n, -f erik quanstrom
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=462816165.fiyU6ZYvxS@coil \
--to=dexen.devries@gmail.com \
--cc=9fans@9fans.net \
/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).