Re: [O] org mode on osx
Even though it's a large and complex application in itself, Org mode is still "just" an Emacs "mode". Very roughly, that translates to an add-on/plug-in/extension for Emacs. So you start Emacs first. Then within Emacs you either create or open an Org-mode file, that is, a plain text file with the ".org" extension. As soon as Emacs recognizes that it is editing an Org-mode file it "switches on" Org mode. The default cross-platform keystroke for "visiting" a file, as we say in Emacs-land, is C-x C-f. That is, hold down the Control key (*not* the Command key) and type first X then F. Then you follow the text prompts to type in the file name you want to open/create. However, if you're using a build of Emacs that is heavily customized for the Mac you may have the more intuitive Mac-standard keystrokes using the standard Mac file chooser: Command-N for "New...", Command-O for "Open", etc. On 11 November 2016 at 21:58, Matthew Pritchard wrote: > How do I get org mode to start in osx emacs? > -- Phil Hudson http://hudson-it.ddns.net Pretty Good Privacy (PGP) ID: 0x887DCA63
Re: [O] Bug: Missing space in Babel disabled evaluation message [9.0 (9.0-elpa @ /home/mir/.emacs.d/elpa/org-20161102/)]
Hello, Allen Li writes: > In ob-core.el, in `org-babel-check-evaluate', when the code block is > missing a name, the formatted message is missing a space. Compare: > > Evaluation of this python code-block (read-future) is disabled. > Evaluation of this python code-blockis disabled. I think this was fixed recently. Regards, -- Nicolas Goaziou
Re: [O] HTML export with ":export" parameter with Orgmode 9.0
Hello, "Charles C. Berry" writes: > On Fri, 11 Nov 2016, Frederick Giasson wrote: > >> Hi Chuck, >> >>> even with a minimal init file. >>> >>> If you ever set the value of `org-export-babel-evaluate' to nil >>> this might produce the behavior you describe. >> >> Maybe, but as stated in the manual: "Setting the >> org-export-babel-evaluate variable to nil will ensure that no code >> blocks are evaluated as part of the export process." > > Argh! That paragraph needs to be revised. Do you want to provide a patch for that? > Like the docstring says > > "Users who wish to avoid evaluating code on export should use the > header argument ‘:eval never-export’." > > It is tempting to `make-obsolete-variable' this variable and change > its name to something that more completely describes what does not > happen when set to nil. It can be done for Org 9.1. Regards, -- Nicolas Goaziou
[O] mobil org manual
Does anyone know were I can get a manual for mobil org?
[O] FR: Hotkey to jump to latest timestamp
I've found in large Org files that it would be very beneficial for me to be able to quickly jump to the latest timestamp in the current buffer with a hotkey, and incrementally search backward from there on subsequent invocation. If I get lost now in a large timestamped file, I pull up the agenda in log mode with inactive timestamps, and browse from there. It just seems like significant overhead. So please consider this a feature request. Thanks! -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] mobil org manual
On Sat, 12 Nov 2016 09:33:23 -0800 Matthew Pritchard wrote: > Does anyone know were I can get a manual for mobil org? > Look at Appendix B in the org manual and https://github.com/matburt/mobileorg-android/wiki/Documentation Best, Tony
Re: [O] Bug: second batch of small documentation problems [9.0 (9.0-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20161102/)]
On 11 November 2016 at 22:47, Nicolas Goaziou wrote: > `org-tag-persistent-alist' is about "characters". I think it is clear > that characters are case-sensitive already. Currently, the docstring of org-tag-alist says "SELECT is a case-sensitive letter" and the docstring of org-tag-persistent-alist says "SELECT is a character". I thought I should point this out, but it is your call whether this inconsistency needs to be fixed. > AFAICT any character is allow, but how could we formulate this?. Any Emacs character is allowed? If so, perhaps we could just say "SELECT is an Emacs character (this includes all Unicode characters)". But beware that I know little Org and very little Elisp, so please take my suggestion with a grain of salt. Regards -- • I am Brazilian. I hope my English is correct and I welcome corrections. • Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z. • Free (as in free speech) software for Android: https://f-droid.org/
[O] Org-mode: need install/config help on org-plus-contrib-20161102
I want to write guides for using Linux Shell. I first tried the features that knitr offers for this via R (http://yihui.name/knitr/demo/engines), but that turned out to be a fail because the shell session was not persistent across code chunks and the working directory was not change-able in a graceful way. Mr. Google says org mode in Emacs can work. I'll try that! (I said on Wednesday). For 2 days I've been fighting with the install & configuration. I am pretty sure I'm caught in a Bermuda triangle configuration, where org-mode that comes with Emacs is too old, but the new one from ELPA results in a fail because its pieces are not finding what they want. I'm running Ubuntu 16.10 with Emacs24.5.1. The org mode that comes with Emacs sorta works. There is no color highlighting in the Emacs session. I can do C-c C-c and the chunks do run. There's no persistent session, but it looks like setting the working directory for each chunk solves about 85% of problem. Unfortunately, the HTML output is completely white. There's a small glimmer of hope in this mission, but the end result is too poor to put to use. Then I got courageous and everything went to hell. After installing org mode from elpa, and then org mode from the elpa server hosted by the org mode server, then org-plus-contrib. In the process, I think I have found all of the stupid error messages that others have posted in this list. I'm punch drunk from putting packages in and debugging Emacs init. I'm stopping to ask for some help. When I install org-plus-contrib, there are plenty of compiler warnings. And Emacs itself cannot load, it chokes on this: File mode specification error: (invalid-function org-babel-header-args-safe-fn) That's gotta mean I should not ignore the installer warnings with org-plus-contrib-20161102, can you help me? Here they are: Compiling file /home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/ob-C.el at Sat Nov 12 18:56:20 2016 Entering directory `/home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/' In end of data: ob-C.el:448:1:Warning: the function `org-babel--get-vars' is not known to be defined. Compiling file /home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/ob-J.el at Sat Nov 12 18:56:20 2016 Compiling file /home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/ob-R.el at Sat Nov 12 18:56:21 2016 ob-R.el:70:11:Warning: reference to free variable `org-babel-safe-header-args' ob-R.el:408:1:Warning: Unused lexical variable `raw' In end of data: ob-R.el:470:1:Warning: the following functions are not known to be defined: org-babel-header-args-safe-fn, org-babel-graphical-output-file, org-babel--get-vars Compiling file /home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/ob-abc.el at Sat Nov 12 18:56:21 2016 In end of data: ob-abc.el:93:1:Warning: the function `org-babel--get-vars' is not known to be defined. Compiling file /home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/ob-asymptote.el at Sat Nov 12 18:56:21 2016 In end of data: ob-asymptote.el:140:1:Warning: the function `org-babel--get-vars' is not known to be defined. Compiling file /home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/ob-awk.el at Sat Nov 12 18:56:21 2016 In end of data: ob-awk.el:112:1:Warning: the function `org-babel--get-vars' is not known to be defined. Compiling file /home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/ob-calc.el at Sat Nov 12 18:56:21 2016 In end of data: ob-calc.el:111:1:Warning: the function `org-babel--get-vars' is not known to be defined. Compiling file /home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/ob-clojure.el at Sat Nov 12 18:56:21 2016 In end of data: ob-clojure.el:119:1:Warning: the function `org-babel--get-vars' is not known to be defined. Compiling file /home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/ob-comint.el at Sat Nov 12 18:56:21 2016 Compiling file /home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/ob-coq.el at Sat Nov 12 18:56:21 2016 Compiling file /home/pauljohn/.emacs.d/elpa/org-plus-contrib-20161102/ob-core.el at Sat Nov 12 18:56:21 2016 In org-babel-check-confirm-evaluate: ob-core.el:221:8:Warning: function org-babel-check-confirm-evaluate used to take 1+ arguments, now takes 1 ob-core.el:221:8:Warning: macro `org-babel-check-confirm-evaluate' being redefined as a function ob-core.el:248:1:Warning: Unused lexical variable `block-name' ob-core.el:248:1:Warning: Unused lexical variable `code-block' ob-core.el:248:1:Warning: Unused lexical variable `query' ob-core.el:248:1:Warning: Unused lexical variable `noeval' In org-babel-check-evaluate: ob-core.el:248:34:Warning: value returned from (format " (%s) " --name) is unused ob-core.el:263:1:Warning: Unused lexical variable `block-name' ob-core.el:263:1:Warning: Unused lexical variable `code-block' ob-core.el:263:1:Warning: Unused lexical variable `query' ob-core.el:263:1:Warning: Unused lexical variable `noeval' In org-babel-confirm-eval
[O] [PATCH] Re: HTML export with ":export" parameter with Orgmode 9.0
On Sat, 12 Nov 2016, Nicolas Goaziou wrote:
[discussion of problems interpreting the variable
`org-export-babel-evaluate' deleted]
It is tempting to `make-obsolete-variable' this variable and change
its name to something that more completely describes what does not
happen when set to nil.
It can be done for Org 9.1.
OK. I changed the name to `org-export-process-with-babel', which I hope
suggests more profound actions than `org-export-babel-evaluate'.
I think the attached patch does this properly, but this is my first use of
`define-obsolete-function-alias', so it might be best to check what I have
done.
ChuckFrom 3885129980a02eb0d4694e9e15888dea6ee95c60 Mon Sep 17 00:00:00 2001
From: Charles Berry
Date: Sat, 12 Nov 2016 18:54:20 -0800
Subject: [PATCH] make-obsolete-variable `org-export-babel-evaluate'
* doc/org.texi: Better explain what the variable
`org-export-process-with-babel' does.
* lisp/ob-exp.el: Small docstring change.
* lisp/org-compat.el: Define `org-export-babel-evaluate' as the
obsolete alias for `org-export-process-with-babel'.
* lisp/ox-icalendar.el, lisp/ox.el, testing/lisp/test-ob-exp.el,
testing/lisp/test-ob-lob.el, testing/lisp/test-ox.el: Change the
obsolete variable name in many places.
Users were often confused that setting this variable to nil will cause
header arguments to be ignored in addition to preventing code from
being evaluated. It is hoped that the documentation changes and the
name `org-export-process-with-babel' will better convey that everything
babel does can be switched off with this variable.
---
doc/org.texi| 24 +---
lisp/ob-exp.el | 12 ++--
lisp/org-compat.el | 2 ++
lisp/ox-icalendar.el| 2 +-
lisp/ox.el | 2 +-
testing/lisp/test-ob-exp.el | 36 ++--
testing/lisp/test-ob-lob.el | 2 +-
testing/lisp/test-ox.el | 2 +-
8 files changed, 43 insertions(+), 39 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index ede2352..81364d2 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -14938,17 +14938,19 @@ Both the code block and its results will be exported.
Neither the code block nor its results will be exported.
@end table
-It is possible to inhibit the evaluation of code blocks during export.
-Setting the @code{org-export-babel-evaluate} variable to @code{nil} will
-ensure that no code blocks are evaluated as part of the export process. This
-can be useful in situations where potentially untrusted Org mode files are
-exported in an automated fashion, for example when Org mode is used as the
-markup language for a wiki. It is also possible to set this variable to
-@code{inline-only}. In that case, only inline code blocks will be
-evaluated, in order to insert their results. Non-inline code blocks are
-assumed to have their results already inserted in the buffer by manual
-evaluation. This setting is useful to avoid expensive recalculations during
-export, not to provide security.
+It is possible to inhibit the evaluation of code blocks and ignore header
+arguments during export. Setting the @code{org-export-process-with-babel}
+variable to @code{nil} will ensure that no code blocks are evaluated as part
+of the export process. This can be useful in situations where potentially
+untrusted Org mode files are exported in an automated fashion, for example
+when Org mode is used as the markup language for a wiki. No header arguments
+will be processed. For this reason it is often better to set `:eval
+never-export' to prevent code evaluation but still allow headers to be
+honored. It is also possible to set this variable to @code{inline-only}. In
+that case, only inline code blocks will be evaluated, in order to insert
+their results. Non-inline code blocks are assumed to have their results
+already inserted in the buffer by manual evaluation. This setting is useful
+to avoid expensive recalculations during export, not to provide security.
Code blocks in commented subtrees (@pxref{Comment lines}) are never evaluated
on export. However, code blocks in subtrees excluded from export
diff --git a/lisp/ob-exp.el b/lisp/ob-exp.el
index 6aebcd5..1d77e6a 100644
--- a/lisp/ob-exp.el
+++ b/lisp/ob-exp.el
@@ -38,10 +38,10 @@
(defvar org-src-preserve-indentation)
-(defcustom org-export-babel-evaluate t
- "Switch controlling code evaluation during export.
+(defcustom org-export-process-with-babel t
+ "Switch controlling code evaluation and header processing during export.
When set to nil no code will be evaluated as part of the export
-process and no header argumentss will be obeyed. When set to
+process and no header arguments will be obeyed. When set to
`inline-only', only inline code blocks will be executed. Users
who wish to avoid evaluating code on export should use the header
argument `:eval never-export'."
@@ -50,7 +50,7 @@ argument `:eval never-export'."
:type '(choice (cons
