Hi Tim,
> At https://orgmode.org/manual/Export-Settings.html#DOCF124
> and (renumbered to "fn:123") in doc/org-manual.org, a foot-
> note is defined as "DEFINITION NOT FOUND":
Well that certainly looks dodgy!
> The original footnote seems to have been added with commit
> e30aed8f0c62e74633f7a0
Hi Thierry,
Thanks for this! Looking at the change you suggest, do you know why the
(match-string 2) bit might have been added in the first place? I'm just
wondering if there might be some edge-case adversely affected by this ---
hence trading one bug for another :P
--
Timothy
tbanelwebmin wr
Hello all,
I am getting this error message:
org-capture: Capture abort: Unknown template placeholder: "%^G"
when attempting to capture a task using this template:
#+begin_src emacs-lisp
(add-to-list 'org-capture-templates
'("t"
"todo"
entry (fi
Hi,
I'm helping a scholar at my institution with his emacs/org-mode
installation. As he'll would like to have automatic citations I
suggested he should try the new org-cite features, but he does not
really want to run the dev version. Is it already predictable when 9.5
will be released? IIUC,
Hi Timothy
I don't know the intention. But the answer may lie in the comment 4
lines above:
;; Don't overwrite TBLFM, we might use text properties to
;; store stuff.
In this case, the intention would be to keep the original "#+TBLFM:"
instead of inserting a fresh new one.
But we are in the
On 19/07/2021 21:03, Eric S Fraga wrote:
On Friday, 16 Jul 2021 at 12:06, William Denton wrote:
People who write one-sentence-per-line, have you had this problem, and if so how
did you handle it?
If I will be exporting to LaTeX, I do the following:
--8<---cut here---st
Hi Thierry,
tbanelwebmin writes:
> I don't know the intention. But the answer may lie in the comment 4
> lines above:
>;; Don't overwrite TBLFM, we might use text properties to
>;; store stuff.
>
> In this case, the intention would be to keep the original "#+TBLFM:"
> instead of inserti
I have run into a problem in implementing a "select-style" function
for an org-cite-insert-processor.
The WIP code is here:
https://github.com/bdarcus/bibtex-actions/pull/182
It was running correctly yesterday morning, but now it doesn't.
I have two related issues:
1. I think, but am not sure,
Eric S Fraga writes:
> Hello all,
>
> I am getting this error message:
>
> org-capture: Capture abort: Unknown template placeholder: "%^G"
>
> when attempting to capture a task using this template:
>
> #+begin_src emacs-lisp
> (add-to-list 'org-capture-templates
>'("t"
>
On 21/07/2021 17:36, Timothy wrote:
At https://orgmode.org/manual/Export-Settings.html#DOCF124
and (renumbered to "fn:123") in doc/org-manual.org, a foot-
note is defined as "DEFINITION NOT FOUND":
Well that certainly looks dodgy!
The original footnote seems to have been added with commit
e
On Wednesday, 21 Jul 2021 at 21:48, Maxim Nikulin wrote:
> It is at least fragile. HTML export results in separate paragraphs:
Yes, I said "if exporting to LaTeX"... ;-)
> I am unsure, but "#+latex:" probably belongs to "Keywords" that are
> elements, so it should end a paragraph. If such interpr
On Wednesday, 21 Jul 2021 at 11:21, Nick Dokos wrote:
> FWIW, it's working for me. There was a change on July 8 having to do
> with tags completion (using completing-read-multiple),
which kind of supports my suspicion that it has to do with
selectrum. :-(
> I would probably edebug `org-capture-f
Maxim Nikulin writes:
> It seems, the footnote was unintentionally lost in the merge commit with a lot
> of conflicts due to renumbering in both branches:
>
> https://code.orgmode.org/bzg/org-mode/commit/9410fbe0606a53b0582cc175b2cc525d556b23fe#diff-6498bd2213e2e527d904942bb214768a1913776L21749
u figured why not learn edebug *now*.
so I instrument that method, start the capture, tell edebug to go when
it stops in that function, and the capture works. And now it works
whether instrumented or not. Hey hum. A total mystery but at least it
works.
Maybe native compilation has somethin
On 21/07/2021 22:22, Eric S Fraga wrote:
On Wednesday, 21 Jul 2021 at 21:48, Maxim Nikulin wrote:
It is at least fragile. HTML export results in separate paragraphs:
Yes, I said "if exporting to LaTeX"... ;-)
I am unsure, but "#+latex:" probably belongs to "Keywords" that are
elements, so it
On Wed, Jul 21, 2021 at 04:38:58PM +0100, Eric S Fraga wrote:
> u figured why not learn edebug *now*.
>
> so I instrument that method, start the capture, tell edebug to go when
> it stops in that function, and the capture works. And now it works
> whether instrumented or not. Hey hum. A tot
* Reproduction
Call ~org-deadline~ with a warning period like so:
(org-deadline nil "<2021-07-20 Tue -1d>")
;; => DEADLINE: <2021-07-20 Tue>
* Expected
Deadline gets added with the warning period provided.
* Actual
Deadline gets added without the provided warning period.
* Discussion
I'
Ok, Timothy, fair enough
Le 21/07/2021 à 17:07, Timothy a écrit :
> Hi Thierry,
>
> tbanelwebmin writes:
>> I don't know the intention. But the answer may lie in the comment 4
>> lines above:
>>;; Don't overwrite TBLFM, we might use text properties to
>>;; store stuff.
>>
>> In this case,
Hi,
I'm not sure if I'm reading the documentation properly, but my
understnading is that I ought to be able to set export options as subtree
properties, and that if I do so, they should be picked up by export engines
when exporting subtrees. However, that doesn't see to be happening for me,
and f
On Tue, Jul 20, 2021 at 3:32 AM Emmanuel Charpentier <
emm.charpent...@free.fr> wrote:
> Le mardi 20 juillet 2021 à 02:55 -0400, Matt Price a écrit :
>
> Certainly citation of personal communications is common in the fields of
> history and philosophy of science, where it represents an effort to
>
Matt,
Check (info "(org) Export Settings")
and especially, the para near bottom:
When exporting sub-trees, special node properties can override the
above keywords. These properties have an ‘EXPORT_’ prefix. For
example, ‘DATE’ becomes, ‘EXPORT_DATE’ when used for a specific
sub-tree. Except f
arg. thx, Chuck.
On Wed, Jul 21, 2021 at 4:25 PM Berry, Charles
wrote:
> Matt,
>
> Check (info "(org) Export Settings")
>
> and especially, the para near bottom:
>
> When exporting sub-trees, special node properties can override the
> above keywords. These properties have an ‘EXPORT_’ prefix.
Does enough material exist on werg tutorials that document how to get a
repeater operational? That or maybe I don't understand repeaters. Had
the repeater I tried to use worked correctly it would have advanced the
original date by 4 weeks when that date got copied down to another cell.
I selected
BTW, here's the info from the debugger:
Debugger entered--Lisp error: (error "Wrong argument type(s)")
error("Wrong argument type(s)")
org-cite-make-insert-processor(bibtex-actions-org-cite-insert
bibtex-actions-org-cite-select-style)
(org-cite-register-processor 'bibtex-actions-org-cite
:insert (
24 matches
Mail list logo
