This is a compiled list of falsehoods programmers tend to believe about working with time.
Don't re-invent a date time library yourself. If you think you understand everything about time, you're probably doing it wrong.
| # | |
| # aerc default styleset | |
| # | |
| # This styleset uses the terminal defaults as its base. | |
| # More information on how to configure the styleset can be found in | |
| # the aerc-styleset(7) manpage. Please read the manual before | |
| # modifying or creating a styleset. | |
| *.default=true | |
| *.selected.reverse=toggle |
A guide to Vim Script development for Python developers. Sample code for the various expressions, statements, functions and programming constructs is shown in both Python and Vim Script. This is not intended to be a tutorial for developing Vim scripts. It is assumed that the reader is familiar with programming in Python.
For an introduction to Vim Script development, refer to usr_41.txt, eval.txt and Learn Vimscript the Hard Way
For a similar guide for JavaScript developers, refer to Vim Script for the JavaScripter
This guide only describes the programming constructs that are present in both Python and Vim. The constructs that are unique to Vim (e.g. autocommands, key-mapping, [abbrevi
| var unified = require('unified') | |
| var markdown = require('remark-parse') | |
| var remark2rehype = require('remark-rehype') | |
| var html = require('rehype-stringify') | |
| var report = require('vfile-reporter') | |
| unified() | |
| .use(markdown) | |
| .use(remark2rehype) | |
| .use(html) |
This gist is part of a blog post. Check it out at:
http://jasonrudolph.com/blog/2011/08/09/programming-achievements-how-to-level-up-as-a-developer
I'm migrating a legacy codebase to Typescript & it has some global objects attached to window & I want these to be available always.
So I created globals.d.ts file that looks something like this
interface Foo {
a: string;
b: number;
}