Dmytro Maluka
Dmytro Maluka
Fixed by #3009
> I tried to write a plug-in that would do that, but could not figure how to access `util.StringWidth` from Lua code (which would be necessary to figure out how...
FWIW a more "proper" implementation (preventing usage of `regexp.Expand()` for non-regex): https://github.com/dmaluka/micro/commit/8ec3273fdba85052ee717181bfabc3adb2e31f28 Although both implementations produce the same result.
Yep, #2440 is a different issue, independent of this PR, since it is about `$` in the search pattern (regex), not in the string the search pattern is replaced with.
I think @teodor256 did not "set up" anything. The issue is with micro's built-in [linter plugin](https://github.com/zyedidia/micro/blob/master/runtime/plugins/linter/linter.lua). It uses these commands for checking C or C++ files: ``` makeLinter("gcc", "c", "gcc",...
It could be implemented via a plugin?
> How to decide what shall be added as an plugin Pretty much any non-trivial feature that can be implemented as a plugin without loss of functionality and performance? BTW...
I believe the problem with very long lines is that micro stores line data in memory simply as an array of raw bytes, not an array of unicode runes. I.e....
Will be great if you take care of it. But why do it in this PR? It is not really a highlighter issue. It is an issue of efficient representation...
> I see one possible reason: [Rune is int32](https://pkg.go.dev/builtin#rune). It would be like using UTF32 for all characters even if our document contains only ASCII Yes, it costs memory. Isn't...