b87ae061afd18e0a594c06c65a5d33a9864aa9cf — Rohan Kumar 1 year, 11 months ago dcdbb03 trunk
Doc: Add some info to README
1 files changed, 2 insertions(+), 1 deletions(-)

M README.md => README.md +2 -1
@@ 9,10 9,11 @@ Be aware that these contain some personal preferences and were designed for my p

Some quirks:

- Shebang lines are `#!/usr/bin/env dash`; you should be able to change them to another common POSIX-y shell (bash, zsh, etc) if you don't have the Debian Almquist Shell installed.
- I run Wayland, so there are some Wayland-specific envvars/paths involved
- I symlink a few FF config files (like my user.js and userChrome.css) from the Flatpak config dir to ~/.mozilla because I use the FF beta version via Flatpak (mostly headless).
- I set my FF GTK theme to Breeze-dark, but my system currently uses Adwaita-dark.
- Browsers get their own "Downloads" subdir.
- Browsers (Chromium, Firefox, NetSurf) get their own "Downloads" subdir. What `chromium-sandbox` thinks is `~/Downloads` is actually `~/Downloads/chromium` on the host system.
- A few of the ro-binds are less granular than I'd like them to be. For instance, all programs get full access to library directories. Chromium gets full access to XDG_CONFIG_HOME because it has chromium configs, fontconfig settings, GTK settings, and a bunch of other stuff that I haven't gotten around to listing.
- Chromium's nav widgets have poor font rendering since they don't have access to all the files needed for proper antialiasing. I'm okay with this because the actual page content looks fine and the text is still readable.