From: John Hendy <jw.hendy@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
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 [thread overview]
Message-ID: <CA+M2ft_puFOGBU4ZieiFJbefSFzsTUGd_LdiQzPBAgXxO6tONQ@mail.gmail.com> (raw)
In-Reply-To: <CA+M2ft-=HDK_ZOvhremWRWdeViVr18Ngypmp-9NK+ygWj_JjuQ@mail.gmail.com>
On Mon, May 20, 2013 at 5:15 PM, John Hendy <jw.hendy@gmail.com> 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
next prev parent reply other threads:[~2013-05-20 22:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 22:15 Starting emacs followed directly by org-agenda search and visiting file removes color formatting John Hendy
2013-05-20 22:34 ` John Hendy [this message]
2013-05-20 22:47 ` John Hendy
2013-05-21 7:47 ` Sebastien Vauban
2013-05-21 10:25 ` Bastien
2013-05-22 13:02 ` Rainer Stengele
2013-05-22 15:04 ` Rainer Stengele
2013-05-23 7:55 ` Bastien
2013-05-23 8:19 ` Rainer Stengele
2013-05-23 9:15 ` Sebastien Vauban
2013-05-23 9:42 ` Michael Brand
2013-05-23 10:07 ` Bastien
2013-05-23 10:16 ` Michael Brand
2013-05-23 10:45 ` John Hendy
2013-05-26 21:12 ` Rainer Stengele
2013-05-27 7:00 ` Bastien
2013-06-12 17:54 ` John Hendy
2013-06-12 21:08 ` Bastien
2013-06-21 12:26 ` Rainer Stengele
2013-06-25 15:09 ` John Hendy
2013-06-25 15:43 ` Rainer Stengele
2013-06-25 15:53 ` John Hendy
2013-06-25 15:43 ` Nicolas Richard
2013-06-25 15:52 ` Bastien
2013-06-26 2:01 ` Mike McLean
2013-06-26 2:36 ` Daniel Clemente
2013-06-26 2:42 ` John Hendy
2013-06-26 3:56 ` Daniel Clemente
2013-06-26 9:44 ` Nicolas Richard
2013-06-12 21:45 ` Samuel Wales
2013-07-03 11:12 ` Mike McLean
2013-07-03 13:07 ` Bastien
2013-07-04 20:26 ` Rainer Stengele
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+M2ft_puFOGBU4ZieiFJbefSFzsTUGd_LdiQzPBAgXxO6tONQ@mail.gmail.com \
--to=jw.hendy@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).