Version 9.6.27 of package Org has just been released in GNU ELPA. You can now find it in M-x list-packages RET.
Org describes itself as: ============================================ Outline-based notes management and organizer ============================================ More at https://elpa.gnu.org/packages/org.html ## Summary: This is a distribution of Org Mode, a major mode for keeping notes, authoring documents, computational notebooks, literate programming, maintaining to-do lists, planning projects, and more — in a fast and effective plain text system. Check the [Org Mode website] for more. [Org Mode website] <https://orgmode.org> 1 Install Org ═════════════ Org is part of GNU Emacs: you probably don't need to install it. To install a more recent version, please use command: `M-x list-packages', find "org" in the list, click on it, and click "Install" in the popped up window. 2 Join the GNU Project ══════════════════════ Org is part of GNU Emacs and GNU Emacs is part of the GNU Operating System, developed by the GNU Project. ## Recent NEWS: ORG NEWS -- history of user-visible changes. -*- mode: org; coding: utf-8 -*- #+STARTUP: overview #+LINK: doc https://orgmode.org/worg/doc.html#%s #+LINK: msg https://list.orgmode.org/%s/ #+LINK: git https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=%s Copyright (C) 2012-2024 Free Software Foundation, Inc. See the end of the file for license conditions. Please send Org bug reports to mailto:emacs-orgm...@gnu.org. * Version 9.7 (not released yet) ** Important announcements and breaking changes *** Underline syntax now takes priority over subscript when both are applicable Previously, Org mode interpreted =(_text_)= as subscript. Now, the interpretation is changed to underline. =(_text_)= matches both subscript and underline markup. The interpretation is changed to keep consistency with other emphasis like =(*bold*)=. Most of the users should not be affected by this change - it only applies when character immediately preceding =_= is one of =-=, =(=, ='=, and ={=. *** ~org-latex-to-mathml-convert-command~ and ~org-latex-to-html-convert-command~ may need to be adjusted Previously, =%i= placeholders in the ~org-latex-to-mathml-convert-command~ and ~org-latex-to-html-convert-command~ user options were replaced with raw LaTeX fragment text, potentially triggering shell-expansion and incorrect result. Now, the =%i= placeholders are shell-escaped to prevent shell expansion. If you have single or double quotes around =%i= then update customizations and remove quotes. *** Org mode faces are now consistently combined, with markup faces taking precedence over the containing element faces Previously, fontification of inline source blocks, macros, footnotes, target links, timestamps, radio targets, targets, inline export snippets, verbatim code, and COMMENT keyword in headings replaced the containing element fontification. Now, this is changed - the inner markup faces and the containing element faces are combined, with "inner" faces taking precedence; just as for all other markup. *** Built-in HTML, LaTeX, Man, Markdown, ODT, and Texinfo exporters preserve the link protocol during export Previously, some link types where not exported as =protocol:uri= but as bare =uri=. This is now changed. When a link is known by Org mode and does not have a custom ~:export~ parameter (see A.3 Adding Hyperlink Types section of the manual), the link protocol is now not stripped. For example, if one adds a link type =tel=, but does not define ~:export~ parameter : (org-link-set-parameters "tel") =[[tel:12345][John Doe]]= link will be correctly exported to LaTeX as =\href{tel:12345}{John Doe}=, not =\href{12345}{John Doe}=. However, links like =[[elisp:(+ 1 2)]]= will be exported as =\url{elisp:(+ 1 2)}=, which may be somewhat unexpected. *** When ~org-link-file-path-type~ is a function, its argument is now a filename as it is read by ~org-insert-link~; not an absolute path Previously, when ~org-link-file-path-type~ is set to a function, the function argument was the filename from the link expanded via ~expand-file-name~. Now, a bare filename is passed to the function. *** Org export backends can now disable citation processors A new global export option ~:with-cite-processors~, when set to nil, disables citation processors completely. This option is available to export backends via ~:options-alist~ when defining the backend. The backends disabling citation processors must take care about exporting citation objects and =print_bibliography= keywords via transcoders. Users can disable citations processors by customizing new ~org-export-process-citations~ option. *** =ox-org= disables citation processors by default Previously, when exporting to Org, all the citations and =print_bibliography= keywords, were transformed according to the chosen citation processor. This is no loner the case. All the citation-related markup is now exported as is. The previous behavior can be reverted by setting new custom option ~org-org-with-cite-processors~. ... ...
