• 29 Posts
  • 688 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle







  • I was using capital letters in the past, but they look so alien and are not fluid to type as small letters only. After some time I wasn’t sure which commands where capital and which were small letters, so left that concept behind me.

    But as a Vim user, I think of using single capital letters to open specific documents and files directly in Vim; emulating the global mark functionality of Vim. At the moment I have a convention of small letter+“rc” that will open configuration file in Vim, like this:

    alias brc='nvim ~/.bashrc && source ~/.bashrc'
    alias mrc='nvim ~/.config/MangoHud/MangoHud.conf'
    alias nrc='nvim ~/.config/nvim'
    ...
    

    But I might replace them with single letters brc as B in example.


  • While the effects of cheat codes are not copyrighted, its probably still possible to patent them. But that would cost the company lot of legal fees and complications, for cheats. Also thankfully the cheat codes themselves are not copyrighted. But I feel like Konami could potentially trademark the “Konami Code” (which is even named and known like this). This EU court is only about Copyright, which is a good thing and is what everyone gets for free. But trademarks and patents could still be a problem if companies really want to be an ass (like Nintendo, Konami or Rockstar).




  • In fact typing these commands by hand all the time won’t save you from a fuck stuff up anyway. The update-alias is the exact same command I would have typed. In fact, as an alias its less likely to make a typo and fuck stuff up. I’m doing this since 2008, when I started with Linux, and named it always “update”.

    Using the update command I’m always aware it changes the system. Not at least because I also often expand the alias to its full command with a shortcut (update will be replaced in the terminal with the actual commands), I also see what the output of the commands. And without my password it wouldn’t do any system changes anyway.

    So typing these commands everything out won’t be safer, as you suggest.




  • It’s just bunch of commands run with a single call, an automation. As long as I know exactly what each command is doing and if I wrote the alias myself, then I think its not a problem. What problem do you see with an update-alias such as I did there? The update-command does exactly that, it updates the box with all relevant package managers.

    However if other people are also using the box, then its obviously a different situation. I wouldn’t want to be reckless in the operation either; respect other users, even if you can do whatever you want.






  • The initial problem with Flatpak thinking it would be a good idea to add dozens of Nvidia drivers and re-download and update all of them on every update (causing a few gigabytes of downloaded files on every run of a normal flatpak update even if nothing needed to be updated)

    100% agree! Up until last year I was also using Nvidia and the Flatpak drivers for Nvidia got out of hand. I was using just a handful of applications in Flatpak, yet I had 6 different versions of the driver, each 350 MB and every of them was downloaded fully and updated every time. And that is besides other updates and other stuff. I would have needed your function so badly back then. :D