Skip Navigation
Best practices for navigating file structure via terminal?
  • Useful one I find is the z program you can install it with package manager and it's also included with zsh shell. It's basically like a smart cd command. Instead of having to type the entire path for cd, when using z you can just type the destination folder and if it's in your history it will resolve the path by itself.

  • Why tile?
  • You don't really get my point though. I am fully on board with using keybinds and using the mouse as little as possible. I just mean why tile windows at all. I just can't focus on anything other than one window if I need the other program I have a shortcut that brings it forward. I keep my eyes mostly in the same position this way.

    Anyway this is just a matter of workflow that's what it comes down to. I may just have to accept that it's not for me.

  • Why tile?
  • I like having a big window open. What annoys me with tiles is that the center of my screen which is the most natural to look at is now just a intersection of the other screens so I have to move my eyes over it just feels uncomfortable.

  • Why tile?
  • I'm also a web dev and I have a similar workflow where each workspace has its purpose. Except I never tile anything. I do have shortcuts that switch to specific windows but I never tile anything. That way my eyes are always on the center of the screen.

    I very rarely need to tile windows next to eachother. So rarely that I just don't see the point in making it the main feature of my WM/DE.

    Very interesting to read though. Thanks for the thorough example.

  • Why tile?

    I feel like my eyes can only look at one thing at a time. I just have shortcuts to switch between programs.

    Why do you prefer using a tiling WM and how do you use the tiling functionality in your workflow?

    46
    The Perfect Linux Distribution
  • What you're saying is correct but all the things you're describing are not 100% foolproof. Flatpaks are community maintained and can contain misconfigurations.

    Also the sandboxed nature and all these foreign concepts for new users would have a user question why they're not seeing their folders or why their cursor or theme doesn't match their system.

    These systems are great but they're not nearly as polished as Windows and Mac.

    It's great for us but Linux has always struggled with any semblance of full polish. I think you're overestimating the average computer user. Probably Ubuntu based distro's are still as close as we got to an OS for the regular person.

    The introduction of new concept could be mitigated by a proper system of introducing and explaining these to a new user but it's difficult not to overwhelm them with info or keep them engaged and willing to learn.

    TLDR;

    True but it's not that simple

  • why did you switch?
  • Windows is just constantly trying to distract you from work. It's slow, hogs resources, kills my battery.

    After tinkering a lot I have found a workflow that works great for me on Linux and I couldn't have found that with windows.

    To be honest though. To switch to Linux I'd say you'd have a reason. If you don't work a techy job and don't plan on doing so and don't have much interest in it, you'd just have an easier time with windows.

    But let me tell you once you go into Linux with an open mind and willingness to learn, you'll love it.

  • Why can't flatpaks just work

    I usually try to stay out of the whole snap vs flatpak discussion. Although I am just really confused as to why flatpak just does not seem to care about usability. You're trying to create a universal packaging format I would think the point of it is that a user can just install an app and after reviewing permissions it should "just work".

    There are so many issues that yes, have simple solutions, but why are these issues here in the first place.

    These are the issues that I have encountered that annoy me:

    • Themes, cursors being inconsistent (needs to be fixed manually with flatpak --user override
    • IDE's are unusable without extensions

    At least snap provides an option --classic to make the app work. Please explain to me why flatpak just evidently refuses to take this same approach.

    42
    InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)ER
    ErnieBernie10 @lemmy.world
    Posts 2
    Comments 32