From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike McLean Subject: Re: Starting emacs followed directly by org-agenda search and visiting file removes color formatting Date: Tue, 25 Jun 2013 22:01:43 -0400 Message-ID: References: <86fvxgkc4c.fsf@somewhere.org> <874ndwfx4z.fsf@bzg.ath.cx> <519CC1CF.3060908@online.de> <519CDE8A.5060604@online.de> <87ip2aw2of.fsf@bzg.ath.cx> <864nduawg2.fsf@somewhere.org> <87ip2ahuwq.fsf@bzg.ath.cx> <51A27AC4.7070702@online.de> <8761y4aoux.fsf@bzg.ath.cx> <874nd3rq8u.fsf@bzg.ath.cx> <8761x2dwlx.fsf@yahoo.fr> <87k3liyyq3.fsf@bzg.ath.cx> Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37836) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Urf3R-0000L4-9k for emacs-orgmode@gnu.org; Tue, 25 Jun 2013 22:01:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Urf3Q-0005Cu-6i for emacs-orgmode@gnu.org; Tue, 25 Jun 2013 22:01:53 -0400 Received: from a-pb-sasl-quonix.pobox.com ([208.72.237.25]:42926 helo=sasl.smtp.pobox.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Urf3Q-0005CH-2j for emacs-orgmode@gnu.org; Tue, 25 Jun 2013 22:01:52 -0400 In-Reply-To: <87k3liyyq3.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: Nicolas Richard , Michael Brand , Rainer Stengele , Org Mode I pulled and tested around 8:00 AM EDT today (because I let myself get = so far behind on commits that I couldn't tell if a fix had been pushed = or not) and the problem still existed at that time. On Jun 25, 2013, at 11:52 AM, Bastien wrote: > Nicolas Richard writes: >=20 >> Meanwhile, John Hendy reported that the issue is resolved for him, so >> maybe I notice the thread too late to be useful, otoh I don't see = which >> commit solved the problem, so maybe luck is involved in his = resolution. >=20 > Well, I'm really curious to see if affected users can confirm it is > solved... I didn't have time to fix it, and I'd be glad Luck did it > for me! >=20 > --=20 > Bastien >=20