Reuben Thomas
Reuben Thomas
> The problem is this - compilation does not always go through pkgconf/pkg-config. Sometimes people compile manually and then things get more complicated. This is something I regard as Not...
I sympathise. I have used tree-sitter-mode, and it's amazing to me that it manages seamlessly to build shared libraries from Rust and install them, but of course that's a much...
Because, as I said, you already know what version of Enchant you are #including when you #include it. It's the same as the reason you don't have a macro to...
Sorry, I must be being very dense here. I don't see what it has to do with controlling the build process. When you `#include ` you are getting libfoo. When...
> They will run commands like this, if for example `pkg-config` is lacking on their installation or if they build Enchant themselves and try to link to it afterwards. >...
> Of course not. But I have seen all these things. But this is understandable: My Emacs module is used by people who may not be experienced C developers -...
Thanks @swilmet, I guess that would be a good thing to look at too.
Not really needed if we remove `enchant -a` (#393).
I agree that it would be good if Pandoc cropped images on output. At the moment I'm working with Word documents of illustrated lectures with scanned slides, all of which...
I had a look at the code, this is all very unfamiliar territory for me (been about 20 years since I did any Haskell!), but would the idea be to...