dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.12.0 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
deadscrews has joined #foot
deadscrews has quit [Client Quit]
deadscrews has joined #foot
deadscrews has quit [Quit: WeeChat 3.5]
deadscrews has joined #foot
deadscrews has quit [Quit: WeeChat 3.5]
noteness_ has joined #foot
noteness has quit [Ping timeout: 240 seconds]
an3223_ has quit [Ping timeout: 240 seconds]
<dnkl> jnes: yup, breaking change in the 'map' particle. Check the changelog, and the 'yambar-particles' man page for details on what you need to change
<mizzunet> Can I update script modules manually?
<mizzunet> By `signal` and `pkill -RTMIN+`
<dnkl> you can send signals to the *script*, but no, not the script *module* (or any other yambar module). There's no config reload support at all in yambar
<mizzunet> >you can send signals to the *script*,
<mizzunet> does that update output in yambar?
<dnkl> if the script is running in non-polling mode, then yambar will update its output as soon as the script sends a new "transaction". So, yeah, if your script is setup to emit new output on a signal, then yes, yambar will be updated
<mizzunet> This is my setup,
<mizzunet> path: /home/missu/.local/bin/_yambar
<mizzunet> - script:
<mizzunet> content: {string: {text: "{CAFFIENE} {MAIL}", font: *icon}}
<mizzunet> > if the script is running in non-polling mode,
<mizzunet> Would you tell me how my the config look like?
<mizzunet> The script is of a while loop running between 30 seconds interval
radu242 has quit [Ping timeout: 256 seconds]
radu242 has joined #foot
qyliss has quit [Quit: bye]
qyliss has joined #foot
cbb has joined #foot
noteness_ has quit [Remote host closed the connection]
noteness has joined #foot
dnkl changed the topic of #foot to: Foot - fast, lightweight and minimalistic Wayland terminal emulator || 1.12.1 || https://codeberg.org/dnkl/foot || channel logs: https://libera.irclog.whitequark.org/foot
<dnkl> 1.12.1 is out!
zdykstra has joined #foot
<zdykstra> hi all - I'm looking for a bit of advice on a visual error I'm seeing in my prompt. https://somebits.link/u/p/984c43a3aa/stream
<zdykstra> On the left edge of each triangle piece, there is a vertical pixel row that is the color of the opposite side. Where do I look in my config + font selection to fix this?
<w0rm> zdykstra: prompt is not coming from foot - but your shell
<w0rm> ah, that
<zdykstra> I'm using Hack Nerd Font, if that's relevant.
<zdykstra> I know enough to know I don't know enough :)
<dnkl> zdykstra: which version of foot?
kraftwerk28 has quit [Quit: bruh]
<zdykstra> I just noticed I'm a bit behind - foot version: 1.11.0 -pgo +ime +graphemes -assertions
<dnkl> zdykstra: still new enough - 1.12 does not change anything related to this
<dnkl> I'm not familiar with all the details of hack nerd, but maybe go through https://codeberg.org/dnkl/foot/issues?q=nerd&type=all&sort=&state=closed&labels=&milestone=0&assignee=0 and see if you find anything relevant
<zdykstra> Thank you. I just switched to generic Hack.ttf, and that seems to have resolved it. Do you want me to open an issue regarding this, or just chalk it up to using a badly-patched ttf ?
<zdykstra> also, thank you / everybody involved for a fantastic terminal. I appreciate it!
<dnkl> zdykstra: no point in opening an issue, as there's (probably) nothing we can do about it. The cause is _usually_ that the font has very specific expecations on how fonts and glyphs are handled
<zdykstra> After reading through https://codeberg.org/dnkl/foot/issues/533 it seemed like that was the case.
<dnkl> fwiw, you _could_ try playing around with letter-spacing
<zdykstra> I could tweak it a bit by setting horizontal-letter-offset=-0.4
<dnkl> one thing has changed since #533 - foot _does_ allow glyphs to overflow under certain conditions. Hoever, there are still some cases where glyphs are clipped. But it didn't look like that was what's happening in your case
<zdykstra> Is there a way to make the URLs in URL mode always be highlighted? e.g. enable what 't' does in URL mode permanently? I couldn't find that in the man page for foot.ini.
<baltazar> dnkl: what do you think of my "clear scrollback and keep current line only" implementation? are you really against the feature or should I create a PR?
<dnkl> zdykstra: OSC-8 URLs can be highlighted, always, by setting url.osc8-underline=always. Auto-detected URLs are *only* highlighted in URL mode
deadscrews has joined #foot
<zdykstra> sorry, not explaining myself well. Is there a way to default url-mode to always look like this: https://somebits.link/u/p/ff39f2ae95/stream ?
<dnkl> baltazar: haven't had time to think about it yet. Though, playing around with the cursor position behind the application's back is generally a bad idea. Which means I'm currently slightly against it. You're of course free to open a PR, to start a discussion
<dnkl> zdykstra: ah, read too fast. No, that's currently not possible. Usually the URL itself is visible anyway (except for some variants of OSC-8 URLs), and thus displaying the URL in the label too isn't really necessary
<cbb> baltazar: wouldn't it make more sense to pipe the data into some kind of pager?
<cbb> and have the pager do something like that instead of the terminal?
p00f has quit [Ping timeout: 240 seconds]
p00f has joined #foot