From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: Starting emacs followed directly by org-agenda search and visiting file removes color formatting Date: Mon, 20 May 2013 17:34:10 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:47996) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UeYem-0007oc-BX for emacs-orgmode@gnu.org; Mon, 20 May 2013 18:34:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UeYeh-0005QA-H6 for emacs-orgmode@gnu.org; Mon, 20 May 2013 18:34:16 -0400 Received: from mail-la0-x22c.google.com ([2a00:1450:4010:c03::22c]:39204) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UeYeh-0005PD-8t for emacs-orgmode@gnu.org; Mon, 20 May 2013 18:34:11 -0400 Received: by mail-la0-f44.google.com with SMTP id fr10so6944844lab.3 for ; Mon, 20 May 2013 15:34:10 -0700 (PDT) In-Reply-To: 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: emacs-orgmode On Mon, May 20, 2013 at 5:15 PM, John Hendy wrote: > Sorry for the long title, but that's the summary! I fired up a fresh > Emacs session and used =C-a s search-term RET= to navigate to a > headline in the results by putting the cursor on the line and pressing > RET. > > The file text was all black. > > If I visited the file directly, I had the typical color-coded text for > headlines/keywords. I decided to replicate with a minimal config, and > I was able to. Here's the context of the min config: > > #+begin_min-config > ;; set load paths > ;; set load dirs and global config options > (add-to-list 'load-path "~/.elisp/org.git/lisp/") > (add-to-list 'load-path "~/.elisp/org.git/contrib/lisp") > #+end_min-config > > This was on a work file, and I couldn't initially replicate with a > test file... but it appears it has to do with my header options. > Here's the test file: > > #+begin_src org > #+setupfile: "~/org/aux/setupfile.org" > #+options: <:t num:t author:t creator:nil tags:t toc:nil date:t > #+latex_header: \usepackage{lscape} > #+latex_header: \usepackage{amsmath} > > * Test headline > > Some paragraph just to give me a keyword to search for > > ** Sub headline > > Some more text in the next headline > #+end_src > > My process: > - emacs -Q > - M-x load-file RET ~/path/to/min-config RET > - C-x C-f /path/to/file.org RET > - C-c [ to add to agenda list > - C-x C-k RET to kill buffer > - M-x org-agenda RET s RET text RET > - Navigate to test.org matching line RET > - File looks like attached pic > > I deleted everything but my #+setupfile line and it still does that. > > Without any #+ options at the top of the file, it appears in color. > > > John As a follow up, if I directly visit the file first, it's in color. Then, while still visiting the file, I run org-agenda s search-text RET and navigate to where I want to go. This pops up the agenda panel in place of the file until I select where I want to navigate. At this point, we're still in color after going from agenda to the desired location... *But*, any headlines that weren't already unfolded (and shown in color) remain in black and white. Additionally, if I change any of the headlines that were in color, they change from fontified in color to only black and white. I also have leading stars hidden; after editing a headline they appear as well. Thankfully, behavior seems normal at this point, so it's not like I'm messing up my org file by working on it. It's just a bit jarring since I'm so used to seeing it in color. John