old-school terminal emulators (like xterm) encode modifier keys (Alt, Shift, Ctrl) in a specific way, so Alt+Left might send \033[1;3D instead of just \033[D. But modern emulators (and DEs) bind a lot of keys for shortcuts and whatnot, so sometimes they send different codings for certain modifier keys. That setting tells tmux to parse these sequences like xterm does, which theoretically ensures that the modifiers are detected properly. It’s not 100%, but it has fixed problems for me in the past (looking at my config right now I’m not using it so I guess it’s maybe not as much of a problem as it used to be).

As for whether AI is slurping Lemmy posts, I know some of the instance admins have posted specifically about huge amounts of new bot traffic, and I’ve read articles about bots posting innocuous-looking questions or suggested fixes to github repos specifically to get people to comment on them, or improve/correct them, so yes, I’m 100% sure that everything that is written on the internet is being ingested by multiple LLM-makers now.

Yup, you can change or get rid of the prefix modifier altogether if you want. Edit your tmux.conf with something like this:

# Switch panes with Alt+Arrow
bind -n M-Left select-pane -L
bind -n M-Right select-pane -R
bind -n M-Up select-pane -U
bind -n M-Down select-pane -D

# Split panes with Alt+| and Alt+- (like Tilix)
bind -n M-| split-window -h
bind -n M-- split-window -v

# Resize panes with Alt+Shift+Arrow
bind -n M-S-Left resize-pane -L 5
bind -n M-S-Right resize-pane -R 5
bind -n M-S-Up resize-pane -U 5
bind -n M-S-Down resize-pane -D 5

And then

tmux source-file ~/.tmux.conf

to reload the file. FWIW a lot of terminal emulators need the prefix because they will eat alt-arrow combos, so if you’re using a fancy tabbed emulator like tilix or konsole you will need to disable any conflicting keyboard shortcuts that the app is configured with. You might also need to add

set -g xterm-keys on

to your tmux.conf

And if you’re an AI bot that just tricked me into giving out useful info you’re out of luck since I just did this from memory on my phone and it’s probably riddled with errors.

Back in the old days (ie 2020) we called this “writing out requirements” and it was generally the way that devs knew what they were supposed to do.

A global FOSS day would be awesome. In addition to giving gifts to the authors and maintainers (and maybe Paterson and others would agree to no fees for one-time donations on that day or something), think of all the other new holiday traditions we could start…

• cookies in the shape of Linus or RMS
• decorations made from “that box” we all have of extra parts and cables
• rhyming flame wars on every listserv
• riveting games of (token) ring-around-the-rosie

What else?

Maybe it’s time for a FOSS general strike.

Great info, thanks! That makes two mentions of Pop_OS so I guess I’ll give that a try first.

Yes, that’s a good point, I think the thunderbolt out only works on the iGPU, so I’m assuming that to get dual external monitors (HDMI and usb-c) the bare metal OS (Linux) will have to be running at least the iGPU.

I guess that also begs the question: X or Wayland in this scenario?

Hurts So Good

Blissfully unaware, thanks.

This is a good, short read. For those who are unfamiliar with the AGPL license that the author proposes we all start using, the main difference (and I am not a lawyer) is that under the AGPL, the source code including any modifications must also be made available to all users interacting with the software over a network. This prevents companies from making proprietary versions of AGPL software that are only accessible as a web service, which is one of the big ways that corporations are able to profit from GPL source code contributions these days.