package.el has been a massive success. I'm aware of 8 repositories so far: http://t.co/pB1JoKUWcw
miniblog.
I've set up my first project using Cask and flycheck-cask for checking my code, and it works wonderfully. Highly recommended.
Blogged: Editing Julia code (with Emacs!) http://t.co/coCUB8XTXU
"you could almost write a book on [colons in ranges] alone" floating-point ranges are hard:
Urgh, something has gone wrong when you seriously consider writing (cons my-regexp ''my-face) ;; yep, two quotes! http://t.co/Tovbkig1E8
Emacs' string model is quite different to anything else I've experienced. They're mutable ropes that can also store arbitrary attributes.
"In Pharo 4, the Inspector and Playground from the Glamorous Toolkit (a part of [Moose]) are now the default." Exciting!
I've seen * used in curse words, but I'm surprised the docstrings in Emacs write 'Un*x' (e.g. man and woman).
Elisp package of the day: eldoc-eval: https://github.com/thierryvolpiatto/eldoc-eval It shows eldoc on the modeline when you use M-: http://t.co/ueyTahxrtD
Dilemma: should the minibuffer (using eldoc or equivalent) show the function parameters or docstring? #emacs
3 stages of code reading: understanding the flow, understanding the details, then assaulting the code until you're persuaded it's correct.
I've seen several Go programmers cite garbage-collection as one of the things they like. Sounds like it is attracting C/C++ programmers.
The code itself matters far less than the team and the culture around it. Code will be different in 5 years, a quality culture should not.
Showing 5,656-5,670 of 7,580 posts