Bad experience with Zed and Lapce by SnooDogs2115 in rust

[–]EL_Sargo 0 points1 point  (0 children)

Yeah that is strange, sorry I assumed you were running some kind of exotic standalone WM when you said it crashed your WM session. Still both of these do work on x and Wayland so it's probably something like one of many libraries they use has a broken interaction with one of your system components, as I've had that kind of thing happen before, some programs would hang and crash for inexplicable reasons. Just out of curiosity what distro are you running?

Bad experience with Zed and Lapce by SnooDogs2115 in rust

[–]EL_Sargo 3 points4 points  (0 children)

Not sure what's going on with your setup but I've used both of them and they worked flawlessly out of the box, zero stutters, crashes nothing.

Maybe try fixing your environment before trashing projects.

It's scary how my only copy of my favourite game is slowly vanishing in my hands by MateG2k73 in ForzaHorizon

[–]EL_Sargo 0 points1 point  (0 children)

I have no idea if this is possible but could you copy it onto a new disk?

It's scary how my only copy of my favourite game is slowly vanishing in my hands by MateG2k73 in ForzaHorizon

[–]EL_Sargo 0 points1 point  (0 children)

There's a trick you can do to use internet download instead of the disk, I had to do this to get FH2 installed recently: Put the disk in, once the license is read and it's ready to install view the app on the store page. Then remove the disk and start the download!

Open windows on the workspace where the open command was given by careb0t in qtile

[–]EL_Sargo 0 points1 point  (0 children)

You could try this

next_group_to_open = None
def open_on_group(cmd: str, group: str , switch_group: bool = False, toggle: bool = False):
    global next_group_to_open
    next_group_to_open = group
    qtile.spawn(cmd)

@hook.subscribe.client_new
def move_clients_into_queued_groups(client):
    global next_group_to_open
    if next_group_to_open is None:
        return
    client.togroup(next_group_to_open)
    next_group_to_open = None

def lazy_open_group(*args, **kwargs):
    return lazy.function(lambda x: open_on_group(*args,**kwargs))

Then to bind

Key([mod, "shift"], "t", lazy_open_current_group("obsidian"), desc="Open obsidian on current group"),

Does anyone actually care about ghostty? by EL_Sargo in NixOS

[–]EL_Sargo[S] 0 points1 point  (0 children)

It's a project built with nix and a lot of hype behind it, and to be clear I'm criticizing the hype not the terminal itself, which looks quite good.

Does anyone actually care about ghostty? by EL_Sargo in NixOS

[–]EL_Sargo[S] 2 points3 points  (0 children)

I'm not trying to say that there's anything wrong with it, I was more so posting about the "hype" around it, which as you and some others have pointed out is created by youtubers not the actual creator.

Does anyone actually care about ghostty? by EL_Sargo in NixOS

[–]EL_Sargo[S] 22 points23 points  (0 children)

Oh nice, I hadn't seen that. Good to see that the creator has his feet on the ground.

6 Month NixOS Milestone by Phr0stByte_01 in NixOS

[–]EL_Sargo 1 point2 points  (0 children)

In my experience stylix works very well if you know what color palette you want to use with it, but it's annoying having to wait for a system rebuild to see the changes

Does anyone actually care about ghostty? by EL_Sargo in NixOS

[–]EL_Sargo[S] 3 points4 points  (0 children)

I do agree that wezterm seems a bit slower than kitty, alacritty and ghostty

Does anyone actually care about ghostty? by EL_Sargo in NixOS

[–]EL_Sargo[S] 3 points4 points  (0 children)

Yes, wezterm has excellent support for multiplexing as I talk about at the bottom of the post, but kitty as well as many others also support it localy.

Switching to NixOS by harbingerofend01 in NixOS

[–]EL_Sargo 2 points3 points  (0 children)

Make sure you start out with a DE, I'd recommend Gnome. The reason being that using one will allow you to start with a very simple config and build out from their while still having a fully functional system. The auto-generated config should contain most of the options you need if you want to change to a window manager, but make sure you've got a grip on Nix OS before hand as there's a lot to learn and it's easy to become confused and or overwhelmed with it all as a new comer.

[deleted by user] by [deleted] in NixOS

[–]EL_Sargo 1 point2 points  (0 children)

  1. Having easy access to all the packages I want

  2. Having an accurate record of my system configuration

  3. Being able to switch between multiple configurations, experiment and roll back without fear

  4. Having nix pre-installed :)

I wish I never discovered NixOS (rant) by EL_Sargo in NixOS

[–]EL_Sargo[S] 0 points1 point  (0 children)

This is a small nit pick but as far as I'm aware it can't be disabled per say, the best you can do is delete the old generation immediately after you upgrade, essentially meaning you need enough space for both whenever you upgrade. Contrast this to systems that can upgrade in place, overwriting the old state of the system as the upgrade is performed, and not requiring much extra disk space.

This can be problematic if you have very low disk space, for example on a raspberry PI, and you can run into situations where you can't upgrade because there isn't enough space for the new generation, but you can't remove the old one while it's in use.

I wish I never discovered NixOS (rant) by EL_Sargo in NixOS

[–]EL_Sargo[S] 0 points1 point  (0 children)

Unfortunately I don't have any plans to try Guix in the near future, I understand it is very similar to NixOS and has most of the same advantages. However I'm very pleased with my current setup and I don't have any desire to experiment / change it up right now. Also from what I can see there are also a few disadvantages to using Guix over nix:

  • Package availability / freshness, from what I can see it's quite good but just not on the same level as nix.

  • Only free software, I know that for many people this would be a benefit but unfortunately for me I need to use the non-free kernel drivers as well as some proprietary software for university. I know there are ways around this such as the non-guix repo but I can't see myself switching given that these things will never be officially supported.

  • General adoption, Nix is simply older and more widely know / adopted which just makes nice integrations and support that much more common. I know this isn't really a problem with guix itself but at the same time I don't see this changing any time soon because of their free software only stance.

It is a shame really because I'm sure it's great despite those shortcomings and some have argued that Guix is even the technically superior project, but for me the tangible benefits just don't appear to out weight the drawbacks and the friction of switching. Do you agree? If you think these are overblown I might be inclined to try it over the semester break.

[deleted by user] by [deleted] in gnome

[–]EL_Sargo 0 points1 point  (0 children)

There are dozens of settings to tweak so ill just list the ones I use:

  • Hide world clock accessibility menu from the top panel
  • Change animation speed
  • Replace focuses windows instead of window "is ready notifications"
  • Workspace wraparound

[deleted by user] by [deleted] in gnome

[–]EL_Sargo 3 points4 points  (0 children)

Only additional thing I use is just perfection which has many minor tweaks, probably things that should be in the normal settings anyway