| # Get editor completions based on the config schema | |
| "$schema" = 'https://starship.rs/config-schema.json' | |
| format = """ | |
| $username\ | |
| $hostname\ | |
| $localip\ | |
| $shlvl\ | |
| $singularity\ | |
| $kubernetes\ |
| { config, pkgs, lib, ... }: | |
| let | |
| cfg = config.services.btrbk; | |
| sshEnabled = cfg.sshAccess != [ ]; | |
| serviceEnabled = cfg.instances != { }; | |
| attr2Lines = attr: | |
| let | |
| pairs = lib.attrsets.mapAttrsToList (name: value: { inherit name value; }) attr; | |
| isSubsection = value: | |
| if builtins.isAttrs value then true |
The package that linked you here is now pure ESM. It cannot be require()'d from CommonJS.
This means you have the following choices:
- Use ESM yourself. (preferred)
Useimport foo from 'foo'instead ofconst foo = require('foo')to import the package. You also need to put"type": "module"in your package.json and more. Follow the below guide. - If the package is used in an async context, you could use
await import(…)from CommonJS instead ofrequire(…). - Stay on the existing version of the package until you can move to ESM.
Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.
The Wayland project seems to operate like they were starting a greenfield project, whereas at the same time they try to position Wayland as "the X11 successor", which would clearly require a lot of thought about not breaking, or at least providing a smooth upgrade path for, existing software.
In fact, it is merely an incompatible alternative, and not e
| .m-0 { margin: 0; } | |
| .p-0 { padding: 0; } | |
| .mt-0 { margin-top: 0; } | |
| .pt-0 { padding-top: 0; } | |
| .mr-0 { margin-right: 0; } | |
| .pr-0 { padding-right: 0; } | |
| .mb-0 { margin-bottom: 0; } | |
| .pb-0 { padding-bottom: 0; } | |
| .ml-0 { margin-left: 0; } | |
| .pl-0 { padding-left: 0; } |
| # ~/.config/starship.toml | |
| [battery] | |
| full_symbol = "🔋" | |
| charging_symbol = "🔌" | |
| discharging_symbol = "⚡" | |
| [[battery.display]] | |
| threshold = 30 | |
| style = "bold red" |
This should make True Color (24-bit) and italics work in your tmux session and vim/neovim when using Alacritty (and should be compatible with any other terminal emulator, including Kitty).
Running this script should look the same in tmux as without.
curl -s https://gist.githubusercontent.com/lifepillar/09a44b8cf0f9397465614e622979107f/raw/24-bit-color.sh >24-bit-color.sh