[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNU ELPA] Org version 9.6.7

From: ELPA update
Subject: [GNU ELPA] Org version 9.6.7
Date: Mon, 26 Jun 2023 17:07:05 -0400

Version 9.6.7 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

## 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] <>

  1 Install Org

    Org is part of GNU Emacs: you probably don't need to install it.

    To install a more recent version, please do it from [GNU ELPA] by
    running this command: `M-x package-install RET org RET'

  [GNU ELPA] <>

  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
#+LINK: msg
#+LINK: git

Copyright (C) 2012-2023 Free Software Foundation, Inc.
See the end of the file for license conditions.

Please send Org bug reports to

* Version 9.7 (not released yet)
** Important announcements and breaking changes
*** ~org-priority=show~ command no longer adjusts for scheduled/deadline

In agenda views, ~org-priority=show~ command previously displayed the
composite rank consisting of the item priority and overdue.  This is
no longer the case.  The displayed and returned value only depends on
the item priority now.

The behavior in Org buffers is unchanged.

*** "Priority" used to sort items in agenda is renamed to "urgency"

Previously, ~priority-up~ and ~priority-down~ in
~org-agenda-sorting-strategy~ used a composite rank depending on
item's priority (=[#A]=, =[#B]=, =[#C]=, etc) and overdue time to
order agenda items (see "11.4.3 Sorting of agenda items" section of
Org manual).

Now, this composite rank is renamed to =urgency= and the relevant
sorting strategies are renamed to ~urgency-up~ and ~urgency-down~.
~priority-up~ and ~priority-down~ sort by item's priority only.

Users relying on the previous composite ranking should adjust their
agenda sorting settings.

*** =python-mode.el (MELPA)= support in =ob-python.el= is removed

=python-mode.el= support has been removed from =ob-python.el=.  The
related customization =org-babel-python-mode= has been changed to a

If you still want to use python-mode with ob-python, you might
[[][ob-python-mode-mode]], where 
the code to support python-mode
has been ported to.

*** =ox-icalendar.el= line ending fix may affect downstream packages

iCalendar export now uses dos-style CRLF ("\r\n") line endings
throughout, as required by the iCalendar specification (RFC 5545).
Previously, the export used an inconsistent mix of dos and unix line

This might cause errors in external packages that parse output from
ox-icalendar.  In particular, older versions of org-caldav may
encounter issues, and users are advised to update to the most recent
version of org-caldav.  See 
 org-caldav commit]] for more information.

*** Icalendar export of unscheduled TODOs no longer have start time of today

For TODOs without a scheduled start time, ox-icalendar no longer
forces them to have a scheduled start time of today when exporting.

Instead, the new customization ~org-icalendar-todo-unscheduled-start~
controls the exported start date for unscheduled tasks.  Its default
is ~recurring-deadline-warning~ which will export unscheduled tasks
with no start date, unless it has a recurring deadline (in which case
the iCalendar spec demands a start date, and
~org-deadline-warning-days~ is used for that).

To revert to the old behavior, set
~org-icalendar-todo-unscheduled-start~ to ~current-datetime~.

*** =org-habit.el= now optionally inherits ~:STYLE: habit~ properties

Currently, the ~STYLE~ property of habits is not inherited when searching
for entries.

This change allows the property to be inherited optionally by customizing
the ~org-use-property-inheritance~ variable.

This change aims to provide more flexibility in managing habits, allowing
users to dedicate separate subtrees or files to habits without manually
setting the ~STYLE~ property for each sub-task.

The change is breaking when ~org-use-property-inheritance~ is set to ~t~.

** New and changed options
*** Commands affected by ~org-fold-catch-invisible-edits~ can now be customized

New user option ~org-fold-catch-invisible-edits-commands~ controls
which commands trigger checking for invisible edits.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]