Re: [O] Alternate format for datetree
c b 24x7x...@gmail.com wrote: Thank a lot for your suggestions. I finally got it working. It took a while to figure out that the back-tick is different from the quote. I am an elisp newbie. Is there an easy explanation of why we need a back-tick vs. quote? quote says: take the next expression as is - do not evaluate anything in it. backquote says: take the next expression as is - do not evaluate anything in it, *except* do evaluate any subexpression preceded by a comma and put the result back into the original expression in place of the comma-ed subexpression. E.g '(a b c) - (a b c) `(a b c) - (a b c) ; because there is no comma '(a (+ 2 3)) - (a (+ 2 3)) `(a (+ 2 3)) - (a (+ 2 3)) ; again no comma `(a ,(+ 2 3)) - (a 5) Incidentally, if you switch to the *scratch* buffer (which is in Lisp Interaction mode), you can type these expressions in and evaluate each one by pressing C-j at the end of each expression. So they both quote: the first one unconditionally, the second mostly but allowing partial evaluation of subexpressions. BTW, '(a b c) is shorthand for (quote (a b c)): internally, the lisp reader translates the first to the second and then the evaluator evaluates the quote form, returning its (unevaluated) argument: that's why quote is a special form - by contrast, ordinary functions always evaluate their arguments. `(a b ,(+ 2 3)) is also shorthand for (backquote (a b ,(+ 2 3))) but the implementation is necessarily more complicated: backquote is implemented as a macro (because it is a special form, its argument is not evaluated, so it cannot be implemented as a function; it has to be implemented as a macro), but then backquote has to dig into the structure to look for , (and also for the somewhat different ,@ construct - see the docs) and do what's necessary. Another example is provided by the docstring of backquote itself: C-h f backquote RET to see it. For more info, see the elisp manual, chapter 9 on evaluation: (info (elisp) Evaluation) and two sections therein in particular, 9.3 Quoting, and 9.4 Backquote: (info (elisp) Quoting) (info (elisp) Backquote) Nick
Re: [O] org-refile failing
On 5 Sep 2012 19:59, Marcelo de Moraes Serpa celose...@gmail.com wrote: Sorry Bastien, should have included it before. Emacs: GNU Emacs 23.4.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2012-01-29 on bob.porkrind.org Org: Org-mode version 7.9.1 (release_7.9.1-145-g0a6165-git @ mixed installation! /Applications/Emacs.app/Contents/Resources/lisp/org/ and /Users/fullofcaffeine/.emacs.d/vendor/org/lisp/) Hi all, I don't have any specific light to shed on the OP's issue. But i did notice the discussion seemed to miss the above which itself can many problems cause. Best, Brian vdB
Re: [O] can't find org-version?
Benjamin Slade writes: Since updating to org 7.9, I've had an odd problem with another package that depends on org-mode (org-toodledo). It reports that it can't find org-version. I did have org installed via git, but I decided, given that I'm running emacs24, to change over to the elpa install to see if that made any difference. It didn't. The following work-around patches the problem, but I was wondering how to really solve it: (require 'org-version) (setq org-version (org-release)) The variable org-version was an internal one that has been removed. The org-toodledo package should not rely on internal variables, but rather use the official interface, in this case the function org-version. HTH, 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
Re: [O] Alternate format for datetree
c b 24x7x...@gmail.com writes: It took a while to figure out that the back-tick is different from the quote. Two useful links in this respect. http://www.lisperati.com/syntax.html http://www.lisperati.com/looking.html Just focus on the diagrams in the link - particularly the flip-flop diagram in the second link. Once you have the flip-flop image in mind, you will realize that characters ` and , are also rotated 180 degrees and are actually flip-flops. Now try mapping what flip to don't evaluate and flop to evaluate. Then you can move on to what Nick says or the doc says. --
[O] [babel] code execution in commented lines
Hi all,
by now I learned not to call behaviour not meeting my expectations a
bug hastily
So, here is my question:
Is it intended that code in commented lines gets executed during export?
# example: buggy, thus commented src_R{Sys.sleep(10) stop(Here is a Bug)}
This kind of violates the I-quickly-comment-this-out style of fixing
broken parts of the document ;-)
Regards,
Andreas
Re: [O] Alternate format for datetree
On 29/08/12 21:01, Ian Barton wrote: On 29/08/12 15:25, John Hendy wrote: On Wed, Aug 29, 2012 at 2:49 AM, Ian Barton li...@manor-farm.org wrote: On 28/08/12 13:50, Nick Dokos wrote: Ian Barton li...@wilkesley.net wrote: I would like to use something like this. However, using a recent git checkout of org mode and the following simple template from the original list message: (u Test entry (file+headline ~/test.org ,(format %s %s (format-time-string %B) (format-time-string %Y I get the following error: Debugger entered--Lisp error: (wrong-type-argument stringp (\, (format %s %s (format-time-string %B) (format-time-string %Y regexp-quote((\, (format %s %s (format-time-string %B) (format-time-string %Y org-capture-set-target-location() org-capture(nil) call-interactively(org-capture nil nil) I also get the same error from John Hendy's template. Is this a bug in recent versions of org, or is there an error in the template lisp? I have tried doing a git bisect, but can only go back a few commits, as my config now includes several things that have only recently been added to org. You are missing the backquote: --8---cut here---start-8--- `(u Test entry (file+headline ~/test.org ,(format %s %s (format-time-string %B) (format-time-string %Y --8---cut here---end---8--- Nick Thanks Nick. Hwever with the following minimal template, from the OP, I still get the error: ;; org-capture settings. (setq org-capture-templates `((t test entry (file+headline ~/file.org ,(format %s (format-time-string %m))) ,(format ** %s \n*** %s-%s \n [%s-%s-%s %s %s:%s] (format-time-string %d) (format-time-string %Y) (format-time-string %A) (format-time-string %Y) (format-time-string %m) (format-time-string %d) (format-time-string %a) (format-time-string %H) (format-time-string %M)) ))) Odd. I just copied and pasted this into my .emacs and commented out my actual capture templates section entirely, leaving only this and it works as expected. (Just saw Nick's response as well and was going to both try and suggest similar with a minimal .emacs). Thanks both. I'll try with a minimal emacs and post the results. However, it may be a day or two as I am currently in the far West of Ireland with very variable Internet connections ! Now back with a reliable Internet connection. Thanks for the minimal example, which worked correctly. In my full setup, I have quite a lot of template definitions. It turned out that I had put the backquote the wrong side of a bracket. Ian.
Re: [O] repeater not working?
Sebastien Vauban wxhgmqzgw...@spammotel.com writes: Hi Alan, Alan Schmitt wrote: * TODO Return books to library [/] ** TODO Search books ** TODO Put books in bag ** TODO Unlock bike ** TODO Drive to library Is there a way for a TODO to be hidden from an agenda until all previous TODOs have been done? Here, there is no point in putting the books in the bag if you have not found them ... Look at the ORDERED property.[1] Best regards, Seb [1] That makes me think that I'd find it useful to see that information as a tag as well. Exactly like for Beamer where some properties have an associated tag automatically created, purely for easier visualization. What do you think? I would clearly use that feature more (I currently don't), if this would be the case. Thanks, this was most helpful. Alan
Re: [O] [babel] code execution in commented lines
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi all,
by now I learned not to call behaviour not meeting my expectations a
bug hastily
So, here is my question:
Is it intended that code in commented lines gets executed during export?
# example: buggy, thus commented src_R{Sys.sleep(10) stop(Here is
a Bug)}
No it isn't intended. There's a pending patch for this, but it requires
some background changes that are not available yet.
I'll try to fix it soon.
Regards,
--
Nicolas Goaziou
[O] superscripts, tables and latex
I'm trying to export a simple table to latex with the only catch being
it has some units I need to superscript.
Here is the org code
--
#+Options: num:nil toc:nil
* section heading
ObjectiveTemporal scaleSpatial Scale (km) Requirement
+-+--+-+---
Vegetation Weekly (target) 200–1000 0.3gC m^{-2} d^{-1}
Land surface Annual 2000 5/25 g C m^{-2} yr^{-1}
Ocean fluxes Annual 2500 3 g C m^{-2} yr^{-1}
Anthropogenic Annual 300 4 g C m^{-2} yr^{-1}
| Objective | Temporal scale | Spatial Scale (km) | Requirement |
|+-+--+-+---|
| Vegetation | Weekly (target) | 200–1000 |0.3gC m^{-2} d^{-1}
|Land surface |Annual |2000 |5/25 g C m^{-2} yr^{-1}
|Ocean fluxes |Annual |2500 |3 g C m^{-2} yr^{-1}
|Anthropogenic |Annual |300 |4 g C m^{-2} yr^{-1}
--
It has the text of the table with the pipe characters removed then the
table itself.
Here is the latex it generates
--
% Created 2012-09-06 Thu 22:27
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\providecommand{\alert}[1]{\textbf{#1}}
\title{test}
\author{Peter Rayner}
\date{\today}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Emacs Org-mode version N/A}}
\begin{document}
\maketitle
\section*{section heading}
\label{sec-1}
CO$_2$ CO$^{\mathrm{-2}}$ 0.3gC m$^{\mathrm{-2}}$ y$^{\mathrm{-1}}$
ObjectiveTemporal scaleSpatial Scale (km) Requirement
+-+--+-+---
Vegetation Weekly (target) 200–1000 0.3gC m$^{\mathrm{-2}}$
d$^{\mathrm{-1}}$
Land surface Annual 2000 5/25 g C m$^{\mathrm{-2}}$ yr$^{\mathrm{-1}}$
Ocean fluxes Annual 2500 3 g C m$^{\mathrm{-2}}$ yr$^{\mathrm{-1}}$
Anthropogenic Annual 300 4 g C m$^{\mathrm{-2}}$ yr$^{\mathrm{-1}}$
\begin{center}
\begin{tabular}{llrl}
ObjectiveTemporal scale Spatial Scale (km)Requirement
\\
\hline
Vegetation Weekly (target) 200–10000.3gC m^\{-2\}
d^\{-1\} \\
Land surface Annual 20005/25 g C m^\{-2\}
yr^\{-1\} \\
Ocean fluxes Annual 25003 g C m^\{-2\}
yr^\{-1\} \\
AnthropogenicAnnual3004 g C m^\{-2\}
yr^\{-1\} \\
\end{tabular}
\end{center}
\end{document}
--
In the untabulated text the ^{-2} is being replaced with math
delimiters while in the tabulated version the braces are being quoted.
This doesn't seem to happen when I export to html where both versions
get superscripted. This could be a bug but it's more likely something
I'm misunderstanding, can someone enlighten me?
please reply directly as well as to the list, I'm behind on my mailing
list browsing.
thanks in advance
Peter
--
Peter Rayner
room 343
School of Earth Sciences, University of Melbourne, 3010, Vic, Australia
tel: work: +61 (0)3 8344 9708; fax: +61 (0)3 8344 7761
mobile +61 402 752 379, skype: petermorag
mail-to: pray...@unimelb.edu.au
and
CLIMMOD ENGINEERING
http://www.climmod.com
mail-to: peter.ray...@climmod.com
Re: [O] org-refile failing
HI Nick, Looks like the 0 was causing the issue. Changing it to any non-zero value solves it. I don't remember how it ended up there though - I might have setup it by accident. Thanks! - Marcelo. On Thu, Sep 6, 2012 at 1:53 AM, Brian van den Broek brian.van.den.br...@gmail.com wrote: On 5 Sep 2012 19:59, Marcelo de Moraes Serpa celose...@gmail.com wrote: Sorry Bastien, should have included it before. Emacs: GNU Emacs 23.4.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2012-01-29 on bob.porkrind.org Org: Org-mode version 7.9.1 (release_7.9.1-145-g0a6165-git @ mixed installation! /Applications/Emacs.app/Contents/Resources/lisp/org/ and /Users/fullofcaffeine/.emacs.d/vendor/org/lisp/) Hi all, I don't have any specific light to shed on the OP's issue. But i did notice the discussion seemed to miss the above which itself can many problems cause. Best, Brian vdB
[O] Narrow to sparse tree
I keep a bibliography in an org file using the excellent org-bibtex functionality. It has over 100 entries with a first level heading for each item. I tag each of the items with keywords/topics. Using sparse trees I can quickly find and navigate to items matching a particular tag, but if only 4 items out of the 100 have that tag the signal to noise is pretty bad. What I would like to do is narrow the buffer to just those entries that match the tag. I've looked in the manual but I couldn't find a way to do this. Can this be done with org? Thanks for the help, Chris. ps. using M-g n or M-g M-n (next-error) with sparse trees I expected it to wrap when you reach the end of the file but sadly this is not the case. Is there a reason for this?
[O] Cached agenda views?
Hi list, It's a known fact that the more files you put into the agenda, the more likely it is to become slower. I've started using Memacs a few weeks ago, and my agenda is still very useable, but significantly slower than before (due to the big amount of temporal data being processed from my gmail emails and git logs). I was wondering if it would be possible to NOT regenerate the agenda everytime. I think this would mean parsing the org files and dumping the elisp objects created somehow. This way, when visiting the agenda again, it would be loaded from the objects dump and would not go through the parsing of all the agenda files again, unless forced by the user; or within a specific time, via a cron or internal emacs timer. This would also, in theory, allow the agenda to be constantly regenerated in a background worker process. What do you think? Cheers, - Marcelo.
Re: [O] Cached agenda views?
Le jeudi 06 sep 2012 à 08:54:04 (-0500), Marcelo de Moraes Serpa a écrit : Hi list, It's a known fact that the more files you put into the agenda, the more likely it is to become slower. I've started using Memacs a few weeks ago, and my agenda is still very useable, but significantly slower than before (due to the big amount of temporal data being processed from my gmail emails and git logs). I was wondering if it would be possible to NOT regenerate the agenda everytime. I think this would mean parsing the org files and dumping the elisp objects created somehow. This way, when visiting the agenda again, it would be loaded from the objects dump and would not go through the parsing of all the agenda files again, unless forced by the user; or within a specific time, via a cron or internal emacs timer. This would also, in theory, allow the agenda to be constantly regenerated in a background worker process. What do you think? Cheers, - Marcelo. Hi Marcello, Have you tried sticky agendas (`*' to toogle on/off in the org-agenda menu)? One of its many uses is to *not* regenerate an agenda each time it is called, but only when the user wants it. Cheers, François.
Re: [O] superscripts, tables and latex
Peter Rayner peter.julien.ray...@gmail.com wrote:
I'm trying to export a simple table to latex with the only catch being
it has some units I need to superscript.
Here is the org code
--
..
--
It has the text of the table with the pipe characters removed then the
table itself.
Here is the latex it generates
--
...
--
In the untabulated text the ^{-2} is being replaced with math
delimiters while in the tabulated version the braces are being quoted.
This doesn't seem to happen when I export to html where both versions
get superscripted. This could be a bug but it's more likely something
I'm misunderstanding, can someone enlighten me?
please reply directly as well as to the list, I'm behind on my mailing
list browsing.
The standard latex exporter does indeed mishandle this, but unless it is
a very easy fix, it's unlikely to be fixed: the exporter is on its way
out.
If you can, please use Nicolas Goaziou's new exporter: it handles the
situation correctly.
Assuming you are running a recent version of org, you can install it
alongside the old one. Just add the following to your init file (with
the path modified appropriately):
--8---cut here---start-8---
(add-to-list 'load-path /path/to/contrib/lisp))
(require 'org-export)
(require 'org-e-ascii) ; if you want
(require 'org-e-html) ; if you want
(require 'org-e-latex)
--8---cut here---end---8---
In my case, I bind the new exporter dispatch to a key sequence, but that
is strictly optional. In addition, when the switchover is complete and
the old exporter is thrown overboard, C-c C-e will be the official
binding. In the meantime, something like this
--8---cut here---start-8---
(define-key org-mode-map (kbd C-c E) 'org-export-dispatch)
--8---cut here---end---8---
will allow you to invoke it with C-c E (which is officially undefined
currently). But you can always skip the define-key stuff and invoke it
the long way:
--8---cut here---start-8---
M-x org-export-dispatch RET
--8---cut here---end---8---
Nick
[O] Save-buffer within a code block
Hello fellow Org-mode'rs: I noticed that now, when editing code in ESS mode (after switching from org-mode using C-') I cannot use save-buffer to save any changes into my org mode file. Instead, when doing save-buffer I get prompted for a new file name and the only the code block gets saved. If I want to save everything (changes into the entire org mode file), I need to switch from ESS to org mode, and then do save-buffer. Is this a bug or a new feature? Can I revert back to the previous functionality (which was much more convenient)? 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] Narrow to sparse tree
Le jeudi 06 sep 2012 à 15:46:42 (+0200), Christopher Witte a écrit : I keep a bibliography in an org file using the excellent org-bibtex functionality. It has over 100 entries with a first level heading for each item. I tag each of the items with keywords/topics. Using sparse trees I can quickly find and navigate to items matching a particular tag, but if only 4 items out of the 100 have that tag the signal to noise is pretty bad. What I would like to do is narrow the buffer to just those entries that match the tag. I've looked in the manual but I couldn't find a way to do this. Can this be done with org? Thanks for the help, Chris. ps. using M-g n or M-g M-n (next-error) with sparse trees I expected it to wrap when you reach the end of the file but sadly this is not the case. Is there a reason for this? Hi Chris, Have you think of using the agenda views? In four keystrokes, you're there with the best signal to noise ratio: - `C-c a' (or M-x org-agenda) - `' (to restrict the agenda view to the current buffer) - `m' (for tags, property and todo keywords) - `abc' (for tag :abc:), or (`YEAR'=2010 for PROPERTY :YEAR: equal to 2010, etc). HTH, François. PS: +1 for the excellent org-bibtex functionality !
Re: [O] Narrow to sparse tree
That's great, it gets me part of the way there. I also keep notes for each reference under their heading and I'd like to be able to see/edit them as well. Is there a way to do this in an agenda buffer? On 6 September 2012 16:44, François Allisson franc...@allisson.co wrote: Le jeudi 06 sep 2012 à 15:46:42 (+0200), Christopher Witte a écrit : I keep a bibliography in an org file using the excellent org-bibtex functionality. It has over 100 entries with a first level heading for each item. I tag each of the items with keywords/topics. Using sparse trees I can quickly find and navigate to items matching a particular tag, but if only 4 items out of the 100 have that tag the signal to noise is pretty bad. What I would like to do is narrow the buffer to just those entries that match the tag. I've looked in the manual but I couldn't find a way to do this. Can this be done with org? Thanks for the help, Chris. ps. using M-g n or M-g M-n (next-error) with sparse trees I expected it to wrap when you reach the end of the file but sadly this is not the case. Is there a reason for this? Hi Chris, Have you think of using the agenda views? In four keystrokes, you're there with the best signal to noise ratio: - `C-c a' (or M-x org-agenda) - `' (to restrict the agenda view to the current buffer) - `m' (for tags, property and todo keywords) - `abc' (for tag :abc:), or (`YEAR'=2010 for PROPERTY :YEAR: equal to 2010, etc). HTH, François. PS: +1 for the excellent org-bibtex functionality !
Re: [O] repeater not working?
Bastien writes: By the way, what is the canonical way to install contribs? The doc.norang.ca site says to simply add a load_path to the source directory of org-mode, but maybe there is another way. Yes, adding the contrib/lisp/ to your load-path is *the* way. Not any longer and it has always been a way of _using_ and never been a way of _installing_ files from contrib. Alan, if you want to truly install something from contrib/ together with the core part of Org, please add a line to local.mk ORG_ADD_CONTRIB = … (or uncomment the example, depending on when local.mk been created) and replace the ellipsis with the base name (that is without the .el suffix and without any path prefix) of those files from contrib you would like to add to your installation. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] Narrow to sparse tree
Le jeudi 06 sep 2012 à 17:02:06 (+0200), Christopher Witte a écrit : That's great, it gets me part of the way there. I also keep notes for each reference under their heading and I'd like to be able to see/edit them as well. Is there a way to do this in an agenda buffer? Just press space, enter or tab on any of your results. Notice the different behaviours between the three commands, and choose your favourite depending on the context (mine is space anyway). François.
Re: [O] superscripts, tables and latex
Nick Dokos nicholas.do...@hp.com writes: (add-to-list 'load-path /path/to/contrib/lisp)) (require 'org-export) (require 'org-e-ascii) ; if you want (require 'org-e-html) ; if you want (require 'org-e-latex) I do this: C-x C-f ~/src/org-mode/contrib/lisp/ M-x update-directory-autoloads RET RET org-contrib-install.el ;; Note the two RETs above (require 'org-contrib-install) ;; in .emacs ps: one more install.el file to knock our heads over :-). --
[O] Appt - How to quit displaying notifications?
Hello, I'm using org-agenda-to-appt to warn me about upcoming appointments. I'm fine with the default warning time of 12 minutes, but I would like to turn off the subsequent reminders that happen every three minutes. I'd like a reminder to occur 12 minutes before the appointment, then at the time of the appointment. I found the appt-display-interval variable which is 3 minutes, but this is described as Number of minutes to wait between checking the appointment list., which is not /quite/ the same thing as a Snooze. I guess I'll just send the appt-display-interval to 11 minutes or something like that. Is that what everyone else does to avoid getting appt messages popping up every 3 minutes? Thanks, --Nate
Re: [O] Alternate format for datetree
On Thu, Sep 6, 2012 at 12:42 AM, c b 24x7x...@gmail.com wrote:
Hi John and Nick,
Thank a lot for your suggestions. I finally got it working. It took a while
to figure out that the back-tick is different from the quote.
I am an elisp newbie. Is there an easy explanation of why we need a
back-tick vs. quote?
Also, I found that while the template works, it creates a new tree every
time I capture an entry as follows
snip
#1. Is there any way to consolidate this like the following?
You might check out a question I asked that's quite similar.
Basically... no, not unless the headline already exists. Then you have
to use file+olp instead of file+headline. Check out my example:
-- http://lists.gnu.org/archive/html/emacs-orgmode/2012-08/msg01465.html
Orgmode can file to a headline passed in the capture template
immediately after the =(... file+headline
headline-to-file-under-here)=, but the longer =`(format...= tells
Org to insert that text every time. Thus, our sub-headline evaluation
will always create that text anew. The workaround will be for you to
re-arrange the =`(format...= section and put it above. In other words,
this:
--
(setq org-capture-templates
`((t test entry
(file+headline ~/file.org
,(format %s
(format-time-string %m)))
,(format ** %s \n*** %s-%s \n [%s-%s-%s %s %s:%s]
(format-time-string %d)
(format-time-string %Y)
(format-time-string %A)
(format-time-string %Y)
(format-time-string %m)
(format-time-string %d)
(format-time-string %a)
(format-time-string %H)
(format-time-string %M))
)))
--
Needs to become something like this:
--
(setq org-capture-templates
`((t test entry
(file+olp ~/file.org
,(format %s ;; first headline
(format-time-string %m)
,(format %s ;; second headline
(format-time-string %d)
,(format %s - %s
(format-time-string %Y)
(format-time-string %A)))
,(format [%s-%s-%s %s %s:%s]
(format-time-string %Y)
(format-time-string %m)
(format-time-string %d)
(format-time-string %a)
(format-time-string %H)
(format-time-string %M))
)))
--
Something like that (I wrote this in email and didn't check it). That
tells Org to look for a *pre-existing* headline structure in this
form:
--
* Month (in ## format, like 09 for September)
** Day (in ## format, like 06 for the 6th)
*** Year - Day (in - Name format like 2012 - Thursday
--
And under that, it will file:
--
[timestamp] what you write
--
But... this means you need to pre-create your daily headline structure.
I think a reasonable feature request would be to have something like a
=:use-existing-capture-headline t= option that would tell Org to
*either* create a new capture headline (as on the first time used that
day) or file into a pre-existing headline if one already exists in
that form. Something like a hybrid between file+headline and file+olp.
Hope that makes sense. I think my example in the link above should help as well.
* 09
** 05
*** 2012 - Wednesday
[2012-09-05 Wed 22:31] My first working month tree note
[2012-09-05 Wed 22:35] My first working month tree note
#2 The time always is reported as 22:31 (I guess that's the time I launched
emacs). Is there a way for the time stamp to be corrected based on the
current time? I generally leave emacs running for days together, so the time
it's launched doesn't really work for me.
Did you change the above to 21:35 or did it file like that? Not sure
why H:M wouldn't expand to the current date. One thing that just
occurred to me, however, is to replace that whole timestamp string
with %%U% and Org will just expand it to a date+time stamp.
Good luck,
John
Once again, thanks a lot for your help!
-c. b.
On Sun, Aug 26, 2012 at 11:08 PM, John Hendy jw.he...@gmail.com wrote:
On Sun, Aug 26, 2012 at 11:04 PM, Nick Dokos nicholas.do...@hp.com
wrote:
John Hendy jw.he...@gmail.com wrote:
On Sun, Aug 26, 2012 at 3:11 PM, c b 24x7x...@gmail.com wrote:
Hi,
I have been using org-mode for about 18 months now and love it. I
recently
came across the org-capture file+datetree format and it is just what
I am
looking for, except that I need a slightly different format described
as
below
Currently format is
* 2012
** 2012-08
*** 2012-08-26 Sunday
[2012-08-26 Sun 13:00] My note for this Sunday afternoon
Needed format is
* 08
** 26
*** 2012 Sunday
[2012-08-26 Sun 13:00] My note for this Sunday afternoon
Basically, I need to have the root of the date tree on the month,
followed
by date and then Year, so that for a particular date, I can see all
yearly
activity.
Is there currently a way to alter this?
If not, how would I go about adding a file+monthtree format for
org-capture?
Any suggestions would be appreciated
I was looking for something similar and someone provided a custom
capture template that allowed for using inactive timestamps vs. the
default
Re: [O] suggestion for org-emphasis-regexp-components: *U*nited *N*ations
Stefan Vollmar writes:
(defcustom org-emphasis-regexp-components
'( #\t('\{ - #\t.,:!?;'\)}\\ \t\r\n,\' . 1)
where # is the unicode character U200B.
AFAIK, such a change would make Org incompatible with Emacs22.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
[O] commit 7719734dd7 org-compat.el: New compatibility function `org-random'
Sorry, but that macro doesn't call `random´ appropriately at all. No package should ever use `(random t)´ at all and especially not repeatedly. Please make org-random an alias to random. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Alternate format for datetree
Hello, On Thu, Sep 6, 2012 at 11:33 AM, John Hendy jw.he...@gmail.com wrote: On Thu, Sep 6, 2012 at 12:42 AM, c b 24x7x...@gmail.com wrote: Hi John and Nick, [snip] * 09 ** 05 *** 2012 - Wednesday [2012-09-05 Wed 22:31] My first working month tree note [2012-09-05 Wed 22:35] My first working month tree note #2 The time always is reported as 22:31 (I guess that's the time I launched emacs). Is there a way for the time stamp to be corrected based on the current time? I generally leave emacs running for days together, so the time it's launched doesn't really work for me. Did you change the above to 21:35 or did it file like that? Not sure why H:M wouldn't expand to the current date. One thing that just occurred to me, however, is to replace that whole timestamp string with %%U% and Org will just expand it to a date+time stamp. Good luck, John This is actually an issue with all of the backtick elements in the capture template but it shows up most obviously in the timestamp portion. I only realized this after providing the solution that John had referenced earlier in this thread. Backticks are expanded on evaluation and resolve to the specific value of their called portions. So for the headlines you will need to re-evaluate the template every day to update it (or restart emacs). For the timestamp itself you should be able to use the %U escape in the capture template and it will insert the date and time on it's own. Regards, -- Jon
Re: [O] Appt - How to quit displaying notifications?
Nathan Neff nathan.n...@gmail.com wrote: Hello, I'm using org-agenda-to-appt to warn me about upcoming appointments. I'm fine with the default warning time of 12 minutes, but I would like to turn off the subsequent reminders that happen every three minutes. I'd like a reminder to occur 12 minutes before the appointment, then at the time of the appointment. I found the appt-display-interval variable which is 3 minutes, but this is described as Number of minutes to wait between checking the appointment list., which is not /quite/ the same thing as a Snooze. Where did you see that? It probably needs some changes. C-h v appt-display-interval RET says , | appt-display-interval is a variable defined in `appt.el'. | Its value is 3 | | Documentation: | Interval in minutes at which to display appointment reminders. | Once an appointment becomes due, Emacs displays reminders every | `appt-display-interval' minutes. You probably want to make | `appt-message-warning-time' be a multiple of this, so that you get | a final message displayed precisely when the appointment is due. | | Note that this variable controls the interval at which | `appt-display-message' is called. The mode line display (if active) | always updates every minute. ` I guess I'll just send the appt-display-interval to 11 minutes or something like that. Is that what everyone else does to avoid getting appt messages popping up every 3 minutes? Just setting appt-display-interval and appt-message-warning-time equal to (say) 12, should work fine, afaict - but I have not tried it. Nick PS A propos of nothing, one strangeness that I have observed is that at least the *final* notification (and maybe all of them) is one minute late, but I haven't chased it down yet.
Re: [O] Filtering Agenda View
Hi Ken, Ken Mankoff mank...@gmail.com writes: I tried setting the regexp to \ WAITING\ but that did not fix it. How can I improve the regexp, or is there a better way to show TODO items that are TODO, STARTED, WHATEVER, but not WAITING (or not WAITING and SOMETHINGELSE). ,[ (describe-function 'org-agenda-skip-if) ] | (org-agenda-skip-if SUBTREE CONDITIONS) | [...] | CONDITIONS is a list of symbols, boolean OR is used to combine the results | from different tests. Valid conditions are: | | scheduled Check if there is a scheduled cookie | notscheduled Check if there is no scheduled cookie | deadline Check if there is a deadline | notdeadline Check if there is no deadline | timestamp Check if there is a timestamp (also deadline or scheduled) | nottimestamp Check if there is no timestamp (also deadline or scheduled) | regexpCheck if regexp matches | notregexp Check if regexp does not match. todo Check if TODO keyword matches | nottodo Check if TODO keyword does not match | | `todo' and `nottodo' accept as an argument a list of todo | keywords, which may include * to match any todo keyword. | (org-agenda-skip-entry-if 'todo '(TODO WAITING)) | | would skip all entries with TODO or WAITING keywords. | | Instead of a list, a keyword class may be given. For example: | | (org-agenda-skip-entry-if 'nottodo 'done) ` Does that help? Memnon
Re: [O] suggestion for org manual
Moin Jonas, Jonas Stein n...@jonasstein.de writes: It says # You have enabled the habits module by customizing the variable org-modules. I would expect here a link about customizing the variable org-modules, and how the setting looks like. Well, customizing variables belongs to the emacs realm; given that, the documentation is pretty good. One way to improve it could be something like You have enabled the habits module by `M-x customize-variable' org-modules. The customize buffer is fairly self-explanatory then I guess. However, while this would make the manual more newcomer friendly, it would also be less pleasant to read imho. ... It says # You must also have state logging for the DONE state enabled, in order for historical data to be represented in the consistency graph. If it is not enabled it is not an error, but the consistency graphs will be largely meaningless. I would expect here # In order to get meaningful consistency graphs state logging for state DONE must be enabled. (Link to article about enable logging or explain it here.) Tracking TODO state changes is in 5.3.2, i.e. just one [ keypress away, if you read the emacs info pages?! But a link rarely hurts, I guess :). Thanks for your suggestions! Memnon
Re: [O] commit 7719734dd7 org-compat.el: New compatibility function `org-random'
Achim Gratz strom...@nexgo.de writes: Sorry, but that macro doesn't call `random´ appropriately at all. The real problem is (random t) in previous versions of org-id.el. Do you mean this should be (random) instead of (random t) in those versions? Why? If so, we can simply get rid of the compatibility macro and use (random). No package should ever use `(random t)´ at all and especially not repeatedly. I thought (random t) was okay especially because related functions (e.g. org-id-new) are *never* repeated at regular intervals. Besides, (random t) is documented in Emacs 24.3 and XEmacs. -- Bastien
Re: [O] can't find org-version?
Christopher J. White writes: If 7.9 is still an early release, I'd suggest adding the org-version variable back to org so as not to break other packages that may also depend the version string. Your use of the variable org-version was completely unnecessary, so this is a non-issue. I've just answered your mail that you apparently sent off-list to me. 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] can't find org-version?
As this is the standard way of checking against a package's version, and now that (org-version) does the right thing, I reintroduced the constant `org-version'. -- Bastien
Re: [O] can't find org-version?
Achim Gratz strom...@nexgo.de writes: The variable org-version was an internal one that has been removed. The org-toodledo package should not rely on internal variables, but rather use the official interface, in this case the function org-version. In the real world, developers rely on a set of stable expectations. Being able to check against `org-version' as a *variable* is one of them, and a very stable one. IMO, it is counter-productive to deceive this expectation and to ask developers to read org.el to know how they can check against Org's version. The way `org-version' is set internally is another topic, and I'm glad you finally come up with something that relies only on make/git. But geee... this has been a long and painful way to go, and I don't count how many users are/were confused about this. The original motivation for this was to spare the maintainer the sweat of possible merge conflicts when syncing with Emacs... which were just very unlikly to happen anyway. So, let's focus more on the users, and less on conceptual purity. -- Bastien
Re: [O] capture templates and org-contacts
Simon Thum writes: recently my org-contacts template broke; I get %![Error: (void-function gnus-alive-p)] in the capture buffer where the name should have been. The template is (c Kontakt entry (file+headline my-org-contacts-file Neu) * %(org-contacts-template-name))) The setup worked before - wanyone an idea what could be the cause? gnus-util must be loaded for this function to be available. This requirement is missing from both org-capture and org-gnus. Actually, this function really should be autoloaded by Gnus but isn't. I'm using org-fixup to generate my autoloads. Sure, but certainly not for Gnus… I've just pushed up a fix that adds (require 'gnus-util) to both files. 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] commit 7719734dd7 org-compat.el: New compatibility function `org-random'
Bastien writes: The real problem is (random t) in previous versions of org-id.el. Yes. Do you mean this should be (random) instead of (random t) in those versions? Why? If so, we can simply get rid of the compatibility macro and use (random). That would be the correct thing to do. No package should ever use `(random t)´ at all and especially not repeatedly. I thought (random t) was okay especially because related functions (e.g. org-id-new) are *never* repeated at regular intervals. That unfortunate misconception is built into many Emacs packages, hence the effort to finally make this operation a no-op and move the seeding of the PRNG to the Emacs init code. Besides, (random t) is documented in Emacs 24.3 and XEmacs. Sure, but you still aren't supposed to re-seed a PRNG each time you want a random number from it. Especially not with the seeding method that Emacs used to use. Each Emacs session should call `(random t)´ exactly once, in the user init file. Regards, 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
Re: [O] can't find org-version?
Bastien writes: As this is the standard way of checking against a package's version, and now that (org-version) does the right thing, I reintroduced the constant `org-version'. You have tested you always get the correct result with Emacs 23 and 24, XEmacs 21.5, with and without compilation, with and without generated autoloads and org-version and with and without load-path shadowings both from Emacs' built-in Org and version installed by the user and via ELPA, both after requiring just 'org and 'org-install, right? Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] can't find org-version?
Bastien writes: As this is the standard way of checking against a package's version, and now that (org-version) does the right thing, I reintroduced the constant `org-version'. You might want to fix this in maint (not master), BTW. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] commit 7719734dd7 org-compat.el: New compatibility function `org-random'
Bastien b...@altern.org wrote: Achim Gratz strom...@nexgo.de writes: Sorry, but that macro doesn't call `random´ appropriately at all. The real problem is (random t) in previous versions of org-id.el. Do you mean this should be (random) instead of (random t) in those versions? Why? If so, we can simply get rid of the compatibility macro and use (random). No package should ever use `(random t)´ at all and especially not repeatedly. I thought (random t) was okay especially because related functions (e.g. org-id-new) are *never* repeated at regular intervals. Besides, (random t) is documented in Emacs 24.3 and XEmacs. My understanding is that (random t) is called *once* to seed the RNG - after that you use (random) or (random N) - where N is a positive integer - to get the next (pseudo) random number in the sequence (scaled to fit in [0, N) in the second case). Nick
Re: [O] superscripts, tables and latex
Nick Dokos nicholas.do...@hp.com wrote: Assuming you are running a recent version of org, you can install it alongside the old one. Just add the following to your init file (with the path modified appropriately): I should have said you can use it ..., instead of you can install it What I described is not an installation method. Nick
[O] still struggling with workflow
I've been using org-mode for, oh about a year now, and it seems like a very useful tool. But I'm still struggling to understand and implement effective workflows for projects, re-using bits and pieces of text. For example, I have a general project related to heat wave morbidity and mortality, and indoor heat index. Hopefully I can parlay it into a number of distinct studies, each with IRB applications, grant applications, and papers (all pdf output), and presentations (beamer pdf output.) For example, all my stuff for the first study is in a single org file, HeatWaves1.org. The second project's documents will need to re-use much of that material, but not all of it; and there will be some new material. Is it viable to keep everything related to my heat wave work, for all substudies, in the one org file, and customize the output to my needs at different times, via judicious use of headlines and :export tags? Or is it best to start a new org file for each substudy and copy/paste what is needed from the old? Thanks. --Chris -- Christopher W. Ryan, MD, MS SUNY Upstate Medical University Clinical Campus at Binghamton 425 Robinson Street, Binghamton, NY 13904 cryanatbinghamtondotedu Once we recognize that we do not err out of laziness, stupidity, or evil intent, we can liberate ourselves from the impossible burden of trying to be permanently right. We can take seriously the proposition that we could be in error, without deeming ourselves idiotic or unworthy. [Karen Schulz, in Being Wrong: Adventures in the Margin of Error]
Re: [O] conditional export based on babel result
Andreas Leha andreas.l...@med.uni-goettingen.de writes: I am a bit late to the thread, but two possibilities come to mind: 1) write a brew template as #+name: brewtemp #+begin_src latex ... #end_src block then call it as #+begin_src R :noweb yes :results output latex brew(text= brewtemp ) #+end_src Brew allows loops and conditionals over both markup and code, which allows you to choose or skip a sub-document as the R code dictates. If the sub-document is of modest size and complexity, this is reasonably easy and the brew markup will be easy to read. 2) Use ravel (at https://github.com/chasberry/orgmode-accessories/) to export an org subtree as a knitr parent document in Rnw format (akin to Sweave) and another org subtree as a knitr child document. The parent document must call the child from within a code block to allow loops and conditionals. Then run knitr. For more complicated sub-documents, this might work better than building brew templates in latex src blocks as editting the org structure and retooling R src blocks is easier (for me at least) than re-organizing a lengthy latex src block with embedded brew calls. HTH, Chuck Eric Schulte eric.schu...@gmx.com writes: Andreas Leha andreas.l...@med.uni-goettingen.de writes: Hi all, is there a possibility to exclude (or include) parts of the document based on some babel source block result? First some use case: Say, I am doing a statistical test. And only if the test turns out to be significant, a follow-up analysis is carried out. Is that possible? One thinkable and ugly option would be to allow lisp-generated tags like in this dummy example: #+begin_org * The Test #+name: sometest #+begin_src R test_result - 0.03 #+end_src ** export maybe (if ( (string-to-number (sbe sometest)) 0.05) :export: :noexport:) The follow-up #+end_org Regards, Andreas Hi Andreas, When doing something this complex you may just want to write your own function which could say... take a subtree ID and a boolean flag as arguments and then set the export flag on that subtree as appropriate. The org-id-goto and org-toggle-comment functions may help in implementing this function. Best, Hi Eric, in my opinion, there are more complex things in org-mode already ;-) I agree, that such functionality doesn't need to be provided in org itself. Thanks a lot for the pointers to possible entry-points for an implementation. I hope, I'll find time to to go for it. Would be good for my elisp, anyway... Regards, Andreas -- Charles C. BerryDept of Family/Preventive Medicine cberry at ucsd edu UC San Diego http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
Re: [O] can't find org-version?
Achim Gratz strom...@nexgo.de writes: Bastien writes: As this is the standard way of checking against a package's version, and now that (org-version) does the right thing, I reintroduced the constant `org-version'. You might want to fix this in maint (not master), BTW. Yes, this is what I did. -- Bastien
Re: [O] still struggling with workflow
Christopher W. Ryan cr...@binghamton.edu wrote: I've been using org-mode for, oh about a year now, and it seems like a very useful tool. But I'm still struggling to understand and implement effective workflows for projects, re-using bits and pieces of text. For example, I have a general project related to heat wave morbidity and mortality, and indoor heat index. Hopefully I can parlay it into a number of distinct studies, each with IRB applications, grant applications, and papers (all pdf output), and presentations (beamer pdf output.) For example, all my stuff for the first study is in a single org file, HeatWaves1.org. The second project's documents will need to re-use much of that material, but not all of it; and there will be some new material. Is it viable to keep everything related to my heat wave work, for all substudies, in the one org file, and customize the output to my needs at different times, via judicious use of headlines and :export tags? Or is it best to start a new org file for each substudy and copy/paste what is needed from the old? I should think you can do it either way: only you can decide what the best way is. If you decide to go the second way, you might want to investigate the #+INCLUDE mechanism: maybe you can use it to reduce duplication. I'm not an org power user, so take the following with the appropriately-sized grain (or boulder) of salt: I would start with a single file and try to organize it in a way that encourages reuse, and be able to do what you need to do today and possibly tomorrow; don't worry too much about the day after tomorrow. If/when you find that the process is broken, or the processing takes too long, then reorganize it, massively if necessary; splitting it into multiple files might be the more natural thing to do at that point, but with the experience you have gained, you will probably be able to do that more reliably than when starting. Obviously, this is my personal biased view, and others might disagree. Bernt Hansen's write-up (http://doc.norang.ca/org-mode.html), as well as some of Tom Dye's project write-ups (check the Reproducible Research Examples section of http://orgmode.org/worg/org-contrib/babel/uses.html) might be good bedtime reading material: it's unlikely that they will answer your specific questions, but they might inspire you to come up with better solutions to your problems. Nick
Re: [O] still struggling with workflow
Nick Dokos nicholas.do...@hp.com writes: Christopher W. Ryan cr...@binghamton.edu wrote: I've been using org-mode for, oh about a year now, and it seems like a very useful tool. But I'm still struggling to understand and implement effective workflows for projects, re-using bits and pieces of text. For example, I have a general project related to heat wave morbidity and mortality, and indoor heat index. Hopefully I can parlay it into a number of distinct studies, each with IRB applications, grant applications, and papers (all pdf output), and presentations (beamer pdf output.) For example, all my stuff for the first study is in a single org file, HeatWaves1.org. The second project's documents will need to re-use much of that material, but not all of it; and there will be some new material. Is it viable to keep everything related to my heat wave work, for all substudies, in the one org file, and customize the output to my needs at different times, via judicious use of headlines and :export tags? Or is it best to start a new org file for each substudy and copy/paste what is needed from the old? I should think you can do it either way: only you can decide what the best way is. If you decide to go the second way, you might want to investigate the #+INCLUDE mechanism: maybe you can use it to reduce duplication. Mind map - Freemind, maybe == Create a mind map - preferably *NOT* using Org - with Pen and Paper or Freemind. Mind map for the underlying form = What you describe is map of your body of work. Now that the body of work is complete, what you need is a map of of how the body of work could be re-purposed. You need an Org file for the meta-map. Transcluding data = If you are transcluding data, graphs or bibliographies then there is not much. They are set in stone and are not fluid. They could be selected and transcluded. not same as transcluding basic forms or ideas == Transcluding ideas (not just literary text) and delivering it in plain text is a different beast. We select a theme. Narrate it with a tone. Choose a point-of-view. Order variously. Emphasize selected aspects. Leave out things on purpose. Strive to achieve various goals. Create a specific impression. Organize multi-dimensionally It seems you are trying to re-purpose your body of work to various ends. What you need is a multi-dimensional approach. Create an one or more Org file. I believe it doesn't matter. Start with what is natural. What is important is that you invent tags for each of the dimensions X dimension = technical axis = morbidity, mortality and head indices Y dimension = goals = grant-seeking, IRB applications Z dimension = Target audience = a specific conference, journal or a sponsoring/funding institution. Tag items on different dimensions == Now invent headlines and try to tag each piece in each of the independent dimensions. Use global agenda. Create custom queries for selection Use global agenda commands and complex tag queries to select the pieces you want. Transcribe (not transclude) == Once you have identified the source material, you can *transcribe* the way you want or the way the audience wants or the way your employer wants. Use Zotero or Org-bibtex = Try Zotero. It is the third software that I actually liked in first run and which seemed natural - first two being Emacs and Org in that order. Share your suggestions == Mind map could be a meta-one - try to articulate how Org was helpful and where it was a misery and what is confusing to you. Share the result with community and make recommendations on how Org could be improved. Ps: Not a power-user. But a sleepless one here. I'm not an org power user, so take the following with the appropriately-sized grain (or boulder) of salt: I would start with a single file and try to organize it in a way that encourages reuse, and be able to do what you need to do today and possibly tomorrow; don't worry too much about the day after tomorrow. If/when you find that the process is broken, or the processing takes too long, then reorganize it, massively if necessary; splitting it into multiple files might be the more natural thing to do at that point, but with the experience you have gained, you will probably be able to do that more reliably than when starting. Obviously, this is my personal biased view, and others might disagree. Bernt Hansen's write-up (http://doc.norang.ca/org-mode.html), as well as some of Tom Dye's project write-ups (check the Reproducible Research Examples section of http://orgmode.org/worg/org-contrib/babel/uses.html) might be good bedtime reading material: it's
[O] Org links that point to filenames with space do not open
Hi list, I have several links that use the file protocol to open files indexed in org entries. They work fine for entries that point to file whose filenames do *not* contain space, but for entries with space in them, it just fails silently. I.e: [[file:/Volumes/ext-hd/pdfs/Name\ Of\ The-\ 4th\ file.pdf]] I even escaped the filename using the (shell-quote-argument) function when indexing, but no luck. Any ideas? More info: - GNU Emacs 23.4.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2012-01-29 on bob.porkrind.org - Org-mode version 7.9.1 (release_7.9.1-145-g0a6165-git @ mixed installation! /Applications/Emacs.app/Contents/Resources/lisp/org/ and /Users/fullofcaffeine/.emacs.d/vendor/org/lisp/) - Mac OSX Lion. Thanks, - Marcelo.
Re: [O] Org links that point to filenames with space do not open
I'm pretty sure a () needs to go right after the first (:) and another needs to be just before the first (]) character. On Thu, 6 Sep 2012, Marcelo de Moraes Serpa wrote: Hi list, I have several links that use the file protocol to open files indexed in org entries. They work fine for entries that point to file whose filenames do *not* contain space, but for entries with space in them, it just fails silently. I.e: [[file:/Volumes/ext-hd/pdfs/Name\ Of\ The-\ 4th\ file.pdf]] I even escaped the filename using the (shell-quote-argument) function when indexing, but no luck. Any ideas? More info: - GNU Emacs 23.4.1 (x86_64-apple-darwin, NS apple-appkit-1038.36) of 2012-01-29 on bob.porkrind.org - Org-mode version 7.9.1 (release_7.9.1-145-g0a6165-git @ mixed installation! /Applications/Emacs.app/Contents/Resources/lisp/org/ and /Users/fullofcaffeine/.emacs.d/vendor/org/lisp/) - Mac OSX Lion. Thanks, - Marcelo. --- jude jdash...@shellworld.net Adobe fiend for failing to Flash
Re: [O] Org links that point to filenames with space do not open
Marcelo de Moraes Serpa celose...@gmail.com wrote: I have several links that use the file protocol to open files indexed in org entries. They work fine for entries that point to file whose filenames do *not* contain space, but for entries with space in them, it just fails silently. I.e: [[file:/Volumes/ext-hd/pdfs/Name\ Of\ The-\ 4th\ file.pdf]] I even escaped the filename using the (shell-quote-argument) function when indexing, but no luck. This is a link to a directory. I grabbed it with C-c l and inserted it with C-c C-l. It seems to work fine: [[file:lib/music/Arnold%20Schoenberg/Moses%20und%20Aron/][Moses und Aron] Nick
Re: [O] superscripts, tables and latex
Nick Dokos writes:
... description of using new exporter
This doesn't *appear* to help. I say appear because I can never be
absolutely sure I'm using the new exporter. I accessed it with
m-x org-export-dispatch
l
which generates
--
% Created 2012-09-07 Fri 14:30
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\providecommand{\alert}[1]{\textbf{#1}}
\author{Peter Rayner}
\date{\today}
\title{test}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Generated by Org mode N/A in Emacs 24.1.1.}}
\begin{document}
\maketitle
\section*{section heading}
\label{sec-1}
ObjectiveTemporal scaleSpatial Scale (km) Requirement
+-+--+-+---
Vegetation Weekly (target) 200–1000 0.3gC m$^{\mathrm{-2}}$
d$^{\mathrm{-1}}$
Land surface Annual 2000 5/25 g C m$^{\mathrm{-2}}$ yr$^{\mathrm{-1}}$
Ocean fluxes Annual 2500 3 g C m$^{\mathrm{-2}}$ yr$^{\mathrm{-1}}$
Anthropogenic Annual 300 4 g C m$^{\mathrm{-2}}$ yr$^{\mathrm{-1}}$
\begin{center}
\begin{tabular}{llrl}
Objective Temporal scale Spatial Scale (km) Requirement\\
\hline
Vegetation Weekly (target) 200–1000 0.3gC m\^\{-2\} d\^\{-1\}\\
Land surface Annual 2000 5/25 g C m\^\{-2\} yr\^\{-1\}\\
Ocean fluxes Annual 2500 3 g C m\^\{-2\} yr\^\{-1\}\\
Anthropogenic Annual 300 4 g C m\^\{-2\} yr\^\{-1\}\\
\end{tabular}
\end{center}
% Generated by Org mode N/A in Emacs 24.1.1.
\end{document}
--
It looks sufficiently different from the previous version to convince
me it is the new exporter being used here but with the same problem.
thanks again
Peter
--
Peter Rayner
room 343
School of Earth Sciences, University of Melbourne, 3010, Vic, Australia
tel: work: +61 (0)3 8344 9708; fax: +61 (0)3 8344 7761
mobile +61 402 752 379, skype: petermorag
mail-to: pray...@unimelb.edu.au
and
CLIMMOD ENGINEERING
http://www.climmod.com
mail-to: peter.ray...@climmod.com
Re: [O] Org links that point to filenames with space do not open
Nick, it's a custom script... however, it looks like I was using the wrong format. Instead of escaping the space chars, I should uri-encode them it seems. I'll try that. Thanks! On Thu, Sep 6, 2012 at 11:03 PM, Nick Dokos nicholas.do...@hp.com wrote: Marcelo de Moraes Serpa celose...@gmail.com wrote: I have several links that use the file protocol to open files indexed in org entries. They work fine for entries that point to file whose filenames do *not* contain space, but for entries with space in them, it just fails silently. I.e: [[file:/Volumes/ext-hd/pdfs/Name\ Of\ The-\ 4th\ file.pdf]] I even escaped the filename using the (shell-quote-argument) function when indexing, but no luck. This is a link to a directory. I grabbed it with C-c l and inserted it with C-c C-l. It seems to work fine: [[file:lib/music/Arnold%20Schoenberg/Moses%20und%20Aron/][Moses und Aron] Nick
Re: [O] Org links that point to filenames with space do not open
OK, found the issue, had to use url-insert-entities-in-string instead of shell-quote-argument. Thanks, - Marcelo. On Thu, Sep 6, 2012 at 11:47 PM, Marcelo de Moraes Serpa celose...@gmail.com wrote: Nick, it's a custom script... however, it looks like I was using the wrong format. Instead of escaping the space chars, I should uri-encode them it seems. I'll try that. Thanks! On Thu, Sep 6, 2012 at 11:03 PM, Nick Dokos nicholas.do...@hp.com wrote: Marcelo de Moraes Serpa celose...@gmail.com wrote: I have several links that use the file protocol to open files indexed in org entries. They work fine for entries that point to file whose filenames do *not* contain space, but for entries with space in them, it just fails silently. I.e: [[file:/Volumes/ext-hd/pdfs/Name\ Of\ The-\ 4th\ file.pdf]] I even escaped the filename using the (shell-quote-argument) function when indexing, but no luck. This is a link to a directory. I grabbed it with C-c l and inserted it with C-c C-l. It seems to work fine: [[file:lib/music/Arnold%20Schoenberg/Moses%20und%20Aron/][Moses und Aron] Nick
Re: [O] superscripts, tables and latex
Peter Rayner pray...@unimelb.edu.au wrote:
Nick Dokos writes:
... description of using new exporter=20
This doesn't *appear* to help. I say appear because I can never be
absolutely sure I'm using the new exporter. I accessed it with
m-x org-export-dispatch
l
which generates=20
--
% Created 2012-09-07 Fri 14:30
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=3D1000
\providecommand{\alert}[1]{\textbf{#1}}
\author{Peter Rayner}
\date{\today}
\title{test}
\hypersetup{
pdfkeywords=3D{},
pdfsubject=3D{},
pdfcreator=3D{Generated by Org mode N/A in Emacs 24.1.1.}}
\begin{document}
\maketitle
\section*{section heading}
\label{sec-1}
ObjectiveTemporal scaleSpatial Scale (km) Requirement =
=20
+-+--+-=
+---=20
Vegetation Weekly (target) 200=E2=80=931000 0.3gC m$^{\mathrm{-2}=
}$ d$^{\mathrm{-1}}$
Land surface Annual 2000 5/25 g C m$^{\mathrm{-2}}$ yr$^{\mathrm{-1}=
}$
Ocean fluxes Annual 2500 3 g C m$^{\mathrm{-2}}$ yr$^{\mathrm{-1}}$
Anthropogenic Annual 300 4 g C m$^{\mathrm{-2}}$ yr$^{\mathrm{-1}}$
\begin{center}
\begin{tabular}{llrl}
Objective Temporal scale Spatial Scale (km) Requirement\\
\hline
Vegetation Weekly (target) 200=E2=80=931000 0.3gC m\^\{-2\} d\^\{=
-1\}\\
Land surface Annual 2000 5/25 g C m\^\{-2\} yr\^\{-1\}\\
Ocean fluxes Annual 2500 3 g C m\^\{-2\} yr\^\{-1\}\\
Anthropogenic Annual 300 4 g C m\^\{-2\} yr\^\{-1\}\\
\end{tabular}
\end{center}
% Generated by Org mode N/A in Emacs 24.1.1.
\end{document}
--
It looks sufficiently different from the previous version to convince
me it is the new exporter being used here but with the same problem.
thanks again
Peter
I get:
--8---cut here---start-8---
% Created 2012-09-07 Fri 00:54
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage[pdfborder={0,0,0},colorlinks=true]{hyperref}
\tolerance=1000
\usepackage{minted}
\author{Nick Dokos}
\date{\today}
\title{superscripts-in-table}
\hypersetup{
pdfkeywords={},
pdfsubject={},
pdfcreator={Generated by Org mode 7.9.1 in Emacs 24.1.50.1.}}
\begin{document}
\maketitle
\section*{section heading}
\label{sec-1}
ObjectiveTemporal scaleSpatial Scale (km) Requirement
+-+--+-+---
Vegetation Weekly (target) 200=E2=80=931000 0.3gC m$^\mathrm{-2}$
d$^\mathrm{-1}$
Land surface Annual 2000 5/25 g C m$^\mathrm{-2}$ yr$^\mathrm{-1}$
Ocean fluxes Annual 2500 3 g C m$^\mathrm{-2}$ yr$^\mathrm{-1}$
Anthropogenic Annual 300 4 g C m$^\mathrm{-2}$ yr$^\mathrm{-1}$
\begin{center}
\begin{tabular}{llrl}
Objective Temporal scale Spatial Scale (km) Requirement\\
\\
\hline
Vegetation Weekly (target) 200=E2=80=931000 0.3gC m$^\mathrm{-2}$
d$^\mathrm{-1}$\\
Land surface Annual 2000 5/25 g C m$^\mathrm{-2}$ yr$^\mathrm{-1}$\\
Ocean fluxes Annual 2500 3 g C m$^\mathrm{-2}$ yr$^\mathrm{-1}$\\
Anthropogenic Annual 300 4 g C m$^\mathrm{-2}$ yr$^\mathrm{-1}$\\
\end{tabular}
\end{center}
% Generated by Org mode 7.9.1 in Emacs 24.1.50.1.
\end{document}
--8---cut here---end---8---
with the versions indicated above. Apart from the mangled Vegatation Spatial
Scale entry (something that some mailer did along the way), everything
else looks good to me.
Nick
