http://t.co/QfsWCLnz4e -- because I don't believe that anyone has made the most of all the #Emacs features that would be useful for them.
miniblog.
Ooh, expand-region is headed for #Emacs upstream: https://github.com/magnars/expand-region.el/pull/83
Language : polyglot :: editor : ?
"A bad idea with good presentation is doomed eventually. A good idea with bad presentation is doomed immediately."
The perils of using XPath like a CSS selector: http://t.co/jzcelnJvhW
OH: "Dev 1 is on the frontend, and dev 2 is on the backend." "Oh, so you're basically a pantomime horse?"
Amazingly blunt phishing: http://t.co/QcwOFGDUJi is a fake site but visiting http://t.co/ZZZjPxlfE2 shows as http://t.co/5MnwNXanx1. Subtle!
I've realised I can't name a single large codebase that I would consider elegant. Can you?
Used #Python metaclasses in anger yesterday -- as with most metaprogramming, usually a bad idea, but occasionally a huge boon.
Announcing with-namespace.el, the namespace solution you didn't know you needed for #Emacs lisp! https://github.com/Wilfred/with-namespace.el
Upgrading to #Emacs 24.3? You probably want to recompile *all* your .elc files, or you will hit quirky issues like: https://github.com/mooz/js2-mode/issues/72
Treating v1.0 as an official release is incompatible with semantic versioning, since you might change your API before a 'grand unveiling'.
PyPI is painfully slow sometimes. We've bitten the bullet and started setting up pep381client internally so we can always set up a fresh env
That feeling when the act of writing a Stack Overflow question helps you solve the problem unaided.
This week has seen Pip 1.9 with SSL support, and a setuptools/distribute merge announced. Things are looking up for Python packaging!
Showing 7,156-7,170 of 7,508 posts