Switch to rofi launcher, install user foot.ini, other QOL Improvements #23
Conversation
Set hotkey in config for rofi-network-manager and rofi-bluetooth
Will be added to /etc/skel/.config/foot/ by branding-greybeard package in OBS, fixes $TERM to xterm-256color rather than foot Nothing out there knows what the hell $TERM=foot is, and the error messages are annoying.
|
|
||
| # shell=$SHELL (if set, otherwise user's default shell from /etc/passwd) | ||
| # term=foot (or xterm-256color if built with -Dterminfo=disabled) | ||
| term=xterm-256color |
There was a problem hiding this comment.
I am on the edge with this, constantly switching between switching it off and on. Yes, this is more robust and works better if it leaks to other machines which have no idea about foot. On the other hand, a non-zero number of applications (e.g., xdg-terminal, which, for better or worse, we have in openSUSE) expect that TERM contains a name of the executable to run new terminal (and there are some historical reasons why it is not completely crazy, it may be even POSIX). Also, rofi-sensible-terminal needs TERMINAL variable (exactly because of the confusing state of TERM), because it doesn’t know about foot otherwise. It is a mess.
| @@ -9,7 +9,7 @@ backup_dir=$HOME/.config/sway/config.d/backup | |||
| sleep 2 | |||
| for i in XXX "Waiting for Internet connection" XXX 10; | |||
| do echo $i; done | |||
| until /usr/bin/ping -q -c 1 flathub.org | |||
| until /usr/bin/curl -s --max-time 5 https://flathub.org > /dev/null | |||
There was a problem hiding this comment.
Why? What’s wrong with ping? Establishing the whole HTTPS connection, just to check whether the server is up, seems a bit expensive.
| ### Set rofi as launcher, and enable hotkeys for rofi-network-manager and rofi-bluetooth | ||
| set $menu exec rofi -combi-modi window,drun,ssh,combi -terminal foot -theme arthur -font "hack 10" -show combi | ||
| bindsym $mod+n exec rofi-network-manager | ||
| bindsym $mod+b exec rofi-bluetooth |
There was a problem hiding this comment.
There is also https://git.cepl.eu/cgit/nmcli-rofi/tree/README.md, which could get included (I may package it, if required). I don’t know what you use for when you are around coffee-house/airport Wi-Fi hotspots.
|
Also, |
|
This https://github.com/nickclyde/rofi-bluetooth looks serviceable (will create a package). |
You mean the package I already packaged, and worked through, and got into :Factory a couple weeks ago? https://build.opensuse.org/package/show/X11:Utilities/rofi-bluetooth |
|
On Thu Feb 8, 2024 at 5:53 PM CET, sfalken wrote:
> This https://github.com/nickclyde/rofi-bluetooth looks serviceable (will create a package).
You mean the package I already packaged, and worked through, and got into :Factory a couple weeks ago?
https://build.opensuse.org/package/show/X11:Utilities/rofi-bluetooth
Yes, exactly that one. ;) Thank you.
|
Switch to using the rofi-wayland desktop launcher, and install a user foot.ini configuration file
See:
ProjectGreybeard/bugs#11
ProjectGreybeard/bugs#34
and:
https://build.opensuse.org/request/show/1143476
https://build.opensuse.org/request/show/1143477