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

help-circle
  • I’m not Nintendo supporter and play Switch games on emulators. But one justification is, that this is current generation system. And while the developers are not responsible for, this enables easy piracy, and basically each first party game got leaked early and was playable before or shortly after launch. So lot of these people connect the wrong dots and say that the emulator “supports” piracy, which is not true, but depending on the view could be interpreted by some haters.

    The Ryujinx isn’t illegal and I am pro emulation (I have terabytes of Roms for all kind of systems) and Open Source. The above statement is not MY justification, but what I think is what most Nintendo supporters will say. I talk about this subject with my bro, watch YouTube videos and read forum comments and that is what I get from them.



  • If I do ps aux | grep root, then the newline is preserved. So I’m not sure what exactly the problem is. There is a user option for ps, but it does not work with aux, ps --user root . You can ps ax --user root, but I’m not sure if this output is what you want.

    Btw if you grep, then I recommend using ^user , so it only matches the beginning of each line (the actual username), as ps aux | \grep ^root (notice the backslash). Do you have an alias for grep? Try \grep instead. The backslash in front of the command will use the actual command and ignore your alias.













  • I like these self made scripts. Some ideas to improve this: a) instead ls, use find command if you want use its output as input in another program (will yield fullpath too), b) fzf has a preview functionality, which I like a lot to use when it comes to directories or script files. As for the run command, I’m not sure why you use xargs and what i3-msg is needed for. Here is an alternative way.

    (Edit: I always forget that beehaw will convert my ampersand to &. Have this in mind if you read the below code.)

    bash -c 'cd "${HOME}/.local/bin"; path="$(find . -maxdepth 1 -type f -executable -printf "%f\n" | fzf --preview "cat {}")" && "${path}"'
    

    below same command in a bit more readable standalone script:

    #!/usr/bin/env bash
    cd "${HOME}/.local/bin" || exit 1
    path="$( \
        find . -maxdepth 1 -type f -executable -printf "%f\n" | \
        fzf --preview "cat {}" \
    )" && "${path}"
    

    The biggest problem with fzf is, that scripts that need an argument are not covered here. One could either use the input string from fzf as arguments or like that, or an optional input after fzf selection.


  • I might be missing something here but I don’t know how other launchers could possibly make this a simpler process.

    Shortcuts to launch an app directly in example. So my keyboard becomes my launcher.

    I use bunch of different tools, including KRunner (on KDE) and previously Rofi. These type name and search tools for launching an app have the problem that you need to remember what name the tool was. For programs I use often this is not an issue, but not all applications have names good to remember and not all of them are used often. The associated description helps, but sometimes I don’t know what words to type.

    Therefore I “need” the app menu with categories and favorites, to navigate with the mouse through. And the most used applications are usually assigned to a shortcut and my panel on the top. In short I use mostly all of these techniques as an application launcher (in that order):

    1. favorites on panel and my keyboard shortcuts
    2. app menu with categories, navigating with mouse
    3. run tool to search for app name and description (also integrated into the app menu)
    4. additional helper scripts to search and launch programs in the terminal

    Edit: Forgot to mention that some of the launchers I use are custom made scripts for the terminal.