Re: [tip] Inline tasks as anonymous sections
Juan Manuel Macías writes: > I think that a very efficient way to take advantage of inline tasks (in > the framework of document authoring and exporting) is to treat them as > anonymous sections, that is, those sections that do not have a title and > are normally separated in books by some special symbol: three asterisks > (a dinkus: https://en.wikipedia.org/wiki/Dinkus), an asterism (three > asterisks forming a triangle), or any other fancy symbol. Users can > associate their own export functions with the variables > `org-latex-format-inlinetask-function', Thanks! It is an interesting idea. In Org, I also prefer to display inline tasks using "⇒⇒⇒" instead of all the asterisks. (see the attached screenshot) Best, Ihor
[PATCH] Prevent blocked tasks from being archived
Hi, When org-archive-mark-done is enabled, org silently fails on setting the TODO state of the archived headline to DONE if the task is blocked. This patch changes that behavior so the headline is prevented from being archived in the first place. Instead, org displays a message about why the task is blocked (this message comes from org-todo). Thanks, Ankit >From fea8941ef13fc3e9cab8b0a69675578b2ee1f611 Mon Sep 17 00:00:00 2001 From: Ankit Pandey Date: Mon, 3 Jan 2022 17:41:49 -0800 Subject: [PATCH] org-archive.el: Prevent archiving of blocked tasks * lisp/org-archive.el (org-archive-subtree): Mark the entry as DONE before it's copied to the destination. The original TODO info is still preserved in the context. * lisp/org.el (org-todo): Return t if the entry was changed successfully, and nil if the change failed. --- lisp/org-archive.el | 417 ++-- lisp/org.el | 7 +- 2 files changed, 216 insertions(+), 208 deletions(-) diff --git a/lisp/org-archive.el b/lisp/org-archive.el index 8b4547a64..202e50f99 100644 --- a/lisp/org-archive.el +++ b/lisp/org-archive.el @@ -214,212 +214,217 @@ cursor is not at a headline when these commands are called, try all level 1 trees. If the cursor is on a headline, only try the direct children of this heading." (interactive "P") - (if (and (org-region-active-p) org-loop-over-headlines-in-active-region) - (let ((cl (if (eq org-loop-over-headlines-in-active-region 'start-level) - 'region-start-level 'region)) - org-loop-over-headlines-in-active-region) - (org-map-entries - `(progn (setq org-map-continue-from (progn (org-back-to-heading) (point))) - (org-archive-subtree ,find-done)) - org-loop-over-headlines-in-active-region - cl (if (org-invisible-p) (org-end-of-subtree nil t -(cond - ((equal find-done '(4)) (org-archive-all-done)) - ((equal find-done '(16)) (org-archive-all-old)) - (t - ;; Save all relevant TODO keyword-related variables. - (let* ((tr-org-todo-keywords-1 org-todo-keywords-1) - (tr-org-todo-kwd-alist org-todo-kwd-alist) - (tr-org-done-keywords org-done-keywords) - (tr-org-todo-regexp org-todo-regexp) - (tr-org-todo-line-regexp org-todo-line-regexp) - (tr-org-odd-levels-only org-odd-levels-only) - (this-buffer (current-buffer)) - (time (format-time-string - (substring (cdr org-time-stamp-formats) 1 -1))) - (file (abbreviate-file-name - (or (buffer-file-name (buffer-base-buffer)) - (error "No file associated to buffer" - (location (org-archive--compute-location - (or (org-entry-get nil "ARCHIVE" 'inherit) - org-archive-location))) - (afile (car location)) - (heading (cdr location)) - (infile-p (equal file (abbreviate-file-name (or afile "" - (newfile-p (and (org-string-nw-p afile) - (not (file-exists-p afile - (buffer (cond ((not (org-string-nw-p afile)) this-buffer) - ((find-buffer-visiting afile)) - ((find-file-noselect afile)) - (t (error "Cannot access file \"%s\"" afile - (org-odd-levels-only - (if (local-variable-p 'org-odd-levels-only (current-buffer)) - org-odd-levels-only - tr-org-odd-levels-only)) - level datetree-date datetree-subheading-p - ;; Suppress on-the-fly headline updates. - (org-element--cache-avoid-synchronous-headline-re-parsing t)) - (when (string-match "\\`datetree/\\(\\**\\)" heading) - ;; "datetree/" corresponds to 3 levels of headings. - (let ((nsub (length (match-string 1 heading - (setq heading (concat (make-string - (+ (if org-odd-levels-only 5 3) - (* (org-level-increment) nsub)) - ?*) - (substring heading (match-end 0 - (setq datetree-subheading-p (> nsub 0))) - (setq datetree-date (org-date-to-gregorian - (or (org-entry-get nil "CLOSED" t) time - (if (and (> (length heading) 0) - (string-match "^\\*+" heading)) - (setq level (match-end 0)) - (setq heading nil level 0)) - (save-excursion - (org-back-to-heading t) - ;; Get context information that will be lost by moving the - ;; tree. See `org-archive-save-context-info'. - (let* ((all-tags (org-get-tags)) - (local-tags - (cl-remove-if (lambda (tag) - (get-text-property 0 'inherited tag)) -all-tags)) - (inherited-tags - (cl-remove-if-not (lambda (tag) - (get-text-property 0 'inherited tag)) -all-tags)) - (context - `((category . ,(org-get-category nil 'force-refresh)) - (file . ,file) - (itags . ,(mapconcat #'identity inherited-tags " ")) - (ltags . ,(mapconcat #'identity local-tags " ")) - (olpath . ,(mapconcat #'identity - (org-get-outline-path) - "/")) - (time . ,time) - (todo . ,(org-entry-get (point) "TODO") - ;; We first only copy, in case something goes wrong - ;; we need to protect `this-command', to avoid kill-region sets
Bug: Incorrect indentation in Org Babel list output with multiline text [9.4.4 (release_9.4.4 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]
Hello,
When I use ':results value list' in an emacs-lisp source block it looks
like Babel does
not indent list items correctly when one of the items is a multi-line text.
To reproduce evaluate the following code block:
#+begin_src emacs-lisp :results value list
'("Foo1\nBar1" "Foo2\n\nBar2")
#+end_src
It outputs:
#+RESULTS:
- Foo1
Bar1
- Foo2
Bar2
Expected output:
#+RESULTS:
- Foo1
Bar1
- Foo2
Bar2
Since the second line of the first item is out of indentation, this makes
the output list actually
finish after the first line of the first item. Re-evaluating the block then
only removes the first line
of the previous output.
My Emacs and Org mode version:
Emacs : GNU Emacs 27.2 (build 1, x86_64-apple-darwin20.6.0, Carbon Version
164 AppKit 2022.6)
of 2021-11-16
Package: Org mode version 9.4.4 (release_9.4.4 @
/Applications/Emacs.app/Contents/Resources/lisp/org/)
--
Thanks,
VIkas
Re: Way to mark contents of an Org special block as verbatim?
On Sat, Jan 8, 2022 at 10:01 PM Berry, Charles wrote:
>
>
> A simple one here:
>
> #+begin_src emacs-lisp
> ;; minimal backend with latex parent
> (org-export-define-derived-backend 'newlatex 'latex
> :translate-alist
> '((special-block . org-newlatex-special-block)))
>
> ;; special block transcoder
> (defun org-newlatex-special-block (special-block contents info)
> "Newlatex special block transcoder."
> (let
> ((type (org-element-property :type special-block)))
> (if (equal type "newlatex")
> (format "{{}}\n%s{{}}\n" contents)
I am already doing something like this, but at this point in the code,
the `contents' already is the modified content i.e. Org entities
replaced and _{..} converted to , etc.
Note that ox-hugo exporter is extended from ox-md, which is extended
from ox-html.
My problem statement is that the contents I am receiving is already
modified and I don't get to access the original/raw/verbatim content.
Thanking the original example in this thread:
#+begin_katex
E = -J \sum_{i=1}^N s_i s_{i+1}
#+end_katex
- \sum will have converted to
- _{i=1} will have converted to i=1 by the time I receive
the contents in ox-hugo's org-hugo-special-block.
[ May be I am doing something wrong in my exporter? ]
Or may be it's due to the fact that my eventual base exporter is ox-html?
> ;; not `newlatex` so default to latex transcoder
> (org-export-with-backend 'latex special-block contents info
> #+end_src
>
> Eval the above, then use this as an example by copying the following
> src block to an org buffer and entering
>
> M-; (org-export-to-buffer 'newlatex "*Org NEW LATEX Export*" nil nil nil t)
> RET
>
> #+begin_src org
>
> ,#+begin_newlatex
> This is the new content
> ,#+end_newlatex
>
>
> ,#+attr_latex: :caption \MyCaption{HeadingA}
> ,#+BEGIN_proof
> dot-dot-dot
> ,#+END_proof
>
> #+end_src
>
> I get an *Org NEW LATEX Export* buffer like this:
>
> #+begin_example
> {{}}
> This is the new content
> {{}}
>
>
> \begin{proof}
> dot-dot-dot
> \MyCaption{HeadingA}
> \end{proof}
>
> #+end_example
Re: [BUG] org-persist.el: The commits after "410afd6f374e9" caused org-agenda buffer does not display scheduled and deadline tasks
"Christopher M. Miles" writes: > Here is my reproduce environment: > > Reproduce test with =emacs -Q= > > #+begin_src shell :eval no > emacs -Q -l ~/.config/emacs/minimal-org-init.el ~/org-persist-test.org > #+end_src > > #+begin_src org :tangle "~/org-persist-test.org" > ,* LEARN Clojure Web Development Stack [2/12] > DEADLINE: <2022-01-01 Sat> > :LOGBOOK: > - Removed deadline, was "[2018-12-09 Sun]" on [2019-04-13 Sat 11:14] > - State "LEARN" from [2018-06-01 Fri 09:18] > :END: > > #+end_src Thanks! I am still unable to reproduce. However, I was not able to use your minimal-org-init directly as I do not have ELPA folder. Also, note that your statement (org-babel-do-load-languages 'org-babel-load-languages '((emacs-lisp . t))) may load built-in org I did the following: 1. go to Org mode source directory 2. create bug.el with the following contents (I tried my best to pull important pieces from your minimal init) (custom-set-variables '(org-modules nil)) (setq org-src-fontify-natively t) (org-babel-do-load-languages 'org-babel-load-languages '((emacs-lisp . t))) 3. Run emacs -Q -L ./lisp -l ./bug.el ~/org-persist-test.org 4. M-x org-agenda 5. < a (set restriction to current buffer and run normal weekly agenda) 6. The heading is displayed Can you follow my steps and report what happens? Best, Ihor
Re: [BUG] org-persist.el: The commits after "410afd6f374e9" caused org-agenda buffer does not display scheduled and deadline tasks
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> I git bisected org-mode source code, and found the commits after
>> "410afd6f374e9" caused org-agenda
>> does not display scheduled and deadline tasks. Also affects org-contacts
>> completion get contacts
>> email property.
>>
>> I'm using the latest commit "dc4b2772e".
>>
>> I use bug-hunter extension to test my Emacs config, confirmed problem is NOT
>> on my Emacs config.
>
> Does it mean that you can reproduce using emacs -Q? If so, could you
> provide a recipe to replicate the bug you are seeing?
>
>> the commits after "410afd6f374e9"
>
> Is "410afd6f374e9" a bad commit? That commit had nothing to do with
> agenda or org-persist. The following fbff082f7 is just a version
> update...
>
> Best,
> Ihor
Here is my reproduce environment:
Reproduce test with =emacs -Q=
#+begin_src shell :eval no
emacs -Q -l ~/.config/emacs/minimal-org-init.el ~/org-persist-test.org
#+end_src
#+begin_src org :tangle "~/org-persist-test.org"
,* LEARN Clojure Web Development Stack [2/12]
DEADLINE: <2022-01-01 Sat>
:LOGBOOK:
- Removed deadline, was "[2018-12-09 Sun]" on [2019-04-13 Sat 11:14]
- State "LEARN" from [2018-06-01 Fri 09:18]
:END:
#+end_src
#+begin_src emacs-lisp :tangle "~/.config/emacs/minimal-org-init.el"
;;; minimal-org-init.el --- minimal Org mode init file for testing.
;;; Commentary:
;;; $ emacs -Q -l ~/.config/emacs/minimal-org-init.el
;;; Code:
;;; [ package.el ] -- Emacs Lisp Package Archive (ELPA)
(require 'package)
(setq package-enable-at-startup nil)
(setq package-menu-async t)
(setq package-user-dir (expand-file-name "elpa" user-emacs-directory))
(package-initialize)
;;; Load `use-package' ahead before `package-initialize' for (use-package org
:pin manual ...).
;;; [ use-package ]
(eval-when-compile
(require 'use-package))
(require 'bind-key) ; if you use any `:bind' variant
(use-package delight; if you use `:delight'
:ensure t)
(setq use-package-verbose t ; 'debug: any evaluation errors report to
`*use-package*` buffer.
use-package-always-ensure nil)
;;; [ Org Mode (source code) ]
(if (not (file-exists-p "~/Code/Emacs/org-mode/lisp/"))
(use-package org
:pin org
:ensure t
:ensure org-plus-contrib
:mode (("\\.org\\'" . org-mode))
;; disable all extra org-mode modules to speed-up Org-mode file opening.
:custom (org-modules nil))
;; disable Emacs built-in Org Mode
(delete (format "/usr/local/share/emacs/%s/lisp/org" emacs-version)
load-path)
(delete "/usr/share/emacs/site-lisp/org/" load-path)
(use-package org
:pin manual
:load-path "~/Code/Emacs/org-mode/lisp/"
:defer t
:mode (("\\.org\\'" . org-mode))
;; disable all extra org-mode modules to speed-up Org-mode file opening.
:custom (org-modules nil)
;; load org before org-mode init files settings.
:init (require 'org)
;; add source code version Org-mode Info into Emacs.
(if (file-exists-p "~/Code/Emacs/org-mode/doc/org")
(with-eval-after-load 'info
(add-to-list 'Info-directory-list "~/Code/Emacs/org-mode/doc/")
(info-initialize)))
(use-package org-contrib
:pin manual
:load-path "~/Code/Emacs/org-contrib/lisp/"
:no-require t)))
;;=== helpful packages
==
;;; add your customizations from here
(use-package ace-window
:ensure t
:bind ("C-x C-j" . ace-window))
;;=== minimal config required for
debugging===
(setq org-src-fontify-natively t)
(org-babel-do-load-languages
'org-babel-load-languages
'((emacs-lisp . t)))
(provide 'minimal-org-init)
;;; minimal-org-init.el ends here
#+end_src
--
[ stardiviner ]
I try to make every word tell the meaning that I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
signature.asc
Description: PGP signature
Re: Way to mark contents of an Org special block as verbatim?
> On Jan 8, 2022, at 3:29 PM, Kaushal Modi wrote:
>
>> What am I missing?
>>
>> It seems like you want your derived backend to transcode special blocks
>> somewhat differently than the parent backend. And adding a special block
>> export filter doesn't quite do the job.
>
> I tried out the example Juan posted and it works perfectly well. But
> it would require to user to do something similar for each arbitrary
> new special block they need. E.g. #+being_katex, #+begin_tikz,
> #+begin_tikzjax (could be anything!) where the content needs to be
> kept unmodified.
>
Right, so maybe use `(member type )' rather than
'(equals type "newlatex")' in the3 example below.
>> For that purpose, you should write a special block transcoder - perhaps
>> falling back to the parent backend for block types you do not wish to handle
>> as described above.
>
> Can you please point me to an example?
>
A simple one here:
#+begin_src emacs-lisp
;; minimal backend with latex parent
(org-export-define-derived-backend 'newlatex 'latex
:translate-alist
'((special-block . org-newlatex-special-block)))
;; special block transcoder
(defun org-newlatex-special-block (special-block contents info)
"Newlatex special block transcoder."
(let
((type (org-element-property :type special-block)))
(if (equal type "newlatex")
(format "{{}}\n%s{{}}\n" contents)
;; not `newlatex` so default to latex transcoder
(org-export-with-backend 'latex special-block contents info
#+end_src
Eval the above, then use this as an example by copying the following
src block to an org buffer and entering
M-; (org-export-to-buffer 'newlatex "*Org NEW LATEX Export*" nil nil nil t) RET
#+begin_src org
,#+begin_newlatex
This is the new content
,#+end_newlatex
,#+attr_latex: :caption \MyCaption{HeadingA}
,#+BEGIN_proof
dot-dot-dot
,#+END_proof
#+end_src
I get an *Org NEW LATEX Export* buffer like this:
#+begin_example
{{}}
This is the new content
{{}}
\begin{proof}
dot-dot-dot
\MyCaption{HeadingA}
\end{proof}
#+end_example
>> Block specific customizations could rely on a backend specific attribute.
>
> Yes, I am doing block-specific customization (like support
> #+attr_shortcode above special blocks here[1]). But I don't know how
> to get back the original content of the special block because the
> `contents` arg received by the exporter's org-hugo-special-block
> already has the Org entities, and sub/super replacements done.
>
> [1]:
> https://urldefense.com/v3/__https://github.com/kaushalmodi/ox-hugo/blob/458142675bb5a0e7ee26ecea07d75c10aa52184b/ox-hugo.el*L2872__;Iw!!LLK065n_VXAQ!xZhh--YwGpo06BbAHLF_A2MY_4mk4gBxHgFG3InZakP_7mdFDpyBNMgqvDVvBimzWQ$
>
Re: [BUG] org-persist.el: The commits after "410afd6f374e9" caused org-agenda buffer does not display scheduled and deadline tasks
"Christopher M. Miles" writes: > I git bisected org-mode source code, and found the commits after > "410afd6f374e9" caused org-agenda > does not display scheduled and deadline tasks. Also affects org-contacts > completion get contacts > email property. > > I'm using the latest commit "dc4b2772e". > > I use bug-hunter extension to test my Emacs config, confirmed problem is NOT > on my Emacs config. Does it mean that you can reproduce using emacs -Q? If so, could you provide a recipe to replicate the bug you are seeing? > the commits after "410afd6f374e9" Is "410afd6f374e9" a bad commit? That commit had nothing to do with agenda or org-persist. The following fbff082f7 is just a version update... Best, Ihor
Re: Way to mark contents of an Org special block as verbatim?
> What am I missing? > > It seems like you want your derived backend to transcode special blocks > somewhat differently than the parent backend. And adding a special block > export filter doesn't quite do the job. I tried out the example Juan posted and it works perfectly well. But it would require to user to do something similar for each arbitrary new special block they need. E.g. #+being_katex, #+begin_tikz, #+begin_tikzjax (could be anything!) where the content needs to be kept unmodified. > For that purpose, you should write a special block transcoder - perhaps > falling back to the parent backend for block types you do not wish to handle > as described above. Can you please point me to an example? > Block specific customizations could rely on a backend specific attribute. Yes, I am doing block-specific customization (like support #+attr_shortcode above special blocks here[1]). But I don't know how to get back the original content of the special block because the `contents` arg received by the exporter's org-hugo-special-block already has the Org entities, and sub/super replacements done. [1]: https://github.com/kaushalmodi/ox-hugo/blob/458142675bb5a0e7ee26ecea07d75c10aa52184b/ox-hugo.el#L2872
Re: Way to mark contents of an Org special block as verbatim?
> On Jan 6, 2022, at 11:46 AM, Kaushal Modi wrote:
>
> On Thu, Jan 6, 2022 at 2:33 PM Juan Manuel Macías
> wrote:
>> I just realized that there is a much simpler solution for your katex
>> environment :-)
>>
>> You can use an example block, and define your custom environment using
>> the attribute :environment
>
> Sorry, but this exporter is derived from md, and before exporting the
> verbatim body of the special block needs to be surrounded with some
> special syntax, with some optional stuff that the user specifies. Also
> it could any special block name:
> - katex
> - tikz
> - tikzjax
>
> In any case, if user has this in Org:
>
> #+begin_FOO
>
> #+end_FOO
>
> I need to export:
>
> {{< FOO custom stuff >}}
>
> {{< /FOO >}}
>
>
What am I missing?
It seems like you want your derived backend to transcode special blocks
somewhat differently than the parent backend. And adding a special block export
filter doesn't quite do the job.
For that purpose, you should write a special block transcoder - perhaps falling
back to the parent backend for block types you do not wish to handle as
described above.
Block specific customizations could rely on a backend specific attribute.
HTH,
Chuck
Re: [BUG] Prefer lowercase #+results [9.5.2 (release_9.5.2-3-geb9f34 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]
Rudolf Adamkovič writes: > If I remember well, Org decided to suggest with lowercase keywords (and > use uppercase keywords in the manual, for some reason). Then, we should > change "org-babel-results-keyword" from "RESULTS" to "results". > > (1) Example #1 > > #+begin_src R :results verbatim :wrap example > […] > #+end_src > > #+RESULT: [<--- inconsistent] > #+begin_example > > […] > #+end_example > > (2) Example #2 > > #+begin_src R :results verbatim :wrap EXAMPLE > […] > #+end_src > > > #+RESULT: > > #+begin_EXAMPLE [< still inconsistent] > […] > #+end_EXAMPLE > > P.S. Org should not leak potentially sensitive information, such as > "/Users/salutis/", in the subject of its bug reports. > > Rudy > This is probably a can of worms not worth opening! >From a technical perspective, case does not matter. Originally, the 'styhle' was to use upper case letters for things like #+BEGIN et. al. (which is probably why they are in upper case in the manual). Then (I think it was with the change to the code to insert block markers) there was a change to use #+begin_*. However, I think for those who reverted to the old block insertion method (now based on tempo), you still get things in upper case. The point is, the begin v BEGIN issue is to some extent bordering on becoming a religious argument and one which is unlikely to gain consensus. While personally I agree with your point and for consistency, I think the default should be lower case, it really doesn't matter. Everyone will have their personal preferences and while it is trivial to set to your preferred format, it is one of those issues which will likely generate lots of noise with little resolution.
Re: [BUG] Prefer lowercase #+results [9.5.2 (release_9.5.2-3-geb9f34 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]
Colin Baxter writes: > Change it for yourself. I did. > Please don't change the default. Why? -- "'Contrariwise,' continued Tweedledee, 'if it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic.'" -- Lewis Carroll, Through the Looking Glass Rudolf Adamkovič [he/him] Studenohorská 25 84103 Bratislava Slovakia
[BUG] org-persist.el: The commits after "410afd6f374e9" caused org-agenda buffer does not display scheduled and deadline tasks
I git bisected org-mode source code, and found the commits after "410afd6f374e9" caused org-agenda does not display scheduled and deadline tasks. Also affects org-contacts completion get contacts email property. I'm using the latest commit "dc4b2772e". I use bug-hunter extension to test my Emacs config, confirmed problem is NOT on my Emacs config. -- [ stardiviner ] I try to make every word tell the meaning that I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3 signature.asc Description: PGP signature
Re: ob-plantuml: Proposal to add 'jar-args' customizable variable
On 07-Jan-22 05:38, Ihor Radchenko wrote: Dejan Josifović writes: I has been a little over a month since i posted this to the mailing list, so I'm trying to bump it. Added to todo list. It may take a little while, but I will take a look at it relatively soon. Best, Ihor Thanks Ihor! Mail me if you need more info. Regards, -- Dejan Josifović | Дејан Јосифовић Software engineer | Софтверски инжењер https://theparanoidtimes.org () ascii ribbon campaign /\ www.asciiribbon.org OpenPGP_signature Description: OpenPGP digital signature
Re: [tip] Inline tasks as anonymous sections
On 2022-01-08, at 12:32, Juan Manuel Macías wrote: > Hi, > > I think that a very efficient way to take advantage of inline tasks (in > the framework of document authoring and exporting) is to treat them as > anonymous sections, that is, those sections that do not have a title and > are normally separated in books by some special symbol: three asterisks > (a dinkus: https://en.wikipedia.org/wiki/Dinkus), an asterism (three > asterisks forming a triangle), or any other fancy symbol. Users can > associate their own export functions with the variables > `org-latex-format-inlinetask-function', > `org-odt-format-inlinetask-function', etc. Well, you can always add the > separation symbol directly in your text, but the advantage of using > inline task is that we can conveniently have those sections delimited, > as real sections (with properties, todo states, etc). > > If anyone wants to explore this possibility, I am attaching a test org > document. I have defined two LaTeX commands: \anonsectionbreak and > \anonsectionmark; and the 'anonsection' environment[1]. I don't expect this to be useful for me personally, but I love the idea! Best, -- Marcin Borkowski http://mbork.pl
[tip] Inline tasks as anonymous sections
Hi, I think that a very efficient way to take advantage of inline tasks (in the framework of document authoring and exporting) is to treat them as anonymous sections, that is, those sections that do not have a title and are normally separated in books by some special symbol: three asterisks (a dinkus: https://en.wikipedia.org/wiki/Dinkus), an asterism (three asterisks forming a triangle), or any other fancy symbol. Users can associate their own export functions with the variables `org-latex-format-inlinetask-function', `org-odt-format-inlinetask-function', etc. Well, you can always add the separation symbol directly in your text, but the advantage of using inline task is that we can conveniently have those sections delimited, as real sections (with properties, todo states, etc). If anyone wants to explore this possibility, I am attaching a test org document. I have defined two LaTeX commands: \anonsectionbreak and \anonsectionmark; and the 'anonsection' environment[1]. [1] The Memoir class includes code for these types of divisions (see section 6.7 FANCY ANONYMOUS BREAKS in Memoir documentation). Best regards, Juan Manuel anon-sec-test.org Description: Lotus Organizer
Re: Feedback on Emacs-Jupyter
Hi, I submitted an issue regarding connection file format incompatibility. Other than that I'm looking forward trying your package! -- Daniel Fleischer
Re: [BUG] Prefer lowercase #+results [9.5.2 (release_9.5.2-3-geb9f34 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]
> Rudolf Adamkovič writes: > If I remember well, Org decided to suggest with lowercase keywords > (and use uppercase keywords in the manual, for some reason). > Then, we should change "org-babel-results-keyword" from "RESULTS" > to "results". Change it for yourself. Please don't change the default.
[BUG] Prefer lowercase #+results [9.5.2 (release_9.5.2-3-geb9f34 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]
If I remember well, Org decided to suggest with lowercase keywords (and
use uppercase keywords in the manual, for some reason). Then, we should
change "org-babel-results-keyword" from "RESULTS" to "results".
(1) Example #1
#+begin_src R :results verbatim :wrap example
[…]
#+end_src
#+RESULT: [<--- inconsistent]
#+begin_example
[…]
#+end_example
(2) Example #2
#+begin_src R :results verbatim :wrap EXAMPLE
[…]
#+end_src
#+RESULT:
#+begin_EXAMPLE [< still inconsistent]
[…]
#+end_EXAMPLE
P.S. Org should not leak potentially sensitive information, such as
"/Users/salutis/", in the subject of its bug reports.
Rudy
Emacs : GNU Emacs 29.0.50 (build 8, x86_64-apple-darwin21.2.0, NS
appkit-2113.20 Version 12.1 (Build 21C52))
of 2022-01-02
Package: Org mode version 9.5.2 (release_9.5.2-3-geb9f34 @
/Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)
current state:
==
(setq
org-pomodoro-format "t₋%s"
org-link-elisp-confirm-function 'yes-or-no-p
org-agenda-skip-deadline-prewarning-if-scheduled t
org-cite-insert-processor 'citar
org-pomodoro-time-format "%mm"
org-bibtex-headline-format-function #[257 "\300.\236A\207" [:title] 3 "\n\n(fn
ENTRY)"]
org-agenda-scheduled-leaders '("Scheduled: " "Scheduled %d×: ")
org-pomodoro-long-break-sound "~/beeping.mp3"
org-agenda-custom-commands '(("a" "Agenda"
((stuck ""
((org-agenda-overriding-header
"Stuck projects and actions")
(org-agenda-files '("~/gtd/next-actions.org"))
(org-agenda-prefix-format "* "))
)
(todo "TODO"
((org-agenda-overriding-header "\nNext
actions")
(org-agenda-files '("~/gtd/next-actions.org"))
(org-agenda-prefix-format "* %b")
(org-agenda-breadcrumbs-separator "\n** ")
(org-agenda-todo-ignore-scheduled 'all)
(org-agenda-todo-ignore-timestamp 'future)
(org-habit-show-habits nil))
)
(agenda ""
((org-agenda-overriding-header "\nHabits")
(org-agenda-files '("~/gtd/habits.org"))
(org-agenda-format-date
(with-temp-buffer (insert (fortune-message))
(fill-paragraph) (buffer-string))
)
(org-agenda-day-face-function
(lambda (date) 'font-lock-comment-face))
(org-agenda-use-time-grid nil)
(org-agenda-span 1)
(org-agenda-prefix-format "* % s"))
)
(agenda ""
((org-agenda-overriding-header "\nToday's
agenda")
(org-agenda-files
'("~/gtd/next-actions.org"
"~/gtd/calendar.org"))
(org-agenda-start-on-weekday nil)
(org-agenda-span 1)
(org-agenda-skip-scheduled-if-done t)
(org-agenda-skip-deadline-if-done t)
(org-agenda-sort-notime-is-late nil)
(org-agenda-use-time-grid nil)
(org-agenda-prefix-format "% t* %b%s")
(org-agenda-breadcrumbs-separator "\n** ")
(org-agenda-skip-function
'(org-agenda-skip-entry-if 'todo 'done))
(org-habit-show-habits nil))
)
(agenda ""
((org-agenda-overriding-header "\nTomorrow's
agenda")
(org-agenda-files
'("~/gtd/next-actions.org"
"~/gtd/calendar.org"))
(org-agenda-span 1) (org-agenda-start-day
"+1d")
(org-agenda-skip-scheduled-if-done t)
(org-agenda-skip-deadline-if-done t)
(org-agenda-sort-notime-is-late nil)
(org-agenda-use-time-grid nil)
(org-agenda-prefix-format "% t* %b%s")
(org-agenda-breadcrumbs-separator "\n** ")
(org-habit-show-habits nil))
)
