From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.help Subject: Re: indirect-region (make-indirect-buffer) breaks major-mode fontification Date: Wed, 18 Nov 2009 16:44:47 +0100 Message-ID: References: <61136d02-7d49-4b29-82e4-3d970cb55175@m38g2000yqd.googlegroups.com> <453D5202-26FA-4AE5-9AC6-1F4973C42A9B@gmail.com> <58207d59-3528-4ee7-b8a7-b3f2f1f3e14a@r24g2000yqd.googlegroups.com> <9be07ac3-7eca-4417-8766-6cf9430ad4a2@l2g2000yqd.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1258559633 22674 80.91.229.12 (18 Nov 2009 15:53:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 18 Nov 2009 15:53:53 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: senny Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Nov 18 16:53:46 2009 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.50) id 1NAmqn-0004ue-Rb for geh-help-gnu-emacs@m.gmane.org; Wed, 18 Nov 2009 16:53:46 +0100 Original-Received: from localhost ([127.0.0.1]:34682 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NAmqn-0004XU-E3 for geh-help-gnu-emacs@m.gmane.org; Wed, 18 Nov 2009 10:53:45 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NAmqA-0004JV-7t for help-gnu-emacs@gnu.org; Wed, 18 Nov 2009 10:53:06 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NAmq5-0004HQ-7n for help-gnu-emacs@gnu.org; Wed, 18 Nov 2009 10:53:05 -0500 Original-Received: from [199.232.76.173] (port=57591 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NAmq4-0004HC-PM for help-gnu-emacs@gnu.org; Wed, 18 Nov 2009 10:53:00 -0500 Original-Received: from mail-yw0-f194.google.com ([209.85.211.194]:33537) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NAmq4-00070f-9d for help-gnu-emacs@gnu.org; Wed, 18 Nov 2009 10:53:00 -0500 Original-Received: by ywh32 with SMTP id 32so1973191ywh.14 for ; Wed, 18 Nov 2009 07:52:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=kOHqnJ4YSL0rld7Hr54yYtuVkoEydizhVCSG+L8OuuE=; b=p6eLXHHRM4ayKeoFDTS1IGUvcGddSct+6N9/FyYEa3der0DGUybgW4TpKR18IEP+Lt HWGbqT5akCod6LPFuX6wGGHPY3IfW44XID7h2EKGHLGRhk7oMoAPeAeKL4/G+1XUu5Zd EI3RIaNNgQmoVVx4rhjYK4YeS8UcmmUEKAyt0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=G+2KpQEdMBq2lHrssyC1wFVsxAsh5YHqd9Ir0DHUC/R3EU86wj0vcgpcG167bpOVAd lHBJaso4LXuyO5AL9RUsWuOjU7Cikl5KfBWHfYwrKsEvA3Vc3C9GRAkHuYjsOse28vhD wSh27HuHuhw+cVHSrbF4Tsq/bynGR5pxAU0Lw= Original-Received: by 10.101.106.9 with SMTP id i9mr344743anm.128.1258559107200; Wed, 18 Nov 2009 07:45:07 -0800 (PST) In-Reply-To: <9be07ac3-7eca-4417-8766-6cf9430ad4a2@l2g2000yqd.googlegroups.com> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor 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:69878 Archived-At: On Wed, Nov 18, 2009 at 2:52 PM, senny wrote: >> > =C2=A0- When I call (cleanup-buffer =3D> starterkit function to indent= , >> > untabify and trailing whitespace removal) >> > =C2=A0 =C2=A0It takes like 6 seconds to clean the buffer where nxml mo= de takes >> > around half a second. >> >> Is this for the example you sent me? That sounds a bit strange. Can >> you please send me a copy of cleanup-buffer so I can see what it does? I tested this a bit more and found that you are right. It is the indentation that takes so long time - but only when you use a multi major mode that has nxml-mode as its main mode. I do not know what to do about it but I will keep it in mind. (I have one solution in mind right now...) > This discussion is probably not the right place to start a discussion > about nXhtml > features and bugs. You should probably name me a place where we can go > into > detail about the bugs I have with nXhtml mode. Yes, please go to Launchpad, https://bugs.launchpad.net/nxhtml/+bugs (this is mentioned on EmacsWiki and in nXhtml documentation). I am a bit curious about what problems you have found. > To conclude: I am still looking for a fontification fix with the > "indirect" buffer > approach. All the fuzz i just had with one page and nXhtml shows me, > that I am better > served with a quick and dirty solution. I need things to work fast and > work as expected. I have no opinion on that, of course. (I believe you will save time using nXhtml instead, but that is just me.) Using a personal quick and dirty solution is indeed sometimes very useful. > Of course there could be conflicts with nXhtml and my .emacs > configuration (which > has grown fairly large and is available here: http://github.com/senny/ema= cs-configs) > but I don't have the time to dig into nXhtml and figure out how > everything works. It should normally be no problem as long as those things are correct. I looked at cleanup-buffer and that should work perfectly well with nXhtml. The difficult problems I see normally comes from either incorrect code in users startup files or problem with using nxml-mode parser in multi major modes. Since the nxml-mode parser also gives a lot back (completion+validation) I still think it may be useful. (I have turned off the use of nxml-mode parser by default in Emacs 22 because of this.) And of course all my +-1 position type bugs when I write the chunk dividing functions. > Thanks for your assistance and the fast feedback. >