From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <509071940708261815k7002323aw1db4ee6e32f43a0@mail.gmail.com> Date: Sun, 26 Aug 2007 21:15:56 -0400 From: "Anthony Sorace" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] handling tabs in text frames In-Reply-To: <72b4f68236adde2ec3716246298389ec@quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8ccc8ba40708261333k4b5c5a38me30920ef188c0f06@mail.gmail.com> <72b4f68236adde2ec3716246298389ec@quanstro.net> Topicbox-Message-UUID: b0baf870-ead2-11e9-9d60-3106f5b1d025 On 8/26/07, erik quanstrom wrote: > p.s. tabs are 8 spaces. ;-) tabs are tabs. spaces are spaces. seriously: i'm less concerned about what actual visual representation is used (i like 4-space equivalent, 8 wouldn't make me upset, and leaving it user-specified is lovely), but it's important that whatever you're doing not mess around with the actual character strings in the stream. i agree tab handling is imperfect and often frustrating (especially when working with people who code in variable-width fonts, which, personally, still seems a bit odd to me) and that programs could do more for me there, but i have a hard time coming up with consistent rules i'd like to see implemented.