Ian MacLeod

A `"postinstall": "HOME=\"$HOME\"/../.. apm install "` appears to work (in a *nix world at least) - though the CLI tool doesn't appear to inform any running copy of atom, so...

Yup! On Wed, Feb 4, 2015, 23:50 Nikolay Yakimov [email protected] wrote: > This is what I'd call "fragile", since it assumes a little too much about > environment and running...

Allowing decorators on assignment (and/or `export`) expressions would certainly help for more complicated decoration, while still being easy to read: ``` js @memoize({ttl: 30}) export function getStuff(id) { ... }...

Agree. I think the combined approach is too difficult to have distinct styles from, and would benefit from additional hierarchy. What about this: - The ToC is split into two...

I'm _guessing_ that this was caused by my `path.sep` bug (see #53) - try out groc 0.2.17+ and see if that fixes it for ya

I think the right approach here is to AJAX in the next page (saving state across pages is less reliable)

Doh, turns out I'm a complete sh newb. I just pushed groc v0.2.5 (with 951c8dd27bd6150ebc7a5a17308941bb44426591), which should fix that issue at least

(this also points to the updated nevir/node-autorequire#2, which tackles the node version requirements that you were running up against over there)

Curses! My hunch is that you have an actual `sh` and I'm doing bad things. Rather than dealing with that, I'm just going to make bash a hard requirement for...

You should be in the gh-pages branch - if so, run the following to get back into a good state: ``` git reset --hard HEAD && git checkout master ```