Matus Goljer

Let's put transient caches/state/files/crap in .emacs.d/.cache

7

I've been cleaning up my config and doing some gitignore grooming and I came to the realization I had over 100 ignore rules in there :O. Packages should put their...

Prefer `nil` for empty lists over `()` or `'()`

2

There are essentially 5 ways to "initialize" a list ```elisp (let (results) (--each ... (push x results))) (let ((results)) (--each ... (push x results))) (let ((results nil)) (--each ... (push...

Use descriptive keyword argument instead of `t` when boolean flag is expected

17

For example, functions which expects 5 arguments, all of which are `t` can get very confusing with calls like `(foo t nil t nil t)`. It is not obvious what...

For example in `Info-mode` the raw text `(*foo::)` is rendered as `(see foo)` which changes how the algorithm should process the tokens. I would like to use `pj-justify` to make...

The `number[]` annotation does not parse ```js function GetQuoteV2(connections) { } const v2 = { GetQuote: async function (connections: number[]) { return GetQuoteV2(connections) }, } ```

- [x] `Promise` fails to parse - [ ] `Promise` fails to parse (probably because a star is an operator and not a name

dynamic object keys seem to be broken: `return {[fieldName]: item.value}` (error at `:`)

2

The error is in the advice on `js2-parse-named-prop`, it does not return the "value" node from the `key: value` pair in case we drop into the `[foo]` branch (`(eq tt...

Fixes #8

This happens in `js2-parse-variables` in the first call to `js2-set-face`. We will probably have to hook into the result of that and refontify the types if we find the "annotated"...