>FYI: I guess there was a commit to fix a stuttering problem, stuttering for
>which I witnessed no stuttering within st-0.2.1.
>
>$ git bisect bad 0.3
>
>Bisecting: 68 revisions left to test af
> On Sun, Mar 08, 2015 at 05:24:53PM +0100, Markus Teich wrote:
>Roger wrote:
>> Whomever coded these early versions, might be able to very easily locate the
>> slowdown explicitly at this point.
>
>Heyho Roger,
>
>just use `git bisect` to locate the commit responsible for the slowdown.
FYI: I g
> On Sun, Mar 08, 2015 at 05:24:53PM +0100, Markus Teich wrote:
>Roger wrote:
>> Whomever coded these early versions, might be able to very easily locate the
>> slowdown explicitly at this point.
>
>Heyho Roger,
>
>just use `git bisect` to locate the commit responsible for the slowdown.
I've heard
Roger wrote:
> Whomever coded these early versions, might be able to very easily locate the
> slowdown explicitly at this point.
Heyho Roger,
just use `git bisect` to locate the commit responsible for the slowdown.
--Markus
> On Tue, Mar 03, 2015 at 09:10:40PM -0800, Ariel A wrote:
>
>
>On March 3, 2015 5:21:04 PM PST, Roger wrote:
>>ST appears to compile and run fine on 64 bit and 32 bit platorms,
>>except on 32
>>bit (i686/pentium3), typing is extremely slow.
>
>Try adjusting xfps and actionfps. When I had this is
Quoth Roberto E. Vargas Caballero:
> My proposal is to simplify the loop even if st becomes a bit
> slower. What do you think guys?
Sure, make it easier for you (and others) to maintain; that's more
important than speed - I'd rather have stability and solidity... not
to mention, your sanity is v
Hi,
> Changing line 3880, "drawtimeout.tv_set=0" to 1, I'm now able to type the
> sentence "The quick brown fox jumped over the lazy brown dog", and all
> characters appear without much apparent delay, except for the last char "g"
> mysteriously takes up to 1-2 seconds to appear. Key repeat
Changing line 3880, "drawtimeout.tv_set=0" to 1, I'm now able to type the
sentence "The quick brown fox jumped over the lazy brown dog", and all
characters appear without much apparent delay, except for the last char "g"
mysteriously takes up to 1-2 seconds to appear. Key repeat also significa
> On Wed, Mar 04, 2015 at 09:22:59AM +0100, Roberto E. Vargas Caballero wrote:
>
>> Try adjusting xfps and actionfps.
>
>I don't like this manual adjusting. We should rework the main
>loop, and it is something we have said lot of times.
I haven't done the tracing (or heavy math) yet, but changing
> Try adjusting xfps and actionfps.
I don't like this manual adjusting. We should rework the main
loop, and it is something we have said lot of times.
Regards,
On March 3, 2015 5:21:04 PM PST, Roger wrote:
>ST appears to compile and run fine on 64 bit and 32 bit platorms,
>except on 32
>bit (i686/pentium3), typing is extremely slow.
Try adjusting xfps and actionfps. When I had this issue on a 32 bit machine, I
seem to remember changing fps worked.
ST appears to compile and run fine on 64 bit and 32 bit platorms, except on 32
bit (i686/pentium3), typing is extremely slow.
Using strace/ltrace on the latest stable 0.5, I see some hangups on the
"select" call. Using the git version, I now see select substituted with
pselect. The following
12 matches
Mail list logo
