From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3e1162e60607141036h1e6f3455n77cb773cb981f333@mail.gmail.com> Date: Fri, 14 Jul 2006 10:36:59 -0700 From: "David Leimbach" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: Re: [9fans] molesting the acme filesystem In-Reply-To: <44B7D4B5.3070808@lanl.gov> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4f99d25e2af2ef50218a5846cfff0f7f@quanstro.net> <20060714104547.B1785@orthanc.ca> <44B7D4B5.3070808@lanl.gov> Topicbox-Message-UUID: 7f0f9764-ead1-11e9-9d60-3106f5b1d025 On 7/14/06, Ronald G Minnich wrote: > Lyndon Nerenberg wrote: > > On Fri, 14 Jul 2006, quanstro@quanstro.net wrote: > > > >> i'm not sure why acme and other plan9 filesystems typically disallow a > >> trailing newline > >> on input and don't provide one on output. > > > > > > Yup. This one is my top entry for the confusomatic contest. > > I think if there were a newline, we'd all have scripts called 'chop' for > removing it. I don't think there's a perfect answer here. > > ron > But some of them are clearly inserting newlines, like event and they require one as well to be a completed "event". I don't care about perfection as much as I do about consistency (and that it works... it could have just been consistently broken too I suppose) :-) Dave