miniblog.

← Back to all posts
Dec 30, 2017 at 01:32
Turns out that Emacs docstrings have an elaborate escaping mechanism. \[foo] shows the keybinding for foo, but \=\[foo] shows \[foo] literally. If you're a Helpful user, we now handle this correctly, *and* show handy buttons!
GitHub - Wilfred/helpful: A better Emacs *help* buffer
GitHub - Wilfred/helpful: A better Emacs *help* buffer
A better Emacs *help* buffer. Contribute to Wilfred/helpful development by creating an account on GitHub.

Related Posts

Aug 12, 2022 at 19:06
Are there examples of IDE services deliberately leveraging elaborate type systems? I'm struggling to think of what a richer type system enables in the IDE space. The existence of void* in C, interface{} in Go, or a lack of generics, doesn't seem to have limited possibilities.
Sep 7, 2019 at 09:47
C : C++, Java : Scala/Kotlin, JS : TypeScript. There definitely seems to be space for languages that target the same platform. AFAICS the success criteria are: great interoperability, similar toolset, similar syntax, and a more elaborate type system. Are there counterexamples?
Mar 4, 2019 at 10:39
I've worked on many projects where tests are have discrete levels, usually something like unit test, integration test, end-to-end test. I've also seen elaborate arguments over what counts as a unit, especially in heavily OO codebases.