From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <25855-1274326837-4010@sneakemail.com> Date: Mon, 24 May 2010 20:08:39 +0200 Message-ID: From: hiro <23hiro@googlemail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Acme-sac integration with Windows NT Topicbox-Message-UUID: 29b01974-ead6-11e9-9d60-3106f5b1d025 Wordpad on windows 7 sucks :D On 5/24/10, Robert Raschke wrote: > On Thu, May 20, 2010 at 4:41 AM, <6o205zd02@sneakemail.com> wrote: > >> How do you folks using acme-sac on Windows deal with the line-ending >> issue? I've been using P9P acme on linux (at work) since Russ announced >> it, but I consider the line-ending issue a show-stopper on Windows. >> >> While the cr displayed at the end of every line is annoying, I could >> probably learn to live with it. When I start editing, though, I doubt I >> have enough discipline to remember add the cr, and if I don't remember I >> would end up with files with mixed line-endings. Some windows tools >> aren't happy if the files don't use windows line endings. >> >> Peter Canning >> >> > When I start editing some random file in acme-sac, I do (pretend it's a > proper c/r character below) > > Edit ,x/=E2=90=8D/d > > and if I need them back in for Windows purposes, I do > > Edit ,x/\n/i/=E2=90=8D/ > > Sometimes I forget. But it's never really been an issue. I do not know of > any Windows tool that requires c/r these days. And most people, when open= ing > in Notepad just go Ach! and open in Wordpad instead. > > Robby >