Re: [O] [PATCH] inline src block results can be removed
On Wed, 12 Nov 2014, Andreas Leha wrote:
Hi Chuck,
"Charles C. Berry" writes:
Inline src blocks cannot update their results --- causing some of us
heaadaches [1].
[deleted announcement of fix]
First of all: Thanks a lot! I'll (try to find time to) test these
patches.
Yes. Please try them.
Reading your description, I already have a first further feature
request, though ;-) Or rather a question.
It sounds as if your patches turn inline source into limited source
blocks in terms of adherence to header arguments. Given that most
likely there are not too many header arguments on inline source blocks,
this might not be a huge problem.
See below ":results latex" and friends seem to work as before.
It would be nice if others could point out any hiccups.
But my first question would be about ':results raw', as I never had a
case where I wanted the results of my inline source block to be
\texttt{}.
If you start with src_R{1+2} and evaluate it, you get the `@@babel:3@@'.
If you modify that to src_R[:results raw]{1+2} and evaluate it, the
`@@...@@' goes away and is replaced with the raw result `3'. Of course,
you are then stuck with that and cannot easily make further revisions.
However, with modest tooling, you can set up the :results header
bufferwide so that when you want to export, the '@@...@@' will be removed
from the temp buffer and the export will use `raw' results for inline src
blocks.
Or you can make a custom version of org-latex-export-snippet that uses a
different transcoder. Or you can just return the raw text and the
`@@babel:3@@' will end up in the *.tex as 3. Just change the last line to
(org-element-property :value export-snippet)[more parens] to get the raw
value all the time.
I guess, my question is: Do your patches restrict the use of babel
headers on inline source blocks. And if so, is that just a matter of
'not implemented yet' or is there a fundamental issue here?
I do not think things are worse with the patches.
src_R[:results latex]{1+2} is the same with the patches, I think. But
ideally, that would generate something that acts like @@latex:3@@ and that
could be safely removed.
In terms of implementation, if one wanted fine control over each inline
src block, more tooling will be needed. Export snippets do not have lots
of stops and whistles to play with, just a :back-end and a :value and
location info. One could use `org-export-get-previous-element' to look up
the header args and figure out what to do next. But that can get hairy if
the header arg needs further processing. Considering the limited use to
which inline src blocks are put, it probably is not coding up loads of
tricky features.
Best,
Chuck
Re: [O] Embedded LaTeX does not work with Unicode quotes
Marcin Borkowski writes: > Hi list, > > I have this: „$n\eps\le b$”, and it seems not to be recognized as a > LaTeX fragment. The manual says: > > > To avoid conflicts with currency specifications, single `$' characters > are only recognized as math delimiters if the enclosed text contains at > most two line breaks, is directly attached to the `$' characters with no > whitespace in between, and if the closing `$' is followed by whitespace, > punctuation or a dash. > > > When I C-u C-x = on the closing quote, I get > > > ... >syntax: . which means: punctuation > ... > > > so I don't know why it is not recognized as punctuation. Consequently, > it is exported verbatim (with `\$') into LaTeX, and also (obviously) C-c > C-x C-l does not fontify it. When I change ” into " (the ASCII #x22 > quote), everything is ok. > The $...$ construct is recognized by a regexp which, while complicated, is not complicated enough to recognize everything that's marked "punctuation" in the syntax tables. Look for org-latex-regexps in org.el (and note that the regexp for "$" is about twice as long as the next longest regexp - the one for "begin"). The others (for \(...\), \[...\] and $$..$$) are fairly trivial. > My questions: > > 1. Isn't it a bug? > Yes, probably - but looking at the regexp, I cringe: I don't want to even try deciphering it, let alone change it - life's too short... > 2. If not, what can I do to in my config so that it is recognized > properly? > > PS. I just recalled that using \(...\) should help, and indeed it does. > Still, I'm curious about the answer to my questions (now that I > remembered a workaround, especially #1). > That is indeed the best solution. -- Nick
[O] Newb me wrote bash script for TOC, for Org-mode in Github repos.
I think I have an okay bash script (below) for producing a TOC for notes I keep
in Github in Org-mode format. It produce bulleted links like
#+BEGIN_SRC org
- [[./fileA.org][fileA.org]]
- [[./dir][dir/]]
- [[./dir/fileB.org][fileB.org]]
#+END_SRC
I run this script from a README.org file in my Github repo. My interaction with
Github is a little frustrating, I think an extra blank line after =#+RESULTS:=
prevents Github from omitting the entire list.
Here is the script, it's more-or-less a very early program in my side project
to learn programming. I think I have some inconsistencies in choosing to ""
quote things. But it doesn't seem to be a problem. Hopefully I can learn Perl
one day so I can do it in one line ;).
I would have written it in Emacs Lisp since that is where I intended to use it,
but I am still a little intimidated to learn this. Perhaps I will try to
convert this to Emacs Lisp as an exercise at some point.
Any comments are appreciated! (The choice of indentation as spaces is not the
Org-mode convention (1,2,3... instead of 0,2,4...), but I choose simplicity in
my scripts for now.)
#+BEGIN_SRC emacs-lisp
(setq org-babel-sh-command "bash")
#+END_SRC
#+BEGIN_SRC sh :results scalar raw replace
#!/bin/bash
echo
PrevDepth=1
PrevDir="."
find -regex '.*\.org' |
while read file
do
Slashes="${file//[^\/]}"
Depth="${#Slashes}"
Dir=${file%/*}
if [[ $Depth -eq $PrevDepth && "$Dir" != "$PrevDir" ]] || \
[[ $Depth -gt $PrevDepth ]]
then
for (( i=1 ; i <= Depth-1 ; i++ )); do echo -n ' '; done
echo "- [[$Dir][${Dir##*/}/]]"
fi
for (( i=1; i<=Depth; i++ )); do echo -n ' '; done
echo -n "- [[$file][${file##*/}]]"
echo
PrevDepth=$Depth
PrevDir=$Dir
done
#+END_SRC
--
Brady
Re: [O] Repeated teaching classes and stopping date
Rasmus gmx.us> writes: > Also check > `org-clone-subtree-with-time-shift'. FWIW, I always create a separate subtree, with a single timestamp, for every class session. Advantages: - Individual status for each session: DONE, POSTPONED or CANCELED. - If a single class in a series needs to be rescheduled, it's easy. - I can add notes under the subtree, to plan for the session or note important things that happened in class. So then my calendar is not just a calendar -- it also helps with content organization. (That IMO is the whole point of org-mode: it's not just a calendar!) YMMV of course. hjh
Re: [O] [PATCH] inline src block results can be removed
Hi Chuck,
"Charles C. Berry" writes:
> Inline src blocks cannot update their results --- causing some of us
> heaadaches [1].
>
> These patches fix that by placing the result of an inline src block in
> an export snippet with a faux :back-end called 'babel'.
>
> So C-c C-c with point on src_R{1+2} will insert
> `@@babel:3@@'. Updating the contents of the inline src block and
> retyping C-c C-c will update the snippet. On export, these snippets
> are rendered using the verbatim transcoder, e.g. \texttt{3} for latex
> backends.
>
> Support for most backends is provided.
>
> org-babel-execute-buffer will also update such snippets.
>
> Please try these patches out.
>
> Remember to recompile the files that these patches modify or you will
> get wrong results when you restart emacs.
>
> HTH,
>
> Chuck
>
> Footnote: [1] http://thread.gmane.org/gmane.emacs.orgmode/92481
>
> p.s. If these patchesa are (eventually) acceptable, FSF has a
> copyright assignment for me on file.
First of all: Thanks a lot! I'll (try to find time to) test these
patches.
Reading your description, I already have a first further feature
request, though ;-) Or rather a question.
It sounds as if your patches turn inline source into limited source
blocks in terms of adherence to header arguments. Given that most
likely there are not too many header arguments on inline source blocks,
this might not be a huge problem.
But my first question would be about ':results raw', as I never had a
case where I wanted the results of my inline source block to be
\texttt{}.
I guess, my question is: Do your patches restrict the use of babel
headers on inline source blocks. And if so, is that just a matter of
'not implemented yet' or is there a fundamental issue here?
Thanks,
Andreas
[O] [PATCH] inline src block results can be removed
Inline src blocks cannot update their results --- causing some of us
heaadaches [1].
These patches fix that by placing the result of an inline src block in an
export snippet with a faux :back-end called 'babel'.
So C-c C-c with point on src_R{1+2} will insert `@@babel:3@@'. Updating
the contents of the inline src block and retyping C-c C-c will update the
snippet. On export, these snippets are rendered using the verbatim
transcoder, e.g. \texttt{3} for latex backends.
Support for most backends is provided.
org-babel-execute-buffer will also update such snippets.
Please try these patches out.
Remember to recompile the files that these patches modify or you will get
wrong results when you restart emacs.
HTH,
Chuck
Footnote: [1] http://thread.gmane.org/gmane.emacs.orgmode/92481
p.s. If these patchesa are (eventually) acceptable, FSF has a copyright
assignment for me on file.From 78a365d223a969f407efa524b0c45e701b4ae908 Mon Sep 17 00:00:00 2001
From: chasberry
Date: Tue, 11 Nov 2014 12:53:01 -0800
Subject: [PATCH 1/5] lisp/ob-exp.el: Enable removable inline src results
* lisp/ob-exp.el (org-babel-exp-do-export): Clean `@@babel:result@@'
after inline src block.
---
lisp/ob-exp.el | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/lisp/ob-exp.el b/lisp/ob-exp.el
index edb889c..83359e5 100644
--- a/lisp/ob-exp.el
+++ b/lisp/ob-exp.el
@@ -315,7 +315,9 @@ The function respects the value of the :exports header
argument."
(let ((silently (lambda () (let ((session (cdr (assoc :session (nth 2
info)
(when (not (and session (equal "none" session)))
(org-babel-exp-results info type 'silent)
- (clean (lambda () (unless (eq type 'inline) (org-babel-remove-result
info)
+ (clean (lambda () (if (eq type 'inline)
+ (org-babel-delete-babel-snippet info)
+ (org-babel-remove-result info)
(case (intern (or (cdr (assoc :exports (nth 2 info))) "code"))
('none (funcall silently) (funcall clean) "")
('code (funcall silently) (funcall clean) (org-babel-exp-code info type))
--
1.9.3 (Apple Git-50)
From 5e84279ff5dbbcb3e9c8f89c88afc15441286aec Mon Sep 17 00:00:00 2001
From: chasberry
Date: Tue, 11 Nov 2014 13:01:22 -0800
Subject: [PATCH 2/5] Inline src blocks are export-snippets
* lisp/ox-latex.el (org-latex-export-snippet): Treat the babel
`:back-end' export-snippet value as verbatim.
* lisp/ox-beamer.el (org-beamer-export-snippet): Treat the babel
`:back-end' export-snippet value as verbatim.
* lisp/ox-html.el (org-html-export-snippet): Treat the babel
`:back-end' export-snippet value as verbatim.
* lisp/ox-ascii.el (org-ascii-export-snippet): Treat the babel
`:back-end' export-snippet value as verbatim.
* lisp/ox-texinfo.el (org-texinfo-export-snippet): Treat the babel
`:back-end' export-snippet value as verbatim.
* lisp/ox-odt.el (org-odt-export-snippet): Treat the babel
`:back-end' export-snippet value as verbatim.
* lisp/ox-man.el (org-man-export-snippet): Treat the babel
`:back-end' export-snippet value as verbatim.
---
lisp/ox-ascii.el | 8 ++--
lisp/ox-beamer.el | 2 ++
lisp/ox-html.el| 7 +--
lisp/ox-latex.el | 8 +---
lisp/ox-man.el | 8 ++--
lisp/ox-odt.el | 8 +---
lisp/ox-texinfo.el | 7 +--
7 files changed, 34 insertions(+), 14 deletions(-)
diff --git a/lisp/ox-ascii.el b/lisp/ox-ascii.el
index daad00f..695277c 100644
--- a/lisp/ox-ascii.el
+++ b/lisp/ox-ascii.el
@@ -1213,8 +1213,12 @@ CONTENTS is nil. INFO is a plist holding contextual
information."
(defun org-ascii-export-snippet (export-snippet contents info)
"Transcode a EXPORT-SNIPPET object from Org to ASCII.
CONTENTS is nil. INFO is a plist holding contextual information."
- (when (eq (org-export-snippet-backend export-snippet) 'ascii)
-(org-element-property :value export-snippet)))
+ (let ((backend (org-export-snippet-backend export-snippet)))
+(cond ((eq backend 'ascii)
+ (org-element-property :value export-snippet))
+ ((eq backend 'babel)
+ (org-ascii-verbatim export-snippet contents info)
+
Export Block
diff --git a/lisp/ox-beamer.el b/lisp/ox-beamer.el
index 15bbce2..9f71cbb 100644
--- a/lisp/ox-beamer.el
+++ b/lisp/ox-beamer.el
@@ -291,6 +291,8 @@ channel."
(value (org-element-property :value export-snippet)))
;; Only "latex" and "beamer" snippets are retained.
(cond ((eq backend 'latex) value)
+ ((eq backend 'babel)
+ (org-latex-verbatim export-snippet contents info))
;; Ignore "beamer" snippets specifying overlays.
((and (eq backend 'beamer)
(or (org-export-get-previous-element export-snippet info)
diff --git a/lisp/ox-html.el b/lisp/ox-html.el
index 20d09eb..e377687 100644
--- a/lisp/ox-html.el
+++ b/lisp/ox-html.el
@@ -22
[O] pdf images in html export
Hi all, how would I export an org file containing [[file:./myimage.pdf]] to html so that a say png version myimage.pdf is inlined in the html which links to the pdf? I guess it should be possible to run imagemagick on all pdf links during export somehow. Any help highly appreciated. Many thanks, Andreas
Re: [O] org-insert-heading
Luke Crook balooga.com> writes: > However at least in my installation (Emacs 34.3, org-mode 8.2.10), Emacs 24.3 obviously.
[O] org-insert-heading
Question concerning the behaviour of org-insert-heading; The manual states the following. >> If the command is used at the end of a folded subtree (i.e., behind the ellipses at the end of a headline), then a headline will be inserted after the end of the subtree. << However at least in my installation (Emacs 34.3, org-mode 8.2.10), the new heading is created prior to the ellipses. For example * Heading folded... ^ cursor here, then M- results in the following. * Heading folded * ... ^ cursor here
[O] Embedded LaTeX does not work with Unicode quotes
Hi list,
I have this: „$n\eps\le b$”, and it seems not to be recognized as a
LaTeX fragment. The manual says:
To avoid conflicts with currency specifications, single `$' characters
are only recognized as math delimiters if the enclosed text contains at
most two line breaks, is directly attached to the `$' characters with no
whitespace in between, and if the closing `$' is followed by whitespace,
punctuation or a dash.
When I C-u C-x = on the closing quote, I get
position: 54465 of 108125 (50%), restriction: <52496-56766>,
column: 152
character: ” (displayed as ”) (codepoint 8221, #o20035, #x201d)
preferred charset: unicode (Unicode (ISO10646))
code point in charset: 0x201D
syntax: .which means: punctuation
category: .:Base, c:Chinese, h:Korean, j:Japanese
to input: type "C-x 8 RET HEX-CODEPOINT" or "C-x 8 RET NAME"
buffer code: #xE2 #x80 #x9D
file code: #xE2 #x80 #x9D (encoded by coding system utf-8-unix)
display: by this font (glyph code)
xft:-unknown-Ubuntu Mono-normal-normal-normal-*-17-*-*-*-m-0-iso10646-1
(#x71)
Character code properties: customize what to show
name: RIGHT DOUBLE QUOTATION MARK
old-name: DOUBLE COMMA QUOTATION MARK
general-category: Pf (Punctuation, Final quote)
decomposition: (8221) ('”')
There are text properties here:
fontifiedt
so I don't know why it is not recognized as punctuation. Consequently,
it is exported verbatim (with `\$') into LaTeX, and also (obviously) C-c
C-x C-l does not fontify it. When I change ” into " (the ASCII #x22
quote), everything is ok.
My questions:
1. Isn't it a bug?
2. If not, what can I do to in my config so that it is recognized
properly?
PS. I just recalled that using \(...\) should help, and indeed it does.
Still, I'm curious about the answer to my questions (now that I
remembered a workaround, especially #1).
TIA,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
Re: [O] A file with 'org-mode rot'?
Hi Karl, Karl Voit writes: > In the recent weeks I had the issue that LOGBOOK drawers were > moved before PROPERTIES drawers ending up in double PROPERTIES > drawers where the second one is ignored (habit, ...) or just one > LOGBOOK drawer followed by one ignored PROPERTIES drawer: > > * example heading with two PROPERTIES drawers > :PROPERTIES: > :CREATED: [2014-08-02 Sat 11:37] > :END: > :LOGBOOK:... > :PROPERTIES: > :CREATED: [2014-07-16 Mon 14:42] > :STYLE: habit > :END: > > * example heading with LOGBOOK before PROPERTIES and thus being ignored > :LOGBOOK:... > :PROPERTIES: > :CREATED: [2014-07-16 Mon 14:42] > :STYLE: habit > :END: > > (I am using (org-expiry-insinuate) to automatically create the > PROPERTIES drawer with the CREATED line if this matters here.) > > This results in a big mess on my agenda and I had to fix those > headings semi-manually. Very annoying! > > I don't have a clue, what causes this behavior since there is only a > (large) sub-set of my headings that got this mix-up. There has been an incompatible change for 8.3 about a month ago. Since then property drawers need "to be located right after a headline and its planning line, when applicable." See file etc/ORG-NEWS and commit 1aad53b. Note also the org-repair-property-drawers function there. HTH, Marco -- http://www.wahlzone.de GPG: 0x0A3AE6F2
[O] Agenda Help
I've been trying to work out a particular agenda for some time now. Due to
some known bugs in sorting with IA time stamps in some of the commands, I've
been forced to branch a little abroad. I've got most of things worked out, but
need a little guidance on the last remaining piece.
Here's the custom agenda command:
("Z" "Last Worked skip" ((alltodo ""
((org-agenda-skip-function (lambda nil
(org-agenda-skip-entry-if (quote notregexp) "\\:LastWorked\\:")))
(org-agenda-sticky nil)
(org-agenda-sorting-strategy (quote (tsia-down todo-state-down)))
Some, but not all, headlines have a 'LastWorked' property holding an IA time
stamp
Some, but not all, headlines with a 'LastWorked' property have a 'TODO' status
IE meetings get an active datestamp but not a TODO status,
And have a 'LastWorked' property based on when meeting occurred.
The above command will pick up all the headlines with a TODO status and a
LastWorked Property, sort by LastWorked, and displayed.
This is great.
What I also need is a way to pick up ALL headlines with a LastWorked Property,
including headlines with closed TODO stati (IE DONE)
Using the 's' type agenda picks up all the right items, but the sort on
'LastWorked' fails
Any ideas?
Subhan
This message is intended for the sole use of the individual and entity to which
it is addressed and may contain information that is privileged, confidential
and exempt from disclosure under applicable law. If you are not the intended
addressee, nor authorized to receive for the intended addressee, you are hereby
notified that you may not use, copy, disclose or distribute to anyone the
message or any information contained in the message. If you have received this
message in error, please immediately advise the sender by reply email and
delete the message. Thank you.
Re: [O] orgtbl-aggregate on Melpa
Le 11/11/2014 14:44, Eric S Fraga a écrit : > I know you've put it on MELPA but could you also add it to org/contrib > maybe? I have issues with MELPA due to trying to share configurations > across systems that run different versions of Emacs... > Sure! I don't have write access to org-mode/contrib. If a maintainer helps me, I would be more than pleased to add it. Thanks Eric. Thierry
Re: [O] A file with 'org-mode rot'?
Hi! * Karl Voit wrote: > Hello Sharon! > > * Sharon Kimble wrote: >> >> So how can I keep a file 'healthy' and working well over many months please? > > I am facing "weird" things as well. Mainly performance drop when > doing (very) simple things like adding | in front of a table line, > changing to the next table column, marking tasks as DONE, archiving > tasks, and so on. Fun fact: this is still an issue but only on my Linux machine. My Windows Emacs performs fine with tables. > This is why I asked here for an Org-mode syntax checker a couple of > days ago. There does not seem to exist such a thing. Another example: In the recent weeks I had the issue that LOGBOOK drawers were moved before PROPERTIES drawers ending up in double PROPERTIES drawers where the second one is ignored (habit, ...) or just one LOGBOOK drawer followed by one ignored PROPERTIES drawer: * example heading with two PROPERTIES drawers :PROPERTIES: :CREATED: [2014-08-02 Sat 11:37] :END: :LOGBOOK:... :PROPERTIES: :CREATED: [2014-07-16 Mon 14:42] :STYLE: habit :END: * example heading with LOGBOOK before PROPERTIES and thus being ignored :LOGBOOK:... :PROPERTIES: :CREATED: [2014-07-16 Mon 14:42] :STYLE: habit :END: (I am using (org-expiry-insinuate) to automatically create the PROPERTIES drawer with the CREATED line if this matters here.) This results in a big mess on my agenda and I had to fix those headings semi-manually. Very annoying! I don't have a clue, what causes this behavior since there is only a (large) sub-set of my headings that got this mix-up. Also: I recognized that many older headings were changed that way that all empty lines were removed. I got the suspicion that generating some Agendas or the org-mobile export might correlate with the time-stamps of the modifications. Besides my personal issues above: is there some kind of automatically regression testing with real-world Org-mode files and non-default settings? I love this community! However, I get the impression that with every "git pull", I end up being tester of a couple of new issues. :-( Thinking about getting rid of the git repository and (only) using "stable" Org releases ...
Re: [O] Inline code :results replace not working
On Mon, Nov 10, 2014 at 7:53 PM, Ista Zahn wrote: > The problem is that I don't want > blocks to be evaluated on export (too time consuming in many cases). > So I turn that off, and either evaluate the blocks one at a time (I'm > aware of the dangers of this, not my point here) or call > org-babel-execute-buffer. Everytime I do that I get duplicate output > from inline code. As far as I can see inline code + > org-babel-execute-buffer is incompatible, which is why I gave up on > the former. Gotcha. The approach that I use requires the operator to keep the object available and in the correct state, in the environment, so that it is available during export. This is probably pretty typical. It requires more forethought as there are more opportunities for mistakes, versus generating the inline output at evaluation time.
Re: [O] orgtbl-aggregate on Melpa
Eric S Fraga writes: > I know you've put it on MELPA but could you also add it to org/contrib > maybe? I have issues with MELPA due to trying to share configurations > across systems that run different versions of Emacs... Yes. It looks useful, but honestly I won't be bothered using it, if I have to install is separately... —Rasmus -- It was you, Jezebel, it was you
Re: [O] Repeated teaching classes and stopping date
Hi Xavier! * Xavier Garrido wrote: > Hi Rasmus, > > Le 10/11/2014 18:37, Rasmus a écrit : >> Hi Xavier, >> >> Xavier Garrido writes: >> >>> * [Master 1] Nuclear & particle class >>> <2015-01-21 mer. 14:00-16:00 +1w>--<2015-03-22 dim.> > > I will try to slightly modify the ical2org.awk file from Eric Fraga > http://orgmode.org/worg/code/awk/ical2org.awk to automatically converts > ical file into org and to manage this repeating task. I have to say that > it is a bit frustrating that the syntax -- > is not working because it is pretty simple and quite elegant. I was there as well[1]. Meanwhile, I prefer the clone-method because I am able to cancel/annotate single events pretty elegant which would not be possible with recurring events. Give it a try :-) [1] http://search.gmane.org/?query=org-clone-subtree-with-time-shift+Voit&group=gmane.emacs.orgmode
Re: [O] orgtbl-aggregate on Melpa
On Tuesday, 11 Nov 2014 at 12:26, Thierry Banel wrote: > Hi The List > > My orgtbl-aggregate package is now available on MELPA. Thanks for this! I could have made very good use of this recently for a paper I wrote, especially the ability to aggregate by blocks defined by hlines. I'm sure I'll be wanting to use this again soon. I know you've put it on MELPA but could you also add it to org/contrib maybe? I have issues with MELPA due to trying to share configurations across systems that run different versions of Emacs... Thanks again, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.4.50.1, Org release_8.3beta-558-g83d8a2
[O] orgtbl-aggregate on Melpa
Hi The List
My orgtbl-aggregate package is now available on MELPA.
It creates an aggragated Org table out of a source table.
Example: here are the 15 largest rivers in the World
(source: Wikipedia "List_of_rivers_by_length").
#+tblname: rivers
| River | Continent| Length | Discharge |
|+--++---|
| Nile-Kagera| Africa | 6853 | 5100 |
| Amazon-Ucayali-Apurímac| SouthAmerica | 6400 |219000 |
| Yangtze (Chang Jiang) | Asia | 6415 | 31900 |
| Mississippi–Missouri–Jefferson | NorthAmerica | 6275 | 16200 |
| Yenisei-Angara-Selenge | Asia | 5539 | 19600 |
| Yellow River (Huang He)| Asia | 5464 | 2110 |
| Ob-Irtysh | Asia | 5410 | 12800 |
| Paraná-Río de la Plata | SouthAmerica | 4880 | 18000 |
| Congo-Chambeshi (Zaïre)| Africa | 4700 | 41800 |
| Amur-Argun (Heilong Jiang) | Asia | | 11400 |
| Lena | Asia | 4400 | 17100 |
| Mekong (Lancang Jiang) | Asia | 4350 | 16000 |
| Mackenzie-Slave-Peace-Finlay | NorthAmerica | 4241 | 10300 |
| Niger | Africa | 4200 | 9570 |
| Murray-Darling | Australia| 3672 | 767 |
We want to aggregate them by continents, with counts, means, and max.
To do so type:
M-x org-insert-dblock:aggregate
or:
C-c C-x i
#+BEGIN: aggregate :table "rivers" :cols "Continent count() mean(Length)
max(Discharge)"
| Continent| count() | mean(Length) | max(Discharge) |
|--+-+--+|
| Africa | 3 | 5251 | 41800 |
| SouthAmerica | 2 | 5640 | 219000 |
| Asia | 7 | 5146 | 31900 |
| NorthAmerica | 2 | 5258 | 16200 |
| Australia| 1 | 3672 |767 |
#+END:
Documentation here:
https://github.com/tbanel/orgaggregate/blob/master/README.org
-
To enable MELPA, add those lines to your .emacs:
(require 'package)
(add-to-list 'package-archives '("melpa" .
"http://melpa.milkbox.net/packages/";) t)
(package-initialize)
Then browse more than 2000 available packages
(including the latest Org Mode and almost 80 Org-related packages)
by typing:
M-x package-list-packages
-
Comments welcome
Have fun
Thierry Banel
Re: [O] Repeated teaching classes and stopping date
Xavier Garrido writes: > Hi Rasmus, > > Le 10/11/2014 18:37, Rasmus a écrit : >> Hi Xavier, >> >> Xavier Garrido writes: >> >>> I'm trying to move to =org-agenda= and I'm converting some of my >>> Google Calendar entries into Org agenda entries. I'm facing an issue >>> with repeated tasks and how to properly stop the event. Consider the >>> following entry : >>> >>> * [Master 1] Nuclear & particle class >>> <2015-01-21 mer. 14:00-16:00 +1w>--<2015-03-22 dim.> >>> >>> For me it means, I will teach every week @ 14:00 to 16:00 until the >>> 22th of March. I am surely doing something bad since the events >>> actually appear every day until the 22th of March. It basically works >>> when I remove the --<2015-03-22 dim.> but then how to stop the >>> repeated tasks. >>> >>> Sorry if the answer is obvious but I have read org-mode manual >>> (http://orgmode.org/manual/Repeated-tasks.html) and other "timestamp" >>> related pages and I didn't find a way to do that. >> >> Did you check `org-class'? Also check >> `org-clone-subtree-with-time-shift'. If you search for the latter you >> will find a recent discussion on what I think is the topic you are >> interested in. >> > > Thanks for the hints, I should have read the FAQ first since my > problem is clearly addressed (here for example > http://orgmode.org/worg/org-faq.html#diary-sexp-in-org-files). In SO > this guy also have the same problem > http://stackoverflow.com/questions/2464598/org-mode-schedule-weekly-event-for-a-period They also point to `org-class` in one of the answers. > I will try to slightly modify the ical2org.awk file from Eric Fraga > http://orgmode.org/worg/code/awk/ical2org.awk to automatically > converts ical file into org and to manage this repeating task. If you want... There are already two functions that were created for this stuff. > I have to say that it is a bit frustrating that the syntax +1w>-- is not working because it is pretty simple and > quite elegant. Patch welcome! I can see the syntax being somewhat intuitive, but I think maybe the double use of "--" is confusing. Why not: +1w> until Anyway. . . Cheers, Rasmus -- Bang bang
Re: [O] Repeated teaching classes and stopping date
Hi Rasmus, Le 10/11/2014 18:37, Rasmus a écrit : Hi Xavier, Xavier Garrido writes: I'm trying to move to =org-agenda= and I'm converting some of my Google Calendar entries into Org agenda entries. I'm facing an issue with repeated tasks and how to properly stop the event. Consider the following entry : * [Master 1] Nuclear & particle class <2015-01-21 mer. 14:00-16:00 +1w>--<2015-03-22 dim.> For me it means, I will teach every week @ 14:00 to 16:00 until the 22th of March. I am surely doing something bad since the events actually appear every day until the 22th of March. It basically works when I remove the --<2015-03-22 dim.> but then how to stop the repeated tasks. Sorry if the answer is obvious but I have read org-mode manual (http://orgmode.org/manual/Repeated-tasks.html) and other "timestamp" related pages and I didn't find a way to do that. Did you check `org-class'? Also check `org-clone-subtree-with-time-shift'. If you search for the latter you will find a recent discussion on what I think is the topic you are interested in. Thanks for the hints, I should have read the FAQ first since my problem is clearly addressed (here for example http://orgmode.org/worg/org-faq.html#diary-sexp-in-org-files). In SO this guy also have the same problem http://stackoverflow.com/questions/2464598/org-mode-schedule-weekly-event-for-a-period I will try to slightly modify the ical2org.awk file from Eric Fraga http://orgmode.org/worg/code/awk/ical2org.awk to automatically converts ical file into org and to manage this repeating task. I have to say that it is a bit frustrating that the syntax -- is not working because it is pretty simple and quite elegant. Cheers, Xavier Hope it helps, Rasmus -- | |__ GARRIDO Xavier Laboratoire de l'Accélérateur Linéaire /\ NEMO Université Paris-Sud 11 /--\garr...@lal.in2p3.fr UMR 8607 | garr...@in2p3.fr Batiment 200 |__ +33 1.64.46.84.2891898 Orsay Cedex, France
