Earlier quoted context omitted.
This. Also, one should keep in mind that having to apply personal patches is perfectly acceptable for suckless software. In fact, for the very same st, to change font, colour scheme, or hotkeys/shortcuts - one has to edit config.h file and recompile. There is no traditional text config file or "Preferences" menu. This might sound bizarre at first, but actually works as well as editing a text config file: config.h is…
It is still bizarre because not every user wants to and/or doesn't have the skills to do that.
St – A simple terminal implementation for X
91–100 of 223 posts
Re: St – A simple terminal implementation for X
#92Re: St – A simple terminal implementation for X
#93Earlier quoted context omitted.
I kind of agree. But, how often do you change your settings after you've found the right ones? A minimalist would see runtime configuration as bloat.
Finding the right settings is a relatively slow process. Also, finding the right values for 80% of the settings is fast, but fiddling with the rest can take time. Trying something new also becomes harder. For the vast majority of user-facing programs, run-time configuration is a must. A fancy GUI for it might be superfluous; a simple text file / command-line way to set options should always be available.
Re: St – A simple terminal implementation for X
#94Earlier quoted context omitted.
What do you use now? Keyboard shortcut for font size change is a must for me.
"Keyboard shortcut for font size change is a must for me." From the st man page: Alt-Shift-Page Up Increase font size. Alt-Shift-Page Down Decrease font size. Alt-Shift-Home Reset to default font size.
Re: St – A simple terminal implementation for X
#95Re: St – A simple terminal implementation for X
#96Earlier quoted context omitted.
This. Also, one should keep in mind that having to apply personal patches is perfectly acceptable for suckless software. In fact, for the very same st, to change font, colour scheme, or hotkeys/shortcuts - one has to edit config.h file and recompile. There is no traditional text config file or "Preferences" menu. This might sound bizarre at first, but actually works as well as editing a text config file: config.h is…
It is still bizarre because not every user wants to and/or doesn't have the skills to do that.
But in this case, I would disagree. The file is quite readable (way more than most text config files I've seen), and the single command to compile is even included in the README. If you're the kind of person that purposefully downloads a new terminal, rather than using the built-in one, you can probably configure st just fine.
Re: St – A simple terminal implementation for X
#97Earlier quoted context omitted.
It is still bizarre because not every user wants to and/or doesn't have the skills to do that.
Yes, and that's perfectly ok. These people simply aren't the target audience, just like you wouldn't recommend Arch to a Linux beginner.
Re: St – A simple terminal implementation for X
#98I can't help myself: suckless sucks. Lots of arbitrary limitations for the code, need to recompile instead of configuration, optimizing for a wrong usage scenario.
Re: St – A simple terminal implementation for X
#99Recompiling software to change options is utterly and totally ridiculous
I kind of agree. But, how often do you change your settings after you've found the right ones? A minimalist would see runtime configuration as bloat.
Edit-compile-run is a rather complicated way to tune font size compared to a slider.
And on that note, while I admire ST for its simplicity, I've been a happy user of Sakura for the past few years (though, sadly not on windows 10... I've yet to find a really good console for w10).
https://launchpad.net/sakura (page down at the moment...)
Re: St – A simple terminal implementation for X
#100Why do people care so much about terminal emulators and their supposed "bloat" and "complexity"?