Melton Low writes:
Thanks Mark & Melton for testing!
> Worked fine with either (setq org-modules nil) or (require 'org-gnus)
> commented out. It stopped working if I comment out both. Hope this
> help.
Ok, then we can conclude that the fontification problems only appear if
org-gnus was loaded
Tassilo,
Yes, I tried it both ways and it works both ways.
Mark
Tassilo Horn wrote:
Mark Elston writes:
Hi Mark!
That did it! Your message didn't have Carsten's message attached so I
don't know what was in it, but you appear to be correct.
Another message Carsten forwarded, where fontif
Tassilo,
Worked fine with either (setq org-modules nil) or (require 'org-gnus)
commented out. It stopped working if I comment out both.
Hope this help.
Mel
On Mon, Sep 7, 2009 at 12:17 PM, Mark Elston wrote:
> Tassilo,
>
> That did it! Your message didn't have Carsten's message attached so I
Mark Elston writes:
Hi Mark!
> That did it! Your message didn't have Carsten's message attached so I
> don't know what was in it, but you appear to be correct.
Another message Carsten forwarded, where fontification problems arose if
some org module was loaded by org's org-modules variable, whi
Tassilo,
That did it! Your message didn't have Carsten's message attached so I
don't know what was in it, but you appear to be correct.
I even commented out the last line (require 'org-gnus) and it still
works.
Mark
Tassilo Horn wrote:
Hi all!
Could you please try another thing (with the gi
Hi all!
Could you please try another thing (with the git version where this bug
occurs):
1. Create a file test.el with these contents:
--8<---cut here---start->8---
(add-to-list 'load-path "~/path/to/org-mode/lisp/") ;; EDIT TO YOUR NEEDS
(setq org-modules nil
Carsten,
Not sure why but now I see the problem on the *other* machine
as well (the one that didn't show the problem before). This
is 6.30d.6.g2066. I haven't updated this machine in the last
few days.
I don't know why I didn't see it before on this machine. Nothing
has changed. Perhaps I di
Melton Low writes:
> I only see it if I reverted org-mode back to 6.30d.
>> Yep problem still there.
Hm, so it seems not to be caused by some external package. I suspected
that maybe the problem occurs only for color-theme users, but it seems
to be something different... :-(
Bye,
Tassilo
__
On Sep 7, 2009, at 6:57 AM, Mark Elston wrote:
Melton Low wrote:
Sorry I made a mistake.
I only see it if I reverted org-mode back to 6.30d. Works fine
with this morning's git pull.
Hmm. Well, as it turns out, so does mine. Whatever the problem *was*
it appears to have gone away now.
Melton Low wrote:
Sorry I made a mistake.
I only see it if I reverted org-mode back to 6.30d. Works fine with
this morning's git pull.
Hmm. Well, as it turns out, so does mine. Whatever the problem *was*
it appears to have gone away now.
Mark
Mel
On Sun, Sep 6, 2009 at 4:32 PM, Melto
Sorry I made a mistake.
I only see it if I reverted org-mode back to 6.30d. Works fine with this
morning's git pull.
Mel
On Sun, Sep 6, 2009 at 4:32 PM, Melton Low wrote:
> Yep problem still there.
> I'm using cvs build of Emacs 23.50.1 on Sept 3rd.
> org-mode build from git pull this morning
Yep problem still there.
I'm using cvs build of Emacs 23.50.1 on Sept 3rd.
org-mode build from git pull this morning
Mac OS X 10.5.8 Intel
On Sun, Sep 6, 2009 at 11:47 AM, Tassilo Horn wrote:
> Scott Otterson writes:
>
> Hi Scott & all others having that problem,
>
> > I also see this problem.
Yep. Still see it.
Mark
Tassilo Horn wrote:
Scott Otterson writes:
Hi Scott & all others having that problem,
I also see this problem. In addition, links are rendered in plain
text instead of being hidden. I'm using emacs 23 on OS X.
This bug is more than strange. Till now, neither Ca
Scott Otterson writes:
Hi Scott & all others having that problem,
> I also see this problem. In addition, links are rendered in plain
> text instead of being hidden. I'm using emacs 23 on OS X.
This bug is more than strange. Till now, neither Carsten nor me was
able to reproduce it, but peop
I had reverted to 6.30c when the problem cropped up.
I too can confirm it is working again. I am using the latest cvs of emacs
from a couple of days ago.
Hope you figure it out.
Mel
On Fri, Sep 4, 2009 at 11:42 PM, Carsten Dominik
wrote:
> Hi everyone,
>
> I am still unable to reproduce this.
On Sat, 5 Sep 2009 07:58:45 +0200
Carsten Dominik wrote:
> For now I have reverted the offending commit.
And I can confirm it works again.
detlef
>
> - Carsten
>
> On Sep 5, 2009, at 7:42 AM, Carsten Dominik wrote:
>
> > Hi everyone,
> >
> > I am still unable to reproduce this. But I am r
For now I have reverted the offending commit.
- Carsten
On Sep 5, 2009, at 7:42 AM, Carsten Dominik wrote:
Hi everyone,
I am still unable to reproduce this. But I am running the latest
cvs emacs.
Two questions:
- if you revert the critical commit, does the problem go away
- if you use t
Hi everyone,
I am still unable to reproduce this. But I am running the latest cvs
emacs.
Two questions:
- if you revert the critical commit, does the problem go away
- if you use the latest Emacs, does the problem go away?
Thanks.
- Carsten
On Sep 4, 2009, at 11:36 PM, Arne wrote:
Mark Elston comcast.net> writes:
>
> Bernt Hansen wrote:
> > William Henney gmail.com> writes:
> >
> >
> > I can reproduce that too
I have the same problem as well, fontification not working upon startup, but
working for subsequent loads within the emacs session. Tried the org-bug-submit
f
Bernt Hansen wrote:
William Henney writes:
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
William Henney writes:
> On Fri, Sep 4, 2009 at 1:33 PM, Bernt Hansen 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
On Fri, Sep 4, 2009 at 1:33 PM, Bernt Hansen 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 b
Melton Low writes:
> 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'
You identify a commit that is bad (probably master) and a commit that is
good (some previous commit) and do something
23 matches
Mail list logo
