From mboxrd@z Thu Jan 1 00:00:00 1970 From: Micah Stetson To: 9fans@cse.psu.edu Subject: Re: [9fans] sam command language Message-ID: <20031006163511.GB16159@epaphras.cnm-vra.com> References: <8956812abe51c0fe7669680d4d907d9a@vitanuova.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Date: Mon, 6 Oct 2003 09:35:11 -0700 Topicbox-Message-UUID: 6257d49c-eacc-11e9-9e20-41e7f4b1d025 > lines, unlike ed. if the whole file is just one long string, which is > exactly > how sam works, shouldn't ^ and $ then mean beginning of file and end > of file? that's not very useful. I would tend to expect that they meant beginning and end of selection. Then if you want to match at the beginnings and ends of lines, it's just ',x /^...$/', and beginning and end of file is ',/^...$/'. I suppose that has its disadvantages, too, like ',x /$/i/foo/' would put foo at the beginning of every line but the first, it's logical, but it's a little unexpected. Having to match '\n' when you wanted it, wouldn't be that bad, though. Micah