From: Lennart Borgman <lennart.borgman@gmail.com>
To: senny <yves.senn@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: indirect-region (make-indirect-buffer) breaks major-mode fontification
Date: Wed, 18 Nov 2009 16:44:47 +0100 [thread overview]
Message-ID: <e01d8a50911180744n6872c881r26174ee27f59f241@mail.gmail.com> (raw)
In-Reply-To: <9be07ac3-7eca-4417-8766-6cf9430ad4a2@l2g2000yqd.googlegroups.com>
On Wed, Nov 18, 2009 at 2:52 PM, senny <yves.senn@gmail.com> wrote:
>> > - When I call (cleanup-buffer => starterkit function to indent,
>> > untabify and trailing whitespace removal)
>> > It takes like 6 seconds to clean the buffer where nxml mode 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/emacs-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.
>
next prev parent reply other threads:[~2009-11-18 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-17 12:43 indirect-region (make-indirect-buffer) breaks major-mode fontification senny
2009-11-17 14:01 ` Lennart Borgman
[not found] ` <mailman.10887.1258466524.2239.help-gnu-emacs@gnu.org>
2009-11-17 14:16 ` senny
2009-11-17 14:20 ` Joost Kremers
2009-11-17 14:40 ` senny
2009-11-17 15:13 ` Lennart Borgman
[not found] ` <ADEECBBC-DEC5-45E1-9A56-C8877DA04F7C@gmail.com>
[not found] ` <e01d8a50911171135g288b67dfk8bcc6d15812a994c@mail.gmail.com>
[not found] ` <453D5202-26FA-4AE5-9AC6-1F4973C42A9B@gmail.com>
2009-11-17 20:28 ` Lennart Borgman
[not found] ` <mailman.10926.1258489768.2239.help-gnu-emacs@gnu.org>
2009-11-18 7:54 ` senny
2009-11-18 13:30 ` Lennart Borgman
[not found] ` <mailman.10965.1258551083.2239.help-gnu-emacs@gnu.org>
2009-11-18 13:52 ` senny
2009-11-18 15:44 ` Lennart Borgman [this message]
2009-11-18 16:38 ` Lennart Borgman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e01d8a50911180744n6872c881r26174ee27f59f241@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=yves.senn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).