Hi Matt,
I finally committed this. Sorry it took so long and thanks
again for the patch!
Best,
--
Bastien
Hi,
How can I obtain the clocked time for each CLOCK entry in the LOGBOOK
drawer using Org Element? Consider the following Org example:
=== Org sample ===
* DONE Task A
CLOSED: [2017-03-20 Mon 12:21]
:PROPERTIES:
:ESTIMATED: 1.5
:ACTUAL:
:OWNER: foo
:END:
:LOGBOOK:
Hello,
Rasmus writes:
>>> Another danger is that someone writes something like,
>>>
>>> \begin{center}
>>> \begin{table}
>>> ...
>>
>> You can start the regexp with "\\`[ \t]*..."
>
> The point is, that the env. will be center rather than table. So the code
> would detect the wrong
Hello,
Rasmus writes:
> Backend-specific keywords are still an issue. E.g. try this example with
> ox-latex or ox-koma-letter.
>
> #+options: ^:nil
> #+author: 2017_03_23
>
> #+subject: 2017_03_23
> #+title: 2017_03_23
>
> #+subtitle: 2017_03_23
>
> In patch 6cd42b08f9347a8d
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> It would seem that parse doesn't behave correctly when
>> org-export-with-sub-superscripts is turned off via #+options.
>>
>> Example:
>>
>> #+options: ^:nil
>> #+date: a_b
>>
>> * test
>> a_b
>>
>> Exported result with ox-
Hi.
Luke writes:
> Sometimes I would like to see the agenda as it would appear if I
> generated it tomorrow. I know that I can change the date of the agenda
> view using org-agenda-goto-date, but any tasks that are scheduled
> today (or have a deadline set today, or in the past) don't appear in
Sometimes I would like to see the agenda as it would appear if I
generated it tomorrow. I know that I can change the date of the agenda
view using org-agenda-goto-date, but any tasks that are scheduled today
(or have a deadline set today, or in the past) don't appear in the
agenda views for any
Nicolas Goaziou writes:
>> This is a simple suggestion to improve function `org-property-action'.
>> Currently `org-property-action' errors when 'not at a property'. But
>> this is unnecessary AFAICS.
>>
>> Without the restriction one can use the function to control any property
>> inclusive set
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Hello,
Marco Wahl writes:
> This is a simple suggestion to improve function `org-property-action'.
> Currently `org-property-action' errors when 'not at a property'. But
> this is unnecessary AFAICS.
>
> Without the restriction one can use the function to control any property
> inclusive settin
Hello,
Sven Bretfeld writes:
> Ah, ok I see. Thank you for the reply. Is there any easy way to return
> to the old rules?
I don't think so. You can, however, advise `org-indent-line' or set
a different `indent-line-function' in Org buffers.
Regards,
--
Nicolas Goaziou
11 matches
Mail list logo