James Reeves

Perhaps something like this: ``` Allow multiple selected options in select elements Allow multiple selected options in order to support select elements that have the 'multiple' attribute. The 'selected' argument...

Thanks! I'll merge this into master once I release 2.0.0, if that's okay by you. Since I've got a release candidate for 2.0.0, I want to delay any new features...

Macros are evaluated from the outside in, so we could certainly look through the syntax tree and do something to reduce the nesting. There may also be a better solution...

I think ideally I want to separate out compilation entirely, but that will require some consideration and probably a `hiccup3` namespace.

See: https://github.com/ring-clojure/ring-ssl/pull/11

See: https://github.com/ring-clojure/ring-ssl/pull/11

Unlike https://github.com/jonase/eastwood/issues/88, this looks like a legitimate warning, not an exception.

I've found myself with some time to mess about with this, and I was wondering what your preference would be in terms of how to handle this. We could handle...

Sounds good. What about an option `:read-passphrase` that defaults to `deps-deploy.gpg/read-passphrase` and expects a zero-argument function that returns a string. If `nil`, it will default to letting GPG handle it.

At this point it's probably better to fork the project. Bringing a new maintainer onto the project is going to take time, and I'm afraid that's something I currently lack.