Subj : Latest sources..
To   : Vitaliy Aksyonov
From : Nicholas Boel
Date : Fri Feb 16 2024 17:26:22

On Fri, 16 Feb 2024 13:10:24 -0700, Vitaliy Aksyonov -> Nicholas Boel wrote:

  NB>> My terminal during that session is already 160 wide, so that's not the
  NB>> issue with the random wrapping of those characters, then.

 VA> So do you have terminal 160 chars wide, but message displayed narrower?

Yes, the message itself was created by a script and was only 78 characters wide to begin with when it was created, and is posted to the message base with 'hpt post'.

I just think that my utf-8 hackery may be moving some of those line drawing characters to the next line when it shouldn't be doing so. Maybe there are some soft CRs in there I should be looking for (I don't know how to spot those)?

  NB>> So am I actually able to specify which commit I would like to go back
  NB>> to with 'git bisect' or should I use 'git checkout'? If checkout is
  NB>> the answer, I won't be able to keep track of good or bad commits any
  NB>> more.

 VA> So how bisect works.
 VA> You start process with git bisect start as you already did.
 VA> First you mark some commit which is good for sure with git bisect good.
 VA> Then mark "bad" commit with git bisect bad. That will be last commit in repo.
 VA> git will checkout commit in the middle of those two for you. Then you build
 VA> it and test. If it's good, run git bisect good, if it's bad, git bisect
 VA> bad. Build it and test again.

That's how I understand it. However, you asked me to roll back to a specific version, and git bisect is not able to do that.

So without going that route, I can say ever since you've started updating Golded I haven't had any display issues, until this latest version. What you seemed to have fixed for Wilfred, did the opposite for me. :)

Regards,
Nick

.... "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
 * Origin: _thePharcyde distribution system (Wisconsin) (1:154/10)

.