whacked

@tabatkins which means 1. `(. a one)` compile to `a[one]` 2. `(. a "one")` compile to `a.one` 3. `(. a ".one")` compile to `a[".one"]` one problem with not having an...

@tabatkins to my knowledge the current state is to use `(. a b)` basically in the same way as `(.-b a)` in cljs, i.e. _always_ compile to `a.b`; and `(get...

@anko re: `:keyword`, that's fair. In https://github.com/Gozala/wisp `:keyword` is just sugar for `"keyword"` so the transform macro is trivial

personal vote :+1: caveat is my experience is only from cljs and wisp, but within these families this change looks not bad, and I will use this feature

Hi, I just reviewed this plugin after upgrading calibre. It seems to break with the newest calibre so I made a few changes and changed the default branch. Please checkout...

I'm not familiar with this error, but it looks like you are running a system install of elixir. The latest elixir online that I can find (`elixir.__version__ == "0.8.0dev"`) has...

That's not enough information for me to make a guess. Does the annotation button just disappear when you change pages? Can you try running `ebook-viewer $BOOK` / `calibre-debug -w $BOOK`...

I can partially reproduce the problem as you describe. When I lose the annotation popups, switching between paged/flow mode restores the functionality. But other times I still have annotation in...

The js is getting re-injected between pages and on page flow change, so that's not the problem. It looks like the paged mode is achieved mainly by applying the `-webkit-column-width`...

I never tried, but would bet that it does not. Is this a big concern? It looks like [calibre itself is stuck on python2](https://bugs.launchpad.net/calibre/+bug/1456642).