Hi Nick,
Nick Dokos nicholas.do...@hp.com writes:
(defun org-force-lazy-text-properties ()
(jit-lock-function 1))
It seems to work at least for small files. There seem to be limits
to how much fontification it does, so if the file is bigger, it might
miss things. The more likely
Hi Nick,
Nick Dokos nicholas.do...@hp.com writes:
Not quite: the file *is* opened in a buffer (the agenda code opens all the
files, I presume with find-file-noselect), but the text properties are
not up to date. It's only when I explicitly visit the buffer
that they get updated.
I updated
Bastien b...@altern.org wrote:
Not quite: the file *is* opened in a buffer (the agenda code opens all the
files, I presume with find-file-noselect), but the text properties are
not up to date. It's only when I explicitly visit the buffer
that they get updated.
I updated the commit
Nick Dokos nicholas.do...@hp.com writes:
Bastien b...@altern.org wrote:
Nick Dokos nicholas.do...@hp.com writes:
to try to reproduce Rainer's problem, when I first construct the agenda,
I get *both* the TODO and the no-heading message: text properties are not
active. If I then visit
Hi,
my agenda shows a line:
No heading for this item in buffer or region.
how should I track down the problematic part of my org files?
Ciao, Gregor
--
-... --- .-. . -.. ..--.. ...-.-
Hi Gregor,
Gregor Zattler telegr...@gmx.net writes:
my agenda shows a line:
No heading for this item in buffer or region.
It means the agenda contains tasks like
* TODO
with no heading.
how should I track down the problematic part of my org files?
You can run this in your Org buffer:
Hi Bastien,
* Bastien b...@altern.org [24. Jan. 2013]:
Gregor Zattler telegr...@gmx.net writes:
my agenda shows a line:
No heading for this item in buffer or region.
It means the agenda contains tasks like
* TODO
with no heading.
how should I track down the problematic part of my
Gregor Zattler telegr...@gmx.net wrote:
When I move the cursor over this lines a message appears in the
echo area:
byte-code: Before first headline at position 64 in buffer org.org [14 times]
The second line of org.org begins at character 64 in the buffer.
It's a timestamp:
Gregor Zattler telegr...@gmx.net wrote:
When I move the cursor over this lines a message appears in the
echo area:
byte-code: Before first headline at position 64 in buffer org.org [14 times]
The second line of org.org begins at character 64 in the buffer.
It's a timestamp:
Gregor Zattler telegr...@gmx.net writes:
#Time-stamp: 2013-01-24 16:30:39 grfz
Till recently this was no problem since it is a comment line.
This is not a comment line, comment lines start with [\t ]*#
(note the space after the #).
--
Bastien
Hi Gregor,
Gregor Zattler telegr...@gmx.net writes:
But alas, the message No heading for this item in buffer or
region. still appears two times in my agenda -- for today.
The attached patch fixes it.
Carsten, was there any special reason for allowing to add
an agenda entry before the first
Bastien b...@altern.org wrote:
Hi Gregor,
Gregor Zattler telegr...@gmx.net writes:
But alas, the message No heading for this item in buffer or
region. still appears two times in my agenda -- for today.
The attached patch fixes it.
Carsten, was there any special reason for allowing
Nick Dokos nicholas.do...@hp.com writes:
to try to reproduce Rainer's problem, when I first construct the agenda,
I get *both* the TODO and the no-heading message: text properties are not
active. If I then visit the file (e.g. RET on the TODO item) and construct
the agenda again, neither the
Bastien b...@altern.org wrote:
Nick Dokos nicholas.do...@hp.com writes:
to try to reproduce Rainer's problem, when I first construct the agenda,
I get *both* the TODO and the no-heading message: text properties are not
active. If I then visit the file (e.g. RET on the TODO item) and
14 matches
Mail list logo
