• 1 Post
  • 89 Comments
Joined 2 years ago
cake
Cake day: June 26th, 2023

help-circle
  • bizdelnick@lemmy.mltoLinux@lemmy.mlThe Terminal Question
    link
    fedilink
    arrow-up
    9
    arrow-down
    2
    ·
    3 months ago

    Are you serious? It’s just a window where text is printed. Use what your DE provides. Now I’m mostly on LXQt, so I use QTerminal. With tiling WMs I prefer urxvt because I don’t need builtin window splitting ans tabs. I can’t imagine what other features may I need.






  • bizdelnick@lemmy.mltoLinux@lemmy.ml[Solved] Suggestions for my next distro
    link
    fedilink
    arrow-up
    1
    arrow-down
    5
    ·
    edit-2
    8 months ago

    You won’t get it here. Everybody will recommend his favorite distro.

    IMHO the best would be to solve your problems in OpenSUSE. This is definitely possible. You really need to switch to another distro only if you feel youself uncomfortable with the release cycle, package management tools or packages present in the repo of your current distro.





  • As I see, you’ve already got an answer how to convert text to lower case. So I just tell you how to replace all occurrences of %20 with -. You need to repeat substitution until no matches found. For such iteration you need to use branching to label. Below is sed script with comments.

    :subst                                         # label
    s/(\[[^]]+\]\([^)#]*#[^)]*)%20([^)]*\))/\1-\2/ # replace the first occurrence of `%20` in the URL fragment
    t subst                                        # go to the `subst` label if the substitution took place
    

    However there are some cases when this script will fail, e. g. if there is an escaped ] character in the link text. You cannot avoid such mistakes using only simple regexps, you need a full featured markdown parser for this.




  • There’s one case when you can’t avoid using command line. If you ask someone on Internet to help you, he will say you to type some commands. No window clicking, no screenshots will help. All GUIs are different, but CLI is (almost) always the same, and its output is well searchable. That’s why you see numerous command line listings in each topic discussing problems and could decide it’s impossible to use Linux without coding.


  • In depends on how dumb the user is. If you want to see drive C:\ and don’t want to learn why there’s no such a thing, forget about Linux (and any other OS except the only one you are familiar with). If you are ready to learn new concepts and just don’t want to remember numerous commands, that’s OK, just pick up a distro with advanced DE and graphical admin tools.





  • Glibc preserves backward compatibility, so if you build against the oldest version you want to support, the resulting binary will work with newer ones.

    However that’s definitely not what I recommend to do. Better learn packaging and build native packages for distros you are going to support. OBS can make this a bit easier (if your software is FOSS), but any modern CI will also do the job.