[O] error in org-mode 9.2 manual p. 239
On this page we have this statement - 15.11 Context Dependent Documentation C-c C-x C-i in an Org file tries to open a suitable section of the Org info documentation I believe that this should be C-c C-x I org-info-find-node -- = Ian Garmaise Consultant Phorix Solutions Group ia...@phorixsol.com Toronto cell: 416.432.2251 NYC: 917.512.9535 https://www.linkedin.com/in/igarmaise/ http://www.PhorixSol.com
[O] bug#34334: 26.1; org-list-make-subtree eating newline after list
Hello, Felix Wiemuth writes: > Start with an empty buffer in org-mode and add the following content: > > * A > - L1 > - L2 > * B > > If we execute `org-list-make-subtree` on any position within the list (the > two lines with L1/L2), we get > > * A > ** L1 > ** L2* B > > So the conversion "eats" the newline after the last list item. > > When having an additional newline before, it still eats the newline: > > * A > - L1 > - L2 > > * B > > After conversion: > > * A > ** L1 > ** L2 > * B > > It happens at any level in a tree, and no matter whether the list is > indented or has further levels. Fixed. Thank you. Regards, -- Nicolas Goaziou
[O] bug#33521: 26.1; org html export fails to recorgnize image urls with query parameters
Hello, Ernesto Alfonso writes: > The following URLs fail to get inlined as an html image: > > https://travis-ci.org/erjoalgo/emacs-buttons.svg?branch=master > https://travis-ci.org/erjoalgo/emacs-buttons.png?branch=master > > But this one does: > > https://travis-ci.org/erjoalgo/emacs-buttons.png > > Reporting this as a bug since I expect that extra query parameters > should not affect whether a URL points to an image. Does customizing `org-html-inline-image-rules' fix your issue? Regards, -- Nicolas Goaziou
[O] [PATCH] ob-emacs-lisp: Set `lexical-binding' in source editing buffers
* lisp/ob-emacs-lisp.el (org-babel-execute:emacs-lisp,
org-babel-emacs-lisp-lexical): Factor out the conversion of the
:lexical source block argument to a form that is appropriate for
`lexical-binding' and the LEXICAL argument to `eval'.
* lisp/ob-emacs-lisp.el (org-babel-edit-prep:emacs-lisp): Set
`lexical-binding'.
* lisp/ob-emacs-lisp.el (org-babel-default-header-args:emacs-lisp):
Update docstring.
TINYCHANGE
---
lisp/ob-emacs-lisp.el | 23 +++
1 file changed, 19 insertions(+), 4 deletions(-)
diff --git a/lisp/ob-emacs-lisp.el b/lisp/ob-emacs-lisp.el
index cd86f4a20..17952069e 100644
--- a/lisp/ob-emacs-lisp.el
+++ b/lisp/ob-emacs-lisp.el
@@ -43,7 +43,8 @@
A value of \"yes\" or t causes source blocks to be eval'd using
lexical scoping. It can also be an alist mapping symbols to
their value. It is used as the optional LEXICAL argument to
-`eval', which see.")
+`eval', which see. And it is used as the value for
+`lexical-binding' in buffers created by `org-edit-src-code'.")
(defun org-babel-expand-body:emacs-lisp (body params)
"Expand BODY according to PARAMS, return the expanded body."
@@ -71,9 +72,7 @@ their value. It is used as the optional LEXICAL argument to
(member "pp" result-params))
(concat "(pp " body ")")
body))
- (if (listp lexical)
- lexical
- (member lexical '("yes" "t"))
+ (org-babel-emacs-lisp-lexical lexical
(org-babel-result-cond result-params
(let ((print-level nil)
(print-length nil))
@@ -88,6 +87,22 @@ their value. It is used as the optional LEXICAL argument to
(org-babel-pick-name (cdr (assq :rowname-names params))
(cdr (assq :rownames params
+(defun org-babel-emacs-lisp-lexical (lexical)
+ "Convert :lexical source block argument LEXICAL into the form
+appropriate for `lexical-binding' and the LEXICAL argument to
+`eval'."
+ (if (listp lexical)
+ lexical
+(not (null (member lexical '("yes" "t"))
+
+(defun org-babel-edit-prep:emacs-lisp (info)
+ "Set `lexical-binding' according to :lexical source block
+argument."
+ (setq lexical-binding
+(org-babel-emacs-lisp-lexical
+ (org-babel-read
+ (cdr (assq :lexical (nth 2 info)))
+
(org-babel-make-language-alias "elisp" "emacs-lisp")
(provide 'ob-emacs-lisp)
--
2.20.1
Re: [O] Order of items after a headline in an Org outline?
David Masterson writes: > Is there a documented requirement of the order of things in a Org > outline? For instance, do these things have to come directly after the > headline and, if so, in what order? Will Org get confused otherwise? > * PROPERTY drawer > * Timestamp > * SCHEDULED and DEADLINE > * Notes > > -- > David I use M-x org-lint to report problems so I can manually fix them in my org-files. Otherwise I don't worry about the ordering. Regards, Bernt
