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: Path to make desktop.el remember hi-lock-interactive-patterns Date: Tue, 12 May 2009 22:25:26 +0200 Message-ID: References: <59779.130.55.118.19.1242139954.squirrel@webmail.lanl.gov> 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 1242159957 9800 80.91.229.12 (12 May 2009 20:25:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 12 May 2009 20:25:57 +0000 (UTC) Cc: Emacs-Devel To: herring@lanl.gov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue May 12 22:25:47 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 1M3yXi-0001ut-2w for ged-emacs-devel@m.gmane.org; Tue, 12 May 2009 22:25:38 +0200 Original-Received: from localhost ([127.0.0.1]:50170 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M3yXh-0006p1-DI for ged-emacs-devel@m.gmane.org; Tue, 12 May 2009 16:25:37 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M3yXc-0006mI-H9 for emacs-devel@gnu.org; Tue, 12 May 2009 16:25:32 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M3yXY-0006gL-Vv for emacs-devel@gnu.org; Tue, 12 May 2009 16:25:32 -0400 Original-Received: from [199.232.76.173] (port=58578 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M3yXY-0006g0-Jk for emacs-devel@gnu.org; Tue, 12 May 2009 16:25:28 -0400 Original-Received: from mail-bw0-f161.google.com ([209.85.218.161]:38517) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M3yXY-0000gO-85 for emacs-devel@gnu.org; Tue, 12 May 2009 16:25:28 -0400 Original-Received: by bwz5 with SMTP id 5so219933bwz.42 for ; Tue, 12 May 2009 13:25:27 -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=6KVjECJjGvcK/rultYtSAMUHaHEaz6rgrm89XWnovj4=; b=ktNculXLU0EGcob7JJbJMu/Lv7BvvugzeAxqNGgtucGmdiV3KCC/znoMQdD4+TscIM vDszOgD180XT1jsuGbREwRzIsvHBUe/Oa3RQsxQz1CamV5S2H38PFMY1A2yN9/4Oanvm nUM1DwY4s7WCYl6GYbNdsfIm504mUaYFxkqwg= 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=gXXFs9FKApzo5HOW9lhttpvf4riygdF8ic53c4GC44PzaepnJ2TVDlJtXQrqh3txXO S+8dNMtObYw3dMYA9qcTrce8RSa2GMmtXGtnSJ16fuC+Buxx+6mB74ajMirz11MFT1+M ivSLDMOXi7WjniuolNHRAVkgXWbUwwJqirvP4= Original-Received: by 10.223.107.135 with SMTP id b7mr131509fap.30.1242159927098; Tue, 12 May 2009 13:25:27 -0700 (PDT) In-Reply-To: <59779.130.55.118.19.1242139954.squirrel@webmail.lanl.gov> 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:110841 Archived-At: On Tue, May 12, 2009 at 4:52 PM, Davis Herring wrote: >> + =C2=A0 =C2=A0 =C2=A0 =C2=A0;; Hi-lock >> + =C2=A0 =C2=A0 =C2=A0 =C2=A0(when (and (boundp 'hi-lock-interactive-pat= terns) >> + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 hi-lock= -interactive-patterns >> + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 hi-lock= -mode) >> + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(font-lock-add-keywords nil hi-lock-= interactive-patterns t) >> + =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0(font-lock-fontify-buffer)))))) > > It would be cleaner to invoke some function in hi-lock.el rather than > going straight into font-lock. Yes, absolutely. This was more of a reminder of what need to be done. > Moreover, hi-lock-mode already has a > persistence mechanism; why does desktop need to additionally provide one > that lasts only as long as you don't kill the buffer? Doesn't they serve very different situations? I could for example save a desktop file for a special problem I am working on. When that is solved I might delete that desktop file (or at least never use it any more...)