[-] dontmindmehere@programming.dev 3 points 5 months ago

there's already official appimages for neovim, I use them (but not with firejail) and they work fine. but the lsp stuff is all installed outside, my guess is it'd be really annoying to mantain a custom compiled appimage

the best option is probably to just run neovim inside a docker container, you can then mount the directories every time you run a neovim container (~/.config/nvim, ~/.local/share/nvim, optionally .local/state/nvim and your undodir/undofile, there may be more I'm not sure).

assuming you want to isolate your home directory, what gets annoying is giving it access to only the code you're editing, I've yet to try this but my next plan is to give it read access to $HOME, then read/write access to the neovim dirs, and then take an argument to mount the project directory

some other options which I also haven't tried are

  • distrobox, which just creates containers as well but by default wants to mount your entire homedir inside them
  • devcontainers
  • lspcontainers which isolate the LSP binaries themselves
  • LXC/LXD/Incus containers which behave a bit different from docker containers, could be worth looking into
[-] dontmindmehere@programming.dev 3 points 5 months ago

it's lightweight and still looks pretty good, and you can have plenty of fun fighting bots, surprised more people haven't mentioned it

[-] dontmindmehere@programming.dev 1 points 5 months ago

I thought most DEs gave apps generic names on their .desktop these days? gedit -> text editor, file-roller -> archive manager, baobab -> disk usage analyzer, etc.

maybe just a Mint thing, I actually used to struggle to find the actual name of an app there

[-] dontmindmehere@programming.dev 3 points 5 months ago

bit of both i guess? "normies need to get good" could be diluted into "do your research before going to linux", which in most sensible online discussions is already the recommended way: test things out in a VM, try out different DEs, practice configuring things, finding alternatives to your current workflow, etc etc. it's a harder sell than "just switch to linux" but IMO it's absolutely necessary

but my comment is more of a reaction to influencers not doing that at all and making le funny challenge of jumping to linux blind and breaking shit because it's good content and "trying out linux" is still trending

problem is they must be getting this idea that "linux is so easy and fun and seamless and you don't have to research anything" from somewhere, which i do think is probably way more from people in their audience hyping up linux and not necessarily the wider linux community but these voices gotta be out there

[-] dontmindmehere@programming.dev 1 points 5 months ago

imo the linus disaster was an unfortunate combination of

  • the unpatched pop_os issue
  • linus going TLDR (reasonable but that's on him)
  • apt messages generally being long
  • linus not having a frame of reference on which long message is good (apt upgrade listing 50 updates) vs which are bad (apt install saying his DE is about to be nuked)
  • and yes, him playing it up for the video, and willingly ignoring his gut feeling that typing "yes, do as I say" can't be doing anything good

in the end i still think it was kinda irresponsible for linus to publish that, but the whole premise of the video was them going blindly into linux (which i also disagree but whatever)

[-] dontmindmehere@programming.dev 1 points 6 months ago

machines are the ones full of weird jibber-susceptible things, the default state for everything is jibbered until dedicated people decide to spend their time unjibbering

[-] dontmindmehere@programming.dev 1 points 6 months ago

in this case, you'll probably have to create a desktop entry in ~/.local/share/applications/ydotoold.desktop

something like

[Desktop Entry]
Name=ydotool daemon
Exec=the command you used to launch
Type=Application

you can look at other .desktop in the same directory for reference

[-] dontmindmehere@programming.dev 2 points 6 months ago

as far as i can tell, those keybindings are handled internally, they don't invoke shell commands

you can use something like wtype or ydotool to send keybindings from kdeconnect

[-] dontmindmehere@programming.dev 3 points 6 months ago

mega piss ray from space

[-] dontmindmehere@programming.dev 2 points 6 months ago

seems to me he's trying to be more general than the Search example and considering that another complex project may actually have those problematic cases

i mean, he doesn't even dismiss the patterns with code duplication, just lists it as a drawback, which agrees with his conclusion that there's no one-size-fits-all solution

[-] dontmindmehere@programming.dev 1 points 7 months ago

yes and with custom readline config (/etc/inputrc) you can use vim keybinds in it

[-] dontmindmehere@programming.dev 2 points 7 months ago

too busy with the rocket boy

view more: ‹ prev next ›

dontmindmehere

0 post score
0 comment score
joined 7 months ago