[O] Tangling and Exporting an Unsupported Language.
All, I'm writing an org document which contains code examples of a language not supported by Babel (a local domain specific language). The language doesn't even have a supporting Emacs mode. I'm wondering what the best portable approach is to managing the code blocks. I'm particularly interested in exporting the document to LaTeX and tangling the code. I may need to share the document with others, so I'd prefer not to require a supporting elisp file if I can help it. Currently I'm using the org language, since it seems to be the most generic: #+begin_src org :tangle foo.bar #+end_src Is there a case for 'begin_src text' to handle arbitrary content? Malcolm -- Malcolm Purvis malc...@purvis.id.au
Re: [O] Changed behaviours of LaTeX exporter in version 8.0+
Hello,
Kyeong Soo (Joseph) Kim kyeongsoo@gmail.com writes:
The real problem is that, except for using the custom id, the current
export engine cannot refer to the correct label (e.g., \label{se-1})
which is automatically generated during the export process.
See the case of section title with only one word in the ECM (e.g.,
\hyperref[sec-1]{OneWord}), where the export engine still cannot properly
refer to the automatically generated label. This has nothing to do with the
URL-encoding.
Could you elaborate about what is wrong with
\hyperref[sec-1]{OneWord}?
AFAICT, it is the desired output.
Regards,
--
Nicolas Goaziou
Re: [O] Changed behaviours of LaTeX exporter in version 8.0+
On Mon, Sep 29, 2014 at 3:07 PM, Nicolas Goaziou m...@nicolasgoaziou.fr
wrote:
Hello,
Kyeong Soo (Joseph) Kim kyeongsoo@gmail.com writes:
The real problem is that, except for using the custom id, the current
export engine cannot refer to the correct label (e.g., \label{se-1})
which is automatically generated during the export process.
See the case of section title with only one word in the ECM (e.g.,
\hyperref[sec-1]{OneWord}), where the export engine still cannot
properly
refer to the automatically generated label. This has nothing to do with
the
URL-encoding.
Could you elaborate about what is wrong with
\hyperref[sec-1]{OneWord}?
AFAICT, it is the desired output.
Regards,
--
Nicolas Goaziou
Now I see the point in your suggestion.
It seems that you suggest using filter to change
\hyperref[sec-1]{OneWord}
to
\ref{sec-1}
Am I right?
By the way, this is a bit of step backward, considering near standard use
of '\ref{...}' in most academic papers and theses; the use of hyperlinks
are even strongly discouraged in many conferences and academic journals
during the publication processes.
If we have to choose, I believe going back to version 7.x behavior (i.e.,
\ref{...}) is a right direction for LaTeX export. Hyperlinks can be done
using filtering in this case.
Regards,
Joseph
[O] macro for iterating over headings and doing things with them
Hi all, Recently, with the help of emacs.help, I wrote a small macro called `org-iter-headings' (essentially a thin wrapper around `org-element-map') for iterating over the child headings in a subtree, and doing something with them. It's meant to be a quick-and-dirty, *scratch*-buffer convenience function, for when you have some regular data in a series of sibling headings, and want to use that data in a one-off way. So anything from mail merges, to quick collections of property values, to launching more complex per-heading processes. You call the macro on a subtree's parent, and the body of the macro is executed once for each child heading. In the macro body, the dynamic variables `head', `item', `todo', `tags', `log-items' and `body-pars' are bound appropriately (see the docstring below). For example, I occasionally evaluate a batch of manuscripts for a publishing house. Each child heading is a manuscript: the heading text is the title, the todo either ACCEPT or REJECT, with my reasons in the todo state log. I might this information to the publishing house by calling the following on the parent heading: (let ((buf (get-buffer-create *temp output*))) (with-current-buffer buf (erase-buffer)) (org-iter-headings (with-current-buffer buf (insert (format Title: %s\nMy recommendation: %s, reasons as follows:\n\n%s\n\n\n item (capitalize (cdr todo)) ;; Get the most recent state log, and insert all its paragraphs ;; but the first one. (mapconcat #'identity (cdar log-items) \n) (compose-mail peo...@pubhouse.com Manuscript evaluation ) (message-goto-body) (insert-buffer-substring buf)) For things you do regularly, you might as well write a proper function using `org-element-map'. But for one-offs, this can be a lot easier to manage. I guess I might stick this on Worg, depending on how useful people think it might be. Enjoy, Eric (defmacro org-iter-headings (rest body) Run BODY forms on each child heading of the heading at point. This is a thin wrapper around `org-element-map'. Note that the former will map over the heading under point as well as its children; this function skips the heading under point, and *only* applies to the children. At present it ignores further nested headline. If you have a strong opinion on how to customize handling of nested children, please contact the author. Within the body of this macro, dynamic variables are bound to various parts of the heading being processed: head: The full parsed heading, as an Org element. Get your property values here. item: The text (ie :raw-value) of the heading. todo: The heading's todo information, as a cons of the todo type (one of the symbols 'todo or 'done) and the todo keyword as a string. tags: The heading's tags, as a list of strings. log-items: If org-log-into-drawer is true, and the drawer is present, then this variable will hold all the list items from the log drawer. Specifically, each member of `log-items' is a further list of strings, containing the text of that item's paragraphs. Not the paragraphs as parsed org structures, just their text. If org-log-into-drawer is false, any state logs or notes will be found in body-pars. body-pars: A list of all the paragraphs in the heading's body text; \paragraphs\ are understood however `org-element-map' understands them. tree: This holds the entire parsed tree for the subtree being operated on. This macro returns a list of whatever value the final form of BODY returns. `(call-org-iter-headings (lambda (tree head item todo tags log-items body-pars) ,@body))) (defun call-org-iter-headings (thunk) (save-restriction (org-narrow-to-subtree) (let ((tree (org-element-parse-buffer)) (log-spec org-log-into-drawer) (first t) returns) (setq returns (org-element-map tree 'headline (lambda (head) ;; Skip the first headline, only operate on children. Is ;; there a less stupid way of doing this? (if first (setq first nil) (let ((item (org-element-property :raw-value head)) (todo (cons (org-element-property :todo-type head) (org-element-property :todo-keyword head))) (tags (org-element-property :tags head)) (log-items (org-element-map (org-element-map head 'drawer ;; Find the first drawer called ;; \LOGBOOK\, or whatever. (lambda (d) (when (string= (if (stringp log-spec) log-spec LOGBOOK) (org-element-property :drawer-name d)) d)) nil t)
Re: [O] Changed behaviours of LaTeX exporter in version 8.0+
Hi,
Kyeong Soo (Joseph) Kim kyeongsoo@gmail.com writes:
On Mon, Sep 29, 2014 at 3:07 PM, Nicolas Goaziou m...@nicolasgoaziou.fr
wrote:
Hello,
Kyeong Soo (Joseph) Kim kyeongsoo@gmail.com writes:
The real problem is that, except for using the custom id, the current
export engine cannot refer to the correct label (e.g., \label{se-1})
which is automatically generated during the export process.
See the case of section title with only one word in the ECM (e.g.,
\hyperref[sec-1]{OneWord}), where the export engine still cannot
properly
refer to the automatically generated label. This has nothing to do with
the
URL-encoding.
Could you elaborate about what is wrong with
\hyperref[sec-1]{OneWord}?
AFAICT, it is the desired output.
Regards,
--
Nicolas Goaziou
Now I see the point in your suggestion.
It seems that you suggest using filter to change
\hyperref[sec-1]{OneWord}
to
\ref{sec-1}
Am I right?
If you don't want to use hyperref (i) make sure your sections are
numbered (e.g. #+OPTIONS: num:5) and (ii) make sure that you are not
giving links a description. Here's an example:
* test my heading
:PROPERTIES:
:CUSTOM_ID: t
:END:
[[*test my heading][my funky label]]
[[*test my heading]]
[[#t]]
→
\section{test my heading}
\label{sec-1}
\hyperref[sec-1]{my funky label}
\ref{sec-1}
\ref{sec-1}
—Rasmus
--
May the Force be with you
[O] org-contacts-anniversaries 'Bad sexp' bug keeps haunting me
Hi all, for a while I had been able to run org-contacts-anniversaries with BIRTHDAY dates successfully, as explained at the bottom of https://julien.danjou.info/projects/emacs-packages#org-contacts. This was on 64-bit Linux. On 32-bit Windows I had the function disabled, as I have contacts both before 1970. (See this thread: http://comments.gmane.org/gmane.emacs.orgmode/42139) Now, for the first time, I'm running a 64-bit Emacs on Windows (http://emacsbinw64.sourceforge.net/). I was confident that org-contacts-anniversaries would work for me, but it didn't. Once more any invocation of an agenda involving org-contacts-anniversaries haunted me with the Bad sexp error message, pointing to the line in my contacts.org that contains %%(org-contacts-anniversaries). I am running org-8.2.7c from ELPA, on Emacs 24.4.50.1. I think I didn't make any of the mistakes documented previously: * running a mixed Org installation (Org as bundled with Emacs, plus non-bundled packages; http://stackoverflow.com/a/15568713/2397768) * using the wrong syntax for org-contacts-files (http://stackoverflow.com/a/14057170/2397768) * using empty BIRTHDAY fields (http://stackoverflow.com/a/21968778/2397768) * not having diary loaded (https://www.mail-archive.com/emacs-orgmode@gnu.org/msg48710.html – but isn't it actually loaded automatically by org-agenda.el when org-agenda-include-diary is set to t?) FYI this is how I disabled org-contacts-anniversaries on non-64-bit systems: ; disable anniversaries on non-64-bit systems (as they don't handle dates before 1970) (defadvice org-contacts-anniversaries (around disable-org-contacts-anniversaries-on-32-bit) No anniversaries on 32-bit systems (if (string-prefix-p x86_64 system-configuration) (ad-do-it))) (ad-activate 'org-contacts-anniversaries) This code does not cause my problem. I have tested it before, and without this code I'm still getting the Bad sexp. I'm giving up for now, reverting to manually maintained entries like this in my contacts.org: %%(org-anniversary MM DD) Name (%d years) Cheers, and thanks in advance for any helpful advice, Christoph -- Christoph Lange, Enterprise Information Systems Department Applied Computer Science @ University of Bonn; Fraunhofer IAIS http://langec.wordpress.com/about, Skype duke4701 → SEMANTiCS conference: Transfer–Engineering–Community. Leipzig, Germany, 4–5 September (workshops 1–3 September). Including Vocabulary Carnival, LOD for SMEs, Linked Data Quality.
Re: [O] Changed behaviours of LaTeX exporter in version 8.0+
Hello,
On Mon, Sep 29, 2014 at 4:53 PM, Rasmus ras...@gmx.us wrote:
If you don't want to use hyperref (i) make sure your sections are
numbered (e.g. #+OPTIONS: num:5) and (ii) make sure that you are not
giving links a description. Here's an example:
* test my heading
:PROPERTIES:
:CUSTOM_ID: t
:END:
[[*test my heading][my funky label]]
[[*test my heading]]
[[#t]]
→
\section{test my heading}
\label{sec-1}
\hyperref[sec-1]{my funky label}
\ref{sec-1}
\ref{sec-1}
—Rasmus
--
May the Force be with you
This is exactly what I wanted to do for cross-referencing in LaTeX export.
With this, now I can use my org files as I did with version 7.x (except for
the description in the link).
It would have been much better to have this information in the manual (like
those for cross-referencing in LaTeX in the older version of manual).
Or, is this already described there?
Anyhow, great thanks for this information!
Regards,
Joseph
Re: [O] macro for iterating over headings and doing things with them
Eric Abrahamsen e...@ericabrahamsen.net writes: Hi all, Recently, with the help of emacs.help, I wrote a small macro called `org-iter-headings' (essentially a thin wrapper around `org-element-map') for iterating over the child headings in a subtree, and doing something with them. It's meant to be a quick-and-dirty, *scratch*-buffer convenience function, for when you have some regular data in a series of sibling headings, and want to use that data in a one-off way. So anything from mail merges, to quick collections of property values, to launching more complex per-heading processes. You call the macro on a subtree's parent, and the body of the macro is executed once for each child heading. In the macro body, the dynamic variables `head', `item', `todo', `tags', `log-items' and `body-pars' are bound appropriately (see the docstring below). For example, I occasionally evaluate a batch of manuscripts for a publishing house. Each child heading is a manuscript: the heading text is the title, the todo either ACCEPT or REJECT, with my reasons in the todo state log. I might this information to the publishing house by calling the following on the parent heading: I realized I might have made this example too complicated. You could use this for something as simple as collecting the heading text of all headings in a subtree: (setq these-headings (org-iter-headings item)) Or, slightly more involved, adding up the :AMOUNT: property (a number) of all the headings whose TODOs are not yet done: (apply #'+ (org-iter-headings (when (equal (car todo) 'todo) (string-to-number (org-element-property :AMOUNT head) Eric (let ((buf (get-buffer-create *temp output*))) (with-current-buffer buf (erase-buffer)) (org-iter-headings (with-current-buffer buf (insert (format Title: %s\nMy recommendation: %s, reasons as follows:\n\n%s\n\n\n item (capitalize (cdr todo)) ;; Get the most recent state log, and insert all its paragraphs ;; but the first one. (mapconcat #'identity (cdar log-items) \n) (compose-mail peo...@pubhouse.com Manuscript evaluation ) (message-goto-body) (insert-buffer-substring buf)) For things you do regularly, you might as well write a proper function using `org-element-map'. But for one-offs, this can be a lot easier to manage. I guess I might stick this on Worg, depending on how useful people think it might be. Enjoy, Eric (defmacro org-iter-headings (rest body) Run BODY forms on each child heading of the heading at point. This is a thin wrapper around `org-element-map'. Note that the former will map over the heading under point as well as its children; this function skips the heading under point, and *only* applies to the children. At present it ignores further nested headline. If you have a strong opinion on how to customize handling of nested children, please contact the author. Within the body of this macro, dynamic variables are bound to various parts of the heading being processed: head: The full parsed heading, as an Org element. Get your property values here. item: The text (ie :raw-value) of the heading. todo: The heading's todo information, as a cons of the todo type (one of the symbols 'todo or 'done) and the todo keyword as a string. tags: The heading's tags, as a list of strings. log-items: If org-log-into-drawer is true, and the drawer is present, then this variable will hold all the list items from the log drawer. Specifically, each member of `log-items' is a further list of strings, containing the text of that item's paragraphs. Not the paragraphs as parsed org structures, just their text. If org-log-into-drawer is false, any state logs or notes will be found in body-pars. body-pars: A list of all the paragraphs in the heading's body text; \paragraphs\ are understood however `org-element-map' understands them. tree: This holds the entire parsed tree for the subtree being operated on. This macro returns a list of whatever value the final form of BODY returns. `(call-org-iter-headings (lambda (tree head item todo tags log-items body-pars) ,@body))) (defun call-org-iter-headings (thunk) (save-restriction (org-narrow-to-subtree) (let ((tree (org-element-parse-buffer)) (log-spec org-log-into-drawer) (first t) returns) (setq returns (org-element-map tree 'headline (lambda (head) ;; Skip the first headline, only operate on children. Is ;; there a less stupid way of doing this? (if first (setq first nil) (let ((item (org-element-property :raw-value head)) (todo (cons (org-element-property :todo-type head) (org-element-property :todo-keyword head))) (tags
Re: [O] [bug?] org-copy-face doesn’t add faces to org-faces customize group
Hi Aaron, Aaron Ecay wrote: 2014ko irailak 23an, Sebastien Vauban-ek idatzi zuen: OK, thanks for the followup. I’m attaching the patch to this email. If I don’t hear any further feedback, I’ll commit it to master in a few days. I'd say: commit it now, so that it really gets to a broad audience. Anyway, would there be problems, they would be very, very limited: face problems, that's all! The patch is now pushed to master. That works great. Thanks. Best regards, Seb -- Sebastien Vauban
Re: [O] passing LC_ALL environment variable to org export call
hi Rasmus, thanks for your hint. I checked Sys.getenv before and after the failing code, but LC_ALL was always properly set. I’m afraid my problem relates to some Mac LLVM and GCC gfortran compiler thing, since I’m using a R version compiled against the Mac Accelerate framework (vecLib)… it is just so strange that I only get the error in Emacs org-mode upon exporting the org file, but not, if I evaluate each code chunk separately. to set all environment variables I’m using the “exec-path-from-shell” extension, so, all environment settings from the shell are available in Emacs. On 26 Sep 2014, at 15:56, Rasmus ras...@gmx.us wrote: Hi Johannes, Johannes Rainer johannes.rai...@gmail.com writes: I stumbled across a strange problem. I’m using org-mode to perform analyses in R and I have one block of R-code in which I use mclapply to perform parallel calculations. evaluating this code block using C-c C-c works fine, but I get a segfault error when I export the org file. This has to do something with the LC_ALL environment variable as I can reproduce the same error above in R in a terminal after “unset LC_ALL”. Is there a way to pass environment variables to the export call? Check the two functions `getenv' and `setenv' and the variable `org-export-async-init-file'. You should be able to cook something up. It sound like there's an issue with your system-setup. I'd look into that before. Hope it helps, Rasmus -- Lasciate ogni speranza, voi che leggete questo.
Re: [O] Difference between eval and export
I checked the environment variables in Emacs and also in R (using Sys.getenv). all environment variables are set correctly (I am now also using “exec-path-from-shell” to make sure that Emacs is reading system environment variables). It is absolutely strange. I only get the error when I export the org file, but not if I execute R code chunk by code chunk sequentially. best, jo On 26 Sep 2014, at 21:58, Grant Rettke g...@wisdomandwonder.com wrote: On Fri, Sep 26, 2014 at 1:44 PM, Rainer M Krug rai...@krugs.de wrote: Grant Rettke g...@wisdomandwonder.com writes: My eye is on you post about that topic because I would also like to know. As you are using R, and if you are using sessions, what about setting them from within R[1]? Footnotes: [1] http://stat.ethz.ch/R-manual/R-devel/library/base/html/Sys.setenv.html Yes indeed. I am quite interested in the general mechanism of how the environment exists for when exports occur and in particular whether or not it is different somehow. Right now I've delegated things between [1] and .Renviron.
Re: [O] Changed behaviours of LaTeX exporter in version 8.0+
Hi Kyeong,
Kyeong Soo (Joseph) Kim kyeongsoo@gmail.com writes:
Hello,
On Mon, Sep 29, 2014 at 4:53 PM, Rasmus ras...@gmx.us wrote:
If you don't want to use hyperref (i) make sure your sections are
numbered (e.g. #+OPTIONS: num:5) and (ii) make sure that you are not
giving links a description. Here's an example:
* test my heading
:PROPERTIES:
:CUSTOM_ID: t
:END:
[[*test my heading][my funky label]]
[[*test my heading]]
[[#t]]
→
\section{test my heading}
\label{sec-1}
\hyperref[sec-1]{my funky label}
\ref{sec-1}
\ref{sec-1}
—Rasmus
--
May the Force be with you
This is exactly what I wanted to do for cross-referencing in LaTeX export.
With this, now I can use my org files as I did with version 7.x (except for
the description in the link).
It would have been much better to have this information in the manual (like
those for cross-referencing in LaTeX in the older version of manual).
Or, is this already described there?
If it's unclear, please consider one of the following:
1. Writing a documentation patch — especially if you have assigned
copyright to FSF For Emacs changes.
2. Explain exactly where you would have expected to find this
information and/or where the manual is unclear.
Thanks,
Rasmus
--
However beautiful the theory, you should occasionally look at the evidence
Re: [O] passing LC_ALL environment variable to org export call
Johannes Rainer johannes.rai...@gmail.com writes: thanks for your hint. I checked Sys.getenv before and after the failing code, but LC_ALL was always properly set. I’m afraid my problem relates to some Mac LLVM and GCC gfortran compiler thing, since I’m using a R version compiled against the Mac Accelerate framework (vecLib)… it is just so strange that I only get the error in Emacs org-mode upon exporting the org file, but not, if I evaluate each code chunk separately. But are you using .C, .Fortran or Rcpp in your code-block? If not, why would your compilers matter? (I'm not an expert on R internals, so my comment may be naïve). As a short turn solution try to add this to the top of your file #+PROPERTY: session *R* These days you might even get away with just #+PROPERTY: session I'm not sure. This should run your code from the same session. [This should be equivalent to adding :session to babel blocks, but check the manual if it ain't working] to set all environment variables I’m using the “exec-path-from-shell” extension, so, all environment settings from the shell are available in Emacs. Are you exporting async or normally? If async, do you get the error when exporting normally? —Rasmus -- Hvor meget poesi tror De kommer ud af et glas isvand?
Re: [O] Changed behaviours of LaTeX exporter in version 8.0+
Hi Rasmus,
On Mon, Sep 29, 2014 at 6:09 PM, Rasmus ras...@gmx.us wrote:
Hi Kyeong,
Kyeong Soo (Joseph) Kim kyeongsoo@gmail.com writes:
This is exactly what I wanted to do for cross-referencing in LaTeX
export.
With this, now I can use my org files as I did with version 7.x (except
for
the description in the link).
It would have been much better to have this information in the manual
(like
those for cross-referencing in LaTeX in the older version of manual).
Or, is this already described there?
If it's unclear, please consider one of the following:
1. Writing a documentation patch — especially if you have assigned
copyright to FSF For Emacs changes.
2. Explain exactly where you would have expected to find this
information and/or where the manual is unclear.
Thanks,
Rasmus
--
However beautiful the theory, you should occasionally look at the evidence
If possible, please let me know where to find the information you provided
(i.e., without the description filed in the org-mode internal link, its
export to LaTeX becomes \ref{...} instead of \hyperref{...}).
I'm currently using Org Manual version 8.2.7c (PDF version), but cannot
find any relevant information. It's not the matter of whether it's clear or
not, but there is no such information in the current manual.
I do wonder where you got that information (directly from the source code?).
For older version, the following link provides all the details for LaTeX
cross referencing in Sec. 16:
http://orgmode.org/worg/org-tutorials/org-latex-export.html
Writing a documentation patch could be an option, but first of all, I need
detailed information on this but currently have not.
Regards,
Joseph
Re: [O] passing LC_ALL environment variable to org export call
On 29 Sep 2014, at 14:06, Rasmus ras...@gmx.us wrote: Johannes Rainer johannes.rai...@gmail.com writes: thanks for your hint. I checked Sys.getenv before and after the failing code, but LC_ALL was always properly set. I’m afraid my problem relates to some Mac LLVM and GCC gfortran compiler thing, since I’m using a R version compiled against the Mac Accelerate framework (vecLib)… it is just so strange that I only get the error in Emacs org-mode upon exporting the org file, but not, if I evaluate each code chunk separately. But are you using .C, .Fortran or Rcpp in your code-block? If not, why would your compilers matter? (I'm not an expert on R internals, so my comment may be naïve). no I’m not using .C in the code-block, the code block contains only R-code, however, one of the R functions is using (like most R functions) either C or fortran code to do the actual calculation. I suspect the loess function in R causing the problem and that this function uses some code from the optimized BLAS (i.e. library for numeric calculation) library from Apple (i.e. the Accelerate, or vecLib framework). So, if I run the code (exporting the org buffer to latex) in parallel processing mode I get a segfault. the same without parallel processing is fine. Strangely enough, the code block evaluated (C-c C-c) in parallel processing mode runs also fine. also, if I tangle the R-code and run the R-code in R it also works fine. It just doesn’t with org-mode export... so, in the end I give up. I think there is some very mystic thing going on. I also tried to understand what the difference between org-mode export and org-mode eval is... without success. I thought that the R-process is somehow started differently, but that doesn’t seem to be the case. As a short turn solution try to add this to the top of your file #+PROPERTY: session *R* These days you might even get away with just #+PROPERTY: session I'm not sure. This should run your code from the same session. [This should be equivalent to adding :session to babel blocks, but check the manual if it ain't working] to set all environment variables I’m using the “exec-path-from-shell” extension, so, all environment settings from the shell are available in Emacs. Are you exporting async or normally? If async, do you get the error when exporting normally? —Rasmus -- Hvor meget poesi tror De kommer ud af et glas isvand?
[O] Selectively archive by timestamp
Sometimes I want to selectively archive all entries in a subtree with
timestamps in the past, whilst keeping all entries with timestamps in the
future.
`org-archive-subtree' only lets you selectively archive entries depending
on whether they have open TODO items.
The attached patch adds a new `org-archive-all-old' counterpart to
`org-archive-all-done' which does timestamp-selective archiving. It also
extends `org-archive-subtree' so it can optionally be invoked for
timestamp-based archiving instead of TODO-based archiving.
Toby
--
Dr T. S. Cubitt
Royal Society University Research Fellow
Fellow of Churchill College, Cambridge
Centre for Quantum Information
DAMTP, University of Cambridge
email: ts...@cantab.net
web: www.dr-qubit.org
From 3183bcf9c005a0d5633dcc8be1719e55e3dfa8c5 Mon Sep 17 00:00:00 2001
From: Toby S. Cubitt ts...@cantab.net
Date: Fri, 17 Jan 2014 15:14:13 +
Subject: [PATCH] Add org-archive-all-old to archive entries with timestamps
before today.
Can be invoked from org-archive-subtree command with double prefix-arg.
---
doc/org.texi| 4
lisp/org-archive.el | 68 +++--
2 files changed, 60 insertions(+), 12 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 7d98d51..d2e61a8 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -7469,6 +7469,10 @@ the archive. To do this, each subtree is checked for open TODO entries.
If none are found, the command offers to move it to the archive
location. If the cursor is @emph{not} on a headline when this command
is invoked, the level 1 trees will be checked.
+@orgkey{C-u C-u C-c C-x C-s}
+As above, but check subtree for timestamps instead of TODO entries. The
+command will offer to archive the subtree if it @emph{does} contain a
+timestamp, and that timestamp is in the past.
@end table
@cindex archive locations
diff --git a/lisp/org-archive.el b/lisp/org-archive.el
index 700e59b..418af3a 100644
--- a/lisp/org-archive.el
+++ b/lisp/org-archive.el
@@ -198,9 +198,11 @@ The archive can be a certain top-level heading in the current file, or in
a different file. The tree will be moved to that location, the subtree
heading be marked DONE, and the current time will be added.
-When called with prefix argument FIND-DONE, find whole trees without any
+When called with a single prefix argument FIND-DONE, find whole trees without any
open TODO items and archive them (after getting confirmation from the user).
-If the cursor is not at a headline when this command is called, try all level
+When called with a double prefix argument, find whole trees with timestamps before
+today and archive them (after getting confirmation from the user).
+If the 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)
@@ -213,8 +215,10 @@ this heading.
(org-archive-subtree ,find-done))
org-loop-over-headlines-in-active-region
cl (if (outline-invisible-p) (org-end-of-subtree nil t
-(if find-done
- (org-archive-all-done)
+(cond
+ ((equal find-done '(4)) (org-archive-all-done))
+ ((equal find-done '(16)) (org-archive-all-old))
+ (t
;; Save all relevant TODO keyword-relatex variables
(let ((tr-org-todo-line-regexp org-todo-line-regexp) ; keep despite compiler
(tr-org-todo-keywords-1 org-todo-keywords-1)
@@ -375,7 +379,7 @@ this heading.
(message Subtree archived %s
(if (eq this-buffer buffer)
(concat under heading: heading)
- (concat in file: (abbreviate-file-name afile))
+ (concat in file: (abbreviate-file-name afile)))
(org-reveal)
(if (looking-at ^[ \t]*$)
(outline-next-visible-heading 1
@@ -456,13 +460,50 @@ sibling does not exist, it will be created at the end of the subtree.
If the cursor is not on a headline, try all level 1 trees. If
it is on a headline, try all direct children.
When TAG is non-nil, don't move trees, but mark them with the ARCHIVE tag.
- (let ((re org-not-done-heading-regexp) re1
- (rea (concat .*: org-archive-tag :))
+ (org-archive-all-matches
+ (lambda (beg end)
+ (unless (re-search-forward org-not-done-heading-regexp end t)
+ no open TODO items))
+ tag))
+
+(defun org-archive-all-old (optional tag)
+ Archive sublevels of the current tree with timestamps prior to today.
+If the cursor is not on a headline, try all level 1 trees. If
+it is on a headline, try all direct children.
+When TAG is non-nil, don't move trees, but mark them with the ARCHIVE tag.
+ (org-archive-all-matches
+ (lambda (beg end)
+ (let (ts)
+ (and (re-search-forward org-ts-regexp end t)
+ (setq ts (match-string 0))
+ ( (org-time-stamp-to-now ts) 0)
+ (if (not (looking-at
+ (concat --\\( org-ts-regexp \\
+ (concat old timestamp ts)
+ (setq ts (concat old timestamp ts (match-string 0)))
+ (and (
Re: [O] Changed behaviours of LaTeX exporter in version 8.0+
Hi,
Kyeong Soo (Joseph) Kim kyeongsoo@gmail.com writes:
If possible, please let me know where to find the information you provided
(i.e., without the description filed in the org-mode internal link, its
export to LaTeX becomes \ref{...} instead of \hyperref{...}).
You can open the info version of the manual with
(info org)
I'm currently using Org Manual version 8.2.7c (PDF version), but cannot
find any relevant information. It's not the matter of whether it's clear or
not, but there is no such information in the current manual.
I do wonder where you got that information (directly from the source code?).
It may be documented in chapter 4, entitled Hyperlinks.
http://orgmode.org/org.html#Hyperlinks
I don't know if this chapter describes export behavior.
You can skim through org-latex-link if you care. For headlines this
is the relevant part
;; LINK points to a headline. If headlines are numbered
;; and the link has no description, display headline's
;; number. Otherwise, display description or headline's
;; title.
(headline
(let* ((custom-label
(and (plist-get info :latex-custom-id-labels)
(org-element-property :CUSTOM_ID destination)))
(label
(or
custom-label
(format sec-%s
(mapconcat
#'number-to-string
(org-export-get-headline-number destination info)
-)
(if (and (not desc)
(org-export-numbered-headline-p destination info))
(format \\ref{%s} label)
(format \\hyperref[%s]{%s} label
(or desc
(org-export-data
(org-element-property :title destination) info))
Writing a documentation patch could be an option, but first of all, I need
detailed information on this but currently have not.
Please see
http://orgmode.org/worg/org-contribute.html
for practical details.
—Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
Re: [O] Changed behaviours of LaTeX exporter in version 8.0+
Hi,
Kyeong Soo (Joseph) Kim kyeongsoo@gmail.com writes:
If possible, please let me know where to find the information you provided
(i.e., without the description filed in the org-mode internal link, its
export to LaTeX becomes \ref{...} instead of \hyperref{...}).
You can open the info version of the manual with
(info org)
I'm currently using Org Manual version 8.2.7c (PDF version), but cannot
find any relevant information. It's not the matter of whether it's clear or
not, but there is no such information in the current manual.
I do wonder where you got that information (directly from the source code?).
It may be documented in chapter 4, entitled Hyperlinks.
http://orgmode.org/org.html#Hyperlinks
I don't know if this chapter describes export behavior.
You can skim through org-latex-link if you care. For headlines this
is the relevant part
;; LINK points to a headline. If headlines are numbered
;; and the link has no description, display headline's
;; number. Otherwise, display description or headline's
;; title.
(headline
(let* ((custom-label
(and (plist-get info :latex-custom-id-labels)
(org-element-property :CUSTOM_ID destination)))
(label
(or
custom-label
(format sec-%s
(mapconcat
#'number-to-string
(org-export-get-headline-number destination info)
-)
(if (and (not desc)
(org-export-numbered-headline-p destination info))
(format \\ref{%s} label)
(format \\hyperref[%s]{%s} label
(or desc
(org-export-data
(org-element-property :title destination) info))
Writing a documentation patch could be an option, but first of all, I need
detailed information on this but currently have not.
Please see
http://orgmode.org/worg/org-contribute.html
for practical details.
—Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
[O] outputting a modified parsetree
I'm trying to update an orgmode document programatically. I can create an AST from a buffer using org-element-parse-buffer, but how do I do the reverse and output the modified AST to a buffer?
Re: [O] odd/unexpected behavior with Python src blocks
Indeed, this passes by org-babel because stderr is not captured, and scipy does what you suggest. I guess this happens inside compiled c/Fortran code since there is nothing catching it in the odeint python function doing that. Thanks, I will try to bring it up on the scipy list. Aaron Ecay aarone...@gmail.com writes: Hi John, 2014ko irailak 28an, John Kitchin-ek idatzi zuen: [...] I am not sure why this happens, but it seems like incorrect behavior to me. In the first case, python exits with a non-zero exit code, whereas in the second it exits with a zero code (i.e. successful exit), and prints the matrix-thing [[1.], [1.]] to stdout. It looks like scipy traps the NameErrors and prints them to stderr, but continues its computation regardless. I’d say babel is performing as desired here, but scipy sadly isn’t reporting its errors in the standard way (by a nonzero exit, which I think would happen automatically if the NameErrors made it to the top level of the stack without being caught). -- --- John Kitchin Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu
Re: [O] outputting a modified parsetree
Pete Bataleck batal...@gmail.com writes: I'm trying to update an orgmode document programatically. I can create an AST from a buffer using org-element-parse-buffer, but how do I do the reverse and output the modified AST to a buffer? I think `org-element-interpret-data' is the function you're looking for. Take a look at the source in org-element.el -- that ought to do it.
[O] Adding new table rows/cols in a formula update
Hi. Suppose I have this .org file: | | #+TBLFM: @1$2=5 It's a 1x1 table with a formula. The formula sets a cell that's out of bounds in the table, so evaluating this formula results in an error. How set-in-stone is this behavior? I haven't dug too deeply into the code, but are there fundamental assumptions here? Would a patch that extends the table before applying such a formula be too naive in some way? Thanks! dima
Re: [O] Babel evaluation of Calc block not working, bug in Calc?
Andrea Rossetti andrea.rosse...@gmail.com writes: 3) temporary workaround: try to change :var v=3 into :var var-v=3, it works for me, does it work for you too? I'm afraid I've been a bit cryptic here. The suggested workaround/test is: replace #+BEGIN_SRC calc :var v=3 v + 4 #+END_SRC with #+BEGIN_SRC calc :var var-v=3 v + 4 #+END_SRC Kindest regards, Andrea
Re: [O] odd/unexpected behavior with Python src blocks
In case anyone else is interested, here is a workaround of sorts to capture stderr in a python block: https://github.com/jkitchin/pycse/blob/master/pycse/sandbox.py You use this module to redefine stdout and stderr. You basically run python like this: #+BEGIN_SRC emacs-lisp (setq org-babel-python-command python -m pycse.sandbox) #+END_SRC Then you get this output. #+BEGIN_SRC python :results output from scipy.integrate import odeint #k = -1 def f(y, x): return -k * y print(odeint(f, 1, [0, 1])) #+END_SRC #+RESULTS: #+begin_example sandbox: ---stdout--- [[ 1.] [ 1.]] ---stderr--- Traceback (most recent call last): File string, line 6, in f NameError: global name 'k' is not defined Traceback (most recent call last): File string, line 6, in f NameError: global name 'k' is not defined Traceback (most recent call last): File string, line 6, in f NameError: global name 'k' is not defined Traceback (most recent call last): File string, line 6, in f NameError: global name 'k' is not defined #+end_example At least until babel captures stderr, this is a way to capture it. It does break the nice behavior of making tables output, since it prints a string. The string could be orgified somewhat, eg #+STDOUT: #+STDERR: I am not sure I will use this routinely, so I am not sure how much I will put into furhter development. Instructor account jkitc...@andrew.cmu.edu writes: Indeed, this passes by org-babel because stderr is not captured, and scipy does what you suggest. I guess this happens inside compiled c/Fortran code since there is nothing catching it in the odeint python function doing that. Thanks, I will try to bring it up on the scipy list. Aaron Ecay aarone...@gmail.com writes: Hi John, 2014ko irailak 28an, John Kitchin-ek idatzi zuen: [...] I am not sure why this happens, but it seems like incorrect behavior to me. In the first case, python exits with a non-zero exit code, whereas in the second it exits with a zero code (i.e. successful exit), and prints the matrix-thing [[1.], [1.]] to stdout. It looks like scipy traps the NameErrors and prints them to stderr, but continues its computation regardless. I’d say babel is performing as desired here, but scipy sadly isn’t reporting its errors in the standard way (by a nonzero exit, which I think would happen automatically if the NameErrors made it to the top level of the stack without being caught). -- --- John Kitchin Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu
Re: [O] Tangling and Exporting an Unsupported Language.
Exporting and tangling don't require any language support. #+begin_src foobarbas :tangle foo.bar #+end_src is perfectly fine and will export and tangle just fine. Or did I misunderstand your question? Best, Ista On Mon, Sep 29, 2014 at 2:53 AM, Malcolm Purvis malc...@purvis.id.au wrote: All, I'm writing an org document which contains code examples of a language not supported by Babel (a local domain specific language). The language doesn't even have a supporting Emacs mode. I'm wondering what the best portable approach is to managing the code blocks. I'm particularly interested in exporting the document to LaTeX and tangling the code. I may need to share the document with others, so I'd prefer not to require a supporting elisp file if I can help it. Currently I'm using the org language, since it seems to be the most generic: #+begin_src org :tangle foo.bar #+end_src Is there a case for 'begin_src text' to handle arbitrary content? Malcolm -- Malcolm Purvis malc...@purvis.id.au
[O] Org-mode previews: equation numbers
I have noticed that the org-preview-latex-fragment command left-aligns previews
for display equations. But it looks like margins are calulated so that equation
numbers line up when display equations are centered (the way they are in
AUCTeX).
Is it possible to re-align these previews?
Here is some sample code:
A numbered display equation:
\begin{equation}
\frac{\partial u}{\partial t}-\alpha\nabla^2u=0\label{eq:1}\tag{1}
\end{equation}
A second numbered equation:
\begin{equation}
E=MC^2\label{eq:2}\tag{2}
\end{equation}
And here is the screenshot of the buffer after running C-c C-x C-l
By-the-way, the only way I could get the equation numbers to increment upward
was to manually include these with \tag{1} and \tag{2}. Otherwise, org-mode
numbers each equation as a (1). Is there some setting that will enable
autonumbering?
Thanks!
-Adam
Adam Sneller
a...@earth2adam.com
(310) 463-0287
Re: [O] Difference between eval and export
How painful would it be to pare it down to the minimal example of the behavior? On Mon, Sep 29, 2014 at 6:14 AM, Johannes Rainer johannes.rai...@gmail.com wrote: I checked the environment variables in Emacs and also in R (using Sys.getenv). all environment variables are set correctly (I am now also using “exec-path-from-shell” to make sure that Emacs is reading system environment variables). It is absolutely strange. I only get the error when I export the org file, but not if I execute R code chunk by code chunk sequentially. best, jo On 26 Sep 2014, at 21:58, Grant Rettke g...@wisdomandwonder.com wrote: On Fri, Sep 26, 2014 at 1:44 PM, Rainer M Krug rai...@krugs.de wrote: Grant Rettke g...@wisdomandwonder.com writes: My eye is on you post about that topic because I would also like to know. As you are using R, and if you are using sessions, what about setting them from within R[1]? Footnotes: [1] http://stat.ethz.ch/R-manual/R-devel/library/base/html/Sys.setenv.html Yes indeed. I am quite interested in the general mechanism of how the environment exists for when exports occur and in particular whether or not it is different somehow. Right now I've delegated things between [1] and .Renviron. -- Grant Rettke g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson
[O] sortable columns in html tables
Hello, How can I make sortable columns in tables? I would be useful to edit or export to html. Some experiences? Thanks!
[O] orgmode in drupal
Hello, Perhaps in this mailing list there are some drupal admin who wants upload his files to drupal. I've a project to make it :) https://www.drupal.org/node/1977240. Regards.
[O] [ob, bug?] org-sbe
Hi, I used sbe a long time ago. Apparently it has been renamed to org-spe. I was unable get org-spe working as a dumb currency converter, so I tried the example in the top of ob-table.el. However, I'm also unable to get this example working, even starting from emacs -q. . . This is the suggested test in ob-table.el: #+begin_src emacs-lisp :results silent (defun fibbd (n) (if ( n 2) 1 (+ (fibbd (- n 1)) (fibbd (- n 2) #+end_src #+name: fibbd #+begin_src emacs-lisp :var n=2 :results silent (fibbd n) #+end_src | original | fibbd | |--+| |0 | #ERROR | |1 | #ERROR | |2 | #ERROR | |3 | #ERROR | |4 | #ERROR | |5 | #ERROR | |6 | #ERROR | |7 | #ERROR | |8 | #ERROR | |9 | #ERROR | #+TBLFM: $2='(org-sbe 'fibbd (n $1)) Did the syntax of org-sbe change or am just missing something obvious here? Thanks in advance, Rasmus -- C is for Cookie
Re: [O] [ob, bug?] org-sbe
Rasmus rasmus at gmx.us writes: Hi, I used sbe a long time ago. Apparently it has been renamed to org-spe. I was unable get org-spe working as a dumb currency converter, so I tried the example in the top of ob-table.el. However, I'm also unable to get this example working, even starting from emacs -q. . . This is the suggested test in ob-table.el: #+begin_src emacs-lisp :results silent (defun fibbd (n) (if ( n 2) 1 (+ (fibbd (- n 1)) (fibbd (- n 2) #+end_src #+name: fibbd #+begin_src emacs-lisp :var n=2 :results silent (fibbd n) #+end_src | original | fibbd | |--+| |0 | #ERROR | |1 | #ERROR | |2 | #ERROR | |3 | #ERROR | |4 | #ERROR | |5 | #ERROR | |6 | #ERROR | |7 | #ERROR | |8 | #ERROR | |9 | #ERROR | #+TBLFM: $2='(org-sbe 'fibbd (n $1)) Did the syntax of org-sbe change or am just missing something obvious here? unquote the fibbd or double quote it --8---cut here---start-8--- | original | fibbd | |--+---| |0 | 1 | |1 | 1 | |2 | 2 | |3 | 3 | |4 | 5 | |5 | 8 | |6 |13 | |7 |21 | |8 |34 | |9 |55 | #+TBLFM: $2='(org-sbe fibbd (n $1)) --8---cut here---end---8--- or --8---cut here---start-8--- #+TBLFM: $2='(org-sbe fibbd (n $1)) --8---cut here---end---8--- HTH, Chuck
[O] Error Embedding SQL Source from code block into R Source of Another (noweb)
Dear List:
It is possible to embed SQL code as a string to be evaluated in R. I am
interested in formatting the SQL code in its own source code block, with
its own syntax highlighting and editing mode (C-c ').
The first time I run the code, I am prompted for R starting directory,
but I get an error:
---
load ESSR: + + + Error: unexpected string constant in:
source('~/.emacs.d/elpa/ess-20140913.1153/etc/ESSR/R/.load.R',
local=TRUE) #define load.ESSR
load.ESSR('
---
and the console locks. I can C-g to get out of it, and then
re-evaluate, and the code prints what I expect -- the text of the SQL
command.
Is this the right way to go about this? Have I discovered a bug, or
perhaps accidentally a wrong way to get the right answer?
Is this an ESS problem, and not an orgmode problem, per se? My ESS
normally starts up fine, so I thought I would ask on this list first.
A minimal example (first failing, second evaluation giving expected
output) follows.
Best regards,
Eric
Debian GNU/Linux (jessie)
Emacs 24.3.93
Org current from org repo
ESS from MELPA (ca. 14.09)
R 3.1.1 compiled from source
- SESSION -
#+TITLE: Test SQL Code
#+AUTHOR: Eric Brown
#+EMAIL: br...@fastmail.fm
#+PROPERTY: session *R*
#+PROPERTY: cache no
#+name: sqlsource
#+begin_src sql :engine postgresql :eval yes :noweb-ref sqlsrc :exports code
:results none
select
*
from
t
limit
10
#+end_src
#+name: rsource
#+begin_src R :noweb yes :results output :exports both
input - '
sqlsrc
'
cat(input)
# dbGetQuery(connectionHandle, input)
#+end_src
#+RESULTS: rsource
:
: select
: *
: from
: t
: limit
: 10
-
Re: [O] orgmode in drupal
Thanks for this -- definitely interesting, but I'll have no time to try it out for a while. Yours, Christian David Arroyo Menendez writes: Hello, Perhaps in this mailing list there are some drupal admin who wants upload his files to drupal. I've a project to make it :) https://www.drupal.org/node/1977240. Regards.
