• 7 Posts
  • 77 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle
  • Lemmy is a far better platform for discussions than Discourse in my opinion. The tree like sub-reply threads in each post (the Reddit concept) is preferable over a single thread of replies. You don’t need to cross quote and for readers no need to read the quote to see who and to what the reply is about. I don’t like Discourse discussion platforms at all.

    However, Discourse has a few features that fits well for a discussion platform. I like the tags and Trust system of it.


  • Very nice. Also thanks for reporting back. Yes, in Linux filenames and extensions are case sensitive, unlike in Windows. Most programs (including Windows itself) treat lowercase and uppercase in filenames as the same thing. And because most developers and users are on Windows, they are used to it this way. So on Linux we have to take extra care and in some cases rename files.

    Next would be to learn how to swap a Disc when the game asks to. I mean for games that are multi-disc, in case you play other games too: https://docs.libretro.com/guides/disc-swapping/

    And I also recommend the official forum of RetroArch too, to ask questions if you have any (I am there too ;-)): https://forums.libretro.com/ Because there are lot of engaged users who know RetroArch pretty good and even developers of RetroArch and some cores respond and help there too. Have fun with Final Fantasy Tactics (one of my alltime favorites). BTW the game was announced to have a remaster.




  • Here is on that I actually don’t use, but want to use it in scripts. It is meant to be used by piping it. It’s simple branch with user interaction. I don’t even know if there is a standard program doing exactly that already.

    # usage: yesno [prompt]
    # example:
    #   yesno && echo yes
    #   yesno Continue? && echo yes || echo no
    yesno() {
        local prompt
        local answer
        if [[ "${#}" -gt 0 ]]; then
            prompt="${*} "
        fi
        read -rp "${prompt}[y/n]: " answer
        case "${answer}" in
        [Yy0]*) return 0 ;;
        [Nn1]*) return 1 ;;
        *) return 2 ;;
        esac
    }
    

  • For the newer version of program, that’s why we have the $PATH. You put your program into one of the directories that is in your $PATH variable, then you can access your script or program from any of these like a regular program. Check the directories with echo "$PATH" | tr ':' '\n'

    My custom scripts and programs directory is “~/.local/bin”, but it has to be in the $PATH variable too. Every program and script i put there can be run like any other program. You don’t even need an alias for this specific program in example.


  • I’m not sure what you mean with the question. If you have any alias like alias rm='ls -l' in your .bashrc in example, then you cannot use the original command rm anymore, as it is aliased to something else. I’m speaking about the terminal, when you enter the command. However, if you put a backslash in front of it like \rm in the terminal, then the alias for it is ignored and the original command is executed instead.

    Edit: Made a more clear alias example.




  • i also have the chmod one, but mine is named just x:

    alias x='chmod +x'
    

    I also have the yt-dlp "$(wl-paste)" one, but its build around a custom script. So sharing it here makes no sense. Its funny how often we do same thing in different ways (extracting or creating archives in example). Often aliases get development into function and then they turn into scripts. For some of the more simple aliases, here a selection:

    alias f='fastfetch -l none'
    alias vim='nvim'
    alias baloo='balooctl6'
    


  • With how many new Linux users we get recently, I don’t like this joke at all without a disclaimer. Yes yes, its your own fault if you execute commands without knowing what it does. But that should not punish someone by deleting every important personal file on the system.

    In case any reader don’t know, rm is a command to delete files and with the option rm -r everything recursively will be searched and deleted on the filesystem. Option -f (here bundled together as -rf) will never prompt for any non existing file. The / here means start from the root directory of you system, which in combination with the recursive option will search down everything, home folder included, and find every file. Normally this is protected todo, but the extra option --no-preserve-root makes sure this command is run with the root / path.

    Haha I know its funny. Until someone loses data. Jokes like these are harmful in my opinion.