stupid_asshole69 [none/use name]

  • 0 Posts
  • 49 Comments
Joined 8 months ago
cake
Cake day: March 3rd, 2025

help-circle
  • I have used multiple brands of audio interface with between one and over fifty mono inputs to record, loop and analyze signals in real time on windows, linux and macos. I have used amd, intel, nvidia and arm/apple gpus to play games on linux, windows and macOS.

    If you can tolerate the old man gaming experience of fiddling with some settings, maybe editing a text file or something then you’ll have a better time gaming on linux than on windows.

    If you understand what your daw is doing under the hood then you will do fine using linux for production. If you need to use a specific daw or you need to be able to use its plugins on an alternate platform without much effort you won’t have an easy time.

    Ubuntu studio is probably a bad choice. You’re likely better off starting from the ground up with a non-Ubuntu distribution. Especially if you have a paid copy of reaper then you’ll have no problem finding support for whatever you wanna do.




  • It doesn’t matter what people on the internet think or what you think, it matters what your partner thinks. When you only get to enjoy it by yourself are you talking about watching or listening to something? If so, and your partner is implacable about piracy, then just treat the cost of buying or renting media the cost of a date night. It’s most likely worth it to enjoy those things together.

    What does your partner dislike about piracy? There’s lots to be weirded out by, the internet culture exposure, often times the quality, the abnormalcy of the experience, the implication that you can’t afford to pay for media, just to name a few.

    Talk to your partner and try to accommodate their concerns instead of asking the internet how to weasel your way past them.





  • I been using torrents since they became a good option a little over twenty years ago. I’ve torrented using public and all manner of private trackers both with and without vpn or tor.

    I have received letters from various ISPs during those years. Here’s what it all boils down to:

    What’s most important: turn off peer exchange and dht, turn on require encryption.

    What’s also important: only use private trackers.

    What’s less important, but good to have: use a vpn with port forwarding with your client bound to its interface. It doesn’t matter if you don’t bind the client to the vpn interface so make sure you do that.

    E: just read through the comments on your native instance that don’t show up to me normally. There’s some old misinformation going around still. I’m not gonna argue or go into great detail but things like only leeching, only using foreign trackers or using someone else’s WiFi don’t do anything to help you avoid some kind of letter.






  • I was able to test out what you’re looking for on macos and its default out of the box terminal does copy and pasting with command-c/x/v just like everywhere else in the os. I haven’t tested Unicode, but rich text and other marked up text types get copied with their formatting between editors that support it and as ansi characters when pasted into the terminal. Option (alt) arrow keys jump to the first letter of each “word” and control arrow keys don’t do what you want because at the os level they’re the keys for switching workspaces. Which is really nice and reminds me I need to set up my windows image to do this instead of uhh win-ctrl or whatever it is.

    The default macos shell is zsh, so maybe with that shift-select extension you can get it the way you like.

    Might be time to switch to a mac!

    I’m really surprised that you couldn’t get alacritty working in Ubuntu, it’s been working fine on Debian stable for at least two major versions when installed through apt.




  • Yeah when I call them the Macintosh keys that’s because I’m almost 100% that the 84 Macintosh was the first thing to use them. Not just the keys specifically, but that operating model we I guess later called wysiwyg. I think it was command instead of control, but it occupies the same place on the keyboard. It’s certainly the oldest thing I’ve used that had them. Windows used to do it like old dos word processors did, with insert and delete etc.

    It’s the design and interface language of gui software for at least 40 years and everyone should know it.

    System wide clipboard would work fine in the terminal but it would be a downgrade, you’d have to give up all the lovely buffers that all your different editors use and are designed around. Even lowly less has a buffer select somewhere in there. Most of the time shift-ctrl-v lets me dump the whatever the system clipboard is out into the command prompt if I need to.

    If the idea of using a different modality for editing text bugs you so much, what do you think of the fact that you already use one? When you’re typing your fingers are on the home row and when you need to edit you switch your right hand to the arrow and function keys. It’s a lot like how editing in vim requires me to move my right hand one key over to the left.

    That way of thinking is how I was able to accept learning vi keys and vim about twenty years ago when I had the same thoughts as you about new shortcuts.

    An alternative might be using macos. I can’t remember if it uses the mac keys to cut and paste into its terminals but it might.


  • I do not hate selecting text with shift. I do not even oppose selecting text with shift. The Macintosh user interface model is the standard for gui operations. It’s good to know how to use the interface of gui applications because usually the majority of your time will be spent in them.

    The terminal has a different interface. It’s different for a lot of reasons. Some are historical, some are technical, some are based on interface standards and ideas.

    I’m trying to help you understand how learning to use the terminal as it exists will be a better solution than making the terminal behave in the way you’re already familiar with.

    The reason it’s a better solution is that using the terminal as it exists allows you to more easily communicate and learn & allows you to use a broad range of tools on any system without having to import a bunch of configurations, programs or environment variables.

    It’s easy to read my comments and come to the conclusion that wanting to use the Macintosh text selection keys is the thing I think is stupid, but what I’m trying to reiterate in every reply is that making the terminal use Macintosh text selection keys is the thing I think is stupid.

    Part of learning how to use a computer is developing a combination of skills and tools that you can use to solve the problems that communicating by doing mathematics really fast always entails. I am trying to convince you to learn the toolbox the computers terminal comes with before you start to weld a tire iron on to your ratchet wrench.


  • I am not trying to insult you, I am trying to help you to not do something stupid.

    I understand that you think everything working the same would be better, I was trying to explain how that’s not the case and you will ultimately be better off not doing the thing you’re suggesting.

    To butcher a car metaphor: a peterbilt has lots more controls and gauges than a camry and they’re in different places some of the time. Wouldn’t it be better to make all the controls the same? No, of course not. A low range gearbox, intercooler temperature gauge, gigantic steering wheel with a knob and all the other differences are necessary for effectively hauling freight. Those same controls are not useful in a sedan. Do truckers have massive problems driving the grocery getter when they’re not working? No, of course they don’t. Sometimes you might give the gear selector a pull in the wrong direction but that’s no big deal.

    Instead of making a mutant terminal and dealing with all the problems that could cause you, you will almost always find it’s better to learn screen or tmux (with one of their default bindings) because then you will have a fewer problems, an easy time communicating with people about the ones you do have, and a broader skillset.

    Again, I am not trying to insult you, I am trying to keep you from doing something stupid.


  • You Will Probably Need To Spend Money

    Get an external 2.5” sata usb enclosure. It costs about $10. here’s one on amazon

    Get a 2.5” sata ssd. 512gb is about $20 here’s a sata ssd on amazon

    Optional, but recommended: get a pair of 8gb sticks of ddr pc3 12800 laptop ram, it’s about $20. here’s a 16gb kit on amazon

    Turn the computer on, let it boot all the way up, turn off fast startup and bitlocker if they’re on and then restart, let it boot all the way up then shut it down using start -> power -> shutdown and let it power off normally. Doing this makes sure the computers disk is in a safe state to be read later.

    Take out the old hard drive, put it in the enclosure, install the ssd and if you got it, the ram.

    Now your old files are in the enclosure.

    Install whatever you like onto the laptop. I always recommend Debian. It will run perfectly fine on your computer especially with the ssd and ram.

    Now plug up your drive and make copies of your files. They’re all on the old drive in the enclosure and the drive could die at any time so do this as soon as you can.

    The benefit of this approach is that it doesn’t rely on the speed of the computer or old operating system, preserves everything so you don’t lose something you didn’t remember to grab and minimizes the possibility of error.

    You also have the option of just plugging the old drive into the computer when you do it this way.


  • zsh shift select is probably a good start. Zsh can most likely be rebound to do what you want with the possible exception of break.

    Don’t do what you want though. It’s stupid, will make you unhappy and cause you problems.

    Your terminal isn’t powershell. Your terminal emulator is an emulation of a terminal. There is a shell that it runs, probably bash, but it’s also an emulated terminal.

    Powershell (and shells that slough off compatibility for the sake of adapting newer ideas, like zsh) is cool, but its able to be the way that it is because it isn’t a terminal emulator.

    If you change a bunch of shit around to make zsh like powershell then you can break your terminal emulation.

    Instead, either use tmux or screen bound the way you want, with their defaults or just don’t use the terminal. You don’t need to. If you do need to then you’ll be exposed to funny things like “the terminal isn’t a wysiwyg editor” and “stdio includes function keys” which require a layer of abstraction in between you and the terminal like tmux or screen, which have existed for many years and are the mature, feature rich solution to your problem.

    The benefit of not doing what you want by making yet another mutant zsh and instead adopting one of the existing solutions is that your terminal will work like all the others, so when someone asks you to try something in order to troubleshoot a problem you’ll be able to instead of having to troubleshoot how your weird garbage is different from theirs.

    Another huge benefit of not creating a special, unique zsh to do what you want is that you will gain competency with every terminal you’ll ever encounter. Which means that instead of being lost when sat down at a terminal other than your own, you’ll be just fine.

    If you want to persist in the doomed world you have created, though, oh-my-zsh documentation will probably get you most of the way to the rest of what you want.