• 15 Posts
  • 370 Comments
Joined 1 year ago
cake
Cake day: December 28th, 2023

help-circle









  • Debian as a server is fine and probably the best ! However as a daily drive OS I don’t think it’s the best choice.

    I have always seen Debian as server distro and that’s probably what they meant ?

    I have debian as my server distro since the beginning of my Linux journey (NEVER failed me !) However I can’t see how Debian as daily drive is a good idea. Sure they try to catch up with testing repo for those who wan’t a more up to date distro, but it’s seems harder to keep up when something breaks along the way.

    That’s where Arch and derivatives shine, if something goes wrong it’s fixed in a few days.


  • I think what happens to me is that I completely lack discipline about structure and will often decide to re-organize things.

    Haha ! Same boat here !

    One slightly more stable system I’ve had for my own code is to use the Issues tracker as a sort of documentation storage system.

    That’s a very nice tip, thank you ! That’s something I will explore.

    Thanks for sharing. :) I hope you don’t mind me saying this but it’s nice to see commits like “Just a commit test”. I also have these as part of learning git.

    Yeah that’s a bit embarrassing 🫠 ! Was playing around with some script to convert Obsidian markdown links to GitHub flavored markdown. Because a comment is necessary to push the commit I have always no idea what to put in there xDD.

    Sorry I couldn’t help you out more and hope you will find a workflow that works for you ! 👍



  • Is there any specific reason to keep the docs in the wiki section? Vs markdown documents right in the wiki itself?

    I don’t know sorry :/ I do use a document but only because I want more control over the TOC (Table of content), which is a bit strange in the wiki itself, but that’s just personal taste !

    I’m not a Dev so take everything I say with a grain of salt, but what I would do is add a comment in the code to specify the change and link to your documentation file for more details (if needed). That’s probably one of the advantage of having your documentation not in the wiki page.

    This would keep your code page clean while having proper documtation in the same repo ! However, I have never seen any project doing it like that (for a good reason probably?).

    Here is my codeberg documentation repo about anime encoding in av1. It’s probably not what you’re looking for but maybe this can give you any idea or see if this could fit your workflow?


  • I will have forgotten a lot; it might be a different system environment. I need to be able to re-learn everything at a later time. Simple solutions that are widely-compatible, and do not rely on my memory are preferred.

    I don’t know if you have already considered it, but you can use a git repository as documentation tool ! It’s a GitHub flavored markdown syntax though.

    Fork the project, upload it to your own git repo (self-hosted codeberg, codeberg, github… Pick your poison :p) and add your own wiki documentation about your changes in the code.

    The only thing you should keep an eye on is probably the license? But I’m not the right person to discuss about licensing :/


  • Back in the day, that’s what I did ALOT on Windows. Specially because of piracy and my younger me having no idea what he was doing XD !

    Still happens on Linux with EndeavourOS but not for the same reasons ! There are millions times more ways to break stuff on Linux but I always learn Something new during the process.

    Story time:

    Learned the other day that some config files are loaded in a specific order and depending what display manager is installed. That was kinda eye opening to understand cause my system didn’t load .profile when .bash_profile was present and I didn’t understood why ! Thanks Archwiki !




  • N0x0n@lemmy.mltoLinux@lemmy.mlLinux is not your Panacea
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    12 days ago

    While I do agree with the general sentiment to rewire your expectation when switching from Windows -> Linux, I do not agree with the following statement:

    Linux is NOT for you, your personality precludes you from using it.

    Linux is for everyone… Though I do also agree if you’re doing something wrong (and you will…) Don’t cry or reflect your frustration on your OS. If there are 1000 ways to break Windows, there are a million times more ways to break your GNU/Linux OS. But most of the time, you’re a doing something wrong. However, sometimes an upstream update can Bork your system… (Yeah this happens 🤷‍♂️).



  • Is that even possible? I’m already in panic when I remove a package and it’s dependencies with pacman 😅.

    Sure I did replaced Thunar with Nemo, but a few things don’t work exactly how it should, like opening the download directory from Firefox (Known issue BTW) even though all mime-types are correctly set !

    Even switching from Alternative -> Base distro seems like a really difficult task :/