| Age | Commit message (Collapse) | Author |
|---|
|
If client use alacritty, after ssh into this remote server, ls doesn't
show color. Can be workarounded by server sshd accept COLORTERM and
client sshd send env. More see my comments in alacritty.toml config.
|
|
|
|
git clone repos from https://git.flylightning.xyz sometimes failed due
to "error: garbage at end of loose object..." and fatal: loose object...".
If I disable cache the problem gone. If I clean the cache and reenable
the cahe the problem gone but will come back. So I'm currently testing
to workaround it by disable some cgit-pink features and it seems also work.
|
|
|
|
Reasons:
1. I don't want to build debug packages
2. It breaks my mpra scirpt
Upstream code change:
- https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/90bf367e61b4f77f8351d0412be3d0c4ddadb85a
- https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/merge_requests/1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It took about 7 seconds to load https://git.flylightning.xyz/config_local_arch/log/
in the past. Now try disable some features to try to make it faster.
|
|
|
|
git blame works so I re-enable it. Add and change some other configs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Pacman hook multiple Depends is OR logic, can be tested via a test.hook
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mycgit.css import cgit.css and highlight.css. Because cgit.css is not a pacman backup file and it will be overwritten once cgit update. I can also update highlight.css automatically via pacman hook or `upd`. Also, I think `highlight` not using `--inline-css` maybe is a better way performance wise and more elegant (less messy generated html source code).
|
|
|
|
Example files are:
- <https://git.flylightning.xyz/config_local_arch/tree/home/xyz/.config/systemd/user/ssh-agent.service>
- <https://git.flylightning.xyz/config_local_arch/tree/etc/systemd/network/10-cloud-init-eth0.network?h=ka>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
config unchanged
In the past, `chmod a-w ~/.config/htop/htoprc` is sufficient to let htop not able to write to htoprc. So configs keeps the same if I press anything in htop. But it seems htop new version 3.3.0 makes it not working. I'm not sure why. I suspect "Write configuration to temporary file first" in changelog is the reason <https://github.com/htop-dev/htop/blob/main/ChangeLog#L19>. Luckily, `chmod a-w ~/.config/htop` still works by making htop config dir not writable.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
