[–] 1 point 9 months ago

There are differences with hardware support. For example my keyboard backlight isn’t supported in all distros equally. From what I know so far, I suspect this has to do with kernel version and desktop environment.

Getting hardware to work that needs proprietary firmware, for example Broadcom wifi and Bluetooth, can involve several steps like adding a new repository, installing packages, and running a program, or two clicks in the UI.

  • source
  • parent
  • context
  • [–] 2 points 9 months ago

    If you spend enough time using the CLI you'll become familiar with it to the point it becomes second nature to you. When I first started using Linux it was intimidating but then again when I started using computers (MSDOS) there wasn't anything else yet I was able to learn. So I forced myself to learn and I'm glad I did.

    I wouldn't use any GUI ever if it wasn't for web content and games.

  • source
  • parent
  • context
  • [–] 2 points 9 months ago

    I've been using the terminal since forever, it has become second nature to me now. The only time I ever load up graphical applications is to load games or browse the web. And honestly it feels slow as hell, not because the UI or system is physically slow but because so many UIs feel like they get in the way.

    Kind of like how Cypher in the matrix says he doesn't even see the code anymore, it's just second nature. It can be hard at first but I rarely make mistakes these days, and when I do, they're usually syntax errors.

  • source
  • parent
  • context
  • [–] 1 point 9 months ago (1 child)

    it is faster, but also has higher mental load, and more more likely you;ll shoot yourself in the foot. if you accidentally delete something via bad command, its gone. In file manager, you an recover file from the bin.

    no. 1 starts with "open file manager", while its commandline counterpart does not start with "open terminal"

    no. 2 is a strawman, you can just select all files, and rename it. the file manager will append the number.

    no. 4 is a dedicated utility that allows you to graphically view and drill down the folders. Example is based off "file manager"...

  • source
  • [–] 2 points 9 months ago

    I mean I would likely use * and call it a day in that scenario or go up a directory and still use mv. Im pretty lazy as rsnc is one I would have to do a quick man before using to remind me. I actually back up mostly with tar over rsync so I don't use it much in civilian life.

  • source
  • parent
  • context
  • [–] 11 points 9 months ago (4 children)

    Command line is always faster than GUI - but only if you know all the commands and parameters.

    Which is why I either spend ages hunting in the GUI, or ask some AI for a quick command without even understanding it.

  • source
  • [–] 8 points 9 months ago (1 child)

    Fullscreen means the entire screen.

    Windowed/Borderless Fullscreen means you can pin other windows above it.

    If you're playing via Proton YMMV because of the various rendering tricks needed to make certain games work, but mostly it should be fine.

  • source
  • [–] 1 point 9 months ago

    it'd make more sense to have a translation layer on top that generates configs for everything from a consistent language. you're never going to get buyin from enough projects to do it directly.

    my system is entirely generated from nix files, 0 handwritten config files. it's json like if you squint, supports comments, but has functions and can be extended to whatever files you need to generate.

    I do think there's alternatives in the area, but I don't think any of them are as complete

  • source
  • parent
  • context
  • [–] 1 point 9 months ago

    ok, I look into DConf. maybe this helps.

    But I get it, that the most projects because of no or not much income, can’t jump onto this to improve their tools. Whereas I think usability is a big big feature for most people. Mostly better a low feature set easy to use instead of a big feature set which are not much people can use.

  • source
  • parent
  • context
  • [–] 2 points 9 months ago

    Is there a compatibility list for Input Remapper?

    Run evtest, a CLI program. In Debian trixie, it's in the evtest package. Choose the device in question. That'll let you see if and what events your keyboard and mouse are emitting when you do stuff. If it's emitting events, I'd expect userspace software to be able to bind to them.

  • source
  • parent
  • context
  • [–] 1 point 9 months ago* (last edited 9 months ago) (2 children)
    [–] [S] 2 points 9 months ago* (1 child)

    As a newbee to Linux (I guess, a lot in EU want to switch to Linux nowadays) it is really hard to learn which config file will how be used for which tool.

    Yep

    Are there any tools around to create config files easier?

    Hmm, I don't know what you mean by 'tools for creating config files'... If you don't want to have to type the syntax of config files manually then there are programs like DConf Editor, which in an ideal world all the system settings would fall under. But the files that I'm talking about are specifically those that haven't been moved to use DConf for whatever reason.

  • source
  • parent
  • context
  • [–] 1 point 9 months ago

    I recently tried out Ironbar because waybar just really annoys me and I was impressed with Ironbars config which was essentially "yeah...use whatever the hell you want."

  • source
  • [–] 3 points 9 months ago (2 children)

    I see and feel what OP does. As a newbee to Linux (I guess, a lot in EU want to switch to Linux nowadays) it is really hard to learn which config file will how be used for which tool. As with the nature of Linux, that it has grown organically since years, plain text has been around since decades.

    Are there any tools around to create config files easier? It is like programming without much knowledge and I guess a lot of "normal" users stick with Windows or Mac because of this.

  • source
  • [–] 5 points 9 months ago* (last edited 9 months ago)

    In abstract, I guess maybe there would be some benefit, but I've been using Linux for decades, and it really hasn't been an issue for me. I've definitely had times where configuring stuff is confusing, but it's not a function of the basic input format not being JSON or XML or TOML or YAML or whatever. I think that the only time that I recall tabs being obnoxious was not with config files, but with Makefiles (they do, in fact, require tabs).

    The majority of software is packaged with an "example" config file, often with comments in place. Traditionally, software will also ship with a section 5 man page for its config files. So, for example:

    $ man 5 fstab
    

    Will describe the format for /etc/fstab.

    EDIT: I think that the biggest hassle I recall was in configuring a sendmail mail server, quite some years back. The issue there wasn't the basic format, but the fact that due to organic growth, even basic configurations were enormous (just to get the sort of common configuration that most users wanted) and required quite a bit of reading through the option documentation. It was common to use a frontend to generate the config files, and a number of subsequent mail servers aimed at having their default, no-configuration-options state being closer to what people wanted, dramatically reducing the number of options that had to be specified.

  • source
  • view more: ‹ prev next ›