There seems to be a bug in Org mode version 9.4.6, (9.4.6-2-g21eb69-elpa
...),
For example, I have a TODO habit task like so:
TODO Some task
SCHEDULED: <2021-06-08 Tue .+1d>
:PROPERTIES:
:STYLE:habit
:LAST_REPEAT: [2021-06-07 Mon 23:19]
:CATEGORY: Daily Chores
:END:
:LOGBOOK:
- State "DONE"
Hi Nick,
On Tue, Jun 8, 2021 at 11:54 PM Kaushal Modi wrote:
>
> Thanks! I tried out your patch and it does fix the truncation of results
> output. Though, it retains the shell prompt in the first eval block and
> removes it only from the second eval block onwards.
>
I have one more feedback
On Thu, May 6, 2021 at 7:45 PM Nick Savage wrote:
> So I have a patch written that doesn't completely fix the problem, but
> maybe makes enough progress that someone else can figure it out.
>
> The issue is that comint-prompt-regexp is reading the "% " as a prompt,
> and taking everyone off
Nicolas Goaziou writes:
> No, for public links, CUSTOM_ID is the only sane way to handle this.
> Even "sec-2" could betray you if you slightly modify the document.
I understand and agree. However, "sec-2" is strictly better than the
current situation in terms of link stability: There are many
Today I ended up on possibly a related issue with ob-shell results.
Observations:
1. Issue triggered when using :session
2. Output text is OK for the the first shell src block's output. But for
the second block, the output before '>' gets truncated.
Here's a minimal reproducible example:
=
Hi Nicolas,
Since this is a fairly small thing and ox-latex seems to be your domain,
I'm wondering if you've had a chance to take a look yet? (just making
sure this hasn't slipped by, given your recent replies in other threads).
> Hi All,
>
> I've started doing some more cross-referencing in
Hi John,
John Kitchin writes:
> I want to attach all the files in a directory on my desktop to the
> attachment directory, something that is more like
> org-attach-attach-mv-directory (that is not an existing command, but
> what I was thinking of doing). Did I misunderstand what
>
John Kitchin writes:
> Is it possible to attach a directory to an org heading?
>
> I have only seen how to attach a file so far.
I use the code below to attach directories and allow multiple selection
while attaching files. Also, if more people are interested in this kind
of functionality, I
On Tue., Jun. 8, 2021, 5:29 a.m. Nicolas Goaziou,
wrote:
> Hello,
>
> Matt Price writes:
>
> > IIUC, the current architecture assigns responsibility for both *citation
> > export* and *in-buffer actions* to a processor shosen by the user (right
> > now, oc-cite, oc-natbib, or oc-csl).
>
>
On Tue, Jun 8, 2021 at 4:25 PM Nicolas Goaziou
wrote:
> > Still, I'm confused why the basic font-locking doesn't work in this
case.
>
> I know it is not terribly useful but… it works here. For example, if no
> bibliography is defined, all cite keys are red (error face).
Actually that is useful;
I am not sure that is what I meant, it looks like that specifies/changes
the attachment directory for a heading.
I want to attach all the files in a directory on my desktop to the
attachment directory, something that is more like
org-attach-attach-mv-directory (that is not an existing command,
Hello,
"Bruce D'Arcus" writes:
> On Tue, Jun 8, 2021 at 7:36 AM Bruce D'Arcus wrote:
>
>> (org-cite-register-processor 'bibtex
>> :follow #'bibtex-completion-open-any)
>
> Actually, looking at the docstrings, I don't think this will work as
> is, as the follow processor "accepts two
Hello,
Michael Dauer writes:
> There seems to be a bug in Org mode version 9.4.6 (9.4.6-gcf30f7:
> EXPORT_OPTIONS (at least p for with-planning) is only respected if there is
> no planning date placed above the properties drawer.
>
> * TODO export options
> :PROPERTIES:
> :EXPORT_OPTIONS:
Not sure if it counts as off-topic for this thread, but does everyone use Git
to manage their Org docs and notes?
I ask because of Greg's previous post.
I've noticed that some times after git merge events across a few machines (ex:
I forgot I had already pushed notes for my private notes on
Juan Manuel, Eric, Jack, Arne,
thank you all very much for your thoughts.
i've sort of come to grips with Jack's + Arne's, solution, and defined a
"capture template" that adds something to a pre-named headline. (note
and capture are among the org features of which i have maintained to
date a
Brian,
> ** A more generalized system that is based on CWeb is NoWeb--useful
> not just for C/C++ code but for every language: Recommend using NoWeb
> for Literate Programming: "NoWeb — A Simple, Extensible Tool for
> Literate Programming":
thanks. in fact, i also make extensive use of =<>= in
Den tis 8 juni 2021 kl 17:56 skrev John Kitchin :
> Is it possible to attach a directory to an org heading?
>
>
> Yes, you do arg-attach-set-directory. After that you need to sync it to
make the files in the directory visible: org-attach-sync
It's quite neat, I use it all the time.
/Henrik
Is it possible to attach a directory to an org heading?
I have only seen how to attach a file so far.
John
---
Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
Hi,
There seems to be a bug in Org mode version 9.4.6 (9.4.6-gcf30f7:
EXPORT_OPTIONS (at least p for with-planning) is only respected if there is
no planning date placed above the properties drawer.
>>>
* TODO export options
:PROPERTIES:
:EXPORT_OPTIONS: p:nil
:END:
SCHEDULED: <2021-06-08 Di.>
On Tue, Jun 8, 2021 at 7:36 AM Bruce D'Arcus wrote:
> (org-cite-register-processor 'bibtex
> :follow #'bibtex-completion-open-any)
Actually, looking at the docstrings, I don't think this will work as
is, as the follow processor "accepts two arguments, the citation or
citation reference
On Tue, Jun 8, 2021 at 5:33 AM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > So would it be so simple as doing something like this, to use the
> > bibtex-completion-open function instead?
> >
> > (org-cite-register-processor 'basic
> > :follow #'bibtex-completion-open)
>
Hello,
John Kitchin writes:
> This is doable with a hook and advice I think. The hook will hide the
> results if you use :results hide in the header.
>
> I had to use the advice to remove the results before hand, so that you
> toggle the visibility off. This is pretty lightly tested. you could
>
Hello,
Matt Price writes:
> IIUC, the current architecture assigns responsibility for both *citation
> export* and *in-buffer actions* to a processor shosen by the user (right
> now, oc-cite, oc-natbib, or oc-csl).
That's incorrect. The current architecture provides three entry points:
Hello,
"Bruce D'Arcus" writes:
> So would it be so simple as doing something like this, to use the
> bibtex-completion-open function instead?
>
> (org-cite-register-processor 'basic
> :follow #'bibtex-completion-open)
>
> As in, that just tells what function to use for at-point?
>
> If yes,
Samuel,
> Neat stuff, will bookmark this, thanks Greg!
you're welcome. i should mention that i don't recommend the .org files
in my gitlab repositories as exemplars of structure/style. but, they
might give an idea. the .org file related to the ESS video is probably
more manageable.
cheers,
25 matches
Mail list logo
