ThibautVerron

An easy work-around for users waiting for an update is to add `(provide 'tex-buf)` in the init file before loading `auctex-latexmk`.

This specification is probably for functions which should not be run in read-only buffers, even though they don't modify the buffer. Attempting to modify a read-only buffer results in an...

Yes I agree. I'd even go further and say that functions which shouldn't run in read-only buffers, regardless of whether they modify the buffer, should take steps to check if...

> @ThibautVerron , the reason non-interactive functions do not have checks for read-only buffers might be performance. However a large chunck of code is called via interactive functions. If all...

> You might want to squash the history, the last commits were very messy (sorry about that). Or should I do it and offer to merge a clean branch?

Ping? :)

What's the current status on this? As far as I could find, the `while-no-input` solution was merged and reverted because it was causing bugs. The solution suggested here might not...

After looking at it more closely, it looks like `sp-get-string` does recognize such generalized strings, then passes it on to `sp--get-string`, which then... chooses to discard it? Why? https://github.com/Fuco1/smartparens/blob/555626a43f9bb1985aa9a0eb675f2b88b29702c8/smartparens.el#L5355-L5357

Okay. It seems that I can get the functionality I want by removing this test (and replacing `:op cl` with `:op op`), and changing `sp-get-thing` as follows: - replacing ```(eq...

Ok so basic functionality (e.g. `sp-forward-sexp`) seems to work and no test break: https://github.com/ThibautVerron/smartparens/tree/feature/generic-string I added tests in ruby based on the existing ones, I had to tweak `sp-get-string` to...