From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Starting emacs followed directly by org-agenda search and visiting file removes color formatting
Date: Tue, 21 May 2013 09:47:47 +0200 [thread overview]
Message-ID: <86fvxgkc4c.fsf@somewhere.org> (raw)
In-Reply-To: CA+M2ft-jRFvqP=fpfCmAB-BXnFvEOJ3-VyzO-xeb_sPQK5Zqzw@mail.gmail.com
Hi John,
John Hendy wrote:
> On Mon, May 20, 2013 at 5:15 PM, John Hendy <jw.hendy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 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.
>
> Last bit of input -- when this behavior is displayed, if I C-c C-c on
> my options block at the top of the file, it returns to fontified
> behavior and stays that way (even if meddling with headlines). It
> appears that navigating to a headline with various #+keyword lines is
> not letting Org recognize something. Refreshing the setup seems to
> handles this. This is on:
>
> Org-mode version 8.0.3 (release_8.0.3-139-g419b69 @
> /home/jwhendy/.elisp/org.git/lisp/)
>
> Happy to try anything else or provide more info. For now, I think I've
> made enough noise about this!
>
>> Without any #+ options at the top of the file, it appears in color.
End of last week, after updating Org, I also got lots of fontification
troubles inside Org buffers, but as well in more places (Gnus, in particular).
I restarted Emacs many, many times, used Org in different contexts, and
problems did always appear after some time (a couple of minutes, generally).
I did check out an older version of Org, and all the highlighting problems are
gone.
Currently used version: Org-mode version 8.0.3 (release_8.0.3-114-gab3f45 @
~/Public/Repositories/org-mode/lisp/).
I did not have time yet to bisect the problem, but it _seems_ to be a newly
introduced feature.
Maybe you can try to check out older versions (< 10 days ago), and see whether
you can replicate your problem?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-05-21 7:47 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
2013-05-20 22:47 ` John Hendy
2013-05-21 7:47 ` Sebastien Vauban [this message]
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=86fvxgkc4c.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).