Re: [dev] [st] wide characters getting cropped
On Wed, Oct 27, 2021 at 09:38:41AM +0200, Hiltjo Posthuma wrote: > Its a longstanding myth st has input latency issues. > The common quoted benchmark is wrong. If we're thinking about the same benchmark then it's also outdated. But regardless I didn't base my decision on that. Sometimes ago (9-10 months) I was testing out a whole bunch of different terminals, some of the worst offenders when it comes to latency was Alacritty and Termite IIRC. ST, in my expereince, has been the 2nd most responsive terminal and quite close to XTerm. But still not as responsive and thus overtime I have switched over to it. It would be interesting to see someone doing a proper benchmark with all latest terminal versions, since I don't have any data to back up what I am saying :) So take it as you may. - NRK
Re: [dev] [st] wide characters getting cropped
The benchmark was done on macOS, if I'm not mistaken
Re: [dev] Whether a css selector applies to given html surf code
> Wrong. I'd argue that the "user experience" in most programs that suck is > worse > than the "user experience" using suckless programs. That's one of the reasons > we > call them like that - "programs that suck" and "suckless programs". > > I believe we already discussed this about four months back. > > > >Addicted to almost all software out > >> there like WhatsApp, Facebook, and many more things, most are never gonna use >> stuff like dwm. And things like Windows would keep them there. I myself >> use dwm, hyperbola OS, but suggesting it to common people wouldn't be >> wise. They'll switch back to Windows, and this time maybe forever. >> > > And? > > This sense of urgency and worry about the size of the userbase seems to be > tied > to "software development" inside (big tech) corporations. They add (or remove) > features to software guided by statistical analysis of the target audience > with > the aim of supporting what is perceived to generate the most profit, not by > the > program's purpose or any other reason. Suckless movement is not a corporation. > It is a gathering of programmers writing software for themselves and others > who > value the principles of simplicity and quality in software. > > If anyone wants to use other software, by all means they should. There's > nothing > wrong with that, but on the other side, that shouldn't influence suckless > programs. > Well, yes, I still hold that viewpoint. For me, targeting maximum people is important. It creates bigger userbase which in turn supports the tools more and creates a culture which becomes difficult to remove. I ask not to be proud that suckless doesn't target profit. Profit is required to survive and suckless depends on other donations. Systems must themselves survive and profits are necessary. Profit is not bad. Harming people by controlling them and overpowering them by unmanageable gigantic software is. I'm repeating myself. I'll stop here. I just ask to keep it a movement but as a movement takes steps to include majority of people, let's do that. Nvm, we'll agree to disagree. Sagar
Re: [dev] [st] wide characters getting cropped
On Wed, Oct 27, 2021 at 03:52:09AM +0600, NRK wrote: > On Tue, Oct 26, 2021 at 07:51:52PM +, Ian Liu Rodrigues wrote: > > I've noticed that in some situations wide characters are being cropped > > on my terminal. The following script, which uses a wide character from > > the "Nerd Font Symbol"[1], shows a test case: > > > > > > echo -e '\e[31m \e[0m c' > > echo -e '\e[31m \e[0mc' > > > > Hi Liu, > > I remember having the same problem in ST, however it works fine now. > Looking at my git log I haven't applied any patches for it and even the > upstream branch works fine for me. > > This might be related to terminfo (5). I won't be delving any deeper > into this as I've moved over to XTerm long ago due to input latency > reasons. You might want to check FAQ provided in the ST repo. > > P.S echo is non-portable. Use printf. > https://wiki.bash-hackers.org/commands/builtin/echo#portability_considerations > > - NRK > Its a longstanding myth st has input latency issues. The common quoted benchmark is wrong. -- Kind regards, Hiltjo
