Re: [O] Patch: Mark org-diary-class as obsolete and skip entries on holidays in org-class
Hi Rüdiger, On Oct 10, 2011, at 9:15 PM, Rüdiger Sonderfeld wrote: > Hello, > I wrote two small patches. The first one marks org-diary-class as obsolete > (according to its documentation it is deprecated). The second one is a > patch for org-class. It changes org-class to skip entries that are on > holidays. The first is accepted. The second I have modified. If any of SKIP-WEEKS is the symbol `holidays', then holidays will be skipped. Thanks! - Carsten > > Maybe the second change should be made optional. > > Regards, > Rüdiger > > P.S. I have signed the FSF papers. > <0001-Mark-org-diary-class-as-obsolete-use-org-class.patch><0002-org-class-Skip-entries-on-holidays.patch> - Carsten
Re: [O] [RFC] Standardized code block keywords
> > Daniel (who used Babel to write his thesis in one big file with all data > > and chart generating code interleaved with the text -- faboulous!) > > Indeed - could we hope to get a glimpse at some examples (or even the whole > thing) at some point? Unfortunately not at the moment, because we're still in the process of getting the topic published. > Nick > > PS. I presume it's clear to all that this silliness I started has a big > smilie wrapped around the whole thing, but just in case somebody decides > that I'm serious: pthvhtththth :-) Yeah, that's clear. :-D Have a nice day Daniel
Re: [O] Bind an agenda filter to a global shortcut
Marcelo de Moraes Serpa writes: > Hmm, I actually already do that. The shortcut is not bad, but what I > want to do is to bind it to a single keypress. With the custom agenda > view, I still need to C-c a and then the shortcut, which is not bad, > but there are one or two views that I use too often, and I'm being > spoiled by VIM, I would like a single keypress :) So just bind your favourite key to the view you want. (global-set-key (kbd "") (lambda () (interactive) (org-agenda nil "X"))) to make f9 do the same as C-c a X -Bernt
Re: [O] Bind an agenda filter to a global shortcut
Hmm, I actually already do that. The shortcut is not bad, but what I want to do is to bind it to a single keypress. With the custom agenda view, I still need to C-c a and then the shortcut, which is not bad, but there are one or two views that I use too often, and I'm being spoiled by VIM, I would like a single keypress :) Anyway, thanks for pointing out the manual page. Marcelo. On Wed, Oct 26, 2011 at 4:44 PM, Marcelo de Moraes Serpa < celose...@gmail.com> wrote: > Obrigado Darlan :) I'll check it out. > > > On Wed, Oct 26, 2011 at 3:34 PM, Darlan Cavalcante Moreira < > darc...@gmail.com> wrote: > >> >> You can do this (and more) with the custom agenda views [1]. >> >> [1] >> http://orgmode.org/manual/Custom-agenda-views.html#Custom-agenda-views >> >> -- >> Darlan >> >> At Wed, 26 Oct 2011 12:13:52 -0500, >> Marcelo de Moraes Serpa wrote: >> > >> > [1 ] >> > Hi list, >> > >> > So, I'd like to bind a specific agenda filter to a simple one-key >> shortcut, >> > maybe one of the function keys. This might be an easy think to do, but >> I'm >> > not sure how. How could I trigger an agenda filter action directly >> through >> > elisp (without needing to go to the agenda view and use the shortcut I >> > made?) so that I can bind it straight to a global shortcut? >> > >> > Thanks, >> > >> > Marcelo. >> > [2 ] >> > >> > >
Re: [O] Bind an agenda filter to a global shortcut
Obrigado Darlan :) I'll check it out. On Wed, Oct 26, 2011 at 3:34 PM, Darlan Cavalcante Moreira < darc...@gmail.com> wrote: > > You can do this (and more) with the custom agenda views [1]. > > [1] http://orgmode.org/manual/Custom-agenda-views.html#Custom-agenda-views > > -- > Darlan > > At Wed, 26 Oct 2011 12:13:52 -0500, > Marcelo de Moraes Serpa wrote: > > > > [1 ] > > Hi list, > > > > So, I'd like to bind a specific agenda filter to a simple one-key > shortcut, > > maybe one of the function keys. This might be an easy think to do, but > I'm > > not sure how. How could I trigger an agenda filter action directly > through > > elisp (without needing to go to the agenda view and use the shortcut I > > made?) so that I can bind it straight to a global shortcut? > > > > Thanks, > > > > Marcelo. > > [2 ] > > >
Re: [O] Bind an agenda filter to a global shortcut
You can do this (and more) with the custom agenda views [1]. [1] http://orgmode.org/manual/Custom-agenda-views.html#Custom-agenda-views -- Darlan At Wed, 26 Oct 2011 12:13:52 -0500, Marcelo de Moraes Serpa wrote: > > [1 ] > Hi list, > > So, I'd like to bind a specific agenda filter to a simple one-key shortcut, > maybe one of the function keys. This might be an easy think to do, but I'm > not sure how. How could I trigger an agenda filter action directly through > elisp (without needing to go to the agenda view and use the shortcut I > made?) so that I can bind it straight to a global shortcut? > > Thanks, > > Marcelo. > [2 ] >
Re: [O] Orgmode performance problem and "solution"
Yes, after the pull, cleaning, then making would have to be done. I believe everyone wass aware of that but the concern here was how to switch grom a lagging repo to the more up to date repo for the pull. On Wednesday, October 26, 2011, Dave Abrahams wrote: > > on Wed Oct 26 2011, suvayu ali wrote: > >> On Wed, Oct 26, 2011 at 10:07, Rainer Stengele >> wrote: >>> Lacking knowledge of git I deleted everything, cloned from the new repo and compiled the files. >>> Result was a significantly faster Org experience. >>> >> >> For future reference, a sinple `git pull` would have sufficed. > > Not if there were compiled files. > > -- > Dave Abrahams > BoostPro Computing > http://www.boostpro.com > > >
[O] Trying to use a custom face for highlighting tags used in agenda filtering
Hello,
I tried modifying the lines of defun org-agenda-set-mode-name, line 6764, so
that tags are highlighted in the mode-line.
#+begin_src emacs-lisp
(if (or org-agenda-filter (get 'org-agenda-filter
:preset-filter))
'(:eval (concat " {" (propertize (mapconcat
'identity
(append (get
'org-agenda-filter
:preset-filter)
org-agenda-filter)
"")
'face 'compilation-warning
'help-echo "Tags used in
filtering"
)
"}")
)
"")
#+end_src
While my code seems correct, it is not applied -- or, maybe, the face is
overwritten by another one, in which case I don't know how to debug: I can't
do C-u C-x = on the mode-line...
Any idea?
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [babel] Announcing ob-picolisp.el
Thorsten writes: > Eric Schulte writes: > >> Thorsten, if copying ob-picolisp to contrib/babel/langs until your FSF >> paperwork is completed sounds agreeable to you I will move it over now. > > Sure, no problem, go ahead. > Done, Thanks -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] Tags included in subtree export title despite tags:nil in header
Hi, I have an org file with lots of notes for myself. I sometimes export it to html for reading on the browser. I also have a subtree where I wrote beamer presentation about the project. I would like to exclude this from the html export, so I tag it with noexport. Now when I do a subtree export to get the beamer presentation, my presentation has the title: "Text in headline :noexport:". Is there any way to exclude the tag from the exported title short of toggling the tag before export or setting the EXPORT_TITLE property? I was expecting this to work out of the box since I already have tags:nil in the file header. Would this be considered as a bug? -- Suvayu Open source is the future. It sets us free.
[O] [PATCH] Stealth org-link-search
Hello, I don't think there is a decent way to search for a link destination without modifying buffer's visibility around match. This can be very annoying when resolving links in background. So, if I'm right, the following patch will fill that gap. Regards, -- Nicolas Goaziou >From d489f27969d4d4e80bfa07d229c3f4a57d2da7c8 Mon Sep 17 00:00:00 2001 From: Nicolas Goaziou Date: Wed, 26 Oct 2011 19:53:06 +0200 Subject: [PATCH] Add a way to search for a link search without impacting buffer visibility * lisp/org.el (org-link-search): Add an optional argument preventing function from revealing context around match. --- lisp/org.el | 13 ++--- 1 files changed, 10 insertions(+), 3 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 2599d41..5cb1fcd 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -9758,13 +9758,18 @@ the window configuration before `org-open-at-point' was called using: (set-window-configuration org-window-config-before-follow-link)") (defvar org-link-search-inhibit-query nil) ;; dynamically scoped -(defun org-link-search (s &optional type avoid-pos) +(defun org-link-search (s &optional type avoid-pos stealth) "Search for a link search option. If S is surrounded by forward slashes, it is interpreted as a regular expression. In org-mode files, this will create an `org-occur' sparse tree. In ordinary files, `occur' will be used to list matches. If the current buffer is in `dired-mode', grep will be used to search -in all files. If AVOID-POS is given, ignore matches near that position." +in all files. If AVOID-POS is given, ignore matches near that position. + +When optional argument STEALTH is non-nil, do not modify +visibility around point, thus ignoring +`org-show-hierarchy-above', `org-show-following-heading' and +`org-show-siblings' variables." (let ((case-fold-search t) (s0 (mapconcat 'identity (org-split-string s "[ \t\r\n]+") " ")) (markers (concat "\\(?:" (mapconcat (lambda (x) (regexp-quote (car x))) @@ -9888,7 +9893,9 @@ in all files. If AVOID-POS is given, ignore matches near that position." (goto-char (match-beginning 1)) (goto-char pos) (error "No match")) -(and (eq major-mode 'org-mode) (org-show-context 'link-search)) +(and (eq major-mode 'org-mode) + (not stealth) + (org-show-context 'link-search)) type)) (defun org-search-not-self (group &rest args) -- 1.7.7.1
[O] [ANN][RFC] org-odt.texi/org-odt.pdf preview (was Re: Org-odt table format)
The org-odt.texi and org-odt.pdf are in the parent of this mail. It is also accessible as attachment at http://article.gmane.org/gmane.emacs.orgmode/48468 Proof readers invited. --
[O] [Accepted] org-capture and XEmacs, indenting too far
Patch 1002 (http://patchwork.newartisans.com/patch/1002/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3Cy9lipnhjd8w.fsf%40deinprogramm.de%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [O] org-capture and XEmacs, indenting too far
> Date: Sat, 22 Oct 2011 19:46:07 -
> From: Michael Sperber
> X-Patchwork-Id: 1002
> Message-Id:
> To: emacs-orgmode@gnu.org, Robert Pluim ,
> carsten.domi...@gmail.com
>
> Robert Pluim writes:
>
> > Hi, I'm using XEmacs 21.5 (beta29) "garbanzo" d27c1ee1943b+ [Lucid]
> > (i686-pc-cygwin, Mule) of Mon Oct 18 2010 on RPluim, with the following
> > org-capture-templates
> >
> > (("t" "Todo" entry (file+headline "~/org/notes.org" "Tasks") "* TODO %?"))
> >
> > The problem is that for some reason the resulting TODO heading is has 2
> > extra spaces, and is placed at too deep a level, giving:
> >
> > * Tasks
> > *** TODO a task
> >
> > I've tested this on a fairly recent emacs24 build, and everything works
> > fine there, so this is probably something XEmacs specific. Can anyone
> > suggest any way to track this down (I'd bisect, but I've yet to find a
> > 'good' version)?
>
> I finally got around to looking into this: The reason is that, in
> org-capture mode, `outline-level' is bound to outline.el's function,
> which is off by one compared to org-mode's. I used this patch to fix
> it:
>
>
> Could somebody review and maybe apply this?
>
>
> diff --git a/lisp/org-capture.el b/lisp/org-capture.el
> index e1b8a4f..cfa35d5 100644
> --- a/lisp/org-capture.el
> +++ b/lisp/org-capture.el
> @@ -848,6 +848,7 @@ it. When it is a variable, retrieve the value. Return
> whatever we get."
>(goto-char (org-capture-get :pos))
>(org-set-local 'org-capture-target-marker
>(move-marker (make-marker) (point)))
> + (org-set-local 'outline-level 'org-outline-level)
>(let* ((template (org-capture-get :template))
>(type (org-capture-get :type)))
> (case type
>
Re: [O] Bug: [testing] missing dependency [7.7 (release_7.7.340.ga342)]
on Wed Oct 26 2011, Bastien wrote: > Hi Dave, > > Dave Abrahams writes: > >> testing/README.org mentions the dependency on jump.el, but not on the >> ESS package, which appears to be required for `(org-test-load)' to >> work > > `org-test-load' works fine here without requiring the ESS package. > > Can you check again? I probably don't have time, sorry. Did you try this with a fresh emacs -Q? -- Dave Abrahams BoostPro Computing http://www.boostpro.com
Re: [O] org-velocity load problem
Hi, d.tchin writes: > This post just to warn that org-velocity is not loaded with Emacs 22.3.1. > > I try to load org-velocity but I have the following message : > error: Unknown keyword :safe > > I use GNU Emacs 22.3.1 (i386-mingw-nt6.1.7601) and Org-mode version 7.7. > > I had the possibility to try with emacs 23.3 with the same org-mode version > and it is loaded correctly. > > After investigation, it seems related to custom.el file. Indeed the keyword > is > defined in the later version of emacs. Thanks for the information -- we try to maintain backward compatibility of Org's core code with old versions of Emacs, but code in contrib/ does not come with the same expectations... it would certainly be too much for many libraries. -- Bastien
Re: [O] org-capture and XEmacs, indenting too far
Hi Michael, Michael Sperber writes: > Looking at this again, my analysis was stupid: The problem is that the > indirect buffer used for capture is not in org-mode at all, and that is > indeed an XEmacs-specific problem, as `make-indirect-buffer' does not > accept the 'clone argument on XEmacs. I therefore retract the rubbish I > sent earlier and suggest this one instead: Applied, thanks for this. -- Bastien
Re: [O] [patch] Re: LATEX_CLASS_OPTIONS in SETUPFILE
Hi Christophe, Christophe Rhodes writes: > Please find a patch attached addressing this issue. Applied, with some minor typo correction in the ChangeLog. Thanks for writing it! -- Bastien
Re: [O] HTML export, TODO keyword face
Hi Peter,
Peter Baranyi writes:
> I set up org todo keyword faces like so:
>
> (setq org-todo-keyword-faces
> '(("FAIL" . org-warning)
> ("MISSING" . org-warning)
> ))
>
> But at html export, the keywords are green because they are done
> states. So additionally I have to set :
>
> (setq org-export-html-style-extra
> "
>
> ")
>
> I think the default style should be what is set in
> org-todo-keyword-faces.
This would be nice but would require much more flexibility than
what `org-export-html-style-default' provides for now. But you
found the workaround, and it's not that far.
Thanks for sharing this,
--
Bastien
Re: [O] [Bug] Return on description link
Hi Maximilian, maxi.mat...@googlemail.com (Maximilian Matthé) writes: > See the attached org-file for more information. Hitting return on a link > in a description list does not follow the link but insert . > > I have org-return-follows-link set to t. This is now fixed in git, thanks! -- Bastien
[O] Bind an agenda filter to a global shortcut
Hi list, So, I'd like to bind a specific agenda filter to a simple one-key shortcut, maybe one of the function keys. This might be an easy think to do, but I'm not sure how. How could I trigger an agenda filter action directly through elisp (without needing to go to the agenda view and use the shortcut I made?) so that I can bind it straight to a global shortcut? Thanks, Marcelo.
[O] [Accepted] Addition of default-description parameter to org-insert-link
Patch 1010 (http://patchwork.newartisans.com/patch/1010/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3CCABAjAKc0XK4ZJX6Cw%3DPhWAq24EmYNwSzbDVu378XUa4JMbEr_g%40mail.gmail.com%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [O] Addition of default-description parameter to org-insert-link > Date: Wed, 26 Oct 2011 21:47:46 - > From: Yuri Lenskiy > X-Patchwork-Id: 1010 > Message-Id: > > To: emacs-orgmode@gnu.org > > This patch, against the stable 7.7 branch version of org.el, adds a > default-description argument to org-insert-link that, if non-nil, will > become the default description. > > - Yuri Lenskiy > > > diff --git a/lisp/org.el b/lisp/org.el > index c29ef11..bf6daab 100644 > --- a/lisp/org.el > +++ b/lisp/org.el > @@ -8854,7 +8854,7 @@ This command can be called in any mode to insert a link > in Org-mode syntax." >(org-load-modules-maybe) >(org-run-like-in-org-mode 'org-insert-link)) > > -(defun org-insert-link (&optional complete-file link-location) > +(defun org-insert-link (&optional complete-file link-location > default-description) >"Insert a link. At the prompt, enter the link. > > Completion can be used to insert any of the link protocol prefixes like > @@ -8890,7 +8890,10 @@ called with the link target, and the result will be > the default > link description. > > If the LINK-LOCATION parameter is non-nil, this value will be > -used as the link location instead of reading one interactively." > +used as the link location instead of reading one interactively. > + > +If the DEFAULT-DESCRIPTION parameter is non-nil, this value will > +be used as the default description." >(interactive "P") >(let* ((wcf (current-window-configuration)) >(region (if (org-region-active-p) > @@ -9020,6 +9023,7 @@ Use TAB to complete link prefixes, then RET for > type-specific completion support > (if org-make-link-description-function > (setq desc (funcall org-make-link-description-function link desc))) > > +(if default-description (setq desc default-description)) > (setq desc (read-string "Description: " desc)) > (unless (string-match "\\S-" desc) (setq desc nil)) > (if remove (apply 'delete-region remove)) >
Re: [O] Bug: [testing] missing dependency [7.7 (release_7.7.340.ga342)]
Hi Dave, Dave Abrahams writes: > testing/README.org mentions the dependency on jump.el, but not on the > ESS package, which appears to be required for `(org-test-load)' to > work `org-test-load' works fine here without requiring the ESS package. Can you check again? Thanks! -- Bastien
Re: [O] "git describe" in version of info file with "make info_git_describe"
Michael Brand writes: > There has not yet been any review or comment on the changes in the > Makefile and in UTILITIES/set-version.pl. I would be happy if these > parts could be reviewed too. The set-version.pl file may be obsolete (perl is still required), there is no version number in the individual lisp files anymore. For installation I've already added a replacement of the version cookie in org.el with git-describe in my own fork of org-mode ([1] - I don't know if you've checked it). It would be easy to do the same for org-texi, albeit before compilation, not only during install. I I agree it would be useful to have the full version recorded in the resulting manual, but you really cannot alter the source file (git status would always be dirty or the version would be wrong, wouldn't it? :-). [1] http://permalink.gmane.org/gmane.emacs.orgmode/44567 Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
[O] [PATCH] Addition of default-description parameter to org-insert-link
This patch, against the stable 7.7 branch version of org.el, adds a default-description argument to org-insert-link that, if non-nil, will become the default description. - Yuri Lenskiy diff --git a/lisp/org.el b/lisp/org.el index c29ef11..bf6daab 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -8854,7 +8854,7 @@ This command can be called in any mode to insert a link in Org-mode syntax." (org-load-modules-maybe) (org-run-like-in-org-mode 'org-insert-link)) -(defun org-insert-link (&optional complete-file link-location) +(defun org-insert-link (&optional complete-file link-location default-description) "Insert a link. At the prompt, enter the link. Completion can be used to insert any of the link protocol prefixes like @@ -8890,7 +8890,10 @@ called with the link target, and the result will be the default link description. If the LINK-LOCATION parameter is non-nil, this value will be -used as the link location instead of reading one interactively." +used as the link location instead of reading one interactively. + +If the DEFAULT-DESCRIPTION parameter is non-nil, this value will +be used as the default description." (interactive "P") (let* ((wcf (current-window-configuration)) (region (if (org-region-active-p) @@ -9020,6 +9023,7 @@ Use TAB to complete link prefixes, then RET for type-specific completion support (if org-make-link-description-function (setq desc (funcall org-make-link-description-function link desc))) +(if default-description (setq desc default-description)) (setq desc (read-string "Description: " desc)) (unless (string-match "\\S-" desc) (setq desc nil)) (if remove (apply 'delete-region remove))
Re: [O] Can't use char ">" in TODO state
Hi Nicolas and Bastien, > Nicolas Goaziou wrote: >> Bastien writes: >>> Michael Brand writes: >>> It works with this patch http://patchwork.newartisans.com/patch/964 from Nicolas which I am still using to test it. >> >>> If so, then Nicolas please apply it. It really simplifies >>> the way headlines are matched in many places in the code. >> >> I've applied it. > > This works as expected from my point of view. Thanks a lot... ... with this exception (when using TODO states from Dan Davison): #+OPTIONS: ^:nil #+SEQ_TODO: DOESN'T_WORK DOESN'T-WORK | WORKS * WORKS Marche In HTML, class is "WORKS" and word in the heading is "WORKS" as well. * DOESN'T_WORK Marche pas The HTML class is "DOESN'T_WORK" (the real name of the state) and "DOESN_T_WORK" in the heading. In LaTeX, the status "DOESN'T_WORK" is kept as-is in the heading, hence provoking a layout bug in the PDF. This is true, whatever the value of the option ^ for interpreting sub- and super-scripts: setting it to =t= or to =nil= makes no difference. * DOESN'T-WORK Marche pas In this last case, the real name "DOESN'T-WORK" is conserved as HTML class, but translated to "DOESN_T_WORK" in the heading. No problem in LaTeX. Best regards, Seb -- Sebastien Vauban
Re: [O] [babel] Announcing ob-picolisp.el
Bastien writes: > This is great, thanks for sharing. Btw, picolisp looks way cool. Thats what I thought when I discovered it, so simple and so smart at the same time. Maybe the perfect language for an Emacs rewrite ... just kidding ;) cheers -- Thorsten
Re: [O] [babel] Announcing ob-picolisp.el
Eric Schulte writes: > Thorsten, if copying ob-picolisp to contrib/babel/langs until your FSF > paperwork is completed sounds agreeable to you I will move it over now. Sure, no problem, go ahead. cheers -- Thorsten
Re: [O] "git describe" in version of info file with "make info_git_describe"
Hi Carsten and Bastien On Fri, Oct 21, 2011 at 16:44, Carsten Dominik wrote: > is there an agreement that this is a good patch? I have not followed the > discussion. Let me summarize: > On Oct 16, 2011, at 9:12 PM, Michael Brand wrote: >> The previous patch attachment had a wrong mime type, could therefore >> not be caught by patchwork and has not been accepted. Only a clarification about "has not been accepted": The first version of my patch has just not been applied, there was no disagreement or reject. The second version was only to get my patch into patchwork at all and to rebase it at the design level. For the change in org-version (substitution of the "-" from the git tag delivered by git describe with "."): As Bernt is the author of this substitution I originally asked him if I could remove it to align with the output of git describe and he agreed. He now has reviewed this part of the second version of my patch and he is fine with it. There has not yet been any review or comment on the changes in the Makefile and in UTILITIES/set-version.pl. I would be happy if these parts could be reviewed too. Michael
[O] Bug: Remote reference (@>$1) doesn't work while ($LR1) works. [7.7]
Hello, First, please check below simple example, I defined two tables (T1 and T2). In table-2, I remotely refer to the @>$1 (last row, column 1) and $LR2 (last row, column 2) of T1. #+TBLNAME: T1 | 11 | 12 | | 21 | 22 | | 31 | 32 | #+TBLNAME: T2 | xxx | xxx | xxx | xxx | | # | 21 | 32 | | #+TBLFM: @>$3=remote(T1,$LR2)::@>$2=remote(T1,@>$1) Obviously, the expected results are: - remote(T1,@>$1) is replaced by 31 - remote(T1,$LR2) is replaced by 32 But I got 21 for remote(T1,@>$1). The $LR version works perfectly (though the manual says $LR is out-dated) Below are debug info when evaluating remote(T1,@>$1). Looks like @> in the remote reference is mapped to the last row of the current table, not of the remote table. Substitution history of formula Orig: remote(T1,@2$1) $xyz-> remote(T1,@2$1) @r$c-> (21) $1->(21) Result: 21 Format: NONE Final: 21 Emacs : GNU Emacs 23.3.1 (i686-pc-linux-gnu, GTK+ Version 2.24.6) of 2011-09-13 on shirley Package: Org-mode version 7.7
Re: [O] Orgmode performance problem and "solution"
on Wed Oct 26 2011, suvayu ali wrote: > On Wed, Oct 26, 2011 at 10:07, Rainer Stengele > wrote: >> Lacking knowledge of git I deleted everything, cloned from the new repo and >> compiled the files. >> Result was a significantly faster Org experience. >> > > For future reference, a sinple `git pull` would have sufficed. Not if there were compiled files. -- Dave Abrahams BoostPro Computing http://www.boostpro.com
Re: [O] [babel] Announcing ob-picolisp.el
Bastien writes: > Hi Thorsten, > > Thorsten writes: > >> Hi list, with help and substancial input from Eric (Schulte) I added a >> new language to org-babel, the minimal lisp dialect picolisp [thanks to >> Eric!]. You can download the ob-picolisp.el file here: >> >> https://github.com/tj64/ob-picolisp > > This is great, thanks for sharing. Btw, picolisp looks way cool. > > Eric, I think this library could go to contrib/babel/langs/ and > then to core when Thorsten is all set with the FSF assignment. > I let you decide on this. > Agreed. Thorsten, if copying ob-picolisp to contrib/babel/langs until your FSF paperwork is completed sounds agreeable to you I will move it over now. Let me know. Best -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines
"Sebastien Vauban" writes: > Hi Eric, > > Eric Schulte wrote: >>> I think that makes sense. >>> >>> While thinking about all of this, and working in real-life documents, I just >>> came back to a suggestion which I made some time ago. It goes about this >>> enhancement: >>> >>> Would it be possible to specify "buffer-wide language specific" header >>> arguments? >> >> Yes, this is already possible. You can customize the >> org-babel-default-header-args:lang variable (where "lang" is the source >> name) as a file local variable. >> Hi Seb, ^ | I just wanted to make sure you saw the above solution for specifying file-wide language-specific header arguments. Emacs' support for buffer local variables makes this fairly easy to implement. In fact buffer local variables could also be used to specify multi-langauge file-wide header arguments using the `org-babel-default-header-args' variable. Cheers -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel] Announcing ob-picolisp.el
Hi Thorsten, Thorsten writes: > Hi list, with help and substancial input from Eric (Schulte) I added a > new language to org-babel, the minimal lisp dialect picolisp [thanks to > Eric!]. You can download the ob-picolisp.el file here: > > https://github.com/tj64/ob-picolisp This is great, thanks for sharing. Btw, picolisp looks way cool. Eric, I think this library could go to contrib/babel/langs/ and then to core when Thorsten is all set with the FSF assignment. I let you decide on this. Best, -- Bastien
[O] [patch] Re: LATEX_CLASS_OPTIONS in SETUPFILE
Christophe Rhodes writes:
> I believe that the
> reason is that LATEX_CLASS_OPTIONS is not handled within
> org-infile-export-plist in org-exp.el.
Please find a patch attached addressing this issue.
>From 1f92aed1a882f93af78c57c67bd6f12401db877e Mon Sep 17 00:00:00 2001
From: Christophe Rhodes
Date: Wed, 26 Oct 2011 16:13:20 +0100
Subject: [PATCH] support LATEX_CLASS_OPTIONS in #+SETUPFILE
* lisp/org-exp.el (org-infile-export-plist): handle LATEX_CLASS_OPTIONS
analogolusly to LATEX_CLASS
---
lisp/org-exp.el |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/lisp/org-exp.el b/lisp/org-exp.el
index 2aad322..4324d38 100644
--- a/lisp/org-exp.el
+++ b/lisp/org-exp.el
@@ -737,13 +737,13 @@ modified) list.")
'("TITLE" "AUTHOR" "DATE" "EMAIL" "TEXT" "OPTIONS" "LANGUAGE"
"MATHJAX"
"LINK_UP" "LINK_HOME" "SETUPFILE" "STYLE"
- "LATEX_HEADER" "LATEX_CLASS"
+ "LATEX_HEADER" "LATEX_CLASS" "LATEX_CLASS_OPTIONS"
"EXPORT_SELECT_TAGS" "EXPORT_EXCLUDE_TAGS"
"KEYWORDS" "DESCRIPTION" "MACRO" "BIND" "XSLT")
(mapcar 'car org-export-inbuffer-options-extra
(case-fold-search t)
p key val text options mathjax a pr style
- latex-header latex-class macros letbind
+ latex-header latex-class latex-class-options macros letbind
ext-setup-or-nil setup-file setup-dir setup-contents (start 0))
(while (or (and ext-setup-or-nil
(string-match re ext-setup-or-nil start)
@@ -770,6 +770,8 @@ modified) list.")
(setq latex-header (concat latex-header "\n" val)))
((string-equal key "LATEX_CLASS")
(setq latex-class val))
+ ((string-equal key "LATEX_CLASS_OPTIONS")
+(setq latex-class-options val))
((string-equal key "TEXT")
(setq text (if text (concat text "\n" val) val)))
((string-equal key "OPTIONS")
@@ -813,6 +815,8 @@ modified) list.")
(setq p (plist-put p :latex-header-extra (substring latex-header 1
(when latex-class
(setq p (plist-put p :latex-class latex-class)))
+(when latex-class-options
+ (setq p (plist-put p :latex-class-options latex-class-options)))
(when options
(setq p (org-export-add-options-to-plist p options)))
(when mathjax
--
1.7.5.4
I believe that this is a trivial change.
> There may be similar keywords for LaTeX or other backends that are also
> not handled which maybe should be; this one is the one I noticed because
> I tried to use it.
I have not spent time auditing backends for other similar keywords.
Best wishes,
Christophe
Re: [O] [RFC] Standardized code block keywords
Daniel Bausch wrote: > Am Mittwoch 26 Oktober 2011, 15:10:03 schrieb Giovanni Ridolfi: > > Nick Dokos writes: > > > Eric Schulte wrote: > > >> Surprisingly (to me) srcname is the winner here, but luckily I haven't > > >> yet voted, and although I would have though #+source: would have been > > >> the winner I like the simplicity of using #+name: for named code blocks > > >> as well as named data. So I'll vote for #+name: here making it a tie, > > >> and I'll also take tie-breaking powers upon myself giving #+name: the > > >> win. > > > > > > This is going to cost you, Schulte! It's not going to go down that > > > easily. I'll call the FTC, the FCC, the SCOTUS, the POTUS, the NYT, the > > > BDFL, the NFL and the MLB: an outrage I tell you! An affront to the > > > democratic rules some of us cherish! We'll fight to the death! Who's > > > with me? > > > > +1 srcname > > > > :-) > > > > Power to the people! Democracy forever! > > > > Giovanni /who has not used babel yet. > > Hmm, then you don't know what we are talking about and should abstain from > voting. ;-) That's another blatant attempt to subvert democracy by the Schulte cabal: whoever said that one has to know anything about it before voting? Both recent and distant history prove that that is not the case (e.g. watch Ken Burns's "Prohibition" and weep - or laugh - or both). > -- > Daniel (who used Babel to write his thesis in one big file with all data and > chart generating code interleaved with the text -- faboulous!) > > Indeed - could we hope to get a glimpse at some examples (or even the whole thing) at some point? Nick PS. I presume it's clear to all that this silliness I started has a big smilie wrapped around the whole thing, but just in case somebody decides that I'm serious: pthvhtththth :-)
Re: [O] [RFC] Standardized code block keywords
Am Mittwoch 26 Oktober 2011, 15:10:03 schrieb Giovanni Ridolfi: > Nick Dokos writes: > > Eric Schulte wrote: > >> Surprisingly (to me) srcname is the winner here, but luckily I haven't > >> yet voted, and although I would have though #+source: would have been > >> the winner I like the simplicity of using #+name: for named code blocks > >> as well as named data. So I'll vote for #+name: here making it a tie, > >> and I'll also take tie-breaking powers upon myself giving #+name: the > >> win. > > > > This is going to cost you, Schulte! It's not going to go down that > > easily. I'll call the FTC, the FCC, the SCOTUS, the POTUS, the NYT, the > > BDFL, the NFL and the MLB: an outrage I tell you! An affront to the > > democratic rules some of us cherish! We'll fight to the death! Who's > > with me? > > +1 srcname > > :-) > > Power to the people! Democracy forever! > > Giovanni /who has not used babel yet. Hmm, then you don't know what we are talking about and should abstain from voting. ;-) -- Daniel (who used Babel to write his thesis in one big file with all data and chart generating code interleaved with the text -- faboulous!)
Re: [O] Bug: tags search in org-sparse-tree is broken
Suvayu Ali writes: Hi, Suvayu > Are the matched headlines highlighted? No. you're right, there's a bug > Can you move to the next match with next-error > (C-x ` or M-g n)? No. bug. :-/ > When I try to move through the > matches with M-g n or M-g p, I get the following error. > > Debugger entered--Lisp error: (error "No more matches") me too. thanks for explaining. cheers, Giovanni
Re: [O] Orgmode performance problem and "solution"
Rainer Stengele wrote: > No, the old repo > > git://repo.or.cz/org-mode.git > > I used is some time behind the one I use now. > If I want to get a fix immediately I learned I have to use the new repo > git://orgmode.org/org-mode.git > > I hope I got this right. > > Rainer > > Am 26.10.2011 14:11, schrieb suvayu ali: > > On Wed, Oct 26, 2011 at 10:07, Rainer Stengele > > wrote: > >> Lacking knowledge of git I deleted everything, cloned from the new repo > >> and compiled the files. > >> Result was a significantly faster Org experience. > >> > > For future reference, a sinple `git pull` would have sufficed. > > > It's too late for it now, but for future reference: you can change the repo with ``git config --replace-all remote.origin.url git://orgmode.org/org-mode.git'' and then do a ``git pull''. AFAIK, the repo.or.cz/org-mode.git repo was a delayed mirror, so it would have the same history (up to the point of the latest sync). But it doesn't really matter: cloning the repo again takes longer but it's a one-time cost and the end result is the same. Nick
Re: [O] Bug: tags search in org-sparse-tree is broken
Hi Giovanni,
On Wed, 26 Oct 2011 15:40:53 +0200
Giovanni Ridolfi wrote:
> suvayu ali writes:
>
> Hi, suvayu
> >
> > The tags search for org-sparse-tree seems to be broken.
> > With a minimal
> > setup, C-c / m RET doesn't perform a tags search.
>
> well, with my org-version, 2 commits before the leading edge:
>
> Org-mode version 7.7 679a0e1fe93d630820185f931087328d32e81077
> GNU Emacs 23.3.1 (i386-mingw-nt5.1.2600) of 2011-03-10 on 3249CTO
>
> I cannot reproduce it.
>
Are the matched headlines highlighted? Can you move to the next match
with next-error (C-x ` or M-g n)? When I try to move through the
matches with M-g n or M-g p, I get the following error.
Debugger entered--Lisp error: (error "No more matches")
signal(error ("No more matches"))
error("No more matches")
byte-code(..)
org-occur-next-match(1 nil)
next-error(nil)
call-interactively(next-error nil nil)
> cheers,
> Giovanni
>
--
Suvayu
Open source is the future. It sets us free.
Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines
Hi Eric, Eric Schulte wrote: >> I think that makes sense. >> >> While thinking about all of this, and working in real-life documents, I just >> came back to a suggestion which I made some time ago. It goes about this >> enhancement: >> >> Would it be possible to specify "buffer-wide language specific" header >> arguments? > > Yes, this is already possible. You can customize the > org-babel-default-header-args:lang variable (where "lang" is the source > name) as a file local variable. > >> That is, be able to say: >> >> "In this document, I want to: >> - tangle all my .sql chunks, but no other; >> - eval all the elisp chunks with query, but no other." >> >> Something we could write quite easily along the lines: >> >> #+PROPERTY: tangle no >> #+PROPERTY: eval never >> #+PROPERTY[SQL]: tangle yes >> #+PROPERTY[EMACS-LISP]: eval query >> >> (the syntax used here is just a draft sample!) >> > > I do not think we can customize the PROPERTY syntax as is exists outside > of Babel. The goal here was to piggy-back on top of rather than co-opt > regular Org-mode syntax. I understand that argument. It's just that the current solution is not optimal (among others) for documents mixing R and shell code: you don't want your "session" property to be common between both languages (shell code sent to your R terminal, or vice-versa). But it's nice this case is already handled in a more generic way than on the code blocks themselves, and I can live with that. Thanks again for your help. Best regards, Seb -- Sebastien Vauban
Re: [O] Bug: tags search in org-sparse-tree is broken
suvayu ali writes: Hi, suvayu > > The tags search for org-sparse-tree seems to be broken. > With a minimal > setup, C-c / m RET doesn't perform a tags search. well, with my org-version, 2 commits before the leading edge: Org-mode version 7.7 679a0e1fe93d630820185f931087328d32e81077 GNU Emacs 23.3.1 (i386-mingw-nt5.1.2600) of 2011-03-10 on 3249CTO I cannot reproduce it. C-c m / tag on this file --- -*- mode: org; -*- * [2011-10-26 mer] ** number one *** hello :tag: *** one *** two ** game *** game2 :tag: game 3 --- C-c m / tag gives: * [2011-10-26 mer] ** number one *** hello *:tag: ** game *** game2 :tag: game 3 /// /// /// cheers, Giovanni
Re: [O] [RFC] Standardized code block keywords
Nick Dokos writes: > Eric Schulte wrote: > >> Surprisingly (to me) srcname is the winner here, but luckily I haven't >> yet voted, and although I would have though #+source: would have been >> the winner I like the simplicity of using #+name: for named code blocks >> as well as named data. So I'll vote for #+name: here making it a tie, >> and I'll also take tie-breaking powers upon myself giving #+name: the >> win. >> > > This is going to cost you, Schulte! It's not going to go down that easily. > I'll call the FTC, the FCC, the SCOTUS, the POTUS, the NYT, the BDFL, the > NFL and the MLB: an outrage I tell you! An affront to the democratic rules > some of us cherish! We'll fight to the death! Who's with me? +1 srcname :-) Power to the people! Democracy forever! Giovanni /who has not used babel yet.
Re: [O] [babel] Property engine can't be set globally
Hi Eric, Eric Schulte wrote: > This is because engine is a ob-sql specific header argument. Language > specific files a supposed to declare the names of their header arguments > so that they may be inherited through variables with names like > `org-babel-header-arg-names:sql'. I've just added such a variable to > ob-sql with "engine" and "out-file" keywords, so this problem should now > be fixed. That works like a charm. Thanks a lot, Seb > "Sebastien Vauban" writes: > >> #+SEQ_TODO: DOESN'T_WORK | WORKS >> #+PROPERTY: eval never >> #+PROPERTY: engine msosql >> #+PROPERTY: cmdline -S -U -P -d -n -w 700 >> #+PROPERTY: results value >> >> * Overview >> >> Some properties, either set at file level or at tree level, still remain >> _invisible_ (unset) to code blocks. >> >> This is at least the case with the =engine= property. >> >> * Test suite >> >> The first 2 cases end in an error: >> >> let: Wrong type argument: stringp, nil >> (See [[id:cada6588-de8a-4225-86cf-9ef840e09aa1][Backtrace]]) >> >> The 3^rd one succeeds. >> >> ** DOESN'T_WORK Buffer-wide properties >> >> #+begin_src sql :eval yes >> select getdate() >> go >> #+end_src >> >> Property engine is unknown. >> >> ** DOESN'T_WORK Properties in subtree >>:PROPERTIES: >>:engine: msosql >>:END: >> >> #+begin_src sql :eval yes >> select getdate() >> go >> #+end_src >> >> Property engine is still unknown... >> >> ** WORKS Properties at block level >> >> #+begin_src sql :eval yes :engine msosql >> select getdate() >> go >> #+end_src >> >> #+results: >> | | >> |-| >> | 2011-10-26 12:25:11.347 | >> | | >> | (1 ligne affectＦ) | >> >> * Backtrace >> :PROPERTIES: >> :ID: cada6588-de8a-4225-86cf-9ef840e09aa1 >> :END: >> >> #+begin_src text >> Debugger entered--Lisp error: (wrong-type-argument stringp nil) >> intern(nil) >> (let ((--cl-var-- (intern engine))) (cond ((member* --cl-var-- (quote (quote > msosql))) (format "osql %s -s \" \" -i %s -o %s" (or cmdline "") > (org-babel-process-file-name in-file) (org-babel-process-file-name out-file))) > ((member* --cl-var-- (quote (quote mysql))) (format "mysql %s < %s > %s" (or > cmdline "") (org-babel-process-file-name in-file) (org-babel-process-file-name > out-file))) ((member* --cl-var-- (quote (quote postgresql))) (format "psql -A > -P footer=off -F \" \" -f %s -o %s %s" (org-babel-process-file-name in-file) > (org-babel-process-file-name out-file) (or cmdline ""))) (t (error "no support > for the %s sql engine" engine >> (case (intern engine) ((quote msosql) (format "osql %s -s \" \" -i %s -o %s" > (or cmdline "") (org-babel-process-file-name in-file) > (org-babel-process-file-name out-file))) ((quote mysql) (format "mysql %s < %s >> %s" (or cmdline "") (org-babel-process-file-name in-file) > (org-babel-process-file-name out-file))) ((quote postgresql) (format "psql -A > -P footer=off -F \" \" -f %s -o %s %s" (org-babel-process-file-name in-file) > (org-babel-process-file-name out-file) (or cmdline ""))) (t (error "no support > for the %s sql engine" engine))) >> (let* ((result-params (cdr (assoc :result-params params))) (cmdline (cdr > (assoc :cmdline params))) (engine (cdr (assoc :engine params))) (in-file > (org-babel-temp-file "sql-in-")) (out-file (or (cdr (assoc :out-file params)) > (org-babel-temp-file "sql-out-"))) (header-delim "") (command (case (intern > engine) ((quote msosql) (format "osql %s -s \" \" -i %s -o %s" (or cmdline "") > (org-babel-process-file-name in-file) (org-babel-process-file-name out-file))) > ((quote mysql) (format "mysql %s < %s > %s" (or cmdline "") > (org-babel-process-file-name in-file) (org-babel-process-file-name out-file))) > ((quote postgresql) (format "psql -A -P footer=off -F \" \" -f %s -o %s %s" > (org-babel-process-file-name in-file) (org-babel-process-file-name out-file) > (or cmdline ""))) (t (error "no support for the %s sql engine" engine) > (with-temp-file in-file (insert (org-babel-expand-body:sql body params))) > (message command) (shell-command command) (if (or (member "scalar" > result-params) (member "verbatim" result-params) (member "html" result-params) > (member "code" result-params) (equal (point-min) (point-max))) > (with-temp-buffer (progn (insert-file-contents-literally out-file) > (buffer-string))) (with-temp-buffer (with-temp-buffer (insert-file-contents > out-file) (goto-char (point-min)) (when (re-search-forward "^\\(-+\\)[^-]" nil > t) (setq header-delim (match-string-no-properties 1))) (goto-char (point-max)) > (forward-char -1) (while (looking-at "\n") (delete-char 1) (goto-char > (point-max)) (forward-char -1)) (write-file out-file)) (org-table-import > out-file (quote (16))) (org-babel-reassemble-table (mapcar (lambda (x) (if > (string= ... header-delim) (quote hline) x)) (org-table-to-lisp)) > (org-babel-pick-name (cdr (assoc :colname-names params)) (cdr (assoc :colnames > params))) (org-babel-pick-name (cdr (
Re: [O] Orgmode performance problem and "solution"
Hi Rainer, On Wed, Oct 26, 2011 at 14:16, Rainer Stengele wrote: > No, the old repo > > git://repo.or.cz/org-mode.git > > I used is some time behind the one I use now. > If I want to get a fix immediately I learned I have to use the new repo > git://orgmode.org/org-mode.git > > I hope I got this right. > I should have been explicit. To change the remote repo, all you need to do is update the url in the .git/config file. [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = git://orgmode.org/org-mode.git ^ You can also update the url with the following command: $ git config remote.origin.url git://orgmode.org/org-mode.git Once you have done that, all you need is `git pull` to get the latest. > Rainer Hope this helps in the future. -- Suvayu Open source is the future. It sets us free.
Re: [O] [babel] Property engine can't be set globally
Hi Seb, This is because engine is a ob-sql specific header argument. Language specific files a supposed to declare the names of their header arguments so that they may be inherited through variables with names like `org-babel-header-arg-names:sql'. I've just added such a variable to ob-sql with "engine" and "out-file" keywords, so this problem should now be fixed. Thanks -- Eric "Sebastien Vauban" writes: > #+SEQ_TODO: DOESN'T_WORK | WORKS > #+PROPERTY: eval never > #+PROPERTY: engine msosql > #+PROPERTY: cmdline -S -U -P -d -n -w 700 > #+PROPERTY: results value > > * Overview > > Some properties, either set at file level or at tree level, still remain > _invisible_ (unset) to code blocks. > > This is at least the case with the =engine= property. > > * Test suite > > The first 2 cases end in an error: > > let: Wrong type argument: stringp, nil > (See [[id:cada6588-de8a-4225-86cf-9ef840e09aa1][Backtrace]]) > > The 3^rd one succeeds. > > ** DOESN'T_WORK Buffer-wide properties > > #+begin_src sql :eval yes > select getdate() > go > #+end_src > > Property engine is unknown. > > ** DOESN'T_WORK Properties in subtree >:PROPERTIES: >:engine: msosql >:END: > > #+begin_src sql :eval yes > select getdate() > go > #+end_src > > Property engine is still unknown... > > ** WORKS Properties at block level > > #+begin_src sql :eval yes :engine msosql > select getdate() > go > #+end_src > > #+results: > | | > |-| > | 2011-10-26 12:25:11.347 | > | | > | (1 ligne affectＦ) | > > * Backtrace > :PROPERTIES: > :ID: cada6588-de8a-4225-86cf-9ef840e09aa1 > :END: > > #+begin_src text > Debugger entered--Lisp error: (wrong-type-argument stringp nil) > intern(nil) > (let ((--cl-var-- (intern engine))) (cond ((member* --cl-var-- (quote > (quote msosql))) (format "osql %s -s \" \" -i %s -o %s" (or cmdline "") > (org-babel-process-file-name in-file) (org-babel-process-file-name > out-file))) ((member* --cl-var-- (quote (quote mysql))) (format "mysql %s < > %s > %s" (or cmdline "") (org-babel-process-file-name in-file) > (org-babel-process-file-name out-file))) ((member* --cl-var-- (quote (quote > postgresql))) (format "psql -A -P footer=off -F \"\" -f %s -o %s %s" > (org-babel-process-file-name in-file) (org-babel-process-file-name out-file) > (or cmdline ""))) (t (error "no support for the %s sql engine" engine > (case (intern engine) ((quote msosql) (format "osql %s -s \"\" -i > %s -o %s" (or cmdline "") (org-babel-process-file-name in-file) > (org-babel-process-file-name out-file))) ((quote mysql) (format "mysql %s < > %s > %s" (or cmdline "") (org-babel-process-file-name in-file) > (org-babel-process-file-name out-file))) ((quote postgresql) (format "psql -A > -P footer=off -F \" \" -f %s -o %s %s" (org-babel-process-file-name > in-file) (org-babel-process-file-name out-file) (or cmdline ""))) (t (error > "no support for the %s sql engine" engine))) > (let* ((result-params (cdr (assoc :result-params params))) (cmdline (cdr > (assoc :cmdline params))) (engine (cdr (assoc :engine params))) (in-file > (org-babel-temp-file "sql-in-")) (out-file (or (cdr (assoc :out-file params)) > (org-babel-temp-file "sql-out-"))) (header-delim "") (command (case (intern > engine) ((quote msosql) (format "osql %s -s \" \" -i %s -o %s" (or cmdline > "") (org-babel-process-file-name in-file) (org-babel-process-file-name > out-file))) ((quote mysql) (format "mysql %s < %s > %s" (or cmdline "") > (org-babel-process-file-name in-file) (org-babel-process-file-name > out-file))) ((quote postgresql) (format "psql -A -P footer=off -F \" \" > -f %s -o %s %s" (org-babel-process-file-name in-file) > (org-babel-process-file-name out-file) (or cmdline ""))) (t (error "no > support for the %s sql engine" engine) (with-temp-file in-file (insert > (org-babel-expand-body:sql body params))) (message command) (shell-command > command) (if (or (member "scalar" result-params) (member "verbatim" > result-params) (member "html" result-params) (member "code" result-params) > (equal (point-min) (point-max))) (with-temp-buffer (progn > (insert-file-contents-literally out-file) (buffer-string))) (with-temp-buffer > (with-temp-buffer (insert-file-contents out-file) (goto-char (point-min)) > (when (re-search-forward "^\\(-+\\)[^-]" nil t) (setq header-delim > (match-string-no-properties 1))) (goto-char (point-max)) (forward-char -1) > (while (looking-at "\n") (delete-char 1) (goto-char (point-max)) > (forward-char -1)) (write-file out-file)) (org-table-import out-file (quote > (16))) (org-babel-reassemble-table (mapcar (lambda (x) (if (string= ... > header-delim) (quote hline) x)) (org-table-to-lisp)) (org-babel-pick-name > (cdr (assoc :colname-names params)) (cdr (assoc :colnames params))) > (org-babel-pick-name (cdr (assoc :rowname-names params)) (cdr (assoc > :rownames p
Re: [O] [RFC] Standardized code block keywords
Daniel Bausch writes: >> > However, I'd like to ask, what happens, if one refers to a >> > name of a source block where data is expected, does it then refer to >> > the results produced by that source block? How are such situations >> > handeled at the moment? >> >> Try it out, but be ready to press C-g, because I would guess that it >> results in an infinite loop. > > Isn't it possible to refer to the results of a code block as input data for > another? I thought it was. If not currently then at least I suppose that it > will be in the future. The new syntax should be ready for that. > Sorry for my confusion. I thought you meant a case in which code block A needs the results of code block B as an input parameter, but code block B needs the results of code block A as an input parameter. Such a reciprocal dependency would result in an infinite loop. But yes, the ability of one code block to call another and make use of its results is (as Tom mentioned) one of the core features of code block support in Org-mode. Cheers -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Orgmode performance problem and "solution"
No, the old repo git://repo.or.cz/org-mode.git I used is some time behind the one I use now. If I want to get a fix immediately I learned I have to use the new repo git://orgmode.org/org-mode.git I hope I got this right. Rainer Am 26.10.2011 14:11, schrieb suvayu ali: > On Wed, Oct 26, 2011 at 10:07, Rainer Stengele > wrote: >> Lacking knowledge of git I deleted everything, cloned from the new repo and >> compiled the files. >> Result was a significantly faster Org experience. >> > For future reference, a sinple `git pull` would have sufficed. >
Re: [O] Orgmode performance problem and "solution"
On Wed, Oct 26, 2011 at 10:07, Rainer Stengele wrote: > Lacking knowledge of git I deleted everything, cloned from the new repo and > compiled the files. > Result was a significantly faster Org experience. > For future reference, a sinple `git pull` would have sufficed. -- Suvayu Open source is the future. It sets us free.
Re: [O] feature suggestion: apply datetime prompt magic to selected region
On 26 Oct 2011 09:56, "Eric S Fraga" wrote: > > Brian van den Broek writes: > > [...] > > > Various people upthread convinced me that my feature request wasn't > > really worth it. (I do hope it didn't cost you too much time!) So, I > > am content to drop it here :-) > > but did you try a simple keyboard macro in the end as suggested by the > first response? Hi Eric, I did. That that solution was pointed out helped me see that my suggestion had little value. :--) Thanks, though, for making the effort to give explicit details! Best, Brian vdB
[O] Org-odt table format
Is there a way to specify (in the org file) column widths of a table when exported to an odt file. Vikas
[O] [babel] Property engine can't be set globally
#+SEQ_TODO: DOESN'T_WORK | WORKS
#+PROPERTY: eval never
#+PROPERTY: engine msosql
#+PROPERTY: cmdline -S -U -P -d -n -w 700
#+PROPERTY: results value
* Overview
Some properties, either set at file level or at tree level, still remain
_invisible_ (unset) to code blocks.
This is at least the case with the =engine= property.
* Test suite
The first 2 cases end in an error:
let: Wrong type argument: stringp, nil
(See [[id:cada6588-de8a-4225-86cf-9ef840e09aa1][Backtrace]])
The 3^rd one succeeds.
** DOESN'T_WORK Buffer-wide properties
#+begin_src sql :eval yes
select getdate()
go
#+end_src
Property engine is unknown.
** DOESN'T_WORK Properties in subtree
:PROPERTIES:
:engine: msosql
:END:
#+begin_src sql :eval yes
select getdate()
go
#+end_src
Property engine is still unknown...
** WORKS Properties at block level
#+begin_src sql :eval yes :engine msosql
select getdate()
go
#+end_src
#+results:
| |
|-|
| 2011-10-26 12:25:11.347 |
| |
| (1 ligne affectＦ) |
* Backtrace
:PROPERTIES:
:ID: cada6588-de8a-4225-86cf-9ef840e09aa1
:END:
#+begin_src text
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
intern(nil)
(let ((--cl-var-- (intern engine))) (cond ((member* --cl-var-- (quote (quote
msosql))) (format "osql %s -s \" \" -i %s -o %s" (or cmdline "")
(org-babel-process-file-name in-file) (org-babel-process-file-name out-file)))
((member* --cl-var-- (quote (quote mysql))) (format "mysql %s < %s > %s" (or
cmdline "") (org-babel-process-file-name in-file) (org-babel-process-file-name
out-file))) ((member* --cl-var-- (quote (quote postgresql))) (format "psql -A
-P footer=off -F \"\" -f %s -o %s %s" (org-babel-process-file-name
in-file) (org-babel-process-file-name out-file) (or cmdline ""))) (t (error "no
support for the %s sql engine" engine
(case (intern engine) ((quote msosql) (format "osql %s -s \" \" -i %s -o %s"
(or cmdline "") (org-babel-process-file-name in-file)
(org-babel-process-file-name out-file))) ((quote mysql) (format "mysql %s < %s
> %s" (or cmdline "") (org-babel-process-file-name in-file)
(org-babel-process-file-name out-file))) ((quote postgresql) (format "psql -A
-P footer=off -F \" \" -f %s -o %s %s" (org-babel-process-file-name
in-file) (org-babel-process-file-name out-file) (or cmdline ""))) (t (error "no
support for the %s sql engine" engine)))
(let* ((result-params (cdr (assoc :result-params params))) (cmdline (cdr
(assoc :cmdline params))) (engine (cdr (assoc :engine params))) (in-file
(org-babel-temp-file "sql-in-")) (out-file (or (cdr (assoc :out-file params))
(org-babel-temp-file "sql-out-"))) (header-delim "") (command (case (intern
engine) ((quote msosql) (format "osql %s -s \"\" -i %s -o %s" (or cmdline
"") (org-babel-process-file-name in-file) (org-babel-process-file-name
out-file))) ((quote mysql) (format "mysql %s < %s > %s" (or cmdline "")
(org-babel-process-file-name in-file) (org-babel-process-file-name out-file)))
((quote postgresql) (format "psql -A -P footer=off -F \" \" -f %s -o %s
%s" (org-babel-process-file-name in-file) (org-babel-process-file-name
out-file) (or cmdline ""))) (t (error "no support for the %s sql engine"
engine) (with-temp-file in-file (insert (org-babel-expand-body:sql body
params))) (message command) (shell-command command) (if (or (member "scalar"
result-params) (member "verbatim" result-params) (member "html" result-params)
(member "code" result-params) (equal (point-min) (point-max)))
(with-temp-buffer (progn (insert-file-contents-literally out-file)
(buffer-string))) (with-temp-buffer (with-temp-buffer (insert-file-contents
out-file) (goto-char (point-min)) (when (re-search-forward "^\\(-+\\)[^-]" nil
t) (setq header-delim (match-string-no-properties 1))) (goto-char (point-max))
(forward-char -1) (while (looking-at "\n") (delete-char 1) (goto-char
(point-max)) (forward-char -1)) (write-file out-file)) (org-table-import
out-file (quote (16))) (org-babel-reassemble-table (mapcar (lambda (x) (if
(string= ... header-delim) (quote hline) x)) (org-table-to-lisp))
(org-babel-pick-name (cdr (assoc :colname-names params)) (cdr (assoc :colnames
params))) (org-babel-pick-name (cdr (assoc :rowname-names params)) (cdr (assoc
:rownames params)))
org-babel-execute:sql("select getdate()\ngo" ((:colname-names)
(:rowname-names) (:result-params "value" "replace") (:result-type . value)
(:comments . "") (:shebang . "") (:cache . "no") (:padline . "") (:noweb .
"no") (:tangle . "no") (:exports . "code") (:results . "value replace") (:eval
. "yes") (:cmdline . "-S cauchy -U sa -P LpmdlP -d pfi-dev -n -w 700")
(:padnewline . "yes") (:hlines . "no") (:session . "none")))
funcall(org-babel-execute:sql "select getdate()\ngo" ((:colname-names)
(:rowname-names) (:result-params "value" "replace") (:result-type . value)
(:comments . "") (:shebang . "")
Re: [O] Orgmode performance problem and "solution"
> Sorry I have no explanation but maybe someone who has performance > problems may try to checkout from scratch and recompile. May be this is the explanation: http://orgmode.org/w/?p=org-mode.git;a=commit;h=1a97f29c342d85960a65c0bd992fee7c87850da5 points to this thread: https://lists.gnu.org/archive/html/emacs-devel/2011-09/msg00276.html People can install daily from ELPA. No knowledge of git is required. Files get compiled automatically and info file also get installed automatically. Only issue could be bandwidth ... Otherwise it is THE method for receiving bugfixes and improvements with the least hassle. --
[O] Orgmode performance problem and "solution"
Hi all, after upgrading my Emacs from version 23 to GNU Emacs 24.0.90.1 (i386-mingw-nt5.1.2600) of 2011-10-19 on MARVIN Org ran terribly slow. Cursor movement was slow, clock adjustment also etc. After having an issue which was solved immediately by Nicolas Goaziou I changed my repository from git://repo.or.cz/org-mode.git to git://orgmode.org/org-mode.git in order to be able to pull his fix immediately. Lacking knowledge of git I deleted everything, cloned from the new repo and compiled the files. Result was a significantly faster Org experience. Sorry I have no explanation but maybe someone who has performance problems may try to checkout from scratch and recompile. Org-mode version 7.7 (release_7.7.464.g679a0.dirty) Windows XP SP3 Regards, Rainer
Re: [O] feature suggestion: apply datetime prompt magic to selected region
Brian van den Broek writes: [...] > Various people upthread convinced me that my feature request wasn't > really worth it. (I do hope it didn't cost you too much time!) So, I > am content to drop it here :-) but did you try a simple keyboard macro in the end as suggested by the first response? this requires no elisp programming. if your actions consist of selecting region and then applying org-time-stamp on it, the following keystrokes should record the steps necessary to do what you want *after* you have selected the desired region: C-x ( C-w C-c . C-y RET C-x ) (untested sequence of keystrokes) Your macro is now recorded and can be executed by "C-x e" once you have selected a region. You can even save that macro (check the info pages for emacs) and bind it to a key. HTH, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.7 (release_7.7.381.g05ea.dirty)
Re: [O] Clocking table for all org-files
I will try it as well. Thanks. sochi 2011/10/26 Carsten Dominik > > On 26.10.2011, at 09:36, ishi soichi wrote: > > > Thanks! That was simple. > > Alternatively, use the :scope parameter, described in the manual. > > - Carsten > > > > > soichi > > > > 2011/10/26 Cecilio Pardo > > > > Hitting R in the daily agenda will give you that > (org-agenda-clockreport-mode). > > > > > I'm wondering if there is a way to generate a clocking table for ALL > org > > > files that are registered as "org-agenda-files" ? > > > > -- > > Cecilio Pardo. > > > > > >
Re: [O] Clocking table for all org-files
On 26.10.2011, at 09:36, ishi soichi wrote: > Thanks! That was simple. Alternatively, use the :scope parameter, described in the manual. - Carsten > > soichi > > 2011/10/26 Cecilio Pardo > > Hitting R in the daily agenda will give you that > (org-agenda-clockreport-mode). > > > I'm wondering if there is a way to generate a clocking table for ALL org > > files that are registered as "org-agenda-files" ? > > -- > Cecilio Pardo. > >
Re: [O] Clocking table for all org-files
Hitting R in the daily agenda will give you that (org-agenda-clockreport-mode). > I'm wondering if there is a way to generate a clocking table for ALL org > files that are registered as "org-agenda-files" ? -- Cecilio Pardo.
Re: [O] Clocking table for all org-files
Thanks! That was simple. soichi 2011/10/26 Cecilio Pardo > > Hitting R in the daily agenda will give you that > (org-agenda-clockreport-mode). > > > I'm wondering if there is a way to generate a clocking table for ALL org > > files that are registered as "org-agenda-files" ? > > -- > Cecilio Pardo. > >
