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

help-circle
  • Discovering tools is not what the question and solution presented here was. But for that question, I recommend downloading a book about Linux as a reference or something like that. Or a basic tutorial series to read and remember basics about Linux.

    You can also just list the ls /usr/bin directory to see what programs are there.

    There is actually a command to search the man pages for terms, to list the commands: apropos

    $ apropos -s 1 search
    apropos (1)          - search the manual page names and descriptions
    find (1)             - search for files in a directory hierarchy
    flatpak-search (1)   - Search for applications and runtimes
    gamemodelist (1)     - search for processes running with gamemode
    rg (1)               - recursively search the current directory for lines matching a pattern
    zipgrep (1)          - search files in a ZIP archive for lines matching a pattern
    

    Note: I cut some parts out in the output to make it shorter. The option -s 1 means, it will list man pages from section 1 only.







    • Breath of Fire 2 (SNES): I don’t know how I managed to finish this game. It’s too drawn out, didn’t have an interesting story to follow with meaningless and annoying stuff to do and the random battles was too often.
    • Killer Instinct (SNES): I played this game seriously, learning the combos and fighting competitive with a friend. But nowadays it just does not feel good to play.
    • Toshinden (PSX): Similar to Killer Instinct, I played this game seriously with a competitive friend. Playing it today, I just can’t do it.


  • Fish can just be a shell. I only write bash scripts.

    That’s the exact problem. You deal with two languages. I did that too BTW. Now for someone who is experienced, its fine. But for someone who just started learning about Linux and scripting, its not ideal, as it adds unnecessary complications and friction for a learning process that is already complicated. Because learning Bash is a must do in my opinion. Regardless what custom shell you use.

    After that learning process and getting familiar, one still can decide to use Fish as the interactive shell. But that’s AFTER the initial learning process of the basics of Linux.


  • Sure. But you need to look at it with context. New users have a hard time to remember how its correctly typed as a command, or it can be easily mistyped on a keyboard and not as fluid. These points do not apply to pharma industry and is just one example. Another point is when you do a websearch and what you get as a result. Its a complex topic on its own with many different points in itself… Just because others have weird and “bad” names, does not mean “we” should do the same. Package managers in an operating system are more than just a brand.

    But as you have a point (in your opinion), I recommend to discuss this in the issue itself with a recommendation of a name, if you have. Or if you like the current (which was actually a placeholder) name. Nothing against opinions, as this is the actual reason why they opened it up.


  • My point is that Fish is not standard Linux tool. If the goal is to learn more about Linux, it makes more sense to learn about Bash first. I’m not against Fish. For a newcomer its just confusing when researching stuff or reading others scripts in Bash and constantly think about the differences in Bash and Fish. Or if you want to share a script with someone who does not have Fish. I’m not saying Fish is bad or anything like that. I’m just saying for a newcomer its not a good idea to ignore Bash and learn Fish first for someone who is interested into learning more about Linux and its eco system. Fish itself has the better language, no doubt about it and is actually better than Bash. But the quality is not my main concern in the reply.


  • I’m curious and tried the AppImage of current development version. Unfortunately it hang in the settings menus with following message, and kind of maxing out my CPU usage and making it a 0.5 fps slideshow. I waited 10 minutes or so and then forcibly killed the process. Clicking the buttons or interacting with anything didn’t do anything. Guess I have to wait until full release. Not sure if this is a problem with the development build or my system:



  • Just type type type type all those commands until remembering them is muscle memory.

    For learning purposes, also try not to use aliases. Because using alias would undermine the learning process of knowing what and how its been done. I recommend (as you said) typing it out over and over again and use aliases on a later stage of your Linux learning only (maybe after weeks at least).


  • Install the fish shell, it makes using the terminal waaay easier, out of the box.

    Not a good idea if the goal is to learn more about Linux. Fish is not compatible to and is different to Bash in some ways, that it would be hard once not using Fish. Also getting help or sharing scripts with others will be problematic, when having a problem and researching it. For someone coming in to Linux and wanting to learn about it, I highly recommend to learn about Bash first and use it at least for months before even thinking about a custom shell. I used Fish too (and I miss some features), so its not like I wouldn’t know what it is.

    Install Alpaca flatpak, and use tinyllama or bigger LLM models.

    Alpaca is nice. GPT4All is also another one (and one that I prefer). Either way, both are good. But again like previous point, I do not recommend to install and use Ai modesl (LLMs) to learn about Linux and to get used to it. Especially the smaller models often hallucinate and lie with false claims. If you don’t know it better and are currently learning, this could be a problem. I highly discourage from installing and learning with an Ai model alongside when you are new to a topic like Linux. Its also not like there wouldn’t be enough good material out there anyway.