Hi,

In order to compare the 1.18.x server version to 1.20.x I have put together a 
new port xorg-server-1.18 than is just a clone of xorg-server prior to the 
recent update. (So far I am not planning on committing this, it is just to 
allow some quick tests, but if there is significant interest it could be 
considered. I would prefer not to though).

So far all I have done is check the initialisation logs for the two versions. 
Attached. There are some differences, but whether these are just changes in the 
printout level, or something significant, I have no idea… 1.20.x does though 
explicitly mention DOUBLE-BUFFER which 1.18 doesn’t, which might mean 
something...

cheers Chris


Attachment: 1.20.4-org.macports.log.bz2
Description: BZip2 compressed data

Attachment: 1.18.4-org.macports.log.bz2
Description: BZip2 compressed data

> On 3 Apr 2019, at 7:47 am, Christopher Jones <jon...@hep.phy.cam.ac.uk> wrote:
> 
> Hi,
> 
> I see no problems with remote terms, forwarding them through an ssh tunnel 
> works fine and I see no evidence of any slowdowns or schilling issues. What 
> system version, xterm version etc., is the remote machine running ?
> 
> As for local Tcl/Tk, I have no idea, I do not use any of them. You will need 
> though to file tickets etc. with more information if you want any chance of 
> any of them looking into.
> 
> cheers Chris
> 
>> On 3 Apr 2019, at 3:29 am, Ken Preslan <k...@preslan.org> wrote:
>> 
>> The new xterm does indeed make xterms running natively on my Mac run
>> faster than they were yesterday.  However, it does not help the
>> performance regression for remote xterms running over X11/ssh forwarding.
>> Those are still majorly slower than they were last week.  Local and remote
>> Tcl/Tk apps are slower too.  Interestingly, scrolling in the "emacs +x11"
>> port is unaffected and seems just as fast as it was.
>> 
>> Thanks for looking into this.
>> 
>> 
>> On Tue, Apr 02, 2019 at 04:25:38PM +0100, Chris Jones wrote:
>>> Hi,
>>> 
>>> I've just pushed an update to xterm enabling the double buffer option in its
>>> configuration step. Could those affected please update to 344_1 and report
>>> back how that goes.
>>> 
>>> cheers Chris
>>> 
>>> On 02/04/2019 3:29 pm, Ken Cunningham wrote:
>>>> looks like the double buffering is not enabled or functioning and xterm is 
>>>> writing directly into the display buffer rather than into the back buffer 
>>>> and blitting it.
>>>> 
>>>>> On Apr 2, 2019, at 04:28, Michael Dickens <michae...@macports.org> wrote:
>>>>> 
>>>>> This issue started with the prior "xorg-server-devel" bump a while back. 
>>>>> I just moved to iTerm2 for the interim; -very- impressed with that 
>>>>> terminal manager! I still need Xterm for some things though ... sigh ... 
>>>>> - MLD
>>>>> 
>>>>> On Mon, Apr 1, 2019, at 11:37 PM, Ken Cunningham wrote:
>>>>>>> Has anybody else noticed that text scrolling in a xterm is now glacially
>>>>>>> slow since xorg-server was upgraded to @1.20.4_0 over the weekend?
>>>>>>> X11 is really painful to use now.
>>>>>> 
>>>>>> It certainly is. There is something wrong with the screen redrawing in
>>>>>> xterm now, it seems.
>>>>>> 
>>>>>> Ken
>> 
>> -- 
>> Ken Preslan <k...@preslan.org>
>> 
> 

Reply via email to