Re: [O] Babel: communicating irregular data to R source-code block
Eric Schulte writes:
>> If I add fill=TRUE to that (on a git branch), then I get this:
>>
>> #+RESULTS: pascals-triangle
>> | 1 | ||| | |
>> | 1 | 1 ||| | |
>> | 1 | 2 | 1 || | |
>> | 1 | 3 | 3 | 1 | | |
>> | 1 | 4 | 6 | 4 | 1 | |
>> | 1 | 5 | 10 | 10 | 5 | 1 |
>>
>> #+NAME: sanity-check
>> #+HEADER: :var sc_input=pascals-triangle
>> #+BEGIN_SRC R
>> sc_input
>> #+END_SRC
>> #+RESULTS: sanity-check
>>
>> | 1 | nil | nil | nil | nil |
>> | 1 | 1 | nil | nil | nil |
>> | 1 | 2 | 1 | nil | nil |
>> | 1 | 3 | 3 | 1 | nil |
>> | 1 | 4 | 6 | 4 | 1 |
>> | 1 | 5 | 10 | 10 | 5 |
>> | 1 | nil | nil | nil | nil |
>>
>> which isn't correct, but gets past the scan error.
>>
>
> Hmm, this happens with my patch applied as well. It seems to me this
> *must* be an R error. The raw textual data pre-import has no such wrap.
>
> 1
> 1 1
> 1 2 1
> 1 3 3 1
> 1 4 6 4 1
> 1 5 10 10 5 1
>
> Why would R intentionally wrap a table at an arbitrary column?
>
>>
>> I'm in over my head here, but hope that my curiosity hasn't been too
>> noisy.
>>
>
> Me too. Unless someone who is familiar with the motivations and design
> decisions behind R's read.table function, I'm inclined to leave the
> current Org-mode code as is.
>
> Thanks,
The documentation of read.table has this:
The number of data columns is determined by looking at the first five
lines of input (or the whole file if it has less than five lines), or
from the length of col.names if it is specified and is longer. This
could conceivably be wrong if fill or blank.lines.skip are true, so
specify col.names if necessary (as in the ‘Examples’).
The example is this:
read.csv(tf, fill = TRUE, header = FALSE,
col.names = paste("V", seq_len(ncol), sep = ""))
where read.csv is a synonym of read.table with preset arguments.
This explains why the sixth line wraps.
Unfortunately, ncol passed to seq_len doesn't cooperate. I can hard
code the read.table call this way:
(format "%s <- read.table(\"%s\", header=%s, row.names=%s, sep=\"\\t\",
as.is=TRUE, fill=TRUE, col.names = paste(\"V\", seq_len(6), sep = \"\"))"
This works for the example with six columns:
#+RESULTS: pascals-triangle
| 1 | ||| | |
| 1 | 1 ||| | |
| 1 | 2 | 1 || | |
| 1 | 3 | 3 | 1 | | |
| 1 | 4 | 6 | 4 | 1 | |
| 1 | 5 | 10 | 10 | 5 | 1 |
#+NAME: sanity-check
#+HEADER: :var sc_input=pascals-triangle
#+BEGIN_SRC R
sc_input
#+END_SRC
#+RESULTS: sanity-check
| 1 | nil | nil | nil | nil | nil |
| 1 | 1 | nil | nil | nil | nil |
| 1 | 2 | 1 | nil | nil | nil |
| 1 | 3 | 3 | 1 | nil | nil |
| 1 | 4 | 6 | 4 | 1 | nil |
| 1 | 5 | 10 | 10 | 5 | 1 |
I think that seq_len(%s) passed the number of columns in the orgtbl-tsv
table might do the trick, but I don't know how to do this, or if this
information is available. I also don't have any idea what these changes
might do to regular tables.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
[O] Google Summer of Code -- 3 Org projects for our first participation!
Dear all, we will have 3 students hacking Org thanks to Google and the GSoC program. The list of all accepted projects can be checked here: http://www.google-melange.com/gsoc/projects/list/google/gsoc2012 Congratulations to Thorsten, Aurélien and Andrew who made it! And special thanks to Thorsten, who really pushed me into this. Here is a short description of these projects: Bugpile - a bugtracker for GNU Emacs Org-mode written in Elisp and Org-mode (Thorsten) The Bugpile project has two goals: 1. Develop a bugtracker (called Bugpile) for GNU Emacs Org-mode, using Elisp, Elnode, Org-mode, and a dVCS. 2. As part of the engineering process, abstract out a web-framework (called iOrg) based on these GNU Emacs technologies. A web-framework written in Elisp, with Org files used for database functionality, is a new approach that enables interactive web applications built on top of GNU Emacs. Bugpile is an example application, but useful in itself. Org-mode – Let Org-mode synchronize with online bug-tracking and todo-list services (Aurélien) There's currently no convenient way to manage services like Redmine, Bugzilla or GitHub issue tracking system in Org-mode. Org-mode already handles TODO-list pretty well, but there's no synchronization functionality for TODO-list services such as Toodledo or Google Tasks. The goal of the project is to let Org-mode import and export to these kind of services in a generic way so that new services can be added easily later on. Emacs-Orgmode Git merge tool for Org Files (Andrew Young) The purpose of the project is to create a specialized Git merge driver for plain text Org-Mode formatted files. A merge driver is a program which will combine two versions of a file based off of a common ancestor into a single file, marking conflicting changes within. A specialized merge driver for Org-Mode files will be able to leverage the structure to understand the effects of modifications on the integrity of sections. The merge driver will solidify Org-Mode as a tool for collaborative work. Eric Schulte will mentor Thorsten's project and I will mentor Aurélien's and Andrew's ones, with the help of Nicolas and Carsten. This is an exciting time for Org: no doubt that having people paid for hacking Org on a full-time basis will boost our favorite software. This is an exciting time for me as a maintainer and future mentor: no doubt that I will *learn* a lot, from both a technical and a human point of view - as usual. Now that my age and pseudo-marital position make me come home with a baguette every evening, it will be good to feel like a student again :) Thanks to all for your long-lasting commitment and support. Happy orging, -- Bastien
Re: [O] make update fails
Achim Gratz writes: > Achim Gratz writes: >> Will do. > > Here's that patch (and some more convenience targets). Also, the first > invocation of make will now create a local.mk configuration template if > it doesn't exist. You don't need to do anything if the defaults are > working for you, otherwise just edit whatever variable needs to be set > differently. Some more esoteric settings can be gleaned from > default.mk, this will probably be needed if you are on Windows and are > maybe missing some programs (some hints are in the comments). Applied, thanks! -- Bastien
Re: [O] [Feature Request] org-mobile edit:add nodes
Henning Weiss writes: > it turns out that there are a couple of problems with that particular > patch. Some issues have already been fixed with the help of someone > else from the mobileorg community, but more work is required. As soon > as it is functional (and hopefully stable) I will post a new patch. Please do -- thanks for the follow up! -- Bastien
Re: [O] Dimming ancestors in the agenda (relevant to indenting nested TODOs in agenda views)
Hi Eric, Eric Abrahamsen writes: > Okay, here's an attempt at indicating nested todos in the todo agenda > view. Sorry to come back to this old patch -- I tried it (I had to rework it to apply it against current git master) and it doesn't work, some calls go beyond `max-lisp-eval-depth' (I don't have a backtrace right now.) I marked the patch as "Not applicable" on the patchwork. If you are still interested in progress in this area and have something to test, please let us know. Thanks! -- Bastien
Re: [O] error on opening org-file with #+startup: indent
fkunze writes: > When I open an org file with #+startup: indent in the header, the cursor > immediately goes to the bottom of the buffer and can not be moved upward. I can't reproduce this error... > This behavior does not occur in Org 6.36. ... and that's surely why. Please update to a more recent version of Org, if possible. Thanks, -- Bastien
Re: [O] Makefile restructuring
Mike McLean writes: >> You can now easily keep multiple installations within the org directory >> if so desired (I do this myself for testing). > > What do you do to make that work? It sounds like an intriguing possibility. In a nutshell, I create multiple install directories (one for each version of Emacs and Org) via the use of a separate local.mk file for each install and set up the load-path in Emacs to select which one to use. HTH, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] [FYI/noise] GSoC 2012 & new email
On 23.4.2012, at 23:59, Thorsten Jolitz wrote: > > Hi List, > my GSoC 2012 proposal was accepted, so I'm going to spend this summer > implementing bugpile - a bugtracker for GNU Emacs Org-mode. > I use the opportunity to change to a different (more serious) email, > just in case you wonder. > > Thanks to Bastien and Eric for the support so far! And thanks to google for making this possible. People may say about Google what they want - I still think they are an amazing company for many reasons - not the least for doing the Google Summer of Code! - Carsten
Re: [O] [FYI/noise] GSoC 2012 & new email
On Tue, Apr 24, 2012 at 3:29 AM, Thorsten Jolitz wrote: > > Hi List, > my GSoC 2012 proposal was accepted, so I'm going to spend this summer > implementing bugpile - a bugtracker for GNU Emacs Org-mode. > I use the opportunity to change to a different (more serious) email, > just in case you wonder. Cool! Congratulations! Looking forward to see and use your work! All the Best! Puneeth
Re: [O] Default show all archived entries for agenda
On Apr 23, 2012, at 2:50 PM, Marcelo de Moraes Serpa wrote:
> Hi guys,
>
> How could I configure it so that the agenda always shows archived entries by
> default? It's a nice way to get a log of what I accomplished chronologically
> without having to keep a specific log file per se (work log, food log,
> whatever-log). I could always just use v A in the agenda filter, but I'd
> rather just make it the default if it's easy to do.
I have something similar to what you are looking for. I have a custom agenda
view that shows the clock check mode. The trick is the list of option settings
when defining the custom agenda view. (Do a describe-variable on
org-agenda-custom-commands).
Using this idea you could have several custom agenda views; a work-log that
selects on your work tag, sets archives mode, log mode, etc. and a second that
selects your food log tag and the same archives and log mode options, and so on
and so on.
HTH
("c" "Clock Review"
(
(agenda ""
(
(org-agenda-overriding-header "Clocking Review")
(org-agenda-archives-mode t)
(org-agenda-span 'day)
(org-agenda-show-log 'clockcheck)
(org-agenda-clockreport-mode t)))
)
)
> Thanks,
>
> - Marcelo.
Re: [O] Org tasks from gnus
On Apr 23, 2012, at 10:57 AM, Rasmus wrote: > jca+...@wxcvbn.org (Jérémie Courrèges-Anglas) writes: > >> Rasmus writes: >> [...] >>> As others said, use org-complete. Most of my TODOs link to a mail. >> [...] >> I think you meant org-capture, as described by your example setup. :) >> Org-capture works indeed fine for me. > > Sure, that's what I meant :) And here I was looking for an Org Mode feature (org-complete) that would have new to me :)
Re: [O] Makefile restructuring
On Apr 22, 2012, at 11:34 AM, Achim Gratz wrote:
> suvayu ali writes:
>> The above recipe works. But just "make", leaves the working tree without
>> lisp/org-install.el. From the log I see it explicitly deletes it, but
>> doesn't generate it again. A subsequent "make autoloads" is required to
>> get a working org setup. Is this expected behaviour?
>
> This is intentional. The autoloads are generated just before
> installing, since that's where they are needed. I really don't want to
> encourage further use of the git worktree as the "org installation",
> although it sort of works if you do a "make auto loads".
This makes sense, and I’ve asked the question on how best to handle for el-get
on Gihub. Meanwhile my original pull request has been merged, so for the moment
at least el-get uses the ("compile" "autoloads" "info") workflow. You are
correct that adding a make autoloads does work, I've used (and updated)
compiled org-mode straight from the work tree for a few days now. If there is a
better or more canonical way to do this, I'd be happy to change and work the
changes back into el-get where I can.
> You can now easily keep multiple installations within the org directory
> if so desired (I do this myself for testing). Using the worktree
> instead can lead to very hard to track bugs when the autoload files get
> out of sync with the sources. This is the reason I always remove them
> before compilation and I should probably remove them just after
> installation as well.
What do you do to make that work? It sounds like an intriguing possibility.
Re: [O] Babel: communicating irregular data to R source-code block
> If I add fill=TRUE to that (on a git branch), then I get this: > > #+RESULTS: pascals-triangle > | 1 | ||| | | > | 1 | 1 ||| | | > | 1 | 2 | 1 || | | > | 1 | 3 | 3 | 1 | | | > | 1 | 4 | 6 | 4 | 1 | | > | 1 | 5 | 10 | 10 | 5 | 1 | > > #+NAME: sanity-check > #+HEADER: :var sc_input=pascals-triangle > #+BEGIN_SRC R > sc_input > #+END_SRC > #+RESULTS: sanity-check > > | 1 | nil | nil | nil | nil | > | 1 | 1 | nil | nil | nil | > | 1 | 2 | 1 | nil | nil | > | 1 | 3 | 3 | 1 | nil | > | 1 | 4 | 6 | 4 | 1 | > | 1 | 5 | 10 | 10 | 5 | > | 1 | nil | nil | nil | nil | > > which isn't correct, but gets past the scan error. > Hmm, this happens with my patch applied as well. It seems to me this *must* be an R error. The raw textual data pre-import has no such wrap. 1 1 1 1 2 1 1 3 3 1 1 4 6 4 1 1 5 10 10 5 1 Why would R intentionally wrap a table at an arbitrary column? > > I'm in over my head here, but hope that my curiosity hasn't been too > noisy. > Me too. Unless someone who is familiar with the motivations and design decisions behind R's read.table function, I'm inclined to leave the current Org-mode code as is. Thanks, -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Babel: communicating irregular data to R source-code block
Michael Hannon writes:
> Greetings. I'm sorry to belabor this, but I thought I had found a relatively
> clean way to pass a "ragged" table to an R source-code block. Simple answer:
> add the "fill=TRUE" option to the read.table function. Please see the
> appended for the log of an R session that does what I want.
>
> I then tried to do the same thing in an R source-code block:
>
> #+RESULTS: pascals_triangle
> | 1 | | | | | |
> | 1 | 1 | | | | |
> | 1 | 2 | 1 | | | |
> | 1 | 3 | 3 | 1 | | |
> | 1 | 4 | 6 | 4 | 1 | |
> | 1 | 5 | 10 | 10 | 5 | 1 |
>
>
> #+NAME: sanity-check(sc_input=pascals_triangle)
> #+BEGIN_SRC R
>
> pt <- read.table(sc_input, fill=TRUE)
> rowSums(pt)
>
> #+END_SRC
>
> Unfortunately, this still results in the "error" that the first line did not
> contain five elements:
>
> <<
>> Error in scan(file, what, nmax, sep, dec, quote, skip, nlines, na.strings,
>> :
> line 1 did not have 5 elements
>
> Enter a frame number, or 0 to exit
>
> 1: read.table("/tmp/babel-3780tje/R-import-37801if", header = FALSE, row.names
> = NULL, sep = "
> 2: scan(file = file, what = what, sep = sep, quote = quote, dec = dec, nmax =
> nrows, skip = 0,
>>>
>
> I.e.,it seems that Org is going to do its own "read.table" before even
> looking at the code in the source block.
Yes, I believe this happens when Org assigns values to R variables.
>
> Is there some way to get Org to use the "fill=TRUE" option on a case-by-case
> basis?
I don't think so. The call to read.table in org-babel-R-assign-elisp
doesn't use the fill option:
(format "%s <- read.table(\"%s\", header=%s, row.names=%s,
sep=\"\\t\", as.is=TRUE)"
If I add fill=TRUE to that (on a git branch), then I get this:
#+RESULTS: pascals-triangle
| 1 | ||| | |
| 1 | 1 ||| | |
| 1 | 2 | 1 || | |
| 1 | 3 | 3 | 1 | | |
| 1 | 4 | 6 | 4 | 1 | |
| 1 | 5 | 10 | 10 | 5 | 1 |
#+NAME: sanity-check
#+HEADER: :var sc_input=pascals-triangle
#+BEGIN_SRC R
sc_input
#+END_SRC
#+RESULTS: sanity-check
| 1 | nil | nil | nil | nil |
| 1 | 1 | nil | nil | nil |
| 1 | 2 | 1 | nil | nil |
| 1 | 3 | 3 | 1 | nil |
| 1 | 4 | 6 | 4 | 1 |
| 1 | 5 | 10 | 10 | 5 |
| 1 | nil | nil | nil | nil |
which isn't correct, but gets past the scan error.
I'm in over my head here, but hope that my curiosity hasn't been too noisy.
All the best,
Tom
>
> Thanks.
>
> -- Mike
>
>
> Appendix: R code that correctly reads and processes a Pascal's triangle
> ===
>
>
>> system("cat pascal.dat")
> 1
> 1 1
> 1 2 1
> 1 3 3 1
> 1 4 6 4 1
>>
>> x <- read.table("pascal.dat", fill=TRUE)
>>
>> x
> V1 V2 V3 V4 V5
> 1 1 NA NA NA NA
> 2 1 1 NA NA NA
> 3 1 2 1 NA NA
> 4 1 3 3 1 NA
> 5 1 4 6 4 1
>>
>> y <- as.matrix(x)
>>
>> y
> V1 V2 V3 V4 V5
> [1,] 1 NA NA NA NA
> [2,] 1 1 NA NA NA
> [3,] 1 2 1 NA NA
> [4,] 1 3 3 1 NA
> [5,] 1 4 6 4 1
>>
>> y[is.na(y)] <- 0
>>
>> y
> V1 V2 V3 V4 V5
> [1,] 1 0 0 0 0
> [2,] 1 1 0 0 0
> [3,] 1 2 1 0 0
> [4,] 1 3 3 1 0
> [5,] 1 4 6 4 1
>>
>> dimnames(y)[[2]]=NULL cosmetic change
>>
>> y
> [,1] [,2] [,3] [,4] [,5]
> [1,] 1 0 0 0 0
> [2,] 1 1 0 0 0
> [3,] 1 2 1 0 0
> [4,] 1 3 3 1 0
> [5,] 1 4 6 4 1
>>
>
>
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] Babel: communicating irregular data to R source-code block
[...]
>
> I.e.,it seems that Org is going to do its own "read.table" before even
> looking at the code in the source block.
>
Yes, this is true, Org will use read.table to read in tabular data. See
the code in lisp/ob-R.el for specifics.
>
> Is there some way to get Org to use the "fill=TRUE" option on a case-by-case
> basis?
>
Yes, The attached patch allows the :fill header argument to be specified
adding "fill=TRUE" to the read.table function call. Please try it out
and let me know if it works for you.
>From 45240d367eb981a93f3c694946d4f2a99044cda5 Mon Sep 17 00:00:00 2001
From: Eric Schulte
Date: Mon, 23 Apr 2012 17:04:37 -0400
Subject: [PATCH] add :fill header argument to R code blocks
* lisp/ob-R.el (org-babel-header-args:R): List this as a viable R
header argument.
(org-babel-variable-assignments:R): Check the value of this new
:fill header argument.
(org-babel-R-assign-elisp): Set "fill=TRUE" if the :fill header
argument has been used.
---
lisp/ob-R.el | 33 +
1 file changed, 21 insertions(+), 12 deletions(-)
diff --git a/lisp/ob-R.el b/lisp/ob-R.el
index 9538dc4..1427641 100644
--- a/lisp/ob-R.el
+++ b/lisp/ob-R.el
@@ -61,6 +61,7 @@
(colormodel . :any)
(useDingbats . :any)
(horizontal . :any)
+(fill. ((yes no)))
(results . ((file list vector table scalar verbatim)
(raw org html latex code pp wrap)
(replace silent append prepend)
@@ -148,7 +149,8 @@ This function is called by `org-babel-execute-src-block'."
(org-babel-R-assign-elisp
(car pair) (cdr pair)
(equal "yes" (cdr (assoc :colnames params)))
- (equal "yes" (cdr (assoc :rownames params)
+ (equal "yes" (cdr (assoc :rownames params)))
+ (equal "yes" (cdr (assoc :fill params)
(mapcar
(lambda (i)
(cons (car (nth i vars))
@@ -164,19 +166,26 @@ This function is called by `org-babel-execute-src-block'."
(concat "\"" (mapconcat 'identity (split-string s "\"") "\"\"") "\"")
(format "%S" s)))
-(defun org-babel-R-assign-elisp (name value colnames-p rownames-p)
+(defun org-babel-R-assign-elisp (name value colnames-p rownames-p fill-p)
"Construct R code assigning the elisp VALUE to a variable named NAME."
(if (listp value)
- (let ((transition-file (org-babel-temp-file "R-import-")))
-;; ensure VALUE has an orgtbl structure (depth of at least 2)
-(unless (listp (car value)) (setq value (list value)))
-(with-temp-file transition-file
- (insert (orgtbl-to-tsv value '(:fmt org-babel-R-quote-tsv-field)))
- (insert "\n"))
-(format "%s <- read.table(\"%s\", header=%s, row.names=%s, sep=\"\\t\", as.is=TRUE)"
-name (org-babel-process-file-name transition-file 'noquote)
- (if (or (eq (nth 1 value) 'hline) colnames-p) "TRUE" "FALSE")
- (if rownames-p "1" "NULL")))
+ (flet ((R-bool (bool) (if bool "TRUE" "FALSE")))
+ (let ((transition-file (org-babel-temp-file "R-import-")))
+ ;; ensure VALUE has an orgtbl structure (depth of at least 2)
+ (unless (listp (car value)) (setq value (list value)))
+ (with-temp-file transition-file
+ (insert (orgtbl-to-tsv value '(:fmt org-babel-R-quote-tsv-field)))
+ (insert "\n"))
+ (format "%s <- read.table(\"%s\", %s, as.is=TRUE)"
+ name (org-babel-process-file-name transition-file 'noquote)
+ (mapconcat (lambda (pair) (concat (car pair) "=" (cdr pair)))
+ `(("header". ,(R-bool (or (eq (nth 1 value)
+ 'hline)
+ colnames-p)))
+ ("row.names" . ,(if rownames-p "1" "NULL"))
+ ("sep" . "\"\\t\"")
+ ("fill" . ,(R-bool fill-p)))
+ ", "
(format "%s <- %s" name (org-babel-R-quote-tsv-field value
(defvar ess-ask-for-ess-directory nil)
--
1.7.10
Best,
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] Babel: communicating irregular data to R source-code block
Greetings. I'm sorry to belabor this, but I thought I had found a relatively
clean way to pass a "ragged" table to an R source-code block. Simple answer:
add the "fill=TRUE" option to the read.table function. Please see the
appended for the log of an R session that does what I want.
I then tried to do the same thing in an R source-code block:
#+RESULTS: pascals_triangle
| 1 | | | | | |
| 1 | 1 | | | | |
| 1 | 2 | 1 | | | |
| 1 | 3 | 3 | 1 | | |
| 1 | 4 | 6 | 4 | 1 | |
| 1 | 5 | 10 | 10 | 5 | 1 |
#+NAME: sanity-check(sc_input=pascals_triangle)
#+BEGIN_SRC R
pt <- read.table(sc_input, fill=TRUE)
rowSums(pt)
#+END_SRC
Unfortunately, this still results in the "error" that the first line did not
contain five elements:
<<
> Error in scan(file, what, nmax, sep, dec, quote, skip, nlines, na.strings,
> :
line 1 did not have 5 elements
Enter a frame number, or 0 to exit
1: read.table("/tmp/babel-3780tje/R-import-37801if", header = FALSE, row.names
= NULL, sep = "
2: scan(file = file, what = what, sep = sep, quote = quote, dec = dec, nmax =
nrows, skip = 0,
>>
I.e.,it seems that Org is going to do its own "read.table" before even
looking at the code in the source block.
Is there some way to get Org to use the "fill=TRUE" option on a case-by-case
basis?
Thanks.
-- Mike
Appendix: R code that correctly reads and processes a Pascal's triangle
===
> system("cat pascal.dat")
1
1 1
1 2 1
1 3 3 1
1 4 6 4 1
>
> x <- read.table("pascal.dat", fill=TRUE)
>
> x
V1 V2 V3 V4 V5
1 1 NA NA NA NA
2 1 1 NA NA NA
3 1 2 1 NA NA
4 1 3 3 1 NA
5 1 4 6 4 1
>
> y <- as.matrix(x)
>
> y
V1 V2 V3 V4 V5
[1,] 1 NA NA NA NA
[2,] 1 1 NA NA NA
[3,] 1 2 1 NA NA
[4,] 1 3 3 1 NA
[5,] 1 4 6 4 1
>
> y[is.na(y)] <- 0
>
> y
V1 V2 V3 V4 V5
[1,] 1 0 0 0 0
[2,] 1 1 0 0 0
[3,] 1 2 1 0 0
[4,] 1 3 3 1 0
[5,] 1 4 6 4 1
>
> dimnames(y)[[2]]=NULL cosmetic change
>
> y
[,1] [,2] [,3] [,4] [,5]
[1,] 1 0 0 0 0
[2,] 1 1 0 0 0
[3,] 1 2 1 0 0
[4,] 1 3 3 1 0
[5,] 1 4 6 4 1
>
[O] [FYI/noise] GSoC 2012 & new email
Hi List, my GSoC 2012 proposal was accepted, so I'm going to spend this summer implementing bugpile - a bugtracker for GNU Emacs Org-mode. I use the opportunity to change to a different (more serious) email, just in case you wonder. Thanks to Bastien and Eric for the support so far! -- cheers, Thorsten
Re: [O] [PATCH] Show human-readable link descriptions first when inserting links
on Mon Apr 23 2012, Bastien wrote: > Hi Dave, > > Dave Abrahams writes: > >> This patch makes it easy to select links from among a forest of >> similar-looking machine-readable forms. Without it, the human-readable >> descriptions tend to fall off the right side of the window. > > I applied a slightly modified version of this patch. Thank you! -- Dave Abrahams BoostPro Computing http://www.boostpro.com
Re: [O] make update fails
Achim Gratz writes: > Will do. Here's that patch (and some more convenience targets). Also, the first invocation of make will now create a local.mk configuration template if it doesn't exist. You don't need to do anything if the defaults are working for you, otherwise just edit whatever variable needs to be set differently. Some more esoteric settings can be gleaned from default.mk, this will probably be needed if you are on Windows and are maybe missing some programs (some hints are in the comments). >From 1276da42f887610bf4f91c54df0e7076728cbfcf Mon Sep 17 00:00:00 2001 From: Achim Gratz Date: Mon, 23 Apr 2012 21:20:58 +0200 Subject: [PATCH] Introduce compatibility and convenience targets, local.mk template, add "helpall" * Makefile: new target "helpall" to document all targets, while "help" continues to show a brief subset. * default.mk: add cutlines for sed to produce local.mk with. * targets.mk: add target "local.mk" to produce an (empty) local.mk configuration template when it isn't already present. Ignore any error when making this target since sed might not be present on all systems. Redefine target "update" to not include testing, similarly add target "update2" to additionally install without test. Add targets "up0" to stop after git pull and "up1" to stop after test, while "up2" continues to do everything and then installs. Complete .PHONY target list. Add "refcard" target for compatibility with old make. Clean contrib in "cleanall", too. --- Makefile | 88 +--- default.mk |4 +-- targets.mk | 35 3 files changed, 93 insertions(+), 34 deletions(-) diff --git a/Makefile b/Makefile index 7a77d42..1258d52 100644 --- a/Makefile +++ b/Makefile @@ -11,31 +11,77 @@ all:: # Describe valid make targets for org-mode. .PHONY: targets help -targets help: +targets help helpall:: $(info ) - $(info make help - show this help) - $(info make - cleanly compile Org ELisp files and documentation) - $(info ) - $(info Installation) + $(info Getting Help) $(info ) - $(info make install - install Org, both ELisp and Info files) - $(info make install-lisp - install Org, only ELisp files) - $(info make install-info - install Org, only Info file) $(info ) - $(info Maintenance) + $(info make help - show brief help) + $(info make targets - dito) + $(info make helpall - show extended help) + $(info ) + $(info Build and Check) + $(info ===) + $(info make - build Org ELisp and all documentation) + $(info make all - dito) + $(info make compile - build Org ELisp files) + $(info make autoloads - create org-install.el to load org in-place) + $(info make check - build Org ELisp files and run test suite) +helpall:: + $(info make test - dito) + $(info make compile-dirty - build only stale Org ELisp files) + $(info make test-dirty- check without building first) + $(info ) + $(info Compatibility) + $(info =) + $(info make oldorg- what the old make did: compile autoloads info) + $(info ) + $(info Convenience) $(info ===) - $(info make doc - make all documentation) - $(info make info - make Info documentation) - $(info make html - make HTML documentation) - $(info make pdf - make pdf documentation) - $(info make card - make refcards documentation) - $(info ) - $(info make check - build org and run complete test suite) - $(info make clean - clean Org ELisp and documentation files) - $(info make compile - cleanly compile Org ELisp files) - $(info make compile-dirty - compile Org ELisp without cleaning) - $(info ) - $(info make clean-install - remove installed Org ELisp and documentation files) + $(info make up0 - pull from upstream) + $(info make up1 - pull from upstream, build and check) + $(info make up2 - pull from upstream, build, check and install) + $(info make update- pull from upstream and build) + $(info make update2 - pull from upstream, build and install) + $(info make local.mk - create new local.mk as template for adaptation) + $(info ) + $(info Cleaning) + $(info ) + $(info make clean - remove built Org ELisp files and documentation) + $(info make cleanall - remove everything that can be built and all remnants) + $(info make cleandirs - clean in etc/, lisp/ and doc/) + $(info make cleancontrib - remove remnants in contrib/) + $(info make cleandoc - remove built documentation) + $(info make cleandocs - dito) + $(info make cleanlisp - remove built Org ELisp files) + $(info make cleanelc - dito) + $(info make cleanrel - remove release remnants) + $(info make cleantest - remove check remnants) + $(info make clean-install - remove previous Org installation) + $(info ) + $(
Re: [O] Babel: communicating irregular data to R source-code block
Eric Schulte writes: > [...] >> >> I'm beginning to see why you have strong feelings about python. > > Semantically meaningful whitespace is a bad idea for a programming > langauge. > Yes, this makes sense to me. I suppose I should wean myself from python now that I use babel as a "glue language." >> In the code above, the blank line before #+end_src is necessary and >> must not contain any spaces, and :var n can be set to anything, since >> it is declared for initialization only. >> >> The code in the JSS article doesn't run for me with a recent Org-mode >> unless I add a blank line before #+end_src, or remove the :return header >> argument. If I remove the :return header argument, then the need for >> the blank line goes away. The following code block seems to work: >> >> #+name: pascals-triangle >> #+begin_src python :var n=2 :exports none >> def pascals_triangle(n): >> if n == 0: >> return [[1]] >> prev_triangle = pascals_triangle(n-1) >> prev_row = prev_triangle[n-1] >> this_row = map(sum, zip([0] + prev_row, prev_row + [0])) >> return prev_triangle + [this_row] >> return pascals_triangle(n) >> #+end_src >> >> #+RESULTS: pascals-triangle >> >> | 1 | | | >> | 1 | 1 | | >> | 1 | 2 | 1 | >> >> I'm guessing that the need for a blank line when using :results has >> arisen since the JSS article was published, because the article was >> generated from source code and didn't show any errors. >> > > I believe that we used to pad code blocks with newlines when they were > extracted from the buffer, which had the effect of automatically adding > this extra line. This behavior however caused problems in some cases > where the extra line was not desired. > >> >> If I have this right (a big if), then might it be possible to >> re-establish the old behavior so the JSS code works? >> > > I've just pushed up a patch in which the addition of the return value in > python is careful to add this newline itself. This should restore the > functionality of the python code from the paper (specifically the > following now works [1]). This is applied to the maint branch so > hopefully it will sync with Emacs before the release of Emacs24. > Thanks Eric. The source block in the paper returns the correct result with the code in the maint branch. All the best, Tom > Best, > > > Footnotes: > [1] > > #+name: pascals-triangle > #+begin_src python :var n=2 :exports none :return pascals_triangle(n) > def pascals_triangle(n): > if n == 0: > return [[1]] > prev_triangle = pascals_triangle(n-1) > prev_row = prev_triangle[n-1] > this_row = map(sum, zip([0] + prev_row, prev_row + [0])) > return prev_triangle + [this_row] > #+end_src > > #+RESULTS: pascals-triangle > > | 1 | | | > | 1 | 1 | | > | 1 | 2 | 1 | -- Thomas S. Dye http://www.tsdye.com
[O] Default show all archived entries for agenda
Hi guys, How could I configure it so that the agenda always shows archived entries by default? It's a nice way to get a log of what I accomplished chronologically without having to keep a specific log file per se (work log, food log, whatever-log). I could always just use v A in the agenda filter, but I'd rather just make it the default if it's easy to do. Thanks, - Marcelo.
Re: [O] embed base64 encoded images in exported html
On Mon, Apr 23, 2012 at 9:35 AM, Eric Schulte wrote: > To include raw html in an Org-mode file you can use either the single > line #+HTML: escape or wrap it in a being/end html block, Thank you! Now I can see where I missed this in the docs (seems perfectly clear in retrospect): http://orgmode.org/manual/results.html#results Take care, Noah
Re: [O] [OT] Defining System, process, methodology and framework
Hi Karl, I'm 60% through the book. I'll share my insights shortly. Thank your for your definitions, they make sense :) - Marcelo. On Sun, Apr 22, 2012 at 5:48 AM, Karl Voit wrote: > * Marcelo de Moraes Serpa wrote: > > > > Well, looks like my text was kind of stupid and or confusing... > > No. At least not to me. > > > Anyway, I started reading "An Introduction To General Systems Thinking" - > > surprisingly interesting book, and it's helping me answer most of those > > questions in deeper ways. I needed to do some additional investigation > > before starting to ask questions ;) > > > > I'll share the insights after I finish it, > > Please do so. > > For me, this approach is especially interesting related to PIM/GTD. > > > Without looking into Wikipedia or such and without deeper background > knowledge, I'd have *guessed*: > > - systems are made of processes > - system is a higher level process, accomplishing bigger things than a > task > - a process defines a method to accomplish a task > - frameworks are generic tools for implementing a process > - a method is the underlying principle of how a process is designed > > YMMV :-) > > -- > Karl Voit > > >
Re: [O] embed base64 encoded images in exported html
Noah Hoffman writes:
> Hello -
>
> I am trying to export a monolithic html file by embedding
> base64-encoded images, and I can't quite figure out how to prevent the
> output from being escaped in one way or another... here's an example
> of one permutation that doesn't do exactly what I want:
>
> #+BEGIN_SRC R :results output
> png('plot.png')
> plot(1:10)
> invisible(dev.off())
> list.files(pattern = '*.png')
> #+END_SRC
>
> #+RESULTS:
> : [1] "plot.png"
>
> #+BEGIN_SRC python :results output raw :exports results
> with open('plot.png', 'rb') as image:
> data = image.read()
> print '' % data.encode("base64")
> #+END_SRC
>
> #+RESULTS:
> src="data:image/png;base64,iVBORw0KGgoNSUhEUgAAAeHgCAMAAABKCk6nAAACuFBMVEUBAQEDAwMEBAQHBwcJ
> CQkKCgoMDAwNDQ0ODg4PDw8QEBARERESEhITExMUFBQVFRUWFhYXFxcYGBgZGRkaGhobGxscHBwf
> Hx8gICAhISEiIiIjIyMkJCQlJSUmJiYnJycoKCgqKiorKyssLCwtLS0uLi4vLy8wMDAxMTEyMjI0
> NDQ4ODg5OTk6Ojo7Ozs8PDw9PT0+Pj4/Pz9AQEBBQUFCQkJDQ0NERERFRUVGRkZHR0dISEhJSUlK
> SkpLS0tMTExNTU1OTk5PT09QUFBRUVFSUlJTU1NUVFRXV1dYWFhZWVlaWlpbW1tcXFxdXV1e
>
>
>
> Here the "results" block is not exposed as raw html in the exported
> file. Can anyone suggest how I might do this? I'm using emacs 23.4.1,
> org-mode 7.8.03
>
Hi Noah,
To include raw html in an Org-mode file you can use either the single
line #+HTML: escape or wrap it in a being/end html block, so adjusting
your example above would yield
#+BEGIN_SRC python :results output raw :exports results
with open('plot.png', 'rb') as image:
data = image.read()
print '#+HTML: ' % data.encode("base64")
#+END_SRC
or
#+BEGIN_SRC python :results output html :exports results
with open('plot.png', 'rb') as image:
data = image.read()
print '' % data.encode("base64")
#+END_SRC
Best,
>
> Thanks a lot,
> Noah
>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] [Feature Request] org-mobile edit:add nodes
Hi Bastien, it turns out that there are a couple of problems with that particular patch. Some issues have already been fixed with the help of someone else from the mobileorg community, but more work is required. As soon as it is functional (and hopefully stable) I will post a new patch. Henning On Fri, Apr 20, 2012 at 1:55 PM, Bastien wrote: > Hi Henning, > > I'm not using org-mobile.el so it's hard to test this patch. > > Can anyone test and report? > > Henning Weiss writes: > > > I am currently trying to allow mobileorg-android to capture new > > headings into files other than mobileorg.org. It seems to me that > > org-mobile does not support refiling of nodes. As my experience with > > lisp programming is very limited, I was hoping someone on this list > > could add this feature. > > -- > Bastien >
Re: [O] Auto tag based on buffer contents?
I don't think there exist an autotag feature, but you can use template expansions [1] to put the sender's name as a tag in the headline. For instance, you could use the template expansions "%:from", "%:fromname" or "%:fromaddress". But I don't know how this will play if you also use the template expansion that prompt for tags. [1] http://orgmode.org/manual/Template-expansion.html#Template-expansion -- Darlan
Re: [O] Babel: communicating irregular data to R source-code block
[...] > > I'm beginning to see why you have strong feelings about python. Semantically meaningful whitespace is a bad idea for a programming langauge. > In the code above, the blank line before #+end_src is necessary and > must not contain any spaces, and :var n can be set to anything, since > it is declared for initialization only. > > The code in the JSS article doesn't run for me with a recent Org-mode > unless I add a blank line before #+end_src, or remove the :return header > argument. If I remove the :return header argument, then the need for > the blank line goes away. The following code block seems to work: > > #+name: pascals-triangle > #+begin_src python :var n=2 :exports none > def pascals_triangle(n): > if n == 0: > return [[1]] > prev_triangle = pascals_triangle(n-1) > prev_row = prev_triangle[n-1] > this_row = map(sum, zip([0] + prev_row, prev_row + [0])) > return prev_triangle + [this_row] > return pascals_triangle(n) > #+end_src > > #+RESULTS: pascals-triangle > > | 1 | | | > | 1 | 1 | | > | 1 | 2 | 1 | > > I'm guessing that the need for a blank line when using :results has > arisen since the JSS article was published, because the article was > generated from source code and didn't show any errors. > I believe that we used to pad code blocks with newlines when they were extracted from the buffer, which had the effect of automatically adding this extra line. This behavior however caused problems in some cases where the extra line was not desired. > > If I have this right (a big if), then might it be possible to > re-establish the old behavior so the JSS code works? > I've just pushed up a patch in which the addition of the return value in python is careful to add this newline itself. This should restore the functionality of the python code from the paper (specifically the following now works [1]). This is applied to the maint branch so hopefully it will sync with Emacs before the release of Emacs24. Best, Footnotes: [1] #+name: pascals-triangle #+begin_src python :var n=2 :exports none :return pascals_triangle(n) def pascals_triangle(n): if n == 0: return [[1]] prev_triangle = pascals_triangle(n-1) prev_row = prev_triangle[n-1] this_row = map(sum, zip([0] + prev_row, prev_row + [0])) return prev_triangle + [this_row] #+end_src #+RESULTS: pascals-triangle | 1 | | | | 1 | 1 | | | 1 | 2 | 1 | -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] embed base64 encoded images in exported html
Hello -
I am trying to export a monolithic html file by embedding
base64-encoded images, and I can't quite figure out how to prevent the
output from being escaped in one way or another... here's an example
of one permutation that doesn't do exactly what I want:
#+BEGIN_SRC R :results output
png('plot.png')
plot(1:10)
invisible(dev.off())
list.files(pattern = '*.png')
#+END_SRC
#+RESULTS:
: [1] "plot.png"
#+BEGIN_SRC python :results output raw :exports results
with open('plot.png', 'rb') as image:
data = image.read()
print '' % data.encode("base64")
#+END_SRC
#+RESULTS:
Re: [O] [odt] Export of LaTeX Fragments
Since org already accepts \SomeCommandName, maybe org-mode could provide
some very basic functionality for the user to provide definitions for these
macros for each (desired) output format. For instance, there could be a
list similar to
#+begin_src emacs-lisp
(
("somecommand" :html 'somecommand-html-export :latex ;
somecommand-latex-export :buffer 'somecommand-buffer-change)
("someothercomand" :html someothercomand-html-export)
)
#+end_src
The export function definitions should be provided by the user for each
desired export format and any unspecified format should do what org-mode
does right now. The "buffer" format would be a function for changing the
way the command (and its argument) look in the org-buffer.
I'm no lisp programmer and this is probably no the best way to implement
this feature, but I think this flexibility could allow orgers to tweak
org-mode to their needs easily.
--
Darlan
At Mon, 23 Apr 2012 17:08:13 +0200,
Bastien wrote:
>
> Torsten Wagner writes:
>
> > However, whats with "\," "\mbox{}" "\noindent" and maybe some others?
> > They helped me to tweak the formatting at some points where the
> > standard stuff did not make much sense.
>
> There commands are meaningful in a TeX context, and there is not
> necessary a precise translation of their meanings in other contexts
> like ODT documents.
>
> In Org file, it is better to stick to Org syntax -- even if some
> flexibility is allowed with \noindent and friends while converting
> to LaTeX.
>
> --
> Bastien
>
Re: [O] make fails on current version
On Mon, Apr 23, 2012 at 09:57:25AM -0700, Richard Stanton wrote:
> I just updated org-mode and typed "make". Two problems:
>
> 1) The doc file seems to have trouble:
>
> org.texi:6703: Misplaced {.
> org.texi:6703: Misplaced }.
> makeinfo: Removing output file `org' due to errors; use --force to
> preserve.
The problem's in the texinfo documentation for the new % capture
template expandos...but please don't shoot me, it's not my fault! (I just
modified the change that Bastien had already committed to org.texi.)
>From the texinfo documentation, it looks like literal "{" and "}" have to
be escaped with "@". Patch attached.
> 2) org-install.el doesn't get created.
>
> From org-version.el, this is git version "release_7.8.09-375-gb7982a"
> (org-version just returns N/A).
No idea about this one.
Toby
--
Dr T. S. Cubitt
Mathematics and Quantum Information group
Department of Mathematics
Complutense University
Madrid, Spain
email: ts...@cantab.net
web: www.dr-qubit.org
>From 9fd3ba1bdfbb3b608fcd86ded73f02c53d50e05d Mon Sep 17 00:00:00 2001
From: "Toby S. Cubitt"
Date: Mon, 23 Apr 2012 19:25:57 +0200
Subject: [PATCH] Fixed bug in texinfo documentation.
* doc/org.texi: Escape literal {}'s.
---
doc/org.texi |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index bb98713..18dba90 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6700,7 +6700,7 @@ dynamic insertion of content. The templates are expanded in the order given her
@r{You may specify a default value and a completion table with}
@r{%^@{prompt|default|completion2|completion3...@}.}
@r{The arrow keys access a prompt-specific history.}
-%@r{Insert the text entered at the nth %^{prompt}, where is}
+%@r{Insert the text entered at the nth %^@{prompt@}, where is}
@r{a number, starting from 1.}
%? @r{After completing the template, position cursor here.}
@end smallexample
--
1.7.8.5
Re: [O] What does prefix argument do to org-goto (C-c C-j)
Hi John, John Hendy writes: > Per Bastien's request (well, org-mode on G+), I'm reproducing my question > here. > > After watching a bug reproduction video which mentioned using > org-goto, C-u C-c C-j, I wondered what C-u did.[1] I couldn't find it > in the manual. It doesn't move the cursor as you type (isearch off?) > and doesn't bring up the various hints in the minibuffer that happens > with C-c C-j alone. C-u C-c C-j calls org-goto and uses the 'outline-path-completion interface if `org-goto-interface' is set to 'outline, and the other way around. It's in the docstring now. Thanks! -- Bastien
[O] What does prefix argument do to org-goto (C-c C-j)
Per Bastien's request (well, org-mode on G+), I'm reproducing my question here. After watching a bug reproduction video which mentioned using org-goto, C-u C-c C-j, I wondered what C-u did.[1] I couldn't find it in the manual. It doesn't move the cursor as you type (isearch off?) and doesn't bring up the various hints in the minibuffer that happens with C-c C-j alone. [1] https://plus.google.com/u/0/102778904320752967064/posts/ekYHxqdpT4a Thanks, John
Re: [O] make fails on current version
Hi Richard,
Richard Stanton writes:
> I just updated org-mode and typed "make". Two problems:
>
> 1) The doc file seems to have trouble:
>
> org.texi:6703: Misplaced {.
> org.texi:6703: Misplaced }.
> makeinfo: Removing output file `org' due to errors; use --force to
> preserve.
Fixed, thanks.
> 2) org-install.el doesn't get created.
make autoloads
will create it.
HTH,
--
Bastien
Re: [O] Change example timestamps to not occur in headlines
On 2012-04-23, Samuel Wales wrote: > If the explanation (which I don't know yet) is short, perhaps the > manual can explain, for similar use cases. Then again maybe I am the only person who doesn't get why the footnote is there. I'm guessing something to do with brackets interfering with link syntax, but then I would think that would be escaped to fix it. Or else the footnote would say don't put brackets in headlines. Is there a different explanation? P.S. I do it like this (and I sort by reverse chrono) which works *fantastically* for me: ... * CALLED [2012-04-24 Tue 11:20] Bastien explained * CALLED [2012-04-23 Mon 10:00] discussed links with Bastien ... :) -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com http://thekafkapandemic.blogspot.com";>http://thekafkapandemic.blogspot.com
Re: [O] Change example timestamps to not occur in headlines
Hi Bastien, Just wanted to make sure. Just so you know: With my settings, I find that if I have: * Details [2012-04-23 Mon 09:58] and I do M-x org-store-link, then the resulting link with ID works when you click on it. So it works for me, but I guess others with other settings will find that it does not work? As I sort headlines with timestamps by time, timestamps in headlines are valuable for me. I don't use date trees because I find sorting to be a much better fit for me. If the explanation (which I don't know yet) is short, perhaps the manual can explain, for similar use cases. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com http://thekafkapandemic.blogspot.com";>http://thekafkapandemic.blogspot.com
[O] make fails on current version
I just updated org-mode and typed "make". Two problems:
1) The doc file seems to have trouble:
org.texi:6703: Misplaced {.
org.texi:6703: Misplaced }.
makeinfo: Removing output file `org' due to errors; use --force to
preserve.
2) org-install.el doesn't get created.
>From org-version.el, this is git version "release_7.8.09-375-gb7982a"
(org-version just returns N/A).
Re: [O] Babel: communicating irregular data to R source-code block
Hi Eric,
Eric Schulte writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha Michael,
>>
>> Michael Hannon writes:
>>
>>> Greetings. I'm sitting in on a weekly, informal, "brown-bag" seminar on
>>> data
>>> technologies in statistics. There are more people attending the seminar
>>> than
>>> there are weeks in which to give talks, so I may get by with being my usual,
>>> passive-slug self.
>>>
>>> But I thought it might be useful to have a contingency plan and decided that
>>> giving a brief talk about Babel might be useful/instructive. I thought (and
>>> think) that mushing together (with attribution) some of the content of the
>>> paper [1] by The Gang of Four and the content of Eric's talk [2] might be a
>>> good approach. (BTW, if this isn't legal, desirable, permissible, etc.,
>>> this
>>> would be a good time to tell me.)
>>>
>
> I would be happy for you to re-use these materials.
>
>>>
>>> I liked the Pascal's Triangle example (which morphed from elisp to Python,
>>> or
>>> vice versa, in the two references), but I was afraid that the elisp routine
>>> "pst-check", used as a check on the correctness of the previously-generated
>>> Pascal's triangle, might be too esoteric for this audience, not to mention
>>> me.
>>> (The recursive Fibonacci function is virtually identical in all languages,
>>> but the second part is more obscure.)
>>>
>
> I was giving a presentation to a local lisp/scheme user group, so I
> figured I'd spare them the pain of trying to read python code :).
>
>>>
>>> I thought it should be possible to use R to do the same sanity check, as R
>>> would be much more-familiar to this audience (and its use would still
>>> demonstrate the meta-language feature of Babel).
>>>
>>> Unfortunately, I haven't been able to find a way to communicate the output
>>> of
>>> the Pascal's Triangle example to an R source-code block. The gist of the
>>> problem seems to be that regardless of how I try to grab the data (scan,
>>> readLines, etc.) Babel always ends up trying to read a data frame (table)
>>> and
>>> I get an error similar to:
>>>
>
> I present some options below specific to Tom's discussion, but another
> option may be to use the ":results output" option on a python code block
> which prints the table to STDOUT, and then use something line readLines
> to read from the resulting string into R.
>
I didn't have any luck with :results output, but didn't spend much time
trying to figure it out.
>>>
>>> <<
Error in scan(file, what, nmax, sep, dec, quote, skip, nlines, na.strings,
: line 1 did not have 5 elements
>>>
>>> Enter a frame number, or 0 to exit
>>>
>>> 1: read.table("/tmp/babel-3780tje/R-import-3780Akj", header = FALSE,
>>> row.names
>>> = NULL, sep = "
>
>>>
>>> If I construct a table "by hand" with all of the cells occupied, everything
>>> goes OK. For instance:
>>>
>>> <<
>>> #+TBLNAME: some-junk
>>> | 1 | 0 | 0 | 0 |
>>> | 1 | 1 | 0 | 0 |
>>> | 1 | 2 | 1 | 0 |
>>> | 1 | 3 | 3 | 1 |
>>>
>>> #+NAME: read-some-junk(sj_input=some-junk)
>>> #+BEGIN_SRC R
>>>
>>> rowSums(sj_input)
>>>
>>> #+END_SRC
>>>
>>> #+RESULTS: read-some-junk
>>> | 1 |
>>> | 2 |
>>> | 4 |
>>> | 8 |
>
>>>
>>> But the following gives the kind of error I described above:
>>>
>>> <<
>>> #+name: pascals_triangle
>>> #+begin_src python :var n=5 :exports none :return pascals_triangle(5)
>>> def pascals_triangle(n):
>>> if n == 0:
>>> return [[1]]
>>> prev_triangle = pascals_triangle(n-1)
>>> prev_row = prev_triangle[n-1]
>>> this_row = map(sum, zip([0] + prev_row, prev_row + [0]))
>>> return prev_triangle + [this_row]
>>>
>>> pascals_triangle(n)
>>> #+end_src
>>
>> A few things are wrong at this point. It seems the JSS article has
>> an error in the header of the pascals_triangle source block. AFAIK
>> there is no header argument :return. I don't know how :return
>> pascals_triangle(5) got there, but am fairly certain it shouldn't be.
>>
>
> The :return header argument *is* a supported header argument of python
> code blocks and is not an error. The python code block should run w/o
> error and without the extra "return pascals_triangle(n)" at the bottom.
> The following works for me.
>
> #+name: pascals_triangle
> #+begin_src python :var n=5 :exports none :return pascals_triangle(5)
> def pascals_triangle(n):
> if n == 0:
> return [[1]]
> prev_triangle = pascals_triangle(n-1)
> prev_row = prev_triangle[n-1]
> this_row = map(sum, zip([0] + prev_row, prev_row + [0]))
> return prev_triangle + [this_row]
>
> #+end_src
>
> #+RESULTS: pascals_triangle
> | 1 | ||| | |
> | 1 | 1 ||| | |
> | 1 | 2 | 1 || | |
> | 1 | 3 | 3 | 1 | | |
> | 1 | 4 | 6 | 4 | 1 | |
> | 1 | 5 | 10 | 10 | 5 | 1 |
>
> [...]
I'm beginning to see why you have strong feelings about python. In the
code above, the blank line before #+end_src is necessary and must not
contain any spaces, and :v
Re: [O] make update fails
Bastien writes: > Looks fine. Could you create a > > make help+ The "+" is a reserved character in some shells, but I'll think of some other name... > directive that will display information about directives that > are not documented through `make help'? Will do. Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] make update fails
Achim Gratz writes: > Detlef Steuer writes: >> Cannot open load file: ert > > It fails at testing because you do not have ert installed. If you want > testing (recommended if you pull from master since it will avoid > installation of the occasional build that fails the test suite), install > ert or better yet switch to Emacs24 which has it built-in already. > > I'll make "update" a compatibility target that doesn't run "check" > (similarly a new "update2" which does installation but no test) and let > a new target "up1" do that (and "up0" does just the update from git). Looks fine. Could you create a make help+ directive that will display information about directives that are not documented throught `make help'? -- Bastien
Re: [O] make update fails
Detlef Steuer writes: > Cannot open load file: ert It fails at testing because you do not have ert installed. If you want testing (recommended if you pull from master since it will avoid installation of the occasional build that fails the test suite), install ert or better yet switch to Emacs24 which has it built-in already. I'll make "update" a compatibility target that doesn't run "check" (similarly a new "update2" which does installation but no test) and let a new target "up1" do that (and "up0" does just the update from git). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: [O] HTML export fails with (void-variable org-version)
Bastien writes: > In the meantime, if you don't want to compile (I do not) the stupid > workaround is to set org-version in your config... but yeah, let's > fix this upstream ASAP. Again, the issue here is not compilation, but missing autoloads. make autoloads And if you still think you must override this, the thing(s) to set is (defconst org-release) (defconst org-git-release) ...which incidentally is what "make autoloads" will put into org-install.el, with a docstring and all that. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Re: [O] HTML export fails with (void-variable org-version)
Hi, I just noticed switching from the standard org-mode comming with emacs 23 to a recent version, there where no org-version command at all. Under Arch-Linux they ask you to add (require 'org-install) to your config. After doing so it was fine. Not sure if this is related. Torsten On 24 April 2012 00:32, Bastien wrote: > Hi Eric, > > Eric Schulte writes: > >> I'm getting export failures due to the org-version variable no longer >> being defined. See the following minimal debug output [1]. If I >> manually give the org-version variable a value, e.g., > > this issue comes from the new Makefile, which creates the org-version > variable at compile time. I reported this to Achim yesterday and we > are looking for a solution. > > In the meantime, if you don't want to compile (I do not) the stupid > workaround is to set org-version in your config... but yeah, let's > fix this upstream ASAP. > > Thanks, > > -- > Bastien >
Re: [O] [PATCH] Allow % escapes to capture templates, expanded to text entered in 'th prompt
Toby Cubitt writes: > On Mon, Apr 23, 2012 at 05:12:51PM +0200, Bastien wrote: >> Hi Toby, >> >> Toby Cubitt writes: >> >> > Ah, I forgot about the texinfo docs. Sorry. I'll try to remember them >> > next time. >> >> No problem. >> >> > - Change the regexp to "%\\([1-9][0-9]*\\)", to match any positive >> > integer, and update the docs accordingly. >> >> Please send a patch for this solution. > > Attached (this time including a texinfo documentation update ;-) Applied, thanks! -- Bastien
Re: [O] HTML export fails with (void-variable org-version)
Hi Eric, Eric Schulte writes: > I'm getting export failures due to the org-version variable no longer > being defined. See the following minimal debug output [1]. If I > manually give the org-version variable a value, e.g., this issue comes from the new Makefile, which creates the org-version variable at compile time. I reported this to Achim yesterday and we are looking for a solution. In the meantime, if you don't want to compile (I do not) the stupid workaround is to set org-version in your config... but yeah, let's fix this upstream ASAP. Thanks, -- Bastien
Re: [O] [PATCH] Allow % escapes to capture templates, expanded to text entered in 'th prompt
On Mon, Apr 23, 2012 at 05:12:51PM +0200, Bastien wrote:
> Hi Toby,
>
> Toby Cubitt writes:
>
> > Ah, I forgot about the texinfo docs. Sorry. I'll try to remember them
> > next time.
>
> No problem.
>
> > - Change the regexp to "%\\([1-9][0-9]*\\)", to match any positive
> > integer, and update the docs accordingly.
>
> Please send a patch for this solution.
Attached (this time including a texinfo documentation update ;-)
Toby
--
Dr T. S. Cubitt
Mathematics and Quantum Information group
Department of Mathematics
Complutense University
Madrid, Spain
email: ts...@cantab.net
web: www.dr-qubit.org
>From 4407cd46e3cf8339a9c90d4dde8337b7dbaca048 Mon Sep 17 00:00:00 2001
From: "Toby S. Cubitt"
Date: Mon, 23 Apr 2012 17:20:19 +0200
Subject: [PATCH] org-capture.el: Fixed bug in org-capture-templates %
expandos
* lisp/org-capture.el (org-capture-fill-template): Fixed regexp for
% expandos to match any positive integer.
(org-capture-templates): Updated docstring accordingly.
* doc/org.texi: Updated documentation accordingly.
---
doc/org.texi|4 ++--
lisp/org-capture.el |6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index a25572d..bb98713 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6700,8 +6700,8 @@ dynamic insertion of content. The templates are expanded in the order given her
@r{You may specify a default value and a completion table with}
@r{%^@{prompt|default|completion2|completion3...@}.}
@r{The arrow keys access a prompt-specific history.}
-%@r{Insert the text entered for at the nth %^{prompt}, where }
-@r{represents a digit, 1 to 9.}
+%@r{Insert the text entered at the nth %^{prompt}, where is}
+@r{a number, starting from 1.}
%? @r{After completing the template, position cursor here.}
@end smallexample
diff --git a/lisp/org-capture.el b/lisp/org-capture.el
index 7fbd438..d507cc2 100644
--- a/lisp/org-capture.el
+++ b/lisp/org-capture.el
@@ -248,8 +248,8 @@ be replaced with content and expanded in this order:
A default value and a completion table ca be specified like this:
%^{prompt|default|completion2|completion3|...}.
%? After completing the template, position cursor here.
- %Insert the text entered for at the nth %^{prompt}, where
- represents a digit, 1 to 9.
+ %Insert the text entered at the nth %^{prompt}, where is
+ a number, starting from 1.
Apart from these general escapes, you can access information specific to the
link type that is created. For example, calling `org-capture' in emails
@@ -1480,7 +1480,7 @@ The template may still contain \"%?\" for cursor positioning."
;; Replace %n escapes with nth %^{...} string
(setq strings (nreverse strings))
(goto-char (point-min))
- (while (re-search-forward "%\\([1-9]\\)+" nil t)
+ (while (re-search-forward "%\\([1-9][0-9]*\\)" nil t)
(unless (org-capture-escaped-%)
(replace-match
(nth (1- (string-to-number (match-string 1))) strings)
--
1.7.8.5
[O] Auto tag based on buffer contents?
Is there any facility to "auto tag" a capture based on the contents of the buffer the capture was started in? To be honest I only need something that would tag a capture with, for example "hostgator", if the gnus message I am capturing from included their email address. thanks, r.
[O] HTML export fails with (void-variable org-version)
Hi, I'm getting export failures due to the org-version variable no longer being defined. See the following minimal debug output [1]. If I manually give the org-version variable a value, e.g., (setq org-version "special") then export works as expected. This can be re-created using the latest git HEAD with $ emacs -Q (add-to-list 'load-path "path/to/org/lisp") (load "path/to/org/lisp/org.el") (org-reload) ;; open an Org-mode buffer ;; Export with C-c C-e h Best, Footnotes: [1] Debugger entered--Lisp error: (void-variable org-version) org-export-as-html(nil hidden) org-export-as-html-and-open(nil) call-interactively(org-export-as-html-and-open) org-export(nil) call-interactively(org-export nil nil) -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [PATCH] Allow % escapes to capture templates, expanded to text entered in 'th prompt
Hi Toby, Toby Cubitt writes: > Ah, I forgot about the texinfo docs. Sorry. I'll try to remember them > next time. No problem. > - Change the regexp to "%\\([1-9][0-9]*\\)", to match any positive > integer, and update the docs accordingly. Please send a patch for this solution. Thanks! -- Bastien
Re: [O] Adding a hyperlink to an attachment using beamer class
Hi Caner, Caner Candan writes: > 1. Add directly my images as attachments (stored then in data folder) It is not possible at the moment. > 2. Then trying something like [[hyperlink]] into the same headline in > order to add the images in the frame. I'm not sure I understand -- can you expand a bit more? (Of course if 2 depends on 1, then 2 is not possible either...) Best, -- Bastien
Re: [O] [PATCH] Allow % escapes to capture templates, expanded to text entered in 'th prompt
On Mon, Apr 23, 2012 at 02:54:31PM +0200, Bastien wrote: > Toby Cubitt writes: > > > Currently, capture templates provide no way of prompting for some text, > > then inserting that text into multiple places in the template. > > Thanks for the patch, I applied it. > > I also updated the documentation in doc/org.texi -- please provide > documentation in the patch containing code changes if relevant next > times. Ah, I forgot about the texinfo docs. Sorry. I'll try to remember them next time. > One tiny thing: the documentation said that %0 would match the first > occurrence but while I tested the first occurrence was on %1, which > looks better to me. > > So I updated the documentation accordingly. Yes, you're right, it starts from 1. That's what comes of adding the documentation later, as an after-thought...(bad programming practice!) And now I look at it again, there's a bug in the regexp (my fault): the regexp "%\\([1-9]\\)+" currently matches any sequence of 1-9's, which is clearly wrong. The two possible fixes are: - Drop the final + from the regexp so that it reads "%\\([1-9]\\)", to match any single non-zero digit, as per the current docs. (The regexp group must be kept, because it's used later in the code.) - Change the regexp to "%\\([1-9][0-9]*\\)", to match any positive integer, and update the docs accordingly. It seems unlikely anyone would ever want to refer back to more than 9 prompts in a capture template. (I think back-references in Emacs regexps are similarly limited to single digits). On the other hand, whenever someone says "it seems unlikely anyone would ever want to..." about Emacs, up pops someone who wants to do exactly that ;-) Your call. If you tell me which fix you prefer, I can supply a patch if you want one (though the change is so small I imagine it'll be easier to do it manually). Toby -- Dr T. S. Cubitt Mathematics and Quantum Information group Department of Mathematics Complutense University Madrid, Spain email: ts...@cantab.net web: www.dr-qubit.org
Re: [O] [odt] Export of LaTeX Fragments
Torsten Wagner writes:
> However, whats with "\," "\mbox{}" "\noindent" and maybe some others?
> They helped me to tweak the formatting at some points where the
> standard stuff did not make much sense.
There commands are meaningful in a TeX context, and there is not
necessary a precise translation of their meanings in other contexts
like ODT documents.
In Org file, it is better to stick to Org syntax -- even if some
flexibility is allowed with \noindent and friends while converting
to LaTeX.
--
Bastien
[O] Adding a hyperlink to an attachment using beamer class
Hi, I was asking this issue in order to do these things: 1. Add directly my images as attachments (stored then in data folder) 2. Then trying something like [[hyperlink]] into the same headline in order to add the images in the frame. Anyone know solutions ? Thanks, Caner signature.asc Description: OpenPGP digital signature
Re: [O] [odt]Problem exporting PDF-based images to odt
Hi Thorsten, Torsten Wagner writes: > One more, > > I used > > #+CAPTION: Figure text > #+LABEL: fig:pop > #+ATTR_LaTeX: width=10cm placement=[!ht] > #+ATTR_LaTeX: > [[file:fig/anwendung.pdf]] > > to add pictures. On the odt export, they appear as links to the PDF > file. The Figure text is missing. > Anything, I am doing wrong. Should I use image formats known by > openoffice? (That would be bad because PDF works very nice for LaTeX). > If so, any chance to run "convert foo.pdf -density 300 foo.png" on the > fly during export (ImageMagick would be a requirement then). > If I get this and the LaTeX fragments right, the export of a rather > complex document works out 99% (well I do not get justify paragraphs > but that needs maybe some tweaking on my side. And there is some way > of having soft carriage returns instead of carriage returns). IMO the easiest thing to do would be to convert to .png yourself and to use the png file in both LaTeX and ODT. -- Bastien
Re: [O] [odt] Export of LaTeX Fragments
Hi Bastien,
I agree.
Some, I used more of a habit reasons (how many orgers are latexers?!
;) ) and they have a org-replacement.
However, whats with "\," "\mbox{}" "\noindent" and maybe some others?
They helped me to tweak the formatting at some points where the
standard stuff did not make much sense.
Thanks
Torsten
On 23 April 2012 23:50, Bastien wrote:
> Hi Thorsten,
>
> Torsten Wagner writes:
>
>> I have a minor problem, I used some LaTeX format commands. I know I
>> might get away by replacing \textbf with **, etc.
>
> Yes, that's the way to go. Should be quick with M-x replace-regexp.
>
>> But know its
>> there already. Sure it worked out great for the LaTeX-PDF export.
>> However, in openoffice I had stuff like \textbf{text}. I was
>> wondering, the exporter is doing all this nifty work already, could we
>> have a flag to replace the most common Linux inline text-formats by
>> the corresponding odt format?
>
> Mhh... I think it would be too hackish. Converting \textbf{...} to
> *...* in .org files just for converting them back to another format
> means that \textbf{...} shouldnot be used on the first place. But
> maybe I'm misunderstanding something...
>
> Best,
>
> --
> Bastien
Re: [O] Org tasks from gnus
jca+...@wxcvbn.org (Jérémie Courrèges-Anglas) writes: > Rasmus writes: > [...] >> As others said, use org-complete. Most of my TODOs link to a mail. > [...] > I think you meant org-capture, as described by your example setup. :) > Org-capture works indeed fine for me. Sure, that's what I meant :) -- In theory, practice and theory are the same. In practice they are not
[O] [odt]Problem exporting PDF-based images to odt
One more, I used #+CAPTION: Figure text #+LABEL: fig:pop #+ATTR_LaTeX: width=10cm placement=[!ht] #+ATTR_LaTeX: [[file:fig/anwendung.pdf]] to add pictures. On the odt export, they appear as links to the PDF file. The Figure text is missing. Anything, I am doing wrong. Should I use image formats known by openoffice? (That would be bad because PDF works very nice for LaTeX). If so, any chance to run "convert foo.pdf -density 300 foo.png" on the fly during export (ImageMagick would be a requirement then). If I get this and the LaTeX fragments right, the export of a rather complex document works out 99% (well I do not get justify paragraphs but that needs maybe some tweaking on my side. And there is some way of having soft carriage returns instead of carriage returns). Thanks Torsten
Re: [O] [odt] Export of LaTeX Fragments
Hi Thorsten,
Torsten Wagner writes:
> I have a minor problem, I used some LaTeX format commands. I know I
> might get away by replacing \textbf with **, etc.
Yes, that's the way to go. Should be quick with M-x replace-regexp.
> But know its
> there already. Sure it worked out great for the LaTeX-PDF export.
> However, in openoffice I had stuff like \textbf{text}. I was
> wondering, the exporter is doing all this nifty work already, could we
> have a flag to replace the most common Linux inline text-formats by
> the corresponding odt format?
Mhh... I think it would be too hackish. Converting \textbf{...} to
*...* in .org files just for converting them back to another format
means that \textbf{...} shouldnot be used on the first place. But
maybe I'm misunderstanding something...
Best,
--
Bastien
Re: [O] Org tasks from gnus
Rasmus writes: [...] > As others said, use org-complete. Most of my TODOs link to a mail. [...] I think you meant org-capture, as described by your example setup. :) Org-capture works indeed fine for me. -- Jérémie Courrèges-Anglas GPG fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494 pgpvKC9fht3Wi.pgp Description: PGP signature
[O] [odt] Export of LaTeX Fragments
Hi,
today I had to send over a document in MS Word format. Suprise suprise
guess I am not the first one on that mailing list.
I was happy to use the new odt export feature and it did the best job
out of some other constellations (org->html->word, org->pdf->odt via
pdf import plugin, org->pdf->copy paste, etc.)
Thanks for this brilliant feature!
I have a minor problem, I used some LaTeX format commands. I know I
might get away by replacing \textbf with **, etc. But know its
there already. Sure it worked out great for the LaTeX-PDF export.
However, in openoffice I had stuff like \textbf{text}. I was
wondering, the exporter is doing all this nifty work already, could we
have a flag to replace the most common Linux inline text-formats by
the corresponding odt format?
\textbf
\textit
\underline
\mbox (no line break)
\, (protected blank)
would be a good start
Thanks
Torsten
Re: [O] flyspell and code blocks
Julian Burgos writes: > Hello fellow org'ers, > > It is possible to make flyspell to ignore (i.e. do not spell check) > the text within code blocks (I mean blocks of texts separated by > #+begin_src and #+end src)? I did my homework but could not find a > good answer. > Many thanks, See http://lists.gnu.org/archive/html/help-gnu-emacs/2012-02/msg00162.html which links to the following bug report http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10804 > Julian --
[O] flyspell and code blocks
Hello fellow org'ers, It is possible to make flyspell to ignore (i.e. do not spell check) the text within code blocks (I mean blocks of texts separated by #+begin_src and #+end src)? I did my homework but could not find a good answer. Many thanks, Julian -- Julian Mariano Burgos, PhD Hafrannsóknastofnunin/Marine Research Institute Skúlagata 4, 121 Reykjavík, Iceland Sími/Telephone : +354-5752037 Bréfsími/Telefax: +354-5752001 Netfang/Email: jul...@hafro.is
Re: [O] [PATCH] Add info when reference to remote table is not in the file
Hi Sébastien, "Sebastien Vauban" writes: > Hi Bastien, > > "Sebastien Vauban" wrote: >>> You can also go back to the *Messages* buffer and check from there. >>> >>> Maybe another option is to silent `org-id-update-id-locations' when called >>> from `org-id-find'? Does the attached patch against master improves the >>> situation for you? >> >> In all cases, this is already an improvement. So, I would definitely check >> this in. Thanks. > > That said, I still find we should be able to refer to tables names whose > TBLNAME keyword could be spelled both: > > - in downcase version (#+tblname: abc) and > - in uppercase version (#+TBLNAME: xyz). I've now pushed a patch for this -- please confirm it works as expected. Thanks, -- Bastien
Re: [O] [PATCH] customize latex table export
Hi Christophe, Bastien writes: > Hi Christophe, > > Christophe Rhodes writes: > >> Again, is there anything more I can do to get this functionality >> (customizing header lines of tables in LaTeX export, in case everyone >> has lost the context) into org-mode? > > I saw your patch, thanks for it. > > I'm willing to apply it, but I will do when I have a good idea of how it > interacts with Niels proposal, and maybe a generalization of Niels idea, > where it would be possible to set a default #+ATTR for tables, images, > etc. I applied an updated version of your patch, without macrolet. Thanks for your patchience*, * The ability to wait for a patch to be applied. -- Bastien
Re: [O] Patch to customize output of tables in LaTeX exporter.
Niels Giesen writes: > Attached is a patch that allows some customization of tables in LaTeX > export. > > It adds three new customizable with default values: > > org-export-latex-tables-tstart : nil > org-export-latex-tables-hline : "\\hline" > org-export-latex-tables-tend : nil Finally applied, thanks. -- Bastien
Re: [O] Leading zeros in plain lists
SW writes: > Bastien gnu.org> writes: > >> >> SW gmail.com> writes: >> >> > Is it possible to include leading zeros in plains lists: >> > >> > 01. Item 1 >> > 02. Item 2 >> >> No, sorry. >> > Ok :) It was just to avoid lists looking out alignment: > > 8. Fetch the package > 9. Open the package > 10. Look inside the package > > But I can live with it :) I hope so :) Again, for such visual changes, a solution based on overlays is clearly the way to go. -- Bastien
Re: [O] [PATCH] Dynamically demote included file relatively to the current heading level
Hi Daniel, Daniel Dehennin writes: > You can get the following patchset by pulling: > > git pull git://git.baby-gnu.net/org-mode dad/add-level-to-headings > > Regards. > > This patch permits a more flexible usage than :minlevel. I applied your patch with a small modification that fixes it. Thanks for your contribution and sorry for the delay. Best, -- Bastien
Re: [O] [PATCH] org-read-date-overlay shown in other buffers, point in calendar window defaults to end of line
Zachary Kanfer writes: > This patch fixes two bugs in the same section of code: Thanks a lot for the clear explanations. This patch has been applied in master. Best, -- Bastien
Re: [O] Leading zeros in plain lists
Bastien gnu.org> writes: > > SW gmail.com> writes: > > > Is it possible to include leading zeros in plains lists: > > > > 01. Item 1 > > 02. Item 2 > > No, sorry. > Ok :) It was just to avoid lists looking out alignment: 8. Fetch the package 9. Open the package 10. Look inside the package But I can live with it :)
Re: [O] [PATCH] Option for clock and timer to be displayed in frame-title
g.kettleboro...@uea.ac.uk writes: > Attached is a patch that gives the option to show the clock and timer > information in the frame title as well as the mode line (or both or > neither). I find this useful as there is often not enough room in the > mode line but there is enough in the frame title. This has been applied to master. Please test and confirm it works as expected. -- Bastien
Re: [O] [patch] Need test: New method which is used to preview latex fragements
Hi Feng, this patch is now in master, with some small modifications. Thanks for this contribution! -- Bastien
Re: [O] [PATCH] org-clock-modify-effort-estimate: display a message when no clock is active
This patch has been applied. Please test and confirm it works as expected. Thanks! -- Bastien
Re: [O] [PATCH] Support hour in repeated task cookie
Hi Takafumi, Takafumi Arakaki writes: > No comments? No one wants to have "+3h" in SCHEDULED? I applied this patch, thanks. Note that timestamps need to be well formatted. If there is a +3d repeat cookie and the original timestamp doesn have any indication for the hour, it will produce an error. -- Bastien
Re: [O] [PATCH] Show human-readable link descriptions first when inserting links
Hi Dave, Dave Abrahams writes: > This patch makes it easy to select links from among a forest of > similar-looking machine-readable forms. Without it, the human-readable > descriptions tend to fall off the right side of the window. I applied a slightly modified version of this patch. Thanks for your patience! -- Bastien
Re: [O] Leading zeros in plain lists
SW writes: > Is it possible to include leading zeros in plains lists: > > 01. Item 1 > 02. Item 2 No, sorry. -- Bastien
Re: [O] [PATCH] Add svg export using pdf2svg, for latex math and src blocks.
Tom Prince writes: > This is my attempt to add export of latex code (for HTML export) > via svg, rather than png. I don't know if this is the best way to go > about doing it, but I wanted to avoid as much duplicated code as > possible. Please let us know about your progress on this feature and on the question whether you want to assign your copyright to FSF for big contributions to Emacs. Thanks, -- Bastien
Re: [O] [PATCH] Replace all calls to (eq major-mode 'org-mode) with (derived-mode-p 'org-mode)
Hi Cássio, Cássio Koshikumo writes: > A while ago I asked about changing the Major Mode checking that happens > throughout Org, so that derived modes would function properly. I finally had > the time to make a patch. I applied an updated version of this patch. Thanks, -- Bastien
[O] Leading zeros in plain lists
Is it possible to include leading zeros in plains lists: 01. Item 1 02. Item 2
Re: [O] [PATCH] Allow % escapes to capture templates, expanded to text entered in 'th prompt
Hi Toby, Toby Cubitt writes: > Currently, capture templates provide no way of prompting for some text, > then inserting that text into multiple places in the template. Thanks for the patch, I applied it. I also updated the documentation in doc/org.texi -- please provide documentation in the patch containing code changes if relevant next times. One tiny thing: the documentation said that %0 would match the first occurrence but while I tested the first occurrence was on %1, which looks better to me. So I updated the documentation accordingly. Best, -- Bastien
Re: [O] [PATCH] Add option to skip timestamp entries if already displayed as deadline entries in agenda
Toby Cubitt writes: > This one's pretty self-explanatory. It adds an > `org-agenda-skip-timestamp-if-deadline-is-shown' customization option, > precisely analogous to the existing > `org-agenda-skip-scheduled-if-deadline-is-shown' option. Thanks for this, I just applied this patch. -- Bastien
Re: [O] [PATCH] Extract prefix information from diary sexp entries for agenda display
Toby Cubitt writes: > This patch adds a new org-agenda-diary-sexp-prefix customization > option. It can be set to a regexp which is used to match the part of the > text produced by a diary sexp entry that should be treated as > deadlining/scheduling information (the "prefix"), and displayed as such > in agenda views. Applied, thanks. -- Bastien
Re: [O] Change example timestamps to not occur in headlines
Hi Brian, Brian van den Broek writes: > I agree that the discouragement of timestamps in headlines should > remain in the docs. > > But I still do think the docs examples should be changed to comply > with that advice. I tried twice to send a patch, yet failed to do so > in a manner recognized by patchwork. One of your patches made it to patchword. > I *think* I know how now, but > elected not to send a third attempt. Should I send it once again? No, it has already been applied: http://orgmode.org/w/?p=org-mode.git;a=commit;h=8f3dc945 Thanks! -- Bastien
Re: [O] Change example timestamps to not occur in headlines
On 23 Apr 2012 12:15, "Bastien" wrote: > > Hi Samuel, > > Samuel Wales writes: > > > On 2012-04-20, John Hendy wrote: > > I've attached a small patch to the documentation that resolves a > > conflict between the manual's advice not to include timestamps in > > headlines and some of its examples where it does just that. > > > > Does this advice apply any more? > > Yes it does. > > > Perhaps it shoudl be removed. > > So no... let's stick to the current version of the manual. Hi Bastien and all, I agree that the discouragement of timestamps in headlines should remain in the docs. But I still do think the docs examples should be changed to comply with that advice. I tried twice to send a patch, yet failed to do so in a manner recognized by patchwork. I *think* I know how now, but elected not to send a third attempt. Should I send it once again? Best, Brian vdB
Re: [O] make update fails
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/04/12 14:25, Rainer M Krug wrote:
> On 23/04/12 14:17, Detlef Steuer wrote:
>> Did a fresh pull
>
>> git clone git://orgmode.org/org-mode.git
>
>> after
>
>> make update
>
>> failed with some errors.
>
>> Did an make update
>
>> immediately after pulling and ended there:
>
>> mkdir -p /tmp/tmp-orgtest TMPDIR=/tmp/tmp-orgtest emacs -batch -Q -L lisp/
>> -L testing/
>> --eval '(defconst org-release "7.8.09-Test")' -l testing/org-test.el --eval
>> '(require
>> '"'"'ob-awk)' --eval '(require '"'"'ob-C)' --eval '(require
>> '"'"'ob-fortran)' --eval
>> '(require '"'"'ob-maxima)' --eval '(require '"'"'ob-lilypond)' --eval
>> '(require
>> '"'"'ob-octave)' --eval '(require '"'"'ob-python)' --eval '(require
>> '"'"'ob-sh)' --eval
>> '(setq org-confirm-babel-evaluate nil)' -f org-test-run-batch-tests Cannot
>> open load file:
>> ert make[1]: *** [check] Fehler 255 make[1]: Leaving directory
>> `/home/steuer/GIT/org-mode'
>> make: *** [update] Fehler 2
>
>
> Can confirm this.
Org version: 7.8.09 (release_7.8.09-373-gd592b0)
>
> In addition: emacs doesn't load emacs.org file anymore:
>
>
> Debugger entered--Lisp error: (void-function org-babel-load-file)
> (org-babel-load-file
> "~/.emacs.d/emacs.org") eval-buffer(# nil
> "/home/rkrug/.emacs.d/init.el" nil t)
> ; Reading at buffer position 625
> load-with-code-conversion("/home/rkrug/.emacs.d/init.el"
> "/home/rkrug/.emacs.d/init.el" t t) load("/home/rkrug/.emacs.d/init" t t)
> #[nil "\205\264
>
>
> Cheers,
>
> Rainer
>
>
>> Thx for looking into this!
>
>
>
>> Detlef
>
>
>
>
- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys.
(Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D):+49 - (0)3 21 21 25 22 44
email: rai...@krugs.de
Skype: RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+VTHgACgkQoYgNqgF2egqoOgCeNPMyjvRbeW+gtJelkK3KtcRn
Hs0Ani6ehiEyE0HOIt42TH0DPBpIs50b
=/w0y
-END PGP SIGNATURE-
Re: [O] Org tasks from gnus
Kyle Sexton writes:
> Does anyone know a way to automatically create/link org-tasks from Gnus
> messages? My current workflow is to just start a new capture and type
> in or paste some of the relevant info, but if org could link to the
> message that would be ideal.
As others said, use org-complete. Most of my TODOs link to a mail.
Here's something to get you started (from my org-config.org). Then just
call C-c c from a Gnus mail. Add what needs to be added and C-c C-c.
It's in your agenda (assuming ~/documents/todo.org in in your Org agenda
list)
#+begin_src org
* Capture
Capture is used to capture things... It is the new thing
#+begin_src emacs-lisp
(setq org-default-notes-file (concat org-directory "~/documents/noter.org"))
(define-key global-map "\C-cc" 'org-capture)
#+end_src
It needs templates
#+begin_src emacs-lisp
(setq org-capture-templates
'(("t" "Todo" entry (file+headline "~/documents/todo.org" "Tasks")
"* TODO %?\n %i\n %a")
("w" "Word" entry
(file+headline "~/documents/words.org" "Sweet Words")
"* %:subject %?
%i%a")
;; ("j" "Journal" entry (file+datetree
"~/documents/unidocs/journal.org")
;; "* %?\nEntered on %U\n %i\n %a")
))
#+end_src
–Ramsus
--
This is the kind of tedious nonsense up with which I will not put
Re: [O] make update fails
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/04/12 14:17, Detlef Steuer wrote:
> Did a fresh pull
>
> git clone git://orgmode.org/org-mode.git
>
> after
>
> make update
>
> failed with some errors.
>
> Did an make update
>
> immediately after pulling and ended there:
>
> mkdir -p /tmp/tmp-orgtest TMPDIR=/tmp/tmp-orgtest emacs -batch -Q -L lisp/
> -L testing/ --eval
> '(defconst org-release "7.8.09-Test")' -l testing/org-test.el --eval
> '(require '"'"'ob-awk)'
> --eval '(require '"'"'ob-C)' --eval '(require '"'"'ob-fortran)' --eval
> '(require
> '"'"'ob-maxima)' --eval '(require '"'"'ob-lilypond)' --eval '(require
> '"'"'ob-octave)' --eval
> '(require '"'"'ob-python)' --eval '(require '"'"'ob-sh)' --eval '(setq
> org-confirm-babel-evaluate nil)' -f org-test-run-batch-tests Cannot open load
> file: ert
> make[1]: *** [check] Fehler 255 make[1]: Leaving directory
> `/home/steuer/GIT/org-mode' make:
> *** [update] Fehler 2
Can confirm this.
In addition: emacs doesn't load emacs.org file anymore:
Debugger entered--Lisp error: (void-function org-babel-load-file)
(org-babel-load-file "~/.emacs.d/emacs.org")
eval-buffer(# nil "/home/rkrug/.emacs.d/init.el" nil t) ;
Reading at buffer
position 625
load-with-code-conversion("/home/rkrug/.emacs.d/init.el"
"/home/rkrug/.emacs.d/init.el" t t)
load("/home/rkrug/.emacs.d/init" t t)
#[nil "\205\264
Cheers,
Rainer
>
> Thx for looking into this!
>
> Detlef
>
>
- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys.
(Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D):+49 - (0)3 21 21 25 22 44
email: rai...@krugs.de
Skype: RMkrug
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+VSlUACgkQoYgNqgF2egrgCQCfXlppwTH/77vLc36+K9lN3sse
kscAnjAc6PAeiPjaFJvcnEeZ2nrPpb7Q
=bNgO
-END PGP SIGNATURE-
[O] make update fails
Did a fresh pull git clone git://orgmode.org/org-mode.git after make update failed with some errors. Did an make update immediately after pulling and ended there: mkdir -p /tmp/tmp-orgtest TMPDIR=/tmp/tmp-orgtest emacs -batch -Q -L lisp/ -L testing/ --eval '(defconst org-release "7.8.09-Test")' -l testing/org-test.el --eval '(require '"'"'ob-awk)' --eval '(require '"'"'ob-C)' --eval '(require '"'"'ob-fortran)' --eval '(require '"'"'ob-maxima)' --eval '(require '"'"'ob-lilypond)' --eval '(require '"'"'ob-octave)' --eval '(require '"'"'ob-python)' --eval '(require '"'"'ob-sh)' --eval '(setq org-confirm-babel-evaluate nil)' -f org-test-run-batch-tests Cannot open load file: ert make[1]: *** [check] Fehler 255 make[1]: Leaving directory `/home/steuer/GIT/org-mode' make: *** [update] Fehler 2 Thx for looking into this! Detlef
Re: [O] Change example timestamps to not occur in headlines
Hi Samuel, Samuel Wales writes: > On 2012-04-20, John Hendy wrote: > I've attached a small patch to the documentation that resolves a > conflict between the manual's advice not to include timestamps in > headlines and some of its examples where it does just that. > > Does this advice apply any more? Yes it does. > Perhaps it shoudl be removed. So no... let's stick to the current version of the manual. -- Bastien
Re: [O] Makefile restructuring
Hi Achim, On Sun, Apr 22, 2012 at 17:34, Achim Gratz wrote: > suvayu ali writes: >> The above recipe works. But just "make", leaves the working tree without >> lisp/org-install.el. From the log I see it explicitly deletes it, but >> doesn't generate it again. A subsequent "make autoloads" is required to >> get a working org setup. Is this expected behaviour? > > This is intentional. The autoloads are generated just before > installing, since that's where they are needed. I really don't want to > encourage further use of the git worktree as the "org installation", > although it sort of works if you do a "make autoloads". > Thanks for the clarifications. :) > You can now easily keep multiple installations within the org directory > if so desired (I do this myself for testing). Using the worktree > instead can lead to very hard to track bugs when the autoload files get > out of sync with the sources. This is the reason I always remove them > before compilation and I should probably remove them just after > installation as well. Okay I'll try this out. -- Suvayu Open source is the future. It sets us free.
Re: [O] [PATCH] Following gnus links: Don't mark unrelated articles read
Hi Matt, Matt Lundin writes: > * lisp/org-gnus.el: (org-gnus-follow-link): Fix argument to > gnus-group-read-group so that following a link does not result in > unread article being selected. Applied, thanks. -- Bastien
Re: [O] Org tasks from gnus
Kyle Sexton writes:
> Does anyone know a way to automatically create/link org-tasks from Gnus
> messages? My current workflow is to just start a new capture and type
> in or paste some of the relevant info, but if org could link to the
> message that would be ideal.
I've the following recipe in my org-capture-template:
("m" "mailnote" entry (file+headline "~/org/notes.org" "Notes")
"** From: %:from Subject: %:subject\n %a" :kill-buffer t)
So when I do `C-c r m` it create a note with a link to the relevant gnus
message. Look at http://orgmode.org/manual/Template-expansion.html for
other %:something.
--
Rémi Vanicat
