Re: [O] [ANN] Beamer back-end for org-export in contrib/
Hello, suvayu ali fatkasuvayu+li...@gmail.com writes: If I understand correctly, having a buffer keyword would mean I would need to find and update it appropriately everytime I want to export something. I can live with this, but it would be great if there was support these export options as properties. Then all the subtree exports can be decoupled easily. I agree. Now, /every/ property set through an export keyword can also be defined with an headline property. That property has the same name as the keyword, with an EXPORT_ prefix (i.e #+DATE: and :EXPORT_DATE:). This is also true for keywords defined by back-ends (#+LATEX_CLASS: and :EXPORT_LATEX_CLASS:). In order to avoid confusion, I've renamed buffer keyword setting select tags (resp. exclude tags) from EXPORT_SELECT_TAGS (resp. EXPORT_EXCLUDE_TAGS) to SELECT_TAGS (resp. EXCLUDE_TAGS). Regards, -- Nicolas Goaziou
[O] Org/LaTeX set-up for business letters?
Hi List, although using Emacs/Org-mode for almost everything, I still write my official correspondence with a (quite nice) OpenOffice template. It would be so much easier and faster to just use Org mode for that too. I tried some LaTeX templates from the web, but they were ugly. I know one could use the Do It Yourself approach, but I would rather save the time and effort and like to ask if anybody on the list has a nice looking Org-mode/ LaTeX setup for business letters and/or facturations and doesn't mind to share it? I found this interesting thread about the same topic: , | http://web.archiveorange.com/archive/v/Fv8aAut19uyEPkEUnsM8 ` but I could not figure out if it resulted in a kind of final setup that is now used by some people and can be downloaded somewhere. Thanks in advance -- cheers, Thorsten
Re: [O] Org/LaTeX set-up for business letters?
On Thu, Jul 5, 2012 at 2:49 PM, Thorsten Jolitz tjol...@googlemail.com wrote: although using Emacs/Org-mode for almost everything, I still write my official correspondence with a (quite nice) OpenOffice template. It would be so much easier and faster to just use Org mode for that too. You can use opendocument export and use your Libreoffice template with it. Check the archives for Jambunathan's post detailing how to do that. -- Suvayu Open source is the future. It sets us free.
Re: [O] Possible bug - C-c * toggles #+(keyword) to headline
Hi Charles, Charles mill...@verizon.net writes: I previously reported this but without the word bug in my subject line. My mistake. When my cursor is on an 'in buffer setting' line #+FOO: bar C-c * toggles it to * #+FOO: bar i.e. a headline. This is not the case anymore, comments are now skipped. Also, the function returns a message when nothing could be done. Thanks, -- Bastien
Re: [O] installation questions
Hi Achim and Yagnesh, Achim Gratz strom...@nexgo.de writes: Yagnesh Raghava Yakkala writes: 1. Is the above snippet is all that is needed to load org.? The public interfaces of org should all be autoloaded, IMHO. Bastien may be able to answer why some of the interactive functions are not autoloaded (my guess is that they may need some initialization, but it may purely be an oversight). This is purely an oversight. If some interactive functions need an autoload cookie, please let me know. I'm not sure a systematic approach is good here. Thanks, -- Bastien
Re: [O] Macros [was: Re: ATTR_HTML for a clickable image, howto?]
Hi, François Pinard pin...@iro.umontreal.ca writes: If macros are there to stay in Org, it might be worth documenting a more complete specification about how to define and use them. I'd welcome some improvement of the manual wrt macros -- any taker? Thanks, -- Bastien
Re: [O] Macros [was: Re: ATTR_HTML for a clickable image, howto?]
Hello, Bastien b...@gnu.org writes: François Pinard pin...@iro.umontreal.ca writes: If macros are there to stay in Org, it might be worth documenting a more complete specification about how to define and use them. I'd welcome some improvement of the manual wrt macros -- any taker? Before documenting anything, we should first define them clearly. That is, we can define them through documentation, but we shouldn't write documentation by looking at their current implementation. Should macros be allowed anywhere (which means that the user can shoot himself in the foot) or should their expansion happen in a protected environment (thus limiting their power)? In the first case, can macros generate inline Babel code, that will be executed before export? In the second case, what types of elements are allowed in the protected environment? Also, do we want to allow multiples macros definitions to stack up? I.e. #+MACRO: a-macro First line of the macro. #+MACRO: a-macro Second line of the macro. If so, do we allow blank lines in them, meaning they can break document structure even more? Can the macros be nested? Since macros arguments are comma-separated, how do one insert commas within an argument? Are newline characters allowed in arguments? If not, what else is forbidden there? There are probably other questions, but it should be a good start for a correct implementation. Regards, -- Nicolas Goaziou
Re: [O] [babel] export of table with inline source blocks
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Hi all,
I am having problems with the export of a minimal org file:
,
| #+PROPERTY: session *R*
|
| * Test
|
| | dtrn | xgnd |
| |--+---|
| | engd | src_R[:exports results :results raw replace]{1/2} |
| | engd | src_R[:exports results :results raw replace]{1/2} |
| | engd | src_R[:exports results :results raw replace]{1/2} |
|
`
Problems:
1. only the first inline code is executed
2. the inline block is not replaced
This is the latex output:
,
| \begin{center}
| \begin{tabular}{ll}
| dtrn xgnd\\
| \hline
| engd src$_{\mathrm{R[}}$:exports results :results raw replace]\{1/2\}
0.5\\
| engd src$_{\mathrm{R[}}$:exports results :results raw replace]\{1/2\}\\
| engd src$_{\mathrm{R[}}$:exports results :results raw replace]\{1/2\}\\
| \end{tabular}
| \end{center}
`
Are inline blocks not allowed in tables?
That is correct, inline code blocks are not intended for use in tables.
Tables already support the execution of arbitrary emacs-lisp functions
using spreadsheet formulas. Using spreadsheet formulas the `sbe'
function may be used to execute code blocks from table cells.
--
Eric Schulte
http://cs.unm.edu/~eschulte
Re: [O] [BUG] babel call lines broken
This is a problem caused by my recent addition of hashing to call lines. I've attached a patch which fixes this problem. For some reason I am currently unable to communicate with the Org-mode git server, so if anyone else is able to apply this patch please do. Thanks for catching this problem, From 9e0e55e0ee2c933de476ca869910c3279df62675 Mon Sep 17 00:00:00 2001 From: Eric Schulte eric.schu...@gmx.com Date: Thu, 5 Jul 2012 07:47:32 -0600 Subject: [PATCH] only try to insert extant hashes * lisp/ob-lob.el (org-babel-lob-execute): Only try to insert extant hashes. --- lisp/ob-lob.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/ob-lob.el b/lisp/ob-lob.el index 66b100c..b1efbbb 100644 --- a/lisp/ob-lob.el +++ b/lisp/ob-lob.el @@ -139,7 +139,7 @@ if so then run the appropriate source block from the Library. (prog1 (org-babel-execute-src-block nil (mkinfo (org-babel-process-params pre-params))) ;; update the hash - (org-babel-set-current-result-hash new-hash)) + (when hash (org-babel-set-current-result-hash new-hash))) (provide 'ob-lob) -- 1.7.11.1 Andreas Leha andreas.l...@med.uni-goettingen.de writes: Hi all, there seems to be a bug in evaluating #+call lines. To reproduce, consider this file: , | * Some Headline | #+name: parameters | #+BEGIN_SRC R | ttt - 1 | #+END_SRC | | * Some Other Headline | #+call: parameters() :results silent :exports none ` and do C-c C-c on the #+call: line. For me that results in: , | Debugger entered--Lisp error: (wrong-type-argument stringp nil) | replace-match(nil nil nil nil 3) | org-babel-set-current-result-hash(nil) | org-babel-lob-execute((parameters() :results silent :exports none 0)) | org-babel-lob-execute-maybe() | org-babel-execute-maybe() | org-babel-execute-safely-maybe() | run-hook-with-args-until-success(org-babel-execute-safely-maybe) | org-ctrl-c-ctrl-c(nil) | call-interactively(org-ctrl-c-ctrl-c nil nil) ` Regards, Andreas PS: I am on emacs24.2.50.1 -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] [Feature Request] org-mobile edit:add nodes
Hi Henning, Henning Weiss hdwe...@gmail.com writes: I have refined the edit nodes patch. Aaron Peromsik has helped me with developing and testing it. He hasn't reported any problems with it and I have been using it for a couple of weeks now without experiencing any problems. I applied this patch now. Thanks for your patience! -- Bastien
Re: [O] Macros [was: Re: ATTR_HTML for a clickable image, howto?]
Hi Nicolas, Nicolas Goaziou wrote: Bastien b...@gnu.org writes: François Pinard pin...@iro.umontreal.ca writes: If macros are there to stay in Org, it might be worth documenting a more complete specification about how to define and use them. I'd welcome some improvement of the manual wrt macros -- any taker? Before documenting anything, we should first define them clearly. I think you're right here, seen the latest threads on this. That is, we can define them through documentation, but we shouldn't write documentation by looking at their current implementation. Should macros be allowed anywhere (which means that the user can shoot himself in the foot) or should their expansion happen in a protected environment (thus limiting their power)? If I had to choose, I would opt for the first case... In the first case, can macros generate inline Babel code, that will be executed before export? ... where macros would be pre-processed à la M4 (or C preprocessing): replacing some keyword with some other expression. In the second case, what types of elements are allowed in the protected environment? Also, do we want to allow multiples macros definitions to stack up? I.e. #+MACRO: a-macro First line of the macro. #+MACRO: a-macro Second line of the macro. If so, do we allow blank lines in them, meaning they can break document structure even more? Can the macros be nested? Since macros arguments are comma-separated, how do one insert commas within an argument? Are newline characters allowed in arguments? If not, what else is forbidden there? There are probably other questions, but it should be a good start for a correct implementation. An extra question is: the replacing expression of a macro, must it be pure text, or can it be anything (such as code that will be interpreted, in a further pass, by some back-end)? Best regards, Seb -- Sebastien Vauban
Re: [O] stop comments and weblinks from being coloured and names of directories from being italised, /etc/
Enda enda...@yahoo.com writes: Also I keep directory names in the org file like /usr/bin/ which in the org file as you know would become italicized. Main Headings are blue (* Heading), but also weblinks are blue, which highlights them and I do not want them to be highlighted. For this I simply suggest =/usr/bin/= instead of /usr/bin/ -- Bastien
Re: [O] [BUG] babel call lines broken
Eric Schulte eric.schu...@gmx.com writes: For some reason I am currently unable to communicate with the Org-mode git server, so if anyone else is able to apply this patch please do. Done - thanks for the patch! -- Bastien
Re: [O] Agenda Upcoming Faces
SW sabrewo...@gmail.com writes: I have agenda TODO items due in 5d (in org-upcoming-deadline face), in 16d (in default face) and in 26d (in org-upcoming-deadline face). Why is the 16d deadline in default face? I can't reproduce this. Can you provide a recipe and/or a screenshot? Thanks, -- Bastien
Re: [O] Bug: Bug report about html export, wrong attachments [7.8.03]
Uwe Brauer o...@mat.ucm.es writes: Sorry I sent the wrong files (I forgot to insert the png) here are the correct ones, as tar files This mailing list doesn't support big attachments. Can you simply post the HTML code instead of the files? Thanks, -- Bastien
[O] #+OPTION that specified headings would be fontified while everything else would not be
Can there be a way to specify headings (and subheadings) in an #+OPTION option, and that these headings would be fontified while everything else would not be, like * Blue1 #!/not/red * Blue2 ** Sierra1 http://www.example.com/notblue (links are usually the same colour as the first level heading.) Org #+OPTIONS (#+STARTUP, #+OPTIONS, etc.) should be fontified so that they can be easily seen. * Not a Heading - list1 *not* bold /not/ italicised - not to be treated like a list #+OPTIONS: headings1: Blue1 Blue2 headings2: Sierra1 lists: list1 #+STARTUP: showall Best wishes, Enda
[O] #+OPTION that specified headings would be fontified while everything else would not be
Can there be a way to specify headings (and subheadings) in an #+OPTION option, and that these headings would be fontified while everything else would not be, like * Blue1 #!/not/red * Blue2 ** Sierra1 http://www.example.com/notblue (links are usually the same colour as the first level heading.) Org #+OPTIONS (#+STARTUP, #+OPTIONS, etc.) should be fontified so that they can be easily seen. * Not a Heading - list1 *not* bold /not/ italicised - not to be treated like a list #+OPTIONS: headings1: Blue1 Blue2 headings2: Sierra1 lists: list1 #+STARTUP: showall Best wishes, Enda
[O] org-icalendar-alarm-time different time for different category
Can there be a per file option to set org-icalendar-alarm-time for a different time for a different category? Best wishes, Enda Debian GNU/Linux Emacs 23.4
Re: [O] Possible bug - C-c * toggles #+(keyword) to headline
Does the word bug in a headline do anything automatically like enter into a DB? -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] Possible bug - C-c * toggles #+(keyword) to headline
Hi Samuel, Samuel Wales samolog...@gmail.com writes: Does the word bug in a headline do anything automatically like enter into a DB? No, using bug or [BUG] in the subject line of the emails sent on this list does no magic -- except that it's easier for developers to skim through the archive and find those subject lines. -- Bastien
Re: [O] doi proxy , a test patch
Hi Fabrice, Fabrice Pardo fabrice.pa...@lpn.cnrs.fr writes: On 12-05-23 06:39 PM, Jambunathan K wrote: Can a given Org document contain links to two different doi proxies? In that case will a defcustom help. No, my doi server is an enhancement or the official http://dx.doi.org/ Hence it would be a goog thing to redirect all the org-mode external links to a customizable address, and to replace the hard-coded string http://dx.doi.org/; in org-open-at-point by a variable. There is now `org-doi-server-url'. Thanks, -- Bastien
Re: [O] Org/LaTeX set-up for business letters?
suvayu ali fatkasuvayu+li...@gmail.com writes: On Thu, Jul 5, 2012 at 2:49 PM, Thorsten Jolitz tjol...@googlemail.com wrote: although using Emacs/Org-mode for almost everything, I still write my official correspondence with a (quite nice) OpenOffice template. It would be so much easier and faster to just use Org mode for that too. You can use opendocument export and use your Libreoffice template with it. Check the archives for Jambunathan's post detailing how to do that. Ok, thanks, though that would not be my perfered solution. -- cheers, Thorsten
Re: [O] new exporter drops :parameters ?
Hello, cbe...@tajo.ucsd.edu writes: BTW, #+name: aname and #+NAME: aname are handled differently in e-latex. The former gets placed in the latex output as \#+name: aname. Bug? There is a known bug about affiliated keywords not being removed during export, but I don't know if you're describing the same problem. Do you have an ECM illustrating it ? Regards, -- Nicolas Goaziou
Re: [O] Org/LaTeX set-up for business letters?
On Thu, Jul 5, 2012 at 9:00 PM, Thorsten Jolitz tjol...@googlemail.com wrote: suvayu ali fatkasuvayu+li...@gmail.com writes: On Thu, Jul 5, 2012 at 2:49 PM, Thorsten Jolitz tjol...@googlemail.com wrote: although using Emacs/Org-mode for almost everything, I still write my official correspondence with a (quite nice) OpenOffice template. It would be so much easier and faster to just use Org mode for that too. You can use opendocument export and use your Libreoffice template with it. Check the archives for Jambunathan's post detailing how to do that. Ok, thanks, though that would not be my perfered solution. Well I assumed it would be since you already have a quite nice OpenOffice template. If you are after latex templates for letters in specific, I think Org mode might be the wrong tool for that. The tree structure is a fundamental part of Org. This works very well for articles, reports, theses; however I'm not sure it works as well for letters. You might be better off by just using latex directly. That said, maybe you could look for a latex template on CTAN[1]. Then you could customise org-export-latex-classes to include the documentclass provided by the package. Although I'm not sure how a tree structure could be mapped to a letter. If you do succeed, I would be interested to know. GL Footnotes: [1] Off the top of the head I recall a package called `scrlttr'. -- Suvayu Open source is the future. It sets us free.
Re: [O] Org/LaTeX set-up for business letters?
suvayu ali fatkasuvayu+li...@gmail.com writes: Well I assumed it would be since you already have a quite nice OpenOffice template. It looks like a professional letter, while everything I found in the web rathers proves that programmers are not designers, even with a tool like LaTeX at hand. If you are after latex templates for letters in specific, I think Org mode might be the wrong tool for that. The tree structure is a fundamental part of Org. This works very well for articles, reports, theses; however I'm not sure it works as well for letters. You might be better off by just using latex directly. That said, maybe you could look for a latex template on CTAN[1]. Then you could customise org-export-latex-classes to include the documentclass provided by the package. Although I'm not sure how a tree structure could be mapped to a letter. If you do succeed, I would be interested to know. Thanks for the tips, but I don't have time for that at the moment and was rather hoping that somebody already did the work and likes to share. Of course this is not a LaTeX list, but it would be OK too to just have a nice LaTeX template and write with AucTeX, even if Org mode is not used (yet). Footnotes: [1] Off the top of the head I recall a package called `scrlttr'. Yes, part of KOMA (?), but thats rather low level if you have to design your own letters - and who knows all that stuff about professional letter design?. I tried that once and the result was ugly, there is a lot of extra work necesary to make it look fancy and modern. -- cheers, Thorsten
Re: [O] Exporting to groff, now in org-export.el ...
Nicolas Goaziou n.goaz...@gmail.com writes: I can't promise to keep an eye on the repository, but if you have any question (if possible with an example to illustrate it, as I don't know groff syntax), do not hesitate to ask. Thanks, I will. The only concern that I have is that there are times that export hangs. I need to figure that one out, I'll keep you posted. (If I do not collapse of exhaustion taking care of them. :( ) There's the `sleep-for' function for that. :) It'll execute for a looong time over the weekend :) In other news I added various enhancements. Including: 1. Automated caption support. I need to figure out how to get the caption text (via CAPTION? via ATTR ? ). Right now generic ones are added which they show up in the table of content. 2. EPS diagrams import support. I mostly needs it for plantuml diagrams. Groff only supports ps and eps only. But automated plantuml diagrams do get created and inlined (via .PSPIC) when the file is exported. 3. Quotes and Verse support. Currently hardcoded to helvetica. I should think of customizing fonts via defcustom, but for now, this is it. 4. Improvements on footnotes. Currently creating footnotes by taking the value from :label. 5. Lists (numeric and bullets). Sample output is here: http://ppl.ug/xgZ7dmDq43Q/ I have a general question though. Equation and Picture creation support in Groff is done with the use of the eqn and pic programs. I've been debating if these should be included in org-babel, for executing these the same way plantuml is executed through the use of #+begin_src #+end_src However considering that these are Groff only I'm not sure if these would be better served by using special attributes to add pic/eqn code. This is because the output of these commands are Groff statements that only make sense in Groff. ??!! Thanks! -- Luis Anaya papo anaya aroba hot mail punto com Do not use 100 words if you can say it in 10 - Yamamoto Tsunetomo
