Consider the following org file:
--8<---cut here---start->8---
* Orig Task 1
SCHEDULED: <2011-11-19 Sat +1w>
:LOGBOOK:
- Note taken on [2011-11-19 Sat 21:24] \\
foo
CLOCK: [2011-11-18 Fri 20:30]--[2011-11-18 Fri 21:24] => 0:54
CLOCK: [2011-11-19 Sat 20:23]--
* lisp/org-clock.el (org-clock-out-if-current): Fix marker in no buffer error
for task state change in an indirect buffer
org-clock-out-when-current was enhanced in 098cf35 (Clock: Clock out
when done also in indirect buffers, 2009-03-23) to handle indirect
buffers.
This enhancement uses (buffe
Hi Torston
Torsten Anders writes:
> Also, the setting results: silent seems to be ignored.
>
> Best wishes,
> Torsten
>
>
> On 19 Nov 2011, at 15:22, Torsten Anders wrote:
>
>> Dear Martyn Jago, dear all,
>>
>> I just pulled the latest version of Org mode and noticed a few bugs
>> in the Lilyp
Nice. Very interesting and informative. Thanks, Eric.
-- Mike
- Original Message -
> From: Eric Schulte
> To: Michael Hannon
> Cc: Org-Mode List
> Sent: Friday, November 18, 2011 11:39 AM
> Subject: Re: [O] Details of compling and running C++ code from Org-mode?
>
> Hi Michael,
>
I just started using:
http://www.emacswiki.org/cgi-bin/wiki/download/pc-keys.el
Very handy indeed. As far as I can see know, it works okay except in
org-mode. I think this is because of these two lines in org.el:
(define-key org-mode-map [home] 'org-beginning-of-line)
(define-key org
Hi everyone,
I wanted to thank everyone for their helpful suggestions and wanted to
share the best solutions I heard of and found.
One solution is to include a rule in the makefile for every sourcecode file
that that copies it and only updates the copy if something has changed (see
Nick's email b
<> and <<>> are great for ensuring that internal
hyperlinks go to the right place in your org document. The problem with
them, though, is that they clutter up the text, making it less readable.
Attempts to get around this problem cause more problems. For example, to
avoid the clutter, I often en
Holger Hoefling writes:
> Hi Carsten, thanks for the suggestion, but as I agree with Brian. If
> there is more than one source file in the org-file, then the whole
> project would still be recompiled, not just the updated file.To be
> more exact, I actually don't want to compile things, but run R
Sorry for the earlier mail: Send got pressed on a half-cooked mail :-)
Heres a cleanup.
--
Build-tools like scons rethink make's "older timestamp => rebuild"
model. You may want to look at one such.
>From http://www.scons.o
Also, the setting results: silent seems to be ignored.
Best wishes,
Torsten
On 19 Nov 2011, at 15:22, Torsten Anders wrote:
> Dear Martyn Jago, dear all,
>
> I just pulled the latest version of Org mode and noticed a few bugs in the
> Lilypond support of Org babel that have not been there in
Christoph LANGE writes:
> Hi Christian,
>
> 2011-11-18 17:32 Christian Egli:
>> Christoph LANGE writes:
>>> is there any way of estimating effort by week?
>>
>> Have a look at the doc string of org-effort-durations.
>>
>> Documentation:
>> Conversion factor to minutes for an effort modifier.
>
>
Such tools are for example scons is a make alternative that rethinks make's
"older timestamp => rebuild"
>From www.scons.org/architecture/index.html
*(S)Cons decides if a file was out-of-date by using MD5 checksums of the
> contents of files, not timestamps. *
>
SCons also comes to mind because
Dear Martyn Jago, dear all,
I just pulled the latest version of Org mode and noticed a few bugs in the
Lilypond support of Org babel that have not been there in the previous version
(so far I was still using version 7.6).
In general, there seems to be problems in parsing the line that starts
#
Hello,
l...@gnu.org (Ludovic Courtès) writes:
> The LaTeX exporter of Org 7.7 from a recent Emacs snapshot improperly
> interprets sequences with angle brackets in Babel snippets as if they
> were footnote references, as in:
>
> #+BEGIN_src C
> int array[2];
> #+END_src
>
> This leads to
14 matches
Mail list logo
