Where are org-mode issues tracked? What I mean, why I ask:

I'm having a problem with arbitrary text immediately preceding inline markup, which is the best way I can find to express the general problem underlying e.se.com posts like this and this and this. It's a problem I've previously encountered in reST. However,

  • reST has (IMHO) a reasonable, general, and clean solution for the general problem
  • IMHO the several workarounds I've seen offered for this problem in org-mode (see comments to the above questions) are either kludges or don't WFM. (YMMV, and note I'm not here to argue this point--it's just part of the motivation for this question.)

At least one of the comments to the above questions suggested that this might/should be a bug on org-mode, so I thought I'd check. Assuming that Org would track their issues in the same UI with their repository (welcome to the 21st century ?-) I searched for their repos, which are here, and particularly found the org-mode code repo here. It's a Gogs instance, and looks like a "normal" git front-end (e.g., bitbucket, github, gitlab) but ... no bugtracker?

I did some more websearching and I got nothing. So apologies if

  • my websearch was incompetent. I searched but did not find, and am not posting this to LMGTFY.
  • this question should be asked in another SE. Given that org-mode is such a major part of Emacs, I guessed this would be the place to post, but ICBW.

... but I'd like to know, how to view org-mode issues? E.g., in order to see if a bug or feature has already been proposed?

  • 1
    You can send bugs to either the Org mode mailing list (but that provides no help in tracking bug reports) or to the emacs bug tracker debbugs.gnu.org/Emacs.html. See this lists.gnu.org/archive/html/emacs-orgmode/2020-05/msg00443.html and the thread around it for some details. Bottom line: I don't think you are going to be happy with the current state of affairs.
    – NickD
    Feb 22, 2021 at 21:42
  • For the underlying question(s), the best answer is stackoverflow.com/a/24540651/256171
    – NickD
    Feb 22, 2021 at 21:51
  • 1
    In addition to the already mentioned mailing list, there also seems to be a relatively nice web interface to the list of org bugs here, via here.
    – aplaice
    Feb 22, 2021 at 21:56
  • @aplaice: thanks for those pointers! I forgot about that.
    – NickD
    Feb 23, 2021 at 15:00

1 Answer 1


[Note: following still "under construction" and active investigation.]

summary: It's a mess. Org-mode issue management seems to have "grown organically."


Thanks to commenters to my question, and going down their rabbitholes, I might understand--maybe-- how org-mode issues are currently tracked.

TODO: ontological problems: issue vs bug, help request vs (non-existent) 'feature request', 'update' as everything (bugs, help requests, patches, releases), etc.

TODO: post the org-mode list about adding an Issues link to the currently-existing org-mode repo.

to propose a bug (aka, make a bug report)

There are at least 4 ways to do this, all involving email at least indirectly. One can

  1. From within any Emacs buffer, do M-x org-submit-bug-report. This launches a new buffer to gather information to send to the Org mailing list (aka org-ML) @ [email protected].
  2. One can send an email directly to the org-ML. If you wish to do this, please
    • provide useful feedback as described here
    • format and add helpful metadata as described here
  3. From within any Emacs buffer, do M-x report-emacs-bug. This launches a new buffer to gather information to send to the mailing list for Emacs bugs (aka b.g.e-ML) @ [email protected]. Which of course means that one can also ...
  4. ... send an email directly to b.g.e-ML. Before doing that, please

to request a feature (aka, make an FR)

Unfortunately, AFAICS the org-mode tracking system (aka OMTS) ontology seems to lack this type. It does have a type=help request, which seems like a superset (FRs plus requests for assistance), or Something Completely Different. (TODO: investigate.) Given that "requesting help" is discussed here, you probably (and I really am guessing here!) don't want to use b.g.e-ML; instead do one of

  1. M-x org-submit-bug-report (see previous section)
  2. Send email directly to org-ML (see previous section)

Either way, be sure to include the metadata discussed here.

to check status of a bug

current issues (which means "new"? as in not "old"?) feed: https://feed2js.org//feed2js.php?src=https%3A%2F%2Fupdates.orgmode.org%2Ffeed%2Fbugs&chan=y&num=10&utf=y&html=y

RSS feed for new bugs: https://updates.orgmode.org/feed/bugs

TODO: determine difference (if any) between "current issue" and "new bug"

confirmed bugs logged here

old (but still open) issues: see https://orgmode.org/worg/org-issues.html#org43c43fd (TODO: needs stable/mnemonic anchor)

org bugs via Emacs

for completeness: check ML archives (b.g.e-ML and org-ML)

to check status of an FR

1st, note again the lack (IIRC) of a separate FR type.

"help request" gets logged here

for completeness: check ML archives (b.g.e and org)

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.