Merge branch 'bugfix'
This commit is contained in:
commit
adb3591436
|
@ -750,7 +750,7 @@ following snippet to allow multiple different ID formats in Org files.
|
|||
(and (or (org-uuidgen-p id)
|
||||
(string-match-p "[0-9a-z]\\{12\\}" id))
|
||||
(org-attach-id-uuid-folder-format id)))
|
||||
;; When ID looks like a timestap-based ID. Group by year-month
|
||||
;; When ID looks like a timestamp-based ID. Group by year-month
|
||||
;; folders.
|
||||
(lambda (id)
|
||||
(and (string-match-p "[0-9]\\{8\\}T[0-9]\\{6\\}\.[0-9]\\{6\\}" id)
|
||||
|
@ -5447,9 +5447,9 @@ doing computation.
|
|||
|
||||
There are now three lookup functions:
|
||||
|
||||
- [[doc:org-loopup-first][org-loopup-first]]
|
||||
- [[doc:org-loopup-last][org-loopup-last]]
|
||||
- [[doc:org-loopup-all][org-loopup-all]]
|
||||
- [[doc:org-lookup-first][org-lookup-first]]
|
||||
- [[doc:org-lookup-last][org-lookup-last]]
|
||||
- [[doc:org-lookup-all][org-lookup-all]]
|
||||
|
||||
See [[https://orgmode.org/org.html#Lookup-functions][the manual]] for details.
|
||||
*** Startup keywords
|
||||
|
|
|
@ -7272,18 +7272,18 @@ Each element indicates the latest `org-element--cache-change-tic' when
|
|||
change did not contain gaps.")
|
||||
|
||||
;;;###autoload
|
||||
(defun org-element-cache-reset (&optional all no-persistance)
|
||||
(defun org-element-cache-reset (&optional all no-persistence)
|
||||
"Reset cache in current buffer.
|
||||
When optional argument ALL is non-nil, reset cache in all Org
|
||||
buffers.
|
||||
When optional argument NO-PERSISTANCE is non-nil, do not try to update
|
||||
When optional argument NO-PERSISTENCE is non-nil, do not try to update
|
||||
the cache persistence in the buffer."
|
||||
(interactive "P")
|
||||
(dolist (buffer (if all (buffer-list) (list (current-buffer))))
|
||||
(org-with-base-buffer buffer
|
||||
(when (and org-element-use-cache (derived-mode-p 'org-mode))
|
||||
;; Only persist cache in file buffers.
|
||||
(when (and (buffer-file-name) (not no-persistance))
|
||||
(when (and (buffer-file-name) (not no-persistence))
|
||||
(when (not org-element-cache-persistent)
|
||||
(org-persist-unregister 'org-element--headline-cache (current-buffer))
|
||||
(org-persist-unregister 'org-element--cache (current-buffer)))
|
||||
|
|
|
@ -517,7 +517,7 @@ content of these blocks will still be treated as Org syntax."
|
|||
(defface org-agenda-structure-filter '((t (:inherit (org-warning org-agenda-structure))))
|
||||
"Face used for the current type of task filter in the agenda.
|
||||
It inherits from `org-agenda-structure' so it can adapt to
|
||||
it (e.g. if that is assigned a diffent font height or family)."
|
||||
it (e.g. if that is assigned a different font height or family)."
|
||||
:group 'org-faces)
|
||||
|
||||
(defface org-agenda-date '((t (:inherit org-agenda-structure)))
|
||||
|
|
|
@ -145,7 +145,7 @@
|
|||
|
||||
;; All the folding specs can be specified by symbol representing their
|
||||
;; name. However, this is not always convenient, especially if the
|
||||
;; same spec can be used for fold different syntaxical structures.
|
||||
;; same spec can be used for fold different syntactical structures.
|
||||
;; Any folding spec can be additionally referenced by a symbol listed
|
||||
;; in the spec's `:alias' folding spec property. For example, Org
|
||||
;; mode's `org-fold-outline' folding spec can be referenced as any
|
||||
|
@ -189,9 +189,9 @@
|
|||
;; all the processing related to buffer modifications.
|
||||
|
||||
;; The library also provides a way to unfold the text after some
|
||||
;; destructive changes breaking syntaxical structure of the buffer.
|
||||
;; destructive changes breaking syntactical structure of the buffer.
|
||||
;; For example, Org mode automatically reveals folded drawers when the
|
||||
;; drawer becomes syntaxically incorrect:
|
||||
;; drawer becomes syntactically incorrect:
|
||||
;; ------- before modification -------
|
||||
;; :DRAWER:<begin fold>
|
||||
;; Some folded text inside drawer
|
||||
|
@ -321,7 +321,7 @@ following symbols:
|
|||
functions relying on this package might not be able to unfold the
|
||||
edited text. For example, removed leading stars from a folded
|
||||
headline in Org mode will break visibility cycling since Org mode
|
||||
will not be avare that the following folded text belonged to
|
||||
will not be aware that the following folded text belonged to
|
||||
headline.
|
||||
|
||||
- `ignore-modification-checks': Do not try to detect insertions in the
|
||||
|
|
Loading…
Reference in New Issue