From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: "Font-lock is limited to text matching" is a myth Date: Tue, 11 Aug 2009 19:19:48 +0200 Message-ID: References: <7b501d5c0908091634ndfba631vd9db6502db301097@mail.gmail.com> <1249942011.29022.15.camel@projectile.siege-engine.com> <1249955428.29022.186.camel@projectile.siege-engine.com> <9c768dc60908102347v57bdf38ara9fe2179f68c07e4@mail.gmail.com> <42D4C5C5-E702-4E30-AB95-A016280F20C7@merrillpress.com> <87r5vipgbs.fsf@catnip.gol.com> <87skfy8htw.fsf@uwakimon.sk.tsukuba.ac.jp> <87prb28ev5.fsf@uwakimon.sk.tsukuba.ac.jp> 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 1250011214 7354 80.91.229.12 (11 Aug 2009 17:20:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 11 Aug 2009 17:20:14 +0000 (UTC) Cc: Miles Bader , emacs-devel@gnu.org To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 11 19:20:08 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Mav13-00080w-Gq for ged-emacs-devel@m.gmane.org; Tue, 11 Aug 2009 19:20:05 +0200 Original-Received: from localhost ([127.0.0.1]:45300 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mav11-0001in-Pq for ged-emacs-devel@m.gmane.org; Tue, 11 Aug 2009 13:20:03 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mav0v-0001h4-B0 for emacs-devel@gnu.org; Tue, 11 Aug 2009 13:19:57 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mav0p-0001e6-UG for emacs-devel@gnu.org; Tue, 11 Aug 2009 13:19:56 -0400 Original-Received: from [199.232.76.173] (port=49710 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mav0p-0001dx-K2 for emacs-devel@gnu.org; Tue, 11 Aug 2009 13:19:51 -0400 Original-Received: from mail-yx0-f172.google.com ([209.85.210.172]:62486) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mav0o-0007F2-AZ; Tue, 11 Aug 2009 13:19:50 -0400 Original-Received: by yxe2 with SMTP id 2so5240173yxe.14 for ; Tue, 11 Aug 2009 10:19:48 -0700 (PDT) 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 :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=im6L06SCRveSurt7RtSlcpdx5s6LvkbdVD/iJ2gqzWg=; b=VchVZiwG+WXz1/WGZ8GELYW6au4kamOebYLJ8Seh418sECzIMWvN7b2if1rPMh7aUJ 5anlUlG9SIxj4MAJfKXmHyPCYrDGqulvaChBfQ/Hj/HCi1Q5JV8cOPPisea6rAS5fZCZ Ve63of8SyxRZGlwv9c3oSINvpUP7zkRr9Kf0Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=hKUwcrVxSdnMkitNSebT237fXyrliSy8ruazPCVCbjlI5MLHusp8Nbda7m8Wxf6J62 JhrY8CZ2qklMOaD7L3p9ygEU4BJQ9WJfm7pmtyKpnE7ReUoFGyyZ03U5OR6D0iv5glTP HfYMcP/NzNvJNUOnoEQVUXA2sh3kHj3Wq84Pw= Original-Received: by 10.100.105.15 with SMTP id d15mr5669038anc.140.1250011188660; Tue, 11 Aug 2009 10:19:48 -0700 (PDT) In-Reply-To: <87prb28ev5.fsf@uwakimon.sk.tsukuba.ac.jp> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:114081 Archived-At: On Tue, Aug 11, 2009 at 7:00 PM, Stephen J. Turnbull wr= ote: > Lennart Borgman writes: > > =C2=A0> I consider this a bug. > > Why? =C2=A0It is the *defining* characteristic of a *text* property that = it > is part of the text, and gets copied with its associated text. I was thinking about the properties set by font-lock. They are dynamic and belong to the context in the buffer they came from. I thought that JIT-lock would be confused. But it looks like that is taken care of now so then I do not see any problems with the current default. Sorry for wasting time.