From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <6ccaf3bc810099bbc427809490020b42@quanstro.net>
References: <1d5d51400907131729o215edc46p856d210973d7853c@mail.gmail.com>
	<6ccaf3bc810099bbc427809490020b42@quanstro.net>
Date: Tue, 14 Jul 2009 18:47:21 +0800
Message-ID: <1d5d51400907140347u3745809co316a8ee50c316d65@mail.gmail.com>
From: Fernan Bolando <fernanbolando@mailc.net>
To: 9fans@9fans.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Guide to using Acme effectively? too many spaces
Topicbox-Message-UUID: 1edec17c-ead5-11e9-9d60-3106f5b1d025

On Tue, Jul 14, 2009 at 10:38 AM, erik quanstrom<quanstro@quanstro.net> wro=
te:
>> I usually get in a situation like the one below, when I forget to
>> format my file with carriage return in acme. It doesn't happen that
>> often, but I was wondering if anybody has some method in there usage
>> of acme to avoid it completely.
>
> it's tempting to claim the solution is to not use vi.
>
> do you really mean that you wish \r\n (cr nl) but
> only have \n? =A0or do you mean something else?
> which version of acme are you using?
>
> - erik
>

Please ignore this email. I got confused with the word wrapping.

I apologize for the noise.

fernan

--=20
http://www.fernski.com