From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.help Subject: Re: Why is Emacs so slow when used remotely? Date: Wed, 22 Sep 2010 15:25:31 +0200 Organization: Organization?!? Message-ID: <87lj6trjuc.fsf@lola.goethe.zz> References: <76f5ba95-cc68-4326-a962-f515c0fb70cd@y31g2000vbt.googlegroups.com> <3ebca0e6-c698-44dd-a4fd-6166233f5eba@q26g2000vbn.googlegroups.com> <87ocbqsq3g.fsf@puma.rapttech.com.au> <87tylizq1x.fsf@kuiper.lan.informatimago.com> <87d3s6s1y3.fsf@lola.goethe.zz> <874odiylly.fsf@kuiper.lan.informatimago.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1291879012 12956 80.91.229.12 (9 Dec 2010 07:16:52 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 9 Dec 2010 07:16:52 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Thu Dec 09 08:16:48 2010 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PQakA-0000ET-OV for geh-help-gnu-emacs@m.gmane.org; Thu, 09 Dec 2010 08:16:46 +0100 Original-Received: from localhost ([127.0.0.1]:52411 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PQaAo-00044t-Ow for geh-help-gnu-emacs@m.gmane.org; Thu, 09 Dec 2010 01:40:14 -0500 Original-Path: usenet.stanford.edu!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed00.sul.t-online.de!t-online.de!inka.de!rz.uni-karlsruhe.de!news.belwue.de!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail Original-Newsgroups: gnu.emacs.help X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:jnyr5ICQsiiF01nnjvMfnu7NE3k= Original-Lines: 38 Original-NNTP-Posting-Date: 22 Sep 2010 15:25:32 CEST Original-NNTP-Posting-Host: 2b482ce7.newsspool2.arcor-online.net Original-X-Trace: DXC=Z5B]:JJj1X2L2C_`koXfC5A9EHlD; 3Yc24Fo<]lROoR18kF5MOK`al0oR:; C5[U List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:76815 Archived-At: pjb@informatimago.com (Pascal J. Bourguignon) writes: > David Kastrup writes: > >> pjb@informatimago.com (Pascal J. Bourguignon) writes: >> >>> Tim X writes: >>> >>>> A few things to try ... >>>> >>>> 1. turn off tooltip mode >>> >>> Yes. Anything graphic. >>> >>> >>>> 2. Try running with -nw to turn off X and only have a terminal UI >>>> and see what the performance is like. this will let you know if >>>> the problem is basic emacs or the X protocol stuff >>> >>> This is not useful, if you only work with text. The X protocol is >>> not significantly worse than any other terminal protocol to send >>> over text. >> >> Font rendering/antialiasing/composition nowadays happens mostly at >> the client side if I am not mistaken. That makes the X protocol >> much worse even with text. > > That's not what I observe. It's possible for an application to deal > with characters itself and send bitmaps but normally, and it looks > like it's what emacs does, it sends only the strings and the font > rendering is done in the X server. For bitmap fonts. I don't think the X protocol channels antialiased fonts yet. Usually xfs (the font server) runs on the client side of the connection. -- David Kastrup