9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /bin/split
Date: Fri, 20 Oct 2000 08:55:29 -0400	[thread overview]
Message-ID: <20001020125533.73ED0199DF@mail> (raw)

[-- Attachment #1: Type: text/plain, Size: 303 bytes --]

Wow... split.  I haven't run that command in a long long time.
It has an unitialized variable. add a call to memset after
/sys/src/cmd/split.c:75:

			Resub match[2];
			memset(match, 0, sizeof match);	/* add this line */
			line[Blinelen(b)-1] = 0;

This fixes your example, anyway.

-rob


[-- Attachment #2: Type: message/rfc822, Size: 1520 bytes --]

From: arisawa@ar.aichi-u.ac.jp
To: 9fans@nx.aichi-u.ac.jp
Subject: [9fans] /bin/split
Date: Thu, 19 Oct 100 09:23:29 +0900
Message-ID: <20001020103912.AA63A199E7@mail>

Hello,

The command
	split -e expression file
produces files that are hard to understand to me.

What is intended by -e option ?

For example, let be samp:
	----- samp ---
	From alice
	abc
	defg
	From bob
	hijk
	lmn
	--------------

Command
	split -e '^From' samp
split samp into two. OK, this is reasonable.

But
	split -e 'From' samp
split samp into 6 files with only one line.

Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp

             reply	other threads:[~2000-10-20 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-20 12:55 rob pike [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-10-19  0:23 arisawa

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=20001020125533.73ED0199DF@mail \
    --to=rob@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).