Missing word on the key sentence ...
On Mon, Jun 14, 2021 at 7:37 PM Bruce D'Arcus wrote:
> The example you are highlighlighting here was why I was earlier
> suggesting for a rule that would allow something like this input:
>
> "A quotation ending with a period." [cite: @hoel-71-whole].
>
> ...
On Mon, Jun 14, 2021 at 7:45 AM Denis Maier wrote:
>
> Below a few examples of what I mean.
>
> WDYT? Am I missing something?
>
> Denis
> ===
> #+cite_export: csl
> #+cite_export: csl
>
Hi Bhavin,
On Mon, 14 Jun 2021 at 15:01, Bhavin Gandhi
wrote:
On Mon, 14 Jun 2021 at 19:10, Gustavo Barros wrote:
The marking of repeated tasks as "done" is currently resulting in
duplicate entries in the "LOGBOOK" drawer, which is not expected. I
don't know exactly when this came to be,
On Mon, 14 Jun 2021 at 19:10, Gustavo Barros wrote:
> The marking of repeated tasks as "done" is currently resulting in
> duplicate entries in the "LOGBOOK" drawer, which is not expected. I
> don't know exactly when this came to be, but it does not happen in the
> current built-in version
Here's the value:
Its value is
((sequence "TODO(t)" "IN_PROGRESS(i)" "|" "DONE(d!)" "POSTPONED(p@)"
"CANCELLED(c@)")
(sequence "TEST(e)" "TESTING(s)" "|" "PASS(p!)" "FAIL(f@)"))
Original value was
((sequence "TODO" "DONE"))
On Mon, Jun 14, 2021 at 1:22 PM Bhavin Gandhi wrote:
> Hello Carlo
Hello Carlo
On Wed, 9 Jun 2021 at 10:42, Carlo Tambuatco wrote:
> When I mark the task as DONE for the day, it logs the task as:
>
> :LOGBOOK:
> - State "DONE" from "TODO" [2021-06-08 Tue 22:20] <-- Repeated
> entry
> - State "DONE" from "TODO" [2021-06-08 Tue 22:20]
>
Uwe Brauer writes:
>
>>> | ob-ipython--dump-error("Traceback (most recent call last):\n File
>>> \"/Users/...")
>
>
>
>> This line seems to be the critical one in the error output. If you can
>> expand out the full error message, it may elucidate what the problem is.
>
> This message drives
Hi All,
The marking of repeated tasks as "done" is currently resulting in
duplicate entries in the "LOGBOOK" drawer, which is not expected. I
don't know exactly when this came to be, but it does not happen in the
current built-in version (9.4.4), while it does in the latest release
(9.4.6).
Samuel,
> I just wanted to put this here in the Literate Programming thread, DistroTube
> just did a video on why Emacs rules, but the following timestamps are pretty
> dang useful for literate programming for still-always learning newbies like
> myself, just wanted to mention them here for
Just one addition: I think it will be perfectly fine if the current
suggestion is added now. I guess adding additional features later will
be always possible, right? I don't know what the plans are for the next
org release, and I don't want this question here to stand in the way.
Denis
Am
Below a few examples of what I mean.
WDYT? Am I missing something?
Denis
===
#+cite_export: csl
#+cite_export: csl
"C:/Users/denis/Zotero/styles/chicago-note-bibliography.csl"
#+bibliography: test.bib
* Original source
"A quotation
Hi Nicolas,
I would understand that the export would take the export settings of the
current heading to control the export of the complete subtree. This would
be the case for the second example, where the scheduled date is (correctly)
placed above the properties drawer.
BUT:
1. The much better
Very neat!
Curious about a design choice: If I understand correctly,
org-critical-edition puts the hidden notes in the description and the
visible annotated text in the target of an org link. This is the reverse
of the out-of-the-box link appearance (description visible, target
hidden if
Tim,, again thanks for your workflow/org-growth, and also for the git
tutorial in your separate reply to S Banya. cheers, Greg
14 matches
Mail list logo
