Grrrr At Textmate

AHHHHHHH!!!

Looks like the update Textmate pushed yesterday changed (or jut broke) the way the editor handles XHTML vs. HTML and now all the tags I have it generate are being added in HTML fashion (eg. <img> vs. <img />). Before I think it just autodetected based on doctype (i dunno, I just never had to think of it before).

Help me change it back please.

(sorry for the whine, but I’ve got a pile of coding on my plate and no time to fiddle with stuff.. guess i shouldn’t have taken the update yesterday knowing the situation.. but silly me thought it was just a easter egg thing)

Comments

  1. I guess its a case of RTFM (or RTFRN).. A few “releases” down the list on the version notes I see:

    [2006-10-15: REVISION 1292]
    [NEW] HTML bundle: HTML tags inserted which have an EMPTY content model now place the value of the TM_XHTML variable before the closing ‘>’. If you want these tags to use the minimized (XHTML) form, go to Preferences > Advanced and set TM_XHTML to “ /”. In the future this variable will automatically be set for documents with an XHTML document type. Though let me just remind anyone planning on writing XHTML pages to (re-)read http://www.hixie.ch/advocacy/xhtml

    And since i don’t live on the ‘cutting edge/ I probably got a few of the other updates yesterday along with the immediate changes.

    Comment by: chris @ Nov 1, 06:49 PM #
  2. Thanks for posting about this. I had this problem too, and appreciate Chris’s comment above. However, I don’t get this XHMTL controversy — I’ve read the Hixie article and I’ve never had any of the drawbacks it mentions. Anyone?

    Comment by: Dylan @ Nov 9, 01:50 PM #
Add Your Comments


NOTE: Your e-mail address will never be displayed to the public.

Post formatting via Textile. Textile Help. Comment moderation is on. Your comment will appear when it is approved by a moderator, well, me.