I had used tuigreet in my own installation for a while as I waited for qtgreet to fix its packaging issues(actually still not fixed). And to be honest, the TUI really grew on me.
When possible I like to make things look more “pleasing” as much as most people, but there was something about the simplicity of it that seemed well suited to the task. The display/login manager really is something you want out of your face as soon as possible, after all.
Yes, you’re right. ui.py is just calling on the language files, not declaring the text to be printed itself.
I wouldn’t know how. I’m not sure that I would anyway if it wasn’t in the nwg-hello settings itself? I’m apprehensive about going too far when configuring this stuff since I think easy maintenance and reproducibility is going to be key to make sure it all keeps working.
On that note, I’m probably just going to restore the welcome text to the way it was. I think it’s a little tacky but that’s also pretty subjective. Safer to maintain the default setting.
I tried it out a few days ago. I like nwg-hello and will probably use it for my own main install of Hyprland.
I know people are expected to find their own way for Hyprland, but since this is a starter kit, I am not sure if it is good idea to change too many of the default keybinds unless you have a way to surface them for users somewhere/somehow. But it could be that I am just getting easily confused lately due to trying out several different dotfiles in a row.
You know, you’re absolutely right. I’ve been pretty confused myself because of how varied some of the default keymaps have thrown at me and I guess I internalized that as “keybindings are chaos I should just use my own”.
But you’re right I should stick closer to the Hyprland default if I don’t have a good way of alerting the user of the custom keymap. And I don’t think I do.
On a totally unrelated side note, I hate the default keymap. Super+Q is the true killactive keybind. None of this Super+C nonsense.
I agree on the config file, which is also why I finally decided to bring up this keybinding feedback, as knowing how to bring up the terminal is a prerequisite of that. There is always trial and error, but still.
The best solution I have to offer(other than reverting to the Hyprland defaults) would be displaying the high priority keybinds in the Codeberg repo readme.md.
Well again, it’s a bit presumptuous, but there’s always going to a tty and viewing the config file. I’ve been there…it’s not that bad. Though if super+m or super+enter doesn’t open a terminal, you can get a bit pissy
And that DOES assume you’re using the std key for super (been there too).
If you ever put something like this together, let me know.
I think I am done experimenting with different dotfiles for now, not really satisfied with any one solution, so if I decide to continue down the Hyprland route I would personally be interested in starting over completely with something like this.
I’ve decided that I’ll do it. When is less certain. Probably sometime within the next week.
Been using Hyprland+Noctalia since early January and it’s very cozy. I’m a fan. It’s not perfect in the way that maintaining my own dots were, but I’ll trade a little perfection for getting a huge chunk of my time back in return.
I cannot say thank you enough for putting this starter kit together and I hope it gets the attention it deserves!
Trying to learn to manually configure hyprland from scratch with no experience using it has been a pain, but the popular dotfiles had so many packages and custom elements it was hard to learn from them. This is the only one I found that makes hyprland completely usable and is small enough to learn from.
I can’t wait to see what you put together for Noctalia once v5 is released and the time is right. Thanks again for your hard work and sharing it!
Sounds good to me. I don’t believe I have that capability as just a TL3 though. Once I truly finished, I intended to make a new post about it and could have done so then, but maybe I’ll just starting editing the first post instead and keep this around.
Thank you for the feedback. Seeing that it actually performs the function I intended is great to hear. It’s absolutely true that a lot of dotfiles get really elaborate which can make it harder to learn from.
I’m a Noctalia user on my desktop so I’ll have my ear to the grindstone for their v5 rework. Excited to put something together for it.
Thank you for sharing the news. I liked what I saw of Noctalia, so I will probably be waiting for the update before I truly start experimenting again, as my time at home is extremely limited due to work at the moment(the next one to two years).
And thanks for putting the starter kit together in the first place.
