material-nf: net block is printed in reverse order when loopback device is used

[MaxVerevkin]

Output in the terminal seems OK.

Config

icons = "material-nf"

[[block]]
block = "net"
format = "{signal_strength} {graph_down}{speed_down;K}{speed_up;K}"
interval = 1

Video

for-gh.mp4

[ammgws]

Did you ever figure out what was going on here?

[MaxVerevkin]

Did you ever figure out what was going on here?

No, it's still happening.

[freswa]

Also happens with the pacman block when using icons = material-nf. If using format = "{pacman} + {aur}" and there are 2 pacman update available, 0 + 2 is printed.

[MaxVerevkin]

Also happens with the pacman block when using icons = material-nf. If using format = "{pacman} + {aur}" and there are 2 pacman update available, 0 + 2 is printed.

Terminal output is correct, right?

[freswa]

So one updatable pkg prints 1 - two pkgs print 0 + 2.
Terminal output is correct, but if I copy & paste it, it's reversed again - wtf? {"full_text":" ﮮ 2 + 0 ","color":"#002b36","background":"#268bd2","name":"9","instance":"0","separator":false,"separator_block_width":0,"markup":"pango"} <- The string after "full_text" is in reverse - it was in the correct order in the terminal.

[ammgws]

Is it backwards no matter what software you paste it into?

Also, try searching on the nerdfonts bug tracker as well because surely others have come across this too

[freswa]

The issue is the glyph 0xfbae. The string is not reversed when it's missing.
@ammgws It's reversed in the browser and the bar but neither in the terminal nor in the editor.

[GladOSkar]

I'mma hazard a wild guess and say that's because 0xfbae is an Arabic letter in UTF-16, which results some text renderers to presume arabic text flow, i.e. RTL

[GladOSkar]

Especially because apparently when @freswa pasted it into their browser it resulted in ﮮ which is that exact character, although i have no idea why/how a UTF-8 byte sequence could be interpreted as UTF-16 when rendering/pasting

[freswa]

Loopback is 0xfbe9 - same problem.

[freswa]

I think adding a 0x200e at the end should do the trick: " ﮮ 2 + 0 ‎"
Any other ideas to force pange/harfbuzz to print this LTR?

[freswa]

Apparently there is an issue that the glyphs are not PUA conform: ryanoasis/nerd-fonts#365

[freswa]

I think adding a 0x200e at the end should do the trick: " ﮮ 2 + 0 ‎"
Any other ideas to force pange/harfbuzz to print this LTR?

Garbage. The LTR marker needs to be right behind the "arabic" glyph, like " ﮮ‎ 2 + 0 ‎". Works here in github, but not for us:

@MaxVerevkin Can you try setting net_loopback = "\ufbe9\u200e" # nf-mdi-loop in your material-nf.toml?

[MaxVerevkin]

@MaxVerevkin Can you try setting net_loopback = "\ufbe9\u200e" # nf-mdi-loop in your material-nf.toml?

No, it doesn't fix everything. However, if if prepend it with any ASCII text, it works...

While

net_loopback = "\ufbe9\u200e" # nf-mdi-loop

Shows

net_loopback = "a\ufbe9\u200e" # nf-mdi-loop

Shows

[GladOSkar]

What happens if you prepend it with a zero-width space?

[MaxVerevkin]

No effect.