Re: [O] question about ODT export behavior
Am 13.07.2011 22:15, schrieb Jambunathan K: > Jambunathan K writes: > >> Rainer Stengele writes: >> >>> Hi, >>> >>> having this in an org file: >>> -- >>> * Test >>> ** header 2 >>>- item 1 >>> * subitem 11 >>> * subitem 12 >>>- item 2 >>> * subitem 21 >>> * subitem 22 >>> -- >> Could you please post your complete #+OPTIONS line - specifically the >> `H: ' and `toc: ' option? > Looking at the code, I believe these options may not be relevant (for > the odt exporter) > > Your org file doesn't use an explicit line break or timestamps. So the > only scenario under which line breaks can occur is precisely when you > have actually requested them. > > Check this variable or the corresponding OPTIONS directive. > > > ,[ C-h v org-export-preserve-breaks RET ] > | org-export-preserve-breaks is a variable defined in `org-exp.el'. > | Its value is nil > | > | Documentation: > | Non-nil means preserve all line breaks when exporting. > | Normally, in HTML output paragraphs will be reformatted. In ASCII > | export, line breaks will always be preserved, regardless of this variable. > | > | This option can also be set with the +OPTIONS line, e.g. "\n:t". > | > | You can customize this variable. > | > | [back] > ` > > Yes. That was it. After changing org-export-preserve-breaks to nil the breaks are gone. Sorry, I did not know how the exporter works. I did therefore not check the export options. Again, thank you for your excellent work! Bastien, thanks for helping! Can you give me a hint where I can find some documentation about changing the styles.xml? - Rainer
Re: [O] Release 7.6
Hi all, Better late than never: From the joy of Lilypond snippets (thanks, Martyn) in ODT exports (thanks, Jambu), to time arithmetic in tables (thanks, Eric)... 7.6 rocks (thanks Bastien). Yours, Christian On 7/7/11 9:16 AM, Bastien wrote: Dear all, I'm releasing Org 7.6. You can get it from the website as an archive: http://orgmode.org/org-7.6.zip http://orgmode.org/org-7.6.tar.gz Apologies for the delay between 7.5 and 7.6 -- it has been hectic times. I owe a big *thank* to everyone who maintain a high level of activity, both in the code and on the mailing list. In particular: Carsten, Eric Schulte, Nicolas Goaziou, David Maus, Julien Danjou, Jambunathan K, Michael Brand, Achim Gratz, Eric S. Fraga, Nick Dokos, Lawrence Mitchell, Memnon Anon, Bernt Hansen, Sébastien Vauban, Thomas S. Dye, Manuel Giraud, Karl Voit, Huy, ... and many more! Thanks to all. The highlight of this release is the new ODT exporter, which lives in the contrib/ directory but will soon make its way to the core: kudos to Jambunathan for this addition, and thanks to him for his patience. Below is the (incomplete) list of changes: Version 7.6 New features and user-visible improvements === Integration of Jambunathan's OpenDocumentText Exporter ~~~ * Activation Org-mode 7.6 supports exporting to OpenDocument Text (=odt=) format using org-odt.el. Depending on how you installed Org, this module can be enabled in one of the following ways: 1. If you have downloaded the Org from the Web, either as a distribution =.zip= or =.tar.gz= file, or as a Git archive, enable the =odt= option in the variable =org-modules=. 2. If you are using Org-mode 7.6 that comes bundled with Emacs-24.0.50 (or future Emacs-24.1), then you can install the OpenDocumentText exporter using the package manager. Check the list of available packages with =M-x list-packages= and install the =org-odt= package. Thanks a lot to Jambunathan K for this great contribution. * Keybindings The following interactive commands are provided: 1. =C-c C-e o= (=org-export-as-odt=): Export as an =odt= file. 2. =C-c C-e O= (=org-export-as-odt-and-open=): Export as an =odt= file and open the resulting file. See the =contrib/odt/README.org= file for further details; you may check in particular the commands =M-x org-lparse= and =M-x org-export-convert=. Ob-Lilypond -- new Babel language to allow score generation ob-lilypond - an org-babel language, provided to allow LilyPond music score generation, complete with optional auditioning via midi, whilst leveraging the full power of org mode, and literate programming. See [https://github.com/mjago/ob-lilypond] for more documentation. Thanks to Martyn Jago for this addition. Org-Bibtex -- major improvements ~ Provides support for managing bibtex bibliographical references data in headline properties. Each headline corresponds to a single reference and the relevant bibliographic meta-data is stored in headline properties, leaving the body of the headline free to hold notes and comments. Org-bibtex is aware of all standard bibtex reference types and fields. The key new functions are org-bibtex-check: queries the user to flesh out all required (and with prefix argument optional) bibtex fields available for the specific reference =type= of the current headline. org-bibtex-create: Create a new entry at the given level, using org-bibtex-check to flesh out the relevant fields. org-bibtex-yank: Yank a bibtex entry on the kill ring as a formatted Org-mode headline into the current buffer org-bibtex-export-to-kill-ring: Export the current headline to the kill ring as a formatted bibtex entry. Spreadsheet computation of durations and time values ~ If you want to compute time values use the =T= flag, either in Calc formulas or Elisp formulas: Task 1 Task 2 Total ++- 35:0035:00 1:10:00 Values must be of the form =[HH:]MM:SS=, where hours are optional. Thanks to Martin Halder, Eric Schulte and Carsten for code and feedback on this. Links within inlined footnotes. It as also possible to have footnotes side-by-side correctly exported. New variables =org-export-latex-footnote-separator=, =org-export-html-footnote-separator= and =org-export-docbook-footnote-separator= are used to separate them in that case. Fontification of footnotes is also more accurate. New variable =org-export-with-tasks= ~ Non-nil means include TODO items for export. This may have the following values: - tinclude tasks independent of state. - todo
Re: [O] How-to evaluate Java-snippets in org-mode/org-babel?
Hi Eric,
You probably don't want to pass the body of a code block to a lisp
function as quoting will become a nightmare, however passing the name to
a lisp block may be reasonable.
I would suggest that rather than implementing this behavior in a code
block you take a look at starting a ob-java.el file. A partial
implementation (e.g., only external evaluation, no session evaluation)
would be a useful contribution, and given the many helper functions and
examples present in the other ob-* files this would most likely be
easier than a custom lisp-block implementation.
o.k. the first round of evaluations is over and it worked out o.k.
However, there was still rather much handwork to do.
I tried to get a ob-java.el file together using the template and mainly
by looking at ob-c.el which I guess comes close what would have to be
done for java.
However, my lisp-skills (which are close to zero) are not enough to get
it working. The main problem was that ob-c.el is working for both C and
C++ and all this if then else troubles me a bit.
Basically, I want only tangle the actual code block into a temp file.
Well temp is not really right, since java demand its file structure and
file naming. Finally execute it externally by your proposed code
javac -cp . mypackage/myclass.java
java -cp . mypackage.myclass
and return the results
Hmm maybe better to give a real world example (stripped down to make it
shorter)
I use now the following way
/---/
#+BABEL: :mkdirp t
* Coursework 1
** StudentID1
#+BEGIN_SRC java
package foo;
public class Bar
{
private double ans = 0
public void set(double d){
ans = d;
}
public void print(){
System.out.println(ans);
}
public static void main(String[] argv){
Bar c = new Bar();
c.set(100);
c.print();
}
}
#+end_src
** StudentID2
#+BEGIN_SRC java
package foo;
public class Bar
{
private double x = 0
public void set(double in){
x = in;
}
public void print(){
System.out.println(x);
}
public static void main(String[] argv){
Bar myclass = new Bar();
myclass.set(100);
myclass.print();
}
}
#+end_src
** Result
#+srcname: result
#+begin_src sh :results output
javac -cp . foo/Bar.java
java -cp . foo.Bar
#+end_src
//
For now I only added the tangle command to a single code block and
created the file via C-c C-v t.
#+BEGIN_SRC java tangle: foo/Bar.java
Then I rushed down to a shell block "result" which executed the the
above commands. I checked the results and started to remove the tangle
object from one block and added it to the next block. Kind of tiring if
you have several dozen of blocks.
Guess you can see from the above example the trouble of having several
dozen of them and then tangeling them one by one and execute the result
block ;)
I tried to make it more easy by giving the shell block a name and call
it under each java code block. This would save me the time going up and
down in my file.
#+call: result()
However, I noticed that the result update was always done at the first
appearances of the call , like under the first java code block but not
at the desired code block?!
if you fold all together it would look like
/---/
#+BABEL: :mkdirp t
* Coursework 1
** StudentID1
#+BEGIN_SRC java
#+call: result()
#+results: result
: 100.0
** StudentID2
#+BEGIN_SRC java :tangle foo/Bar.java
#+call: result()
** Result
#+srcname: result
/---/
Calling the second call function updates the result on the first!
Anyhow, I guess having it working with a ob-java.el minimal system would
be the most easiest. Simply type C-c C-c and it would be done.
Would be very glad if you could help me to get this somehow working.
Totti
Re: [O] OLUG talk about Org-mode
Hi Sebastien, > I've uploaded it on my Web site: > http://www.mygooglest.com/sva/OLUG_Meeting_July_2011.flv > Please download it, as this link may become unavailable in the future. Thanks! Got it, its working. And while I am at it, thank you very much for making your .emacs available there and keeping it very well documented. It prompted a reorganization of mine and me making it available, too. Memnon
Re: [O] OLUG talk about Org-mode
Hi Jonathan, Jonathan Leech-Pepin writes: > The direct link to the video on the UStream site is: > http://ustream.vo.llnwd.net/pd15/0/1/15/15820/15820239/1_365053_15820239.flv If I understood Pieter Praet correctly, this did not work for him: ,[ Message ID: <878vsa2msg@praet.org>] | I've tried the obvious one [1] but no joy. It's a waste of 225,6 MiB. | ... | [1] http://ustream.vo.llnwd.net/pd15/0/1/15/15820/15820239/1_365053_15820239.mp4 `[Archived-At: http://permalink.gmane.org/gmane.emacs.orgmode/43844] This did work for me: ,[ Sebastien Vauban: Message-ID: <804o2qtvbd@somewhere.org> ] | http://www.mygooglest.com/sva/OLUG_Meeting_July_2011.flv | Please download it, as this link may become unavailable in the future. `[Archived-At: http://permalink.gmane.org/gmane.emacs.orgmode/44175] Memnon
[O] babel work flow
Aloha all, I want to use one of the dot utilities, tred, in a way that preserves my ability to distribute the Org-mode file as reproducible research, i.e., intermediate results should end up in the Org-mode file or be passed along in a chain. Right now I have a python routine that reads a couple of Org-mode tables and outputs a valid dot graph. I'm saving this to a file, dot-temp.gv, and then running some shell commands, like this: #+begin_src sh tred dot-temp.gv > test.gv dot -o test.pdf -Tpdf test.gv open test.pdf #+end_src The graph is just what I want, but I can't see how to automate the process in Org-mode. In particular, the tred step trips me up. Do I have to make babel, tred-aware? Tom -- T.S. Dye & Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
[O] [babel] Problem with tangling and newlines
Hi,
Tangling this:
#+begin_src sh :tangle my-csv2ledger-wrapper.sh :noweb yes
#!/bin/bash
# my-csv2ledger-wrapper.sh -- Convert CSV files to Ledger data
<> |\
<> |\
<>
exit 0
#+end_src
now gives:
--8<---cut here---start->8---
#!/bin/bash
# my-csv2ledger-wrapper.sh -- Convert CSV files to Ledger data
cat
|\
sed -r 's/^([[:digit:]]{2})\/([[:digit:]]{2})\/([[:digit:]]{2})/\2\/\1\/20\3/g'
|\
sed -r 's/^([[:digit:]]{2})-([[:digit:]]{2})-([[:digit:]]{4})/\2\/\1\/\3/g'
|\
sed -r 's/([[:digit:]])\.([[:digit:]]{3})/\1\2/g' |\
sed -r 's/([[:digit:]]),([[:digit:]]{2})/\1.\2/g' |\
sed -r 's/,/./g' |\
sed -r 's/;/,/g'
exit 0
--8<---cut here---end--->8---
which is not executable anymore because the pipe is not ending the line of
commands.
This is quite recent (v7.6?).
Best regards,
Seb
--
Sebastien Vauban
[O] Tbl: addition of two times results in error
,[ http://orgmode.org/org.html#Durations-and-time-values ] | | Task 1 | Task 2 | Total | | |++-| | | 35:00 | 35:00 | 1:10:00 | | #+TBLFM: @2$3=$1+$2;T ` ... results in #ERROR at @2$3 on my system with current Org-mode (I did «git pull» right now): ,[ debug message ] | Substitution history of formula | Orig: $1+$2;T | $xyz-> $1+$2 | @r$c-> $1+$2 | $1->(35:00)+(35:00) |--^ | Error: Bad format ` Where is the problem? -- Karl Voit
Re: [O] question about ODT export behavior
Bastien writes: > I cannot reproduce your error. Same here. Some custom setting (global or per-file) is kicking in Rainer's setup. It is more likely to be org-export-preserve-breaks. Jambunathan K. --
Re: [O] question about ODT export behavior
Jambunathan K writes: > Rainer Stengele writes: > >> Hi, >> >> having this in an org file: >> -- >> * Test >> ** header 2 >>- item 1 >> * subitem 11 >> * subitem 12 >>- item 2 >> * subitem 21 >> * subitem 22 >> -- > > Could you please post your complete #+OPTIONS line - specifically the > `H: ' and `toc: ' option? Looking at the code, I believe these options may not be relevant (for the odt exporter) Your org file doesn't use an explicit line break or timestamps. So the only scenario under which line breaks can occur is precisely when you have actually requested them. Check this variable or the corresponding OPTIONS directive. ,[ C-h v org-export-preserve-breaks RET ] | org-export-preserve-breaks is a variable defined in `org-exp.el'. | Its value is nil | | Documentation: | Non-nil means preserve all line breaks when exporting. | Normally, in HTML output paragraphs will be reformatted. In ASCII | export, line breaks will always be preserved, regardless of this variable. | | This option can also be set with the +OPTIONS line, e.g. "\n:t". | | You can customize this variable. | | [back] ` > How exactly are you exporting - Are you exporting the file, a subtree, > region etc etc? > > What interactive command are you using for export? > >> and exporting to ODT I get (I simply copied the Org doc contents via >> clipboard) I get this: >> >> -- >> Test >> Table of Contents >> 1. header 2 >> 1. header 2 >> item 1 >> >> subitem 11 >> >> subitem 12 >> >> item 2 >> >> subitem 21 >> >> subitem 22 >> -- >> >> Why do I get extra lines between the items and subitems? > > This is beacause there is an explicit line break at the end of the list > items. > > If you open content.xml and remove the and save the > buffer, does the altered odt file match your expectations. > > If you export the above outline with the same settings, does the HTML > exporter also introduce at the end of the list items? IIRC, the (x)html exporter adds a line break after emitting an headline which is listified. > odt exporter is a derived from the html exporter and mimics the HTML > exporter mindlessly. I believe the line breaks can be removed. The odt exporter doesn't emit the line break like the xhtml exporter. (May be I was a bit mindful while typing out org-odt.el) So the options H, toc etc may not be relevant. > > Once I get the relevant details from you I can post a patch after a > closer look. > >> Where or how can I adjust the behaviour of the exporter? >> >> I'll attach the org file. >> >> - Rainer >> --
Re: [O] Calendar-like view of the org-agenda
"Sebastien Vauban" writes: Hi Sebastien, > - I was hoping `r' to redraw the grid, after I've changed Emacs frame size. It > does not seem to be the case. Could that be foreseen? I've seen you already > all the available space, when drawing the grid for the first time. I've implemented that in my fork. http://github.com/tsdh/emacs-calfw Masashi, feel free to pull if you think it's ok. Bye, Tassilo
[O] org-bibtex
Aloha Eric,
I ran into an odd problem exporting org-bibtex references. It turned
out that I had inadvertently added a space, ":TYPE: book " The space is
invisible in the Org-mode buffer, but it leads to an export like this:
@book {kirch10:_how_chief_becam_kings,
}
Note the lack of contents except for the bibkey and the space between
@book and the opening curly brace.
Would it be possible to trim this field for the pleasure of clumsy
typists like me?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Re: [O] OLUG talk about Org-mode
Hi Memnon, Memnon Anon wrote: >> Can someone provide a working download link ? > > Can someone provide a working video? ;) The direct link to the video on the UStream site is: http://ustream.vo.llnwd.net/pd15/0/1/15/15820/15820239/1_365053_15820239.flv Even if it doesn't load the video (simply a white box) you should still be able to Save As... and watch it offline. Regards, Jonathan
Re: [O] ThoughtBack
On Wed, Jul 13, 2011 at 11:11 AM, Bastien wrote: > Hi Brian, > > brian powell writes: > >> https://thoughtback.com >> >> Any thoughts? > > Well, I don't give my email to services that don't even > try to give a detailed idea of the service they provide. > > Or did I miss something? Don't think so. Googling produces little, either. I did find a link to it on AlternativeTo.net, which lists EverNote as an alternative and has this caption: ,- | The private, unfiltered, personally meaningful micro-journal that sends | your thoughts back to you in unexpected ways. Try it - the effect is poignant. | "Basically, it's a lightweight, more proactive version of evernote. `- So... looks like notes + some other feature set that's unexplained? John > > -- > Bastien > >
Re: [O] [babel] Piping from sh code to shell?
On Wed, Jul 13, 2011 at 7:43 PM, Eric Schulte wrote: > Hi Rainer, > > Hi Eric, > I am not entirely sure what you are asking, but there is currently no > support for piping portions of code blocks to a shell. That is exactly what I am asking - thanks for decrypting my email. > sh code blocks > do however support session evaluation, which could be similar. > True - I haven't thought about that. Thanks, Rainer > > Best -- Eric > > Rainer M Krug writes: > > > Hi > > > > this is not strictly an org-babel question - but here is it anyway. > > > > If I have an sh code block as follow > > > > #+begin_src sh > > TXT="Hello World" > > echo $TXT > > #+end_src > > > > and enter it with C-c ' --- is there a way of piping single lines, > regions, > > the whole block to a shell, similar to the functionality provided by ESS > and > > R? > > > > Thanks, > > > > Rainer > > -- > Eric Schulte > http://cs.unm.edu/~eschulte/ > -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax (F): +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug
Re: [O] org-mode fontification error when exporting to LaTeX
Bastien altern.org> writes: > Yes -- also please give more details about your setup: what version > of Org and Emacs? What system? I tracked it down to the following in my text; - list item - list item - list item - Note :: Blah - list item - Note :: Blah - list item The error goes away when I correct this to the following; - list item - list item - list item - Note :: Blah - list item - Note :: Blah - list item Thanks folks. -Luke
Re: [O] [PATCH] Adding support for :results output for clojure src blocks.
Yes, please do consider signing the FSF papers to enable this and future contributions to be included into Org-mode. However, in this particular case, you could easily sneak your patch into under 10 lines by replacing the `cond' with a nested `if', and I would be happy to include such a patch immediately. Also, for patches directed at ob-* files, if you don't mind building the patch with "git format-patch" I would prefer that format -- although I'll happily take patches in any format. Thanks for contributing! -- Eric Bastien writes: > Hi Robert, > > Robert McIntyre writes: > >> This small patch handles :results output for clojure src blocks by >> using clojure's with-out-str function. > > I let Eric Schulte apply (or not) your patch. > >> Please let me know if I've done anything wrong as this is my first >> patch to org-mode. > > It is more than 10 lines long, so for the patch to be applied we would > need you to sign FSF papers. I will send them to you privately. > > Thanks! -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] Compile warnings on Win7/Emacs24.0.50
I've tested some things on Win7 and happen to have an Emacs24 installed there, so I compiled the latest org-mode. I got quite a few warnings that I've never seen before with Emacs23, so I assume this is Emacs24 tightening the screws on some loseness. I don't remember the exact warning text, but it was something about top-level forms and global variables not having a prefix (presumably to keep them in their own namespace and not step on the toes of other packages). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [O] question about ODT export behavior
I cannot reproduce your error. Check the test_bastien.org file I get by exporting your test.org, there is no extra line. test_bastien.odt Description: application/vnd.oasis.opendocument.text -- Bastien
Re: [O] question about ODT export behavior
Rainer Stengele writes: > Hi, > > having this in an org file: > -- > * Test > ** header 2 >- item 1 > * subitem 11 > * subitem 12 >- item 2 > * subitem 21 > * subitem 22 > -- Could you please post your complete #+OPTIONS line - specifically the `H: ' and `toc: ' option? How exactly are you exporting - Are you exporting the file, a subtree, region etc etc? What interactive command are you using for export? > and exporting to ODT I get (I simply copied the Org doc contents via > clipboard) I get this: > > -- > Test > Table of Contents > 1. header 2 > 1. header 2 > item 1 > > subitem 11 > > subitem 12 > > item 2 > > subitem 21 > > subitem 22 > -- > > Why do I get extra lines between the items and subitems? This is beacause there is an explicit line break at the end of the list items. If you open content.xml and remove the and save the buffer, does the altered odt file match your expectations. If you export the above outline with the same settings, does the HTML exporter also introduce at the end of the list items? odt exporter is a derived from the html exporter and mimics the HTML exporter mindlessly. I believe the line breaks can be removed. Once I get the relevant details from you I can post a patch after a closer look. > Where or how can I adjust the behaviour of the exporter? > > I'll attach the org file. > > - Rainer > --
Re: [O] ThoughtBack
Hi Brian, brian powell writes: > https://thoughtback.com > > Any thoughts? Well, I don't give my email to services that don't even try to give a detailed idea of the service they provide. Or did I miss something? -- Bastien
Re: [O] org-babel: session support for node.js
Hi Marcus, There is no technical reason why sessions are not supported for node.js. At the time ob-js.el was written node was still fairly young, and there was no real Emacs support for node.js sessions. Patches Welcome! Thanks -- Eric Marcus Klemm writes: > Hello List, > > Org-babel supports Javascript through node.js but does > not support session evaluation. I wonder if there is a > technical reason or if simply nobody implemented it > (yet). > > Ciao, Marcus > > -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel] Piping from sh code to shell?
Hi Rainer, I am not entirely sure what you are asking, but there is currently no support for piping portions of code blocks to a shell. sh code blocks do however support session evaluation, which could be similar. Best -- Eric Rainer M Krug writes: > Hi > > this is not strictly an org-babel question - but here is it anyway. > > If I have an sh code block as follow > > #+begin_src sh > TXT="Hello World" > echo $TXT > #+end_src > > and enter it with C-c ' --- is there a way of piping single lines, regions, > the whole block to a shell, similar to the functionality provided by ESS and > R? > > Thanks, > > Rainer -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Again problems with latex inside footnotes.
Hi Bastien, I have enough interest in using org-mode to produce latex texts to get involved. I can't do it right now cause I'm in a critical time to produce results for my thesis, but I've been delaying learning e-lisp and taking a good look on org-mode for some time. Nick Dokos above said that org-mode uses a huge regexp to parse the latex. When this pressing phase pass I'll certainly take a look on that. I played a bit (only a bit) with funcional parsers in Haskell (monadic parsers and parsers based on arrows) and, in my experience, they are much, much more easy to write and more powerful than regexp's (they can parse html! :D). Well, lisp is functional... Maybe I'll take a look at this in the near future. --- Rafael Calsaverini Dep. de Física Geral, Sala 336 Instituto de Física - Universidade de São Paulo rafael.calsaver...@gmail.com http://stoa.usp.br/calsaverini/weblog CEL: (11) 7525-6222 USP: (11) 3091-6803 On Wed, Jul 13, 2011 at 05:40, Bastien wrote: > Hi Rafael, > > Nick Dokos writes: > > > Although patches have been applied to deal with a host of > > such problems, it is a long-standing problem that is unlikely to be > > completely solved - ever[fn:1]. > > Yes, we need to rework the way the exporters handle espace chars, > especially the LaTeX one --- it's not only ugly and buggy. > > Don't hold your breath though, I won't be on this before 7.7. > > Thanks for your understanding, > > -- > Bastien >
Re: [O] [PATCH] was: patch makefile solve a couple debian build problems and a slackware build problem
Nick Dokos writes: >> +and it's derivatives use two different versions of install-info and you may > >its Thanks for catching that. My patch also did not remove the documentation of the removed target in the help/targets section of the Makefile. I'm attaching a patch to correct that. >From 5372528a02d29ef92487d2a9cf46663804f8c9e2 Mon Sep 17 00:00:00 2001 From: Achim Gratz Date: Wed, 13 Jul 2011 17:26:45 +0200 Subject: [PATCH] remove documentation for removed make target install-info-debian * Makefile: also remove the documentation explaining the use of target install-info-debian, which was removed previously TINYCHANGE --- Makefile |1 - 1 files changed, 0 insertions(+), 1 deletions(-) diff --git a/Makefile b/Makefile index eb2597f..10093ed 100644 --- a/Makefile +++ b/Makefile @@ -527,4 +527,3 @@ targets help: @echo "make install - install Org" @echo "make install-lisp - install Org ELisp files" @echo "make install-info - install Org Info file" - @echo "make install-info-debian - install info on old debian systems (newer use ginstall)" -- 1.7.6 Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] question about ODT export behavior
Am 13.07.2011 16:23, schrieb Bastien: > Rainer Stengele writes: > >> I'll attach the org file. > > You forgot the org file, you just attached the odt file. > > I don't know when Jambunathan can have a loot at this, but please > bare in mind that such formatting issues are relatively hard to fix > (talking from experience). > > Thanks, > Org file is attached. I think this is the most simple org file - nothing special - and the odt file just extends some extra lines, so I thought this to be a fundamental issue. I would like to be able to export the minutes of a meeting but cannot as my colleagues will wonder why I put all these extra lines in ... Thanks, Rainer * Test ** header 2 - item 1 * subitem 11 * subitem 12 - item 2 * subitem 21 * subitem 22
Re: [O] Makefile restructuring
Bastien writes: > Okay - I'll follow that branch till the change becomes mature. I've set up the feature branch "Makefile" in my org-mode clone on repo.or.cz. Assuming you already have orgmode.git cloned (it does not really matter where from), do a git remote add -t Makefile remote-tableheadings git://repo.or.cz/org-mode/org-tableheadings.git git fetch remote-tableheadings Makefile:local-Makefile git checkout local-Makefile to get it (change remote-tableheadings and local-Makefile to suit your naming conventions for remotes and local branches, respectively). I will be _rebasing_ against master during development, so expect history in this branch to be volatile. As always, testers and their comments are welcome. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
[O] ThoughtBack
https://thoughtback.com Any thoughts? Useful to OrgMode users? (MindMapping and remember.el (or whatever) are often linked to GTD/OrgMode activities--by some users) I'm in no way connected to https://thoughtback.com--nor do I know much about it at all.
Re: [O] Problems with executing babel code
Hi Christopher, Christopher Witte writes: > After a recent git pull, I've been having some problems executing and > editing babel code. Confirmed. The problem was introduced by this commit: http://orgmode.org/w/?p=org-mode.git;a=commit;h=1b95d2e9ce50db56435a1912c37c436388e703af I let Eric fix this... Thanks for the report! -- Bastien
Re: [O] question about ODT export behavior
Rainer Stengele writes: > I'll attach the org file. You forgot the org file, you just attached the odt file. I don't know when Jambunathan can have a loot at this, but please bare in mind that such formatting issues are relatively hard to fix (talking from experience). Thanks, -- Bastien
Re: [O] Using org-mode for Research and Notetaking
Hello, Bastien writes: > I'm talking about the way they _look_. So many asterisks looks > cumbersome to mee, and I'd favor a non-intrusive syntax like the > one proposed above. > > My question was: what is the rationale behind using so many asterisks? > > I can think of three things: > > 1. people want inline tasks with possibly no TODO keyword > 2. people prefer to detect them *very easily* > 3. changing the syntax of inline tasks from changing todos >(like !TODO) is too complicated code-wise 4. people do not want to break the main flow of text. By default, the text in the inline task starts at the 15th column. > My proposal is this: > > - enforce the use of TODO keywords in inline tasks (wrt 1) I think it is an unnecessary restriction. I remember some people use inline tasks without even a title (they only write the stars). IMO, inline tasks are used in two distinct fashions. Obviously, one is to use them as tasks. The other one is to use them as marginal notes, like drawers with a title. Let's not forget that second category, unless we provide an alternative solution for them, i.e. an annotation system. > - make a special face for inline tasks (wrt 2) I think it is a good idea. >> Your proposition would be (very) nice when we don't have to link a >> note to the task. > > My change would affect the content you can add to inline tasks and > the way they are treated by exporters. For the record, there is also a degenerated version of inline tasks in which "*** END" is optional. Those cannot hold any contents, though. Regards, -- Nicolas Goaziou
[O] org-babel: session support for node.js
Hello List, Org-babel supports Javascript through node.js but does not support session evaluation. I wonder if there is a technical reason or if simply nobody implemented it (yet). Ciao, Marcus
[O] question about ODT export behavior
Hi, having this in an org file: -- * Test ** header 2 - item 1 * subitem 11 * subitem 12 - item 2 * subitem 21 * subitem 22 -- and exporting to ODT I get (I simply copied the Org doc contents via clipboard) I get this: -- Test Table of Contents 1. header 2 1. header 2 item 1 subitem 11 subitem 12 item 2 subitem 21 subitem 22 -- Why do I get extra lines between the items and subitems? Where or how can I adjust the behaviour of the exporter? I'll attach the org file. - Rainer test.odt Description: application/vnd.oasis.opendocument.text
Re: [O] Calendar-like view of the org-agenda
On Wed, 13 Jul 2011 11:34:48 +0530, Aankhen wrote: That's odd. I'm using Emacs 24 on Windows 7 64-bit (and before this I've used 23 on both 7 and Vista), and my font is set to Consolas. Emacs happily substitutes other fonts where Consolas is missing glyphs (see the attached screenshot). The only snag is that it takes a while to find a suitable font, at times. I'm using a precompiled binary from emacs-for-windows.[1] Perhaps it has special support for font substitution or something… Huh. I looked at the HELLO file, and you seem to be right. It's pulling in fonts as needed for various South Asian, East Asian, and Middle/Near Eastern languages, but still failing horribly with unicode box drawing, as well as various symbols (like the recycle symbol, which we use abundantly on identi.ca). Perhaps Consolas falsely reports that it has those symbols.
Re: [O] Using org-mode for Research and Notetaking
Hi Bastien, Bastien wrote: > "Sebastien Vauban" writes: >>> * !TODO This would be an inline task, not a headline >> >> I've no clear cut opinion on this right now. Maybe yes, maybe not. > > :) > >> Though, there are differences between inline tasks and headlines: > > Yep, I know the differences. Not intended to you in particular, just to put context around my answer! > I'm talking about the way they _look_. So many asterisks looks > cumbersome to mee, and I'd favor a non-intrusive syntax like the > one proposed above. > > My question was: what is the rationale behind using so many asterisks? That's right there are a lot of them... > I can think of three things: > > 1. people want inline tasks with possibly no TODO keyword Of course, this is needed as well. Or maybe this is a wrong use of them: to make things outstand as notes in the produced PDF (with todonotes package, in my case, for the inline "tasks" -- or "notes" then). > 2. people prefer to detect them *very easily* Yes, for sure. > 3. changing the syntax of inline tasks from changing todos >(like !TODO) is too complicated code-wise Dunno. > My proposal is this: > > - enforce the use of TODO keywords in inline tasks (wrt 1) I'm divided about this, as you can see. Maybe, though, I have to respect the fact that inline tasks are supposed to be _tasks_ which are inlined. > - make a special face for inline tasks (wrt 2) You see we're not far from it, and what I typically use inline tasks for... http://i.imgur.com/rrI6Q.png >> Your proposition would be (very) nice when we don't have to link a >> note to the task. > > My change would affect the content you can add to inline tasks and > the way they are treated by exporters. > >> All such questions certainly merit more attention. > > Sure -- thanks for your input! To be continued... Best regards, Seb -- Sebastien Vauban
[O] Problems with executing babel code
After a recent git pull, I've been having some problems executing and editing babel code. The following will execute: #+srcname: Blah1 #+begin_src emacs-lisp :results value (concat "" "works") #+end_src #+results: Blah1 : works #+call: Blah1(x=1) :results value raw #+results: Blah1(x=1) works #+srcname: Blah4(x) #+begin_src emacs-lisp (concat "" "works") #+end_src #+results: : works #+call: Blah4(x=1) :results value raw #+results: Blah4(x=1) works but this #+srcname: Blah2(x) #+begin_src emacs-lisp :results value (concat "doesn't" "work") #+end_src #+call: Blah2(x=1) :results value raw fails with the error message "setf: Wrong type argument: consp, nil", when it had previously worked. nb. the only difference between Blah4 and Blah2, is the white space between the srcname and begin_src. I get the same error when I try and edit the code with C-'. I'm not sure exactly when this started, this was probably the first git pull I have done in a month or so. Sorry I can't help track down this problem further, my lisp skills are slim to none. Cheers, Chris.
Re: [O] Calendar-like view of the org-agenda
Hi Achim, Achim Gratz wrote: > "Sebastien Vauban" writes: >> Look at the results under Windows (in 8 pt): > > You may be interested in this: > http://cygutils.fruitbat.org/mintty-font-test/ What your article showed to me is that the version of the Consolas font is important. I had version 1.0, and installed 5.22 (the best coverage, from the article author). Here is the new look of the calendar under Consolas 8pt: http://i.imgur.com/M3mUv.png. Better, not perfect yet... Thanks for your pointer. Best regards, Seb -- Sebastien Vauban
Re: [O] Using MobileOrg without sync?
On 12 Jul 2011, at 22:12, Steinar Bang wrote: I installed MobileOrg on an HTC desire. The idea was to just use it to take notes, no sync to an emacs with org-mode would be needed. What's the point of MobileOrg then? There are dozens of note-taking apps for Android that do a better job than MobileOrg for note taking. Personally I use Epistle, which syncs with Dropbox, yielding plain- text files on my desktop that I can access from Emacs. Konrad.
Re: [O] How to 'undo' filter
> Hi Jim, > > j...@sdf-eu.org writes: > >> Hi Noorul, I'm talking about constructing a sparse tree, e.g. by a >> property or tag. Sorry if I used the wrong term. Something like >> >> C-c / p MYPROP MYVAL >> >> Then, after looking at the filtered document, go back to previous >> visibility. > > You cannot. Storing and retrieving the folded state of a document is a > longstanding wish... and issue. I believe there are a few hacks though > on Worg and elsewhere. Thanks for the clarification Bastien. Jim > > What you can do is C-c C-c on setup lines to remove overlays from > the buffer. > > Sorry that I cannot help further, > > -- > Bastien >
Re: [O] Using org-mode for Research and Notetaking
Hi Sébastien, "Sebastien Vauban" writes: >> * !TODO This would be an inline task, not a headline > > I've no clear cut opinion on this right now. Maybe yes, maybe not. :) > Though, there are differences between inline tasks and headlines: Yep, I know the differences. I'm talking about the way they _look_. So many asterisks looks cumbersome to mee, and I'd favor a non-intrusive syntax like the one proposed above. My question was: what is the rationale behind using so many asterisks? I can think of three things: 1. people want inline tasks with possibly no TODO keyword 2. people prefer to detect them *very easily* 3. changing the syntax of inline tasks from changing todos (like !TODO) is too complicated code-wise My proposal is this: - enforce the use of TODO keywords in inline tasks (wrt 1) - make a special face for inline tasks (wrt 2) > Your proposition would be (very) nice when we don't have to link a > note to the task. My change would affect the content you can add to inline tasks and the way they are treated by exporters. > All such questions certainly merit more attention. Sure -- thanks for your input! -- Bastien
Re: [O] Python script to download Google Calendar events
Felix Geller writes: > no, not at all :) Okay, done. Thanks a lot! -- Bastien
[O] [babel] Piping from sh code to shell?
Hi this is not strictly an org-babel question - but here is it anyway. If I have an sh code block as follow #+begin_src sh TXT="Hello World" echo $TXT #+end_src and enter it with C-c ' --- is there a way of piping single lines, regions, the whole block to a shell, similar to the functionality provided by ESS and R? Thanks, Rainer -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax (F): +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug
Re: [O] How to 'undo' filter
Hi Jim, j...@sdf-eu.org writes: > Hi Noorul, I'm talking about constructing a sparse tree, e.g. by a > property or tag. Sorry if I used the wrong term. Something like > > C-c / p MYPROP MYVAL > > Then, after looking at the filtered document, go back to previous > visibility. You cannot. Storing and retrieving the folded state of a document is a longstanding wish... and issue. I believe there are a few hacks though on Worg and elsewhere. What you can do is C-c C-c on setup lines to remove overlays from the buffer. Sorry that I cannot help further, -- Bastien
Re: [O] Python script to download Google Calendar events
Hi Bastien, On Wed, 13 Jul 2011 10:38:22 +0200, Bastien wrote: > This looks nice. I've not tested it yet, I'm busy with the release. > > Would you have any objection if I put this in this section of Worg: > > http://orgmode.org/worg/org-translators.html > > ? no, not at all :) Cheers, Felix > > > Thanks! > > -- > Bastien pgpV5itQIFZyl.pgp Description: PGP signature
Re: [O] How to 'undo' filter
> On Wed, Jul 13, 2011 at 3:31 AM, Jim Burton wrote: >> Hi, after filtering an org document, I'd like to be able to go back to >> the previous visibility. The closest I can get at the moment is to make >> everything visible with S-TAB, but I'd like whatever was >> expanded/collapsed before the filter to be as it was. How is this done? >> > > Which filtering are you talking about? > > agenda? > narrow-to-block? > narrow-to-subtree? > Hi Noorul, I'm talking about constructing a sparse tree, e.g. by a property or tag. Sorry if I used the wrong term. Something like C-c / p MYPROP MYVAL Then, after looking at the filtered document, go back to previous visibility. Thanks, Jim > Thanks and Regards > Noorul >
Re: [O] Using org-mode for Research and Notetaking
Hi Bastien, Bastien wrote: > As suggested, you want to check inline tasks. > > I really don't like the current syntax for inline tasks, I would much > prefer something like special TODO keywords: > > * !TODO This would be an inline task, not a headline I've no clear cut opinion on this right now. Maybe yes, maybe not. > But perhaps I'm missing something about why the current inline task > syntax is useful. I'd be interested in hearing more by people who are > actually using them... > > Thanks for your input! Though, there are differences between inline tasks and headlines: - inline tasks are delimited with an ** END marker (many asterisks) - hence, they can contain a lot of things inside them: + paragraphs + lists + etc. I am sure they could somehow be improved, but I already use them a lot for the big advantage they offer: being tasks, and not breaking the document structure (not adding levels in your document). Your proposition would be (very) nice when we don't have to link a note to the task. Does that mean it should be added? Does that mean that, then, the notes could or should be made available thru drawers? All such questions certainly merit more attention. Best regards, Seb -- Sebastien Vauban
Re: [O] Using MobileOrg without sync?
> Tassilo Horn :
> Not sure, but MobileOrg (at least on Android) is not very
> sophisticated for note taking. For sure, it's not a stand-alone
> org-mode for Android as you might have expected.
Ah, ok. It looked like it might be, from the screen shots.
> For example, there's no widget ("activity" in andro-speak) to input
> timestamps and stuff like that. I use it, but mainly for viewing my
> agendas pushed from org-mode and for capturing quick and ugly notes,
> which I format correctly, timestamp, tag, and refile after pulling
> them to my emacs.
Ok. Looks like something I will try at some point in time, but not
right now.
> So I see no reason to use MobileOrg if you don't want to interact with
> org-mode. Probably, you'd be better off with a plain text editor (Jota
> Text Editor is quite good and free software).
Thanks for the tip!
So far, I have installed, but not yet tried:
Evernote
http://gizmodo.com/5427595/evernote-the-android-note-app-you-need-is-here
AK Notepad
https://market.android.com/details?id=com.akproduction.notepad
GDocs (notepad synking with google docs)
http://sites.google.com/site/gdocsforandroid/
Re: [O] [PATCH] Adding support for :results output for clojure src blocks.
Hi Robert, Robert McIntyre writes: > This small patch handles :results output for clojure src blocks by > using clojure's with-out-str function. I let Eric Schulte apply (or not) your patch. > Please let me know if I've done anything wrong as this is my first > patch to org-mode. It is more than 10 lines long, so for the patch to be applied we would need you to sign FSF papers. I will send them to you privately. Thanks! -- Bastien
Re: [O] OLUG talk about Org-mode
Hi Memnon, Memnon Anon wrote: >> Can someone provide a working download link ? > > Can someone provide a working video? ;) I've uploaded it on my Web site: http://www.mygooglest.com/sva/OLUG_Meeting_July_2011.flv Please download it, as this link may become unavailable in the future. Best regards, Seb -- Sebastien Vauban
Re: [O] OLUG talk about Org-mode
Hi Memnon, Memnon Anon writes: > :(, my firefox only shows a white box. Surely a problem with the flash/gnash plugin. > Do I have to sign up and login to view it? Nope. >> Can someone provide a working download link ? > > Can someone provide a working video? ;) Yes, that'd be nice! -- Bastien
Re: [O] Using org-mode for Research and Notetaking
Hi Florian, Florian Beck writes: > A couple of questions and observations, first impressions really: > > 2. Tags are SLOW (no doubt due to my 8.5M file). Completion takes > minutes. I fixed that by adding all my (hundreds of) tags to > `org-tag-alist' and restricting capture to »%g«, checking only the > current file. `org-id-find' is slow as well and so will be property > completions, I guess. How about caching the data and update on saving > an org-agenda file? We might consider this. I doubt updating on saving is the right thing to do -- people tend to save very often, and for solving problems like yours, it will be as slow as the current interface. We need to be more clever in defining the update cycle for caches, and this depends on _what_ the cache is containing. > 3. By default, tags cannot contain spaces or commas. I rectified that > with an ugly hack in `org-set-tags-to', which replaces spaces with > ?\x2008 (punctuation space), and setting it to word syntax. Also, many > long tags display ugly. How about showing only the first twenty > characters and show the rest via help echo? You will need to live with it for now. > 4. muse-mode has this nice feature that it easily allows you to define > your own like > … or > …; not only for export but also for > fontification. Can I do something similar in org-mode? What do you mean? What I can think of are "tag aliases": for example, the tag ":code:" would be an alias for ":code python lisp:". The buffer would display the alias. Tag search would match the expanded version. This adds a semantic layer for tags, so maybe there are complexities I cannot think of right now, but I think it might be interesting. What do you think? > 5. According to the manual »TODO items are an integral part of the > notes file«. I like that, but I do not find it so. TODO items are > headings which I find somewhat confusing: My files are either articles > to be (with the appropriate headlines) or notes where headlines usually > formulate the topic the note is about. Todo items, on the other hand, > would be »clarify the paragraph«, »check what X says about Y«, »add > more sources«, etc. As it is TODOs are not integrated but stand out, > breaking the structure of the file. How about allowing TODO items in > comments? This would seem much more natural to me: a TODO item should > not be part of your text but disappear when it is done. As suggested, you want to check inline tasks. I really don't like the current syntax for inline tasks, I would much prefer something like special TODO keywords: * !TODO This would be an inline task, not a headline But perhaps I'm missing something about why the current inline task syntax is useful. I'd be interested in hearing more by people who are actually using them... Thanks for your input! -- Bastien
Re: [O] Again problems with latex inside footnotes.
Hi Rafael, Nick Dokos writes: > Although patches have been applied to deal with a host of > such problems, it is a long-standing problem that is unlikely to be > completely solved - ever[fn:1]. Yes, we need to rework the way the exporters handle espace chars, especially the LaTeX one --- it's not only ugly and buggy. Don't hold your breath though, I won't be on this before 7.7. Thanks for your understanding, -- Bastien
Re: [O] Python script to download Google Calendar events
Hi Felix, Felix Geller writes: > I wrote a Python script that [1] uses the GData API to download events > for your Google Calendar and prints them to a given org-file. It is a > very tiny script, but perhaps it is of use to other people as well. > > Small disclaimer: I've tested this on Mac OS X only, using Python > 2.7.2. This looks nice. I've not tested it yet, I'm busy with the release. Would you have any objection if I put this in this section of Worg: http://orgmode.org/worg/org-translators.html ? Thanks! -- Bastien
Re: [O] Default indent level
Hi Mike, Mike Owens writes: > I've googled and scoured the list and can't seem to find a way to get > indent level to work like I want. I simply want M-LEFT to indent 3 > spaces rather than 2 by default. I set > org-indent-indentation-per-level to 3 in my .emacs file, but this > still does not seem to work. Any help would be greatly appreciated. You need to do M-x org-indent-mode RET in the file you need this special indentation feature. HTH, -- Bastien
Re: [O] org-mode fontification error when exporting to LaTeX
Hi Luke, "David O'Toole" writes: > try doing (setq debug-on-error t) and then re-export; this should give > you a backtrace. > > but sometimes fontification stuff can have errors without backtraces. > try checking the *Messages* buffer. misbehaving font-lock rules and > improperly defined faces can also be issues. Yes -- also please give more details about your setup: what version of Org and Emacs? What system? Thanks! -- Bastien
[O] Inconsistent behaviour when #+setupfile is used recursively
Hi, we use Org-mode for software documentation and have come across the following behaviour with version 7.6 (release_7.6.71.g22fa9): our documentation is located in the directory doc/usage, e.g. doc/usage/index.org or doc/usage/tutorial.org, whereas Org-Mode's setupfiles are stored in doc/common/org, e.g. doc/common/org/setup-toc-large or doc/common/org/setup-common. When we include a setupfile from doc/usage/index.org using #+setupfile: ../common/org/setup-toc-large everything works fine. The path of the setupfile is relative to the path of index.org. However, when setup-toc-large itself includes another setupfile with setup-common using a relative path, the path is still treated as relative to index.org, not relative to setup-toc-large. Therefore, when using the line #+setupfile: setup-common within setup-toc-large, Org-Mode fails to find setup-common. When changing the above line to #+setupfile: ../common/org/setup-common the documentation builds successfully. We would expect Org-mode to search for an include file relative to the file that contains the setupfile-statement. Maybe a simple solution would be to temporarily set the current working dir to the path of the including file (around line 17620 in org.el)? Many thanks in advance! Warm regards, Stefan -- Dr. Stefan Vollmar, Dipl.-Phys. Head of IT group Max-Planck-Institut für neurologische Forschung Gleuelerstr. 50, 50931 Köln, Germany Tel.: +49-221-4726-213 FAX +49-221-4726-298 Tel.: +49-221-478-5713 Mobile: 0160-93874279 E-Mail: voll...@nf.mpg.de http://www.nf.mpg.de smime.p7s Description: S/MIME cryptographic signature
Re: [O] Org-mode as a replacement for LaTeX
Hi Nick, Nick Dokos wrote: > Sebastien Vauban wrote: >> Thomas S. Dye wrote: >> > The first of what I hope will be three public reproducible >> > research papers written in Org-mode is now at >> > https://ts...@github.com/tsdye/hawaii-colonization.git >> >> I get a 404 error (page not found) when clicking on this!? > > Try visiting https://github.com/tsdye/ and > >git clone https://github.com/tsdye/hawaii-colonization.git Of course!!! I should stop playing with Org so late at night ;-) Best regards, Seb -- Sebastien Vauban
