Bjørn Erik Pedersen

> But specifying this at every call can be boring. I wouldn't say that, and it is much better than adding this to some global setting that you forgot you...

Just wanted to chime and say that I have a Hugo branch testing the `plugins` branch out, and it is a perfect fit, works great. I'm only using the resolver...

@evanw a quick yes/no question: * I understand that the `plugins` branch is work in progress and that API changes may/will happen. * But I notice that branch is most...

>Does the plugins have to be based on JavaScript? There will be a similar Go API (I'm looking forward to using that in Hugo), but that would not allow you...

I agree that it would be useful, and I would welcome a fix -- but it needs to be a config flag that enables it (so we don't break existing...

I'm not sure how generally usefull such a feature would be (I understand that you need it), but it should be possible to do the mods in this theme. Your...

This looks to be an issue with Chroma and I would appreciate if you could create and issue at https://github.com/alecthomas/chroma/issues which is closer to where it needs to be fixed....

This is more or less a direct port of Slate, and I think this behaves the same here as there. I haven't thought too hard about this, but changing this...

>But probably worth trying to achieve via AST post-processing in v2. I assume that, for this to be possible, there must be some kind of processing tokens that gets ignored...

>What I did mean to suggest was a workaround: for somebody storing those attributes as metadata outside of the document That may solve the adding `class="table"` to all tables (which...