From: Bernt Hansen <bernt@norang.ca>
To: William Henney <whenney@gmail.com>
Cc: emacs-orgmode@gnu.org, Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Org-mode version 6.30d; Hide stars
Date: Fri, 04 Sep 2009 15:26:35 -0400 [thread overview]
Message-ID: <87bplqh5p0.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: 41c818190909041200t6825b280gd57db397ffd30917@mail.gmail.com
William Henney <whenney@gmail.com> writes:
> On Fri, Sep 4, 2009 at 1:33 PM, Bernt Hansen<bernt@norang.ca> wrote:
>>> When I get a chance later today or this evening, I will try to
>>> identify which git commit the problem started for me.
>>
>> For that you want to use 'git bisect'
>>
>
> I see the same problem - no fontification at all in org mode. I used
> the 'git bisect' method that Bernt suggested and this is the result:
>
> --------------------------------------------------------------
> 79839719bfdf3b199657b22a4592691f6bfbb6db is first bad commit
> commit 79839719bfdf3b199657b22a4592691f6bfbb6db
> Author: Carsten Dominik <carsten.dominik@gmail.com>
> Date: Thu Sep 3 09:11:07 2009 +0200
I can reproduce that too - but it behaves differently for compiled
versus uncompiled files. If I do a make clean removing all the .elc
files then it works (for that commit) - but after make there it no
fontification when the file is originally loaded. The commit before
this one works with and without compiling.
After loading compiled sources and starting a minimal emacs on the
provided test.org I get (Org Fly Ind Font) on the status line indicating
the active modes.
If I C-c C-c on the #+STARTUP: line it changes to (Org Fly Font) and
fontification returns.
GNU Emacs 22.2.1 (i486-pc-linux-gnu, GTK+ Version 2.12.11) of 2008-11-09
on raven, modified by Debian
Org-mode version 6.30trans (release_6.30c.7.g7983)
-Bernt
next prev parent reply other threads:[~2009-09-04 19:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 14:44 Org-mode version 6.30d; Hide stars Melton Low
2009-09-04 15:07 ` Carsten Dominik
2009-09-04 17:05 ` Melton Low
2009-09-04 18:33 ` Bernt Hansen
2009-09-04 19:00 ` William Henney
2009-09-04 19:26 ` Bernt Hansen [this message]
2009-09-04 20:56 ` Mark Elston
2009-09-04 21:36 ` Arne
2009-09-05 5:42 ` Carsten Dominik
2009-09-05 5:58 ` Carsten Dominik
2009-09-05 9:44 ` Detlef Steuer
2009-09-05 14:23 ` Melton Low
[not found] <cmu-lmtpd-24989-1252080523-5@store70m.internal>
2009-09-04 16:26 ` Scott Otterson
2009-09-06 17:47 ` Tassilo Horn
2009-09-06 22:32 ` Melton Low
2009-09-06 22:40 ` Melton Low
2009-09-07 8:35 ` Tassilo Horn
2009-09-07 18:04 ` Tassilo Horn
2009-09-07 18:17 ` Mark Elston
2009-09-07 18:32 ` Tassilo Horn
2009-09-07 21:50 ` Melton Low
2009-09-08 7:47 ` Tassilo Horn
-- strict thread matches above, loose matches on Subject: below --
2009-09-04 5:20 Melton Low
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=87bplqh5p0.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=whenney@gmail.com \
/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).