title > head > html > title error: closing wrong tag > You can also check to see if tags make sense or bad tags are nested. For > example, don't see <body><body></body></body> as normal, nor

From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 20 Aug 2008 09:48:11 +0100 From: Eris Discordia To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>, wendellxe@yahoo.com Message-ID: In-Reply-To: <9F788D9D-8A71-4A6A-BE56-A1CBBB10F3B3@mac.com> References: <382936.47212.qm@web57610.mail.re1.yahoo.com> <9F788D9D-8A71-4A6A-BE56-A1CBBB10F3B3@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: [9fans] Using the Acme Editor Topicbox-Message-UUID: 024b8f28-ead4-11e9-9d60-3106f5b1d025 > style(6) says not to convert tabs to spaces. I see. People on Plan 9 are "told" which characters they "should" or "shouldn't" use in their text. Great! > An awk program can do this. The idea is to interpret tags as they come in > the form of a stack: > code stack > html > head > html > title > head > html > title error: closing wrong tag > You can also check to see if tags make sense or bad tags are nested. For > example, don't see <body><body></body></body> as normal, nor > <title>. That stack has been implemented in vim. There're nearly 500 different syntax matching and highlighting schemes for vim, and there's a simple language for writing your own schemes. Why not use vi? --On Tuesday, August 19, 2008 11:54 PM -0400 Pietro Gagliardi wrote: > Just a few other bits of relevance to the original topic: > > On Aug 19, 2008, at 11:52 AM, Wendell xe wrote: >> 07. Automatic insertion of spaces for tabs > > style(6) says not to convert tabs to spaces. > >> 11. Bookmarks > If you know what text the bookmark will point to, make a comment on the > line above it: > /* C comment */ > .\" troff comment > # rc/awk comment > Set the comment to the text of the bookmark. Then, search for the text of > the bookmark with the appropriate comment delimiters. Easy enough. > >> 16. HTML tag matching > An awk program can do this. The idea is to interpret tags as they come in > the form of a stack: > code stack > html > head > html > title > head > html > title error: closing wrong tag > You can also check to see if tags make sense or bad tags are nested. For > example, don't see <body><body></body></body> as normal, nor > <title>. > >