Comments for code.h(oe)kje

Comment on Inconsolata – a nice programming font by Ron

Ron — Sun, 12 Oct 2008 06:20:38 +0000

Ubuntu Hardy (8.04) also has a ttf-inconsolata package, which works without a symlink. I really like the font on first impression. I set it for xterm with the following (in .Xresources or .Xdefault, as appropriate):

XTerm*faceName: Inconsolata
XTerm*faceSize: 11

(Be sure to run “xrdb -merge .Xresources” to update X config.)

Side-by-side, the letter l and the number 1 are very distinct, but the letter l does look like the number 1 from other fonts. Personally, I don’t have a problem there.

Thanks for the post.

-Ron

Comment on Inconsolata – a nice programming font by VK

VK — Mon, 16 Jun 2008 16:16:07 +0000

I really like the stroked zero but it still bears another regular oops: too subtle difference between the small letter l and the number 1. If it would have that fixed then I would rate it 9 out of 10 at least.

Comment on Emacs Javascript mode update by Wentao Zheng

Wentao Zheng — Fri, 28 Mar 2008 08:06:30 +0000

I used this javascript mode in my emacs (v22) and found the following error

open a new file, and switch to javascritp mode

then in the FIRST line, type “for (“, then the text are idented automatically

but if I type “for (” in the second or other line, no problem

it is weird

As I am a newbie of elisp, so maybe you can help me on solving this problem

Comment on Inconsolata – a nice programming font by Larry

Larry — Thu, 20 Mar 2008 18:35:26 +0000

Looks a lot like the monaco font I use on my Mac. I love it.

Comment on Inconsolata – a nice programming font by Remco

Remco — Tue, 26 Feb 2008 21:19:15 +0000

Ooooh mooi! Die ga ik ook proberen. Dank voor de tip.

Comment on Javascript regex en string literal highlighting in Emacs by Joost

Joost — Thu, 31 Jan 2008 15:34:54 +0000

Hey Michael,

I’m not sure that can be fixed. At least not with the changes I made – I disabled all built-in string detection and all built-in comment detection except for the /* … */ style comments – I left those in because I couldn’t work out how to check for multi-line constructs.

Basically that means that /* and */ are detected before any other comment and string detection, so even inside a string or regex they will be interpreted as comment markers.

As a work around, you can escape the * character, which should not have any effect on the code:

getElementsByXPath(‘.//\*’ + cond, element)

I’m going to try and find a better solution, but don’t hold your breath :-)

Comment on Javascript regex en string literal highlighting in Emacs by Michael Alan Dorman

Michael Alan Dorman — Thu, 31 Jan 2008 14:32:59 +0000

Joost, I just wanted to say thanks for posting this modified version of javascript.el—Karls last published version was causing emacs to fall over when looking at the source for prototype.js.

That said, if you’re interested, there’s one expression in the latest version at http://prototypejs.org/assets/2008/1/25/prototype-1.6.0.2.js that causes some mis-hilighting. If you look at line 4160, there’s an xpath expression involving // that causes the rest of the file to be highlighted as a comment.

Still, much much better than sending Emacs into some sort of tight loop! Many thanks!

Mike.