Fix graphical issues from kanshi, other updates and fixes from recent

re-install

Kanshi seemed to have been the root cause of weird graphical glitches
starting sometime earlier this year. Weird flickering green and
occasional drm crashes where I lost sway for minutes at a time and it
would partially recover. Games would stutter very badly intermittently.
It is likely due to refresh rate synchronization somehow, but in my case
it's been simpler to turn it off. I'll maybe look into it again in the
future.
This commit is contained in:
Daniel Flanagan 2022-08-09 09:08:11 -05:00
parent 6b5355b370
commit 0478f47694
Signed by: lytedev
GPG key ID: 5B2020A0F9921EF4
10 changed files with 67 additions and 44 deletions

View file

@ -1,6 +1,6 @@
#!/usr/bin/env fish #!/usr/bin/env fish
set profile_dirs "$HOME/.mozilla/firefox/*.dev-edition-default" set profile_dirs $HOME/.mozilla/firefox/*.dev-edition-default
if test (uname) = Darwin if test (uname) = Darwin
set profile_dirs $HOME/Library/Application\ Support/Firefox/Profiles/*.dev-edition-default set profile_dirs $HOME/Library/Application\ Support/Firefox/Profiles/*.dev-edition-default
end end

View file

@ -1,3 +1,3 @@
#webrtcIndiator { #webrtcIndicator {
display: none; display: none;
} }

View file

@ -1,4 +1,4 @@
#!/usr/bin/env sh #!/usr/bin/env sh
# use `efibootmgr` to list boot entries # use `efibootmgr` to list boot entries
sudo efibootmgr -n 0002 sudo efibootmgr -n 0001
sudo reboot sudo reboot

1
host/desktop/config Normal file
View file

@ -0,0 +1 @@
exec output '"Dell Inc. DELL U2720Q CWTM623"' transform 270 scale 1.5

1
host/desktop/sway/config Normal file
View file

@ -0,0 +1 @@
exec output '"Dell Inc. DELL U2720Q CWTM623"' transform 270 scale 1.5

View file

@ -29,7 +29,7 @@ paru -Sy --needed --noconfirm \
pass pass-otp `# Password Management` \ pass pass-otp `# Password Management` \
hexyl `# CLI Hex Viewer` \ hexyl `# CLI Hex Viewer` \
rsync `# File Transfer` \ rsync `# File Transfer` \
neovim `# Text Editors` \ neovim helix `# Text Editors` \
unzip `# Simple Unzipping` \ unzip `# Simple Unzipping` \
tmux `# Terminal Multiplexer` \ tmux `# Terminal Multiplexer` \
kitty-terminfo `# Almost Better Terminal Emulator` \ kitty-terminfo `# Almost Better Terminal Emulator` \
@ -37,7 +37,7 @@ paru -Sy --needed --noconfirm \
w3m `# Terminal Browser` \ w3m `# Terminal Browser` \
jq `# CLI for Interacting with JSON` \ jq `# CLI for Interacting with JSON` \
xh `# New HTTP Utility` \ xh `# New HTTP Utility` \
age sops `# Simple Secretes Managements` \ age sops `# Simple Secrets Managements` \
inotify-tools `# Watching` \ inotify-tools `# Watching` \
fish `# Shell` \ fish `# Shell` \
time `# GNU time` \ time `# GNU time` \

View file

@ -24,8 +24,8 @@ profile desktop-H-2x4kside2 {
# } # }
profile desktop-primary { profile desktop-primary {
output "Dell Inc. DELL U2720Q CWTM623" enable mode 3840x2160@59.997Hz position 0,500 scale 1.5 transform 90 output "Dell Inc. DELL U2720Q CWTM623" enable mode 3840x2160@60Hz position 0,500 scale 1.5 transform 90
output "Samsung Electric Company SyncMaster H1AK500000" enable mode 3840x2160@59.997Hz position 1440,0 scale 1.0 transform normal output "Samsung Electric Company SyncMaster H1AK500000" enable mode 3840x2160@60Hz position 1440,0 scale 1.0 transform normal
} }
profile tv4k { profile tv4k {

View file

@ -163,7 +163,7 @@ mode "resize" {
for_window [app_id="floating_terminal"] floating enable for_window [app_id="floating_terminal"] floating enable
for_window [class="floating_terminal"] floating enable for_window [class="floating_terminal"] floating enable
for_window [app_id="zoom"] border none, floating enable for_window [app_id="zoom"] border none, floating enable
for_window [app_id="zoom" title="^zoom$"] border none, floating enable for_window [title="^zoom$"] border none, floating enable
bindsym $mod+shift+alt+f for_window [class=".*"] floating toggle bindsym $mod+shift+alt+f for_window [class=".*"] floating toggle
for_window [class=".*"] layout floating enable for_window [class=".*"] layout floating enable
for_window [class=".*"] layout splith for_window [class=".*"] layout splith
@ -177,8 +177,8 @@ bar {
} }
exec mako exec mako
exec gammastep -t 6500:3500 -l 39.0:-94.5 # exec gammastep -t 6500:3500 -l 39.0:-94.5
exec_always 'killall kanshi; kanshi' # exec_always 'killall kanshi; kanshi'
# exec /usr/lib/kdeconnectd # exec /usr/lib/kdeconnectd
# exec sway-init-tmux # exec sway-init-tmux
# exec $term # exec $term

View file

@ -1,7 +1,7 @@
{ {
"layer": "top", "layer": "top",
"position": "bottom", "position": "bottom",
"output": ["eDP-1", "DP-1"], "output": ["eDP-1", "DP-3"],
"height": 32, "height": 32,
"modules-left": ["clock"], "modules-left": ["clock"],
"modules-center": ["sway/workspaces"], "modules-center": ["sway/workspaces"],

View file

@ -9,34 +9,40 @@ take what you like.
# Basic Setup # Basic Setup
```bash
curl -LO lyte.dev/df.sh && sh -i df.sh curl -LO lyte.dev/df.sh && sh -i df.sh
```
## Manual Setup ## Manual Setup
```bash
git clone https://git.lyte.dev/lytedev/dotfiles.git "$HOME/.config/lytedev-dotfiles" git clone https://git.lyte.dev/lytedev/dotfiles.git "$HOME/.config/lytedev-dotfiles"
"$HOME/.config/lytedev-dotfiles/common/bin/dotfiles-setup" "$HOME/.config/lytedev-dotfiles/common/bin/dotfiles-setup"
```
# Repo Structure # Repo Structure
My dotfiles are composed together by layering "environments" since I want my dotfiles to be flexible across servers, laptops, desktops, and even my phone (via Termux). My dotfiles are composed together by layering "environments" since I want my dotfiles to be flexible across servers, laptops, desktops, and even my phone (via Termux).
```
lytedev-dotfiles lytedev-dotfiles
|- common --- common to all hosts and operating systems |- common --- common to all hosts and operating systems
| |- bin ------- programs or scripts useful to all hosts/OSs | |- bin ------- programs or scripts useful to all hosts/OSs
| |- data ------ shared storage for certain scripts | |- data ------ shared storage for certain scripts
| `- {app...} -- configuration related to {app} | '- {app...} -- configuration related to {app}
|- host ----- specific to specific hosts or types of hosts |- host ----- specific to specific hosts or types of hosts
| |- desktop --- for desktop-class machines | |- desktop --- for desktop-class machines
| |- headless -- for server-class machines with no display/GUI | |- headless -- for server-class machines with no display/GUI
| `- laptop ---- for portable, battery-having machines | '- laptop ---- for portable, battery-having machines
`- os ------- specific to operating systems '- os ------- specific to operating systems
|- linux ----- you alread know <3 |- linux ----- you alread know <3
| |- desktop ------ for desktop-class machines | |- desktop ------ for desktop-class machines
| |- headless ----- for server-class machines with no display/GUI | |- headless ----- for server-class machines with no display/GUI
| |- bin ---------- programs/scripts useful to linux machines | |- bin ---------- programs/scripts useful to linux machines
| |- {distro...} -- configuration related to {distro} | |- {distro...} -- configuration related to {distro}
| `- {app...} ----- linux-specific configuration related to {app} | '- {app...} ----- linux-specific configuration related to {app}
`- macos ----- for those stupid macbooks work tries to make you use '- macos ----- for those stupid macbooks work tries to make you use
```
Any environment should be able to extend the configuration of any application Any environment should be able to extend the configuration of any application
in some unique way. This isn't possible with all applications, of course, since in some unique way. This isn't possible with all applications, of course, since
@ -46,7 +52,9 @@ globs or some other mechanism.
One example of doing this well is with fish: One example of doing this well is with fish:
```fish
for s in $ENV_PATH/*/config.d.fish; source $s (dirname $s); end for s in $ENV_PATH/*/config.d.fish; source $s (dirname $s); end
```
This way, if any environment (a dir in $ENV_PATH) has a `config.f.fish` script This way, if any environment (a dir in $ENV_PATH) has a `config.f.fish` script
inside, it will be sourced by the main configuration file. inside, it will be sourced by the main configuration file.
@ -69,31 +77,40 @@ applications configured for the host OS.
There's a handy `fzf`-based script that makes this super easy (note that you There's a handy `fzf`-based script that makes this super easy (note that you
can select multiple environments with TAB): can select multiple environments with TAB):
```bash
dotfiles-link-environments dotfiles-link-environments
You can also list the possible environments: You can also list the possible environments:
```bash
cat $DOTFILES_PATH/common/envs cat $DOTFILES_PATH/common/envs
```
And then link them yourself (note that environments must be in $ENV_PATH and And then link them yourself (note that environments must be in $ENV_PATH and
cannot be nested, so replacing slashes with dashes is a nice way to show what's cannot be nested, so replacing slashes with dashes is a nice way to show what's
going on): going on):
```
ln -s (pwd)/os/linux $ENV_PATH/os-linux ln -s (pwd)/os/linux $ENV_PATH/os-linux
ln -s (pwd)/os/linux/arch $ENV_PATH/os-linux-arch ln -s (pwd)/os/linux/arch $ENV_PATH/os-linux-arch
ln -s (pwd)/host/laptop $ENV_PATH/host-laptop ln -s (pwd)/host/laptop $ENV_PATH/host-laptop
ln -s (pwd)/host/laptop/third $ENV_PATH/os-laptop-third ln -s (pwd)/host/laptop/third $ENV_PATH/os-laptop-third
# etc... # etc...
```
And run setup again once you've finished linking all related environments: And run setup again once you've finished linking all related environments:
```bash
dotfiles-setup dotfiles-setup
```
# Updating # Updating
Fork this repo, update your origin to point to your fork, and commit changes: Fork this repo, update your origin to point to your fork, and commit changes:
```bash
git remote origin set-url $YOUR_REPO git remote origin set-url $YOUR_REPO
```
Then you can just pull your changes down from wherever. Then you can just pull your changes down from wherever.
@ -104,12 +121,16 @@ machine. Remember about not using other people's dotfiles directly?
But if you must, you can add an upstream remote to point to my repo: But if you must, you can add an upstream remote to point to my repo:
```bash
git remote add upstream https://git.lyte.dev/lytedev/dotfiles.git git remote add upstream https://git.lyte.dev/lytedev/dotfiles.git
```
Then you can fetch and merge in my changes whenever you want: Then you can fetch and merge in my changes whenever you want:
```bash
git fetch upstream git fetch upstream
git merge upstream/master git merge upstream/master
```
# Screenshots # Screenshots