Just to close the loop here:
Despite multiple reproductions at the time, I can no longer reproduce this.
I'll keep an eye on this function though. Thank you.
On Tue, Jun 14, 2022, at 12:20 AM, Ihor Radchenko wrote:
> "Justin Abrahms" writes:
>
> > All of that is cor
All of that is correct, yes.
On Mon, Jun 13, 2022, at 11:59 PM, Ihor Radchenko wrote:
> "Justin Abrahms" writes:
>
> > I saw this error when opening emacs.org via (counsel-find-file &optional
> > INITIAL-INPUT INITIAL-DIRECTORY)
> >
> > Slightl
2022, at 10:03 PM, Ihor Radchenko wrote:
> "Justin Abrahms" writes:
>
> > I've recently upgraded to emacs 29 w/ native-comp support. I'm
> > consistently getting this error when I load emacs.org and it stops
> > parsing my document, which is a bit pai
https://updates.orgmode.org/ is broken, unfortunately. Not sure how to address
that, but guessing that this email list will know.
-justin
I think you're looking for org-super-agenda[0]. This is how I'm using it
in my own emacs config.
```
(use-package org-super-agenda
:init (setq org-super-agenda-groups
'(
(:priority "A" :name "High priority")
(:auto-property "WAITING_ON" :log t)
I'm happy to take over ob-mscgen and also ob-dot.
I've not got an account on code.org-mode.org, yet. I've emailed Bastien
directly with my preferred username and have sent the requisite copyright
assignment forms to the relevant gnu email.
Let me know if there are other things to take on there.
Thank you so much!
On Sat, Dec 28, 2019, at 12:22 PM, Thomas Fitzsimmons wrote:
> Hi,
>
> Thomas Fitzsimmons writes:
>
> [...]
>
> > Justin confirmed the attached patch fixes the problem for him. Can an
> > Org mode maintainer review it?
>
> I also reported this upstream to the Org maintainer