user202729
user202729
Interestingly `∂(a, b)` does not get the same special treatment as `f(a, b)`. (this one is especially common in Jacobian notation for multivariate calculus)
I think best compromise would be #254.
Interesting. I think the current design is scalable though -- except for the state system, everything else is memoized. (there's another issue #322 but that's not really an issue here)
https://gitlab.com/giacomogallina/typst-cd A hack.
Line 4 of `vimtex#jobs#cached` is ``` function! vimtex#jobs#cached(cmd) abort " {{{1 " Cached version of vimtex#jobs#capture(...) let l:cache = vimtex#cache#open('capture') > return l:cache.has(a:cmd) \ ? l:cache.get(a:cmd) \ : l:cache.set(a:cmd, vimtex#jobs#capture(a:cmd))...
Some quick testing: ``` let a={} function A_abc() echoerr 123 endfunction let a.abc=function('A_abc') call a.abc() ``` seems to work well enough at displaying the function name. Could anything go wrong?...
That code looks... strange (and without much rationale what's going on). Is it just that if `match(x, '[\x80-\x9F,\xE1]') > 0` then it's considered "likely" that the thing is invalid UTF8...
For the first part, I mean that if the code is rewritten to avoid numbered-function, then the traceback in the log will contain the name of the function. (admittedly the...
Anyway the reason why I suspect that is because the time I see that happen, I run `:9verb set shell` and see that that function is the culprit. Is there...
Let's see... if I understood correctly, currently `"q"` and `q` is parsed to exactly the same thing in math mode. The option whether or not to use italic font is...