Re: [O] HowTo: Letter template method using yasnippet
* Nicolas Goaziou wrote: > > Hello, Hello Nicolas! > Based on your work, I've put up the attached back-end: > org-koma-letter.el. ... and this is why I *love* this community so much :-) Yes, you are absolutely right that my method is unnecessary complex using this «generate TeX-files and Makefile using a shell script within Org-mode». For a non-LISPer like me, my method was straightforward and more general: my method can generate any kind of ASCII file template such as new shellscripts, new Python projects and so forth :-) And yes, your method is much simpler in terms of complexity and I definitely will take a closer look on how to implement such a thing with the export functions. Thanks for your work! -- Karl Voit
Re: [O] [ANN] Beamer back-end for org-export in contrib/
Hi Nicolas, Apologies for taking so long to respond. On Thu, Jul 5, 2012 at 1:56 PM, Nicolas Goaziou wrote: > 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:). I tested this and it works just as I was expecting it to. :) Another question, I noticed that the new exported does not have the exported file open in Emacs after it is done. I presume it is because the new engine doesn't work on a buffer anymore. Would it be possible to have Emacs open the exported file in the end? While exporting often I feel the need to see the exported result when I am working on a fairly complicated document. Sometimes it is to check if org did the export correctly or to check if LaTeX rendered my figure/equation as I am expecting it to. I realise at other times this might be undesirable and maybe even intrusive. I guess it seems like an adhoc addition but then the option could be user customisable (turned off by default). In any case it is a "nice to have" request, nothing to lose sleep over. :) Thanks again for all the hard work. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] Org/LaTeX set-up for business letters?
Mehul Sanghvi writes:
> Just out of curiosity, what was the CV template you used ?
I attach 3 variations of the same template, I used the one from TRAVIS
as a basis for my CV, but the others are nice too.
%% start of file `template_en.tex'.
%% Copyright 2007 Xavier Danaux (xdan...@gmail.com).
%
% This work may be distributed and/or modified under the
% conditions of the LaTeX Project Public License version 1.3c,
% available at http://www.latex-project.org/lppl/.
\documentclass[11pt,a4paper]{moderncv}
% moderncv themes
\moderncvtheme[red]{casual} % optional argument are 'blue' (default), 'orange', 'red', 'green', 'grey' and 'roman' (for roman fonts, instead of sans serif fonts)
%\moderncvtheme[green]{classic}% idem
% character encoding
\usepackage[utf8]{inputenc} % replace by the encoding you are using
% adjust the page margins
\usepackage[scale=0.8]{geometry}
\recomputelengths % required when changes are made to page layout lengths
% personal data
\firstname{Holly}
\familyname{Krieger}
%\title{Resumé title (optional)} % optional, remove the line if not wanted
\address{851 S. Morgan}{Chicago, IL 60607}% optional, remove the line if not wanted
%\mobile{mobile (optional)}% optional, remove the line if not wanted
\phone{312.996.2132} % optional, remove the line if not wanted
%\fax{fax (optional)} % optional, remove the line if not wanted
\email{hkrie...@uic.edu} % optional, remove the line if not wanted
%\extrainfo{additional information (optional)} % optional, remove the line if not wanted
%\photo[64pt]{picture} % '64pt' is the height the picture must be resized to and 'picture' is the name of the picture file; optional, remove the line if not wanted
\quote{"They can kill you, but the legalities of eating you are quite a bit dicier" - David Foster Wallace} % optional, remove the line if not wanted
%\nopagenumbers{} % uncomment to suppress automatic page numbering for CVs longer than one page
%--
%content
%--
\begin{document}
\maketitle
\section{Education}
\cventry{2007--present}{MS, Mathematics (expected 2008)}{University of Illinois at Chicago}{}{\textit{Chicago, IL}}{} %arguments 3 to 6 are optional
\cventry{2006--2007}{Graduate Study}{Michigan State University}{}{\textit{East Lansing, MI}}{} %arguments 3 to 6 are optional
\cventry{2001--2006}{BS, Mathematics with High Distinction}{University of Illinois at Urbana-Champaign}{}{\textit{Urbana, IL}}{} %arguments 3 to 6 are optional
%\section{Master thesis}
%\cvline{title}{\emph{Title}}
%\cvline{supervisors}{Supervisors}
%\cvline{description}{\small Short thesis abstract}
\section{Experience}
\subsection{Research}
\cventry{2007}{Independent Summer Research}{}{Urbana, IL}{}{- Studied approximations of functions in $L_{p}$ spaces for $0 < p < 1$ \newline{}- Supervised by Richard S. Laugesen}% arguments 3 to 6 are optional
\cventry{2005}{Undergraduate Research Course}{Urbana, IL}{}{}{- Studied invariant polynomials in several complex variables on subgroups of the unitary group \newline{}- Supervised by Bruce Reznick and John P. D'Angelo}% arguments 3 to 6 are optional
\subsection{Teaching}
\cventry{2007--present}{Graduate Teaching Assistant}{University of Illinois at Chicago}{}{}{Supervised an online section of Beginning Algebra}% arguments 3 to 6 are optional
\cventry{2006--2007}{Graduate Teaching Assistant}{Michigan State University}{}{}{Created and taught stand-alone courses in Business Calculus and Mathematics for Teachers}% arguments 3 to 6 are optional
\cventry{2004--2006}{Undergraduate Teaching Assistant}{University of Illinois at Urbana-Champaign}{}{}{Taught a discussion section for Calculus I}% arguments 3 to 6 are optional
\section{Languages}
\cvlanguage{Icelandic}{reading proficient}{language classes taken at H\'{a}sk\'{o}la \'{I}slands, Reykjav\'{i}k}
\cvlanguage{Italian}{reading proficient}{language classes taken at University of Illinois}
%\cvlanguage{language 3}{Skill level}{Comment}
\section{Computer skills}
\cvcomputer{Math Packages}{Mathematica, Matlab}{Programming Languages}{Java, C++}
\section{Other Interests}
\cvline{}{\small I also enjoy travel, music, and good food and wine.}
%\cvline{hobby 2}{\small Description}
%\cvline{hobby 3}{\small Description}
\closesection{} % needed to renewcommands
\renewcommand{\listitemsymbol}{-} % change the symbol for lists
% Publications from a BibTeX file
\nocite{*}
\bibliographystyle{plain}
\bibliography{publications} % 'publications' is the name of a BibTeX file
\end{document}
%% end of file `template_en.tex'.
%%
Re: [O] Org/LaTeX set-up for business letters?
Vikas Rawal writes: >> > >> > [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. > > May be relevant to look at this thread from the list: > > http://comments.gmane.org/gmane.emacs.orgmode/29926 So package 'isodoc' seems to be another (maybe simpler?) option. However, the thread proves again that it is not trivial to do-it-yourself. but there are quite a lot of options, it seems. -- cheers, Thorsten
Re: [O] [ANN] Beamer back-end for org-export in contrib/
Hello, suvayu ali writes: > Another question, I noticed that the new exported does not have the > exported file open in Emacs after it is done. It does here. Exporting with "l" or "d" leaves the corresponding tex file open in a buffer. Am I misunderstanding your request? Regards, -- Nicolas Goaziou
Re: [O] [ANN] Beamer back-end for org-export in contrib/
On Sat, Jul 7, 2012 at 2:32 PM, Nicolas Goaziou wrote: > It does here. Exporting with "l" or "d" leaves the corresponding tex > file open in a buffer. > > Am I misunderstanding your request? No you understood it correctly. This does not happen for me. Do you have any idea how I can track this issue down? PS: I tried with a minimal emacs instance. -- Suvayu Open source is the future. It sets us free.
Re: [O] [ANN] Beamer back-end for org-export in contrib/
suvayu ali writes: > No you understood it correctly. This does not happen for me. Do you > have any idea how I can track this issue down? You may try to debug `org-export-to-file'. I have no idea about what could remove the buffer containing the tex file.
[O] #+CAPTION: Not being protected when they are used with #+begin_src
>From the documentation, I know that captions work with inline images and tables, but for some reason when then inline images are generated through org-babel, #+CAPTION keys turns into regular text. What am I doing wrong now? :) -- ORG Source -- #+TITLE: Graphic Tests #+AUTHOR: Luis R. Anaya #+GROFF_ATTR: :alignment center #+GROFF_CLASS: file * PlantUML #+CAPTION: plantuml drawing #+begin_src plantuml :cmdline -Teps :file x.eps [A] --> [B] #+end_src * Gnuplot #+CAPTION: gnuplot drawing #+begin_src gnuplot :file salida.pic set term gpic plot sin(x) #+end_src -- Groff Output -- .MT 1 .H 1 "PlantUML" .P #+CAPTION: plantuml drawing .P .PSPIC "x.eps" .FG "" .H 1 "Gnuplot" .P #+CAPTION: gnuplot drawing .P .PS copy "salida.pic" .PE .FG "" --- Resultant output in PDF at: http://ppl.ug/YGVUBTwhknY/ Regards, -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] org-capture: keeping window visible during date entry
Eric Abrahamsen writes: > On Thu, Jun 14 2012, Christoph Groth wrote: >> How to ensure that the buffer which was active when org-capture was >> executed remains visible during date entry? > I've had the same annoyance. The attached patch is *not* a real > solution to the problem, as it still produces some weird windowing, > and I have no idea if it will wreck other uses of capture, but it does > preserve gnus windows so you can see the information you're trying to > capture. It's at least a pointer in the right direction… Yes, the problems are mostly due to calls to delete-other-windows which is used quite often in org (19 times) and other emacs packages as well. I would say that a proper solution would be to reserve delete-other-windows for interactive use and to replace it by something more sensible which ensures that a given window is well visible but tries to preserve the visibility and arrangement other windows if possible. That hypothetical function could be given the minimum required height for the current window. Does anyone know of such functionality already existing anywhere in the emacs world? If not, I believe it would be useful to think of something like this. Given current screen sizes, it would be good to replace most uses of delete-other-windows by something more gentle. But this is a topic for the general emacs mailing list.
Re: [O] org-capture: keeping window visible during date entry
On 7/7/12, Christoph Groth wrote: > I would say that a proper solution would be to reserve > delete-other-windows for interactive use and to replace it by something > more sensible which ensures that a given window is well visible but > tries to preserve the visibility and arrangement other windows if > possible. That hypothetical function could be given the minimum > required height for the current window. This is something that needs to be under user control. We cannot force a regression on an accessibility issue. Not all screen sizes are large and not all fonts are small. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
[O] Is LAST_REPEAT needed?
Unless I misunderstand, you can set org-log-repeat to 'time to log state changes and also store a LAST_REPEAT, or to nil to not log state changes and also not store a LAST_REPEAT. You can't tell it to do one and not the other. I want to log state changes but not store LAST_REPEAT unless it is algorithmically necessary. This is because the information is often redundant. Would it be possible to allow the user to set org-log-repeat accordingly? Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] #+CAPTION: Not being protected when they are used with #+begin_src
Luis Anaya writes: > From the documentation, I know that captions work with inline images > and tables, but for some reason when then inline images are generated > through org-babel, #+CAPTION keys turns into regular text. What am I > doing wrong now? :) > Instead of putting the #+Caption: line on the source block, place it on the result. This requires the use of named code blocks and results. The following alternate version of your example should give the behavior you're after. --8<---cut here---start->8--- #+TITLE: Graphic Tests #+AUTHOR: Luis R. Anaya #+GROFF_ATTR: :alignment center #+GROFF_CLASS: file * PlantUML #+name: plantuml-drawing #+begin_src plantuml :cmdline -Teps :file x.eps [A] --> [B] #+end_src #+CAPTION: plantuml drawing #+RESULTS: plantuml-drawing [[file:x.eps]] * Gnuplot #+name: gnuplot-drawing #+begin_src gnuplot :file salida.pic set term gpic plot sin(x) #+end_src #+CAPTION: gnuplot drawing #+RESULTS: gnuplot-drawing [[file:salida.pic]] --8<---cut here---end--->8--- Best, -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] org-capture: keeping window visible during date entry
Samuel Wales writes: > On 7/7/12, Christoph Groth wrote: >> I would say that a proper solution would be to reserve >> delete-other-windows for interactive use and to replace it by >> something more sensible which ensures that a given window is well >> visible but tries to preserve the visibility and arrangement other >> windows if possible. That hypothetical function could be given the >> minimum required height for the current window. > > This is something that needs to be under user control. We cannot > force a regression on an accessibility issue. Not all screen sizes > are large and not all fonts are small. My proposal is not about reducing accessibility but increasing usability. What's the point of deleting all the other windows to show a buffer containing only five lines of text (a typical capture buffer) and unlikely to grow much? If the user wants to type a lot into the new buffer, he can press C-x 1 himself. By "something more sensible" I meant functionality which would do the right thing both for small and large emacs frames. In many cases a reasonable minimum size for the new window to be displayed can be estimated. My font is actually not small and my screen typical. Still, my emacs frame is 70 lines high.
Re: [O] org-capture: keeping window visible during date entry
Not all use cases are identical to yours. -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
[O] Functions in SBE blocks
Hi, I can't get SBE blocks called from a table to work, if they use functions like org-parse-time-string. Suppose I have the following table: | Start| Ende | | |--+--+-| | [2011-06-29 Wed] | [2012-02-29 Wed] | | #+TBLFM: $3='(sbe "billable-month" (start $1) (end $2)) and the following source block: #+NAME: billable-month(start="[2011-06-29 Wed]", end="[2012-02-29 Wed]") #+BEGIN_SRC emacs-lisp (let* ((start-date start)) (message "%s" start-date)) #+END_SRC If I evaluate the table, the start date is put into the last column. However, if I change the code to the following: #+NAME: billable-month(start="[2011-06-29 Wed]", end="[2012-02-29 Wed]") #+BEGIN_SRC emacs-lisp (let* ((start-date (org-parse-time-string start))) (message "%s" (nth 4 start-date))) #+END_SRC then the string #ERROR is inserted into the table. Evaluating the source block directly yields the correct result. What's going on here? Thanks, Viktor
Re: [O] #+CAPTION: Not being protected when they are used with #+begin_src
Eric Schulte writes: > > Instead of putting the #+Caption: line on the source block, place it on > the result. This requires the use of named code blocks and results. > The following alternate version of your example should give the behavior > you're after. > [chomp...] Hi Eric: Thanks for your help but not quite what I expected. I did get the caption now, but I am still getting the #+NAME: See results: .H 1 "PlantUML" .P #+NAME: plantuml-drawing .P .PSPIC "x.eps" .FG "\fRplantuml drawing\fP" .H 1 "Gnuplot" .P #+name: gnuplot-drawing .P .PS copy "salida.pic" .PE .FG "\fRgnuplot drawing\fP" I'm getting suspicious on the ".P" on my results during paragraph generation. What I'll do is to temporary remove generating that ".P" and see if that removes the #+NAME: tag. If that's the case, I have to add another exception clause on the backend... Thanks a bunch! -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] #+CAPTION: Not being protected when they are used with #+begin_src
Hello, Luis Anaya writes: > Eric Schulte writes: > >> >> Instead of putting the #+Caption: line on the source block, place it on >> the result. This requires the use of named code blocks and results. >> The following alternate version of your example should give the behavior >> you're after. >> > [chomp...] > > Hi Eric: > > Thanks for your help but not quite what I expected. I did get the > caption now, but I am still getting the #+NAME: > > See results: > > .H 1 "PlantUML" > .P > #+NAME: plantuml-drawing > .P > .PSPIC "x.eps" .FG "\fRplantuml drawing\fP" .H 1 "Gnuplot" .P > #+name: gnuplot-drawing > .P > .PS > copy "salida.pic" > .PE > .FG "\fRgnuplot drawing\fP" > > > I'm getting suspicious on the ".P" on my results during paragraph > generation. What I'll do is to temporary remove generating that ".P" and see > if that removes the #+NAME: tag. If that's the case, I have to add > another exception clause on the backend... This is the known bug I told you about in another thread. It will be fixed soon after org-element hits core. Regards, -- Nicolas Goaziou
Re: [O] #+CAPTION: Not being protected when they are used with #+begin_src
Nicolas Goaziou writes: Hi: > This is the known bug I told you about in another thread. It will be > fixed soon after org-element hits core. Oh... I guess I missed that email :( At least I know that named captions are working for images. In other news... Other things I got working today are: 1. Checklists, in Groff will be: White bullet for on, Black bullet for off and hyphen. These map to .BL command. 2. Descriptive lists. It maps to a .VL statement with an inch separation (2.54 cm's for those in metric) between item and description. 3. Inline links for image types [[file:image.eps]] resolves to .PSPIC "image.eps" while a [[file:image.pic]] link resolves to a .PS/.PE pair. 4. Gnuplot support, embeds gpic or eps. You get better results with gpic. 5. Direct Groff commands. Now equations can be embedded. (via EQ/EN/EC) commands. 6. Cleaned up some of the links output to make it look pretty :) -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
[O] org-html: subtree specific footnote references
running org-export-as-html on a subtree is currently problematic if the result
is to be merged into a document which contains html-ized versions of other
subtrees: the footnote references and definitions get clobbered.
this patch uses the CUSTOM_ID property of the subtree to generate unique
footnote references and definitions. if the subtree does not have the CUSTOM_ID
property set the result is a nop.
>From 27f89f8bfff334810aba5c33af621e351fa0be79 Mon Sep 17 00:00:00 2001
From: Suhail Shergill
Date: Sun, 8 Apr 2012 10:49:51 -0400
Subject: [PATCH] org-html.el: Make footnotes unique to an entry
* lisp/org-html.el (org-export-as-html): Assign unique ids to footnotes
if possible
If the entry (or its ancestor) has the CUSTOM_ID property defined, then
use that as part of the generated footnote references and definitions.
---
lisp/org-html.el | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/lisp/org-html.el b/lisp/org-html.el
index c9c9d78..8b79c39 100644
--- a/lisp/org-html.el
+++ b/lisp/org-html.el
@@ -1248,6 +1248,9 @@ PUB-DIR is set, use this as the publishing directory."
(org-export-have-math nil)
(org-export-footnotes-seen nil)
(org-export-footnotes-data (org-footnote-all-labels 'with-defs))
+ (custom-id (or (org-entry-get nil "CUSTOM_ID" t) ""))
+ (footnote-def-prefix (format "fn-%s" custom-id))
+ (footnote-ref-prefix (format "fnr-%s" custom-id))
(lines
(org-split-string
(org-export-preprocess-string
@@ -1685,8 +1688,8 @@ PUB-DIR is set, use this as the publishing directory."
(format
(concat "%s"
(format org-export-html-footnote-format
- (concat "%s")))
- (or (match-string 1 org-line) "") n extra n n)
+ (concat "%s")))
+ (or (match-string 1 line) "") n extra n n)
;; If another footnote is following the
;; current one, add a separator.
(if (save-match-data
@@ -1773,8 +1776,9 @@ PUB-DIR is set, use this as the publishing directory."
(format
(concat ""
(format org-export-html-footnote-format
- "%s"))
- n n n) t t org-line)
+ (concat
+ "%s")))
+ n n n) t t line)
;; Check if the line break needs to be conserved
(cond
((string-match "[ \t]*$" org-line)
--
1.7.10
--
Suhail
Re: [O] Functions in SBE blocks
Viktor Rosenfeld wrote:
> Hi,
>
> I can't get SBE blocks called from a table to work, if they use
> functions like org-parse-time-string.
>
> Suppose I have the following table:
>
> | Start| Ende | |
> |--+--+-|
> | [2011-06-29 Wed] | [2012-02-29 Wed] | |
> #+TBLFM: $3='(sbe "billable-month" (start $1) (end $2))
>
> and the following source block:
>
> #+NAME: billable-month(start="[2011-06-29 Wed]", end="[2012-02-29 Wed]")
> #+BEGIN_SRC emacs-lisp
> (let* ((start-date start))
>(message "%s" start-date))
> #+END_SRC
>
> If I evaluate the table, the start date is put into the last column.
> However, if I change the code to the following:
>
> #+NAME: billable-month(start="[2011-06-29 Wed]", end="[2012-02-29 Wed]")
> #+BEGIN_SRC emacs-lisp
> (let* ((start-date (org-parse-time-string start)))
>(message "%s" (nth 4 start-date)))
> #+END_SRC
>
> then the string #ERROR is inserted into the table. Evaluating the source
> block directly yields the correct result.
>
> What's going on here?
>
Finicky type matching: if you evaluate the second code block in the buffer with
ESC ESC : (sbe "billable-month" (start "[2011-06-29 Wed]") (end
"[2012-02-29 Wed]")) RET
you get a backtrace similar to this:
,
| Debugger entered--Lisp error: (wrong-type-argument stringp [2011-06-29 Wed])
|
string-match("\\(\\([0-9]\\{4\\}\\)-\\([0-9]\\{2\\}\\)-\\([0-9]\\{2\\}\\)\\(
+[^]+0-9>
\n -]+\\)?\\( +\\([0-9]\\{1,2\\}\\):\\([0-9]\\{2\\}\\)\\)?\\)" [2011-06-29 Wed])
| (if (string-match org-ts-regexp0 s) (list 0 (if (or (match-beginning 8)
(not nodefault)) (string-to-number (or (match-string 8 s) "0"))) (if (or
(match-beginning 7) (not nodefault)) (string-to-number (or (match-string 7 s)
"0"))) (string-to-number (match-string 4 s)) (string-to-number (match-string 3
s)) (string-to-number (match-string 2 s)) nil nil nil) (error "Not a standard
Org-mode time string: %s" s))
| org-parse-time-string([2011-06-29 Wed])
| (let* ((start-date (org-parse-time-string start))) (format "%d" (nth 4
start-date)))
| ...
`
Somewhere, the string becomes not a string. Try modifying the block to this:
#+BEGIN_SRC emacs-lisp
(let* ((start-date (org-parse-time-string (format "%s" start
(message "%s" (nth 4 start-date)))
#+END_SRC
Nick
Re: [O] org-html: subtree specific footnote references
oops. attached the wrong patch. amended patch follows.
>From b9192f5e9a3bbe9620d9f588313d7f62e33135a5 Mon Sep 17 00:00:00 2001
From: Suhail Shergill
Date: Sun, 8 Apr 2012 10:49:51 -0400
Subject: [PATCH] org-html.el: Make footnotes unique to an entry
* lisp/org-html.el (org-export-as-html): Assign unique ids to footnotes
if possible
If the entry (or its ancestor) has the CUSTOM_ID property defined, then
use that as part of the generated footnote references and definitions.
---
lisp/org-html.el |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/lisp/org-html.el b/lisp/org-html.el
index c9c9d78..b9123a1 100644
--- a/lisp/org-html.el
+++ b/lisp/org-html.el
@@ -1248,6 +1248,9 @@ PUB-DIR is set, use this as the publishing directory."
(org-export-have-math nil)
(org-export-footnotes-seen nil)
(org-export-footnotes-data (org-footnote-all-labels 'with-defs))
+ (custom-id (or (org-entry-get nil "CUSTOM_ID" t) ""))
+ (footnote-def-prefix (format "fn-%s" custom-id))
+ (footnote-ref-prefix (format "fnr-%s" custom-id))
(lines
(org-split-string
(org-export-preprocess-string
@@ -1685,7 +1688,7 @@ PUB-DIR is set, use this as the publishing directory."
(format
(concat "%s"
(format org-export-html-footnote-format
- (concat "%s")))
+ (concat "%s")))
(or (match-string 1 org-line) "") n extra n n)
;; If another footnote is following the
;; current one, add a separator.
@@ -1773,7 +1776,8 @@ PUB-DIR is set, use this as the publishing directory."
(format
(concat ""
(format org-export-html-footnote-format
- "%s"))
+ (concat
+ "%s")))
n n n) t t org-line)
;; Check if the line break needs to be conserved
(cond
--
1.7.10
Suhail Shergill writes:
> running org-export-as-html on a subtree is currently problematic if the result
> is to be merged into a document which contains html-ized versions of other
> subtrees: the footnote references and definitions get clobbered.
>
> this patch uses the CUSTOM_ID property of the subtree to generate unique
> footnote references and definitions. if the subtree does not have the
> CUSTOM_ID
> property set the result is a nop.
>
>
> From 27f89f8bfff334810aba5c33af621e351fa0be79 Mon Sep 17 00:00:00 2001
> From: Suhail Shergill
> Date: Sun, 8 Apr 2012 10:49:51 -0400
> Subject: [PATCH] org-html.el: Make footnotes unique to an entry
>
> * lisp/org-html.el (org-export-as-html): Assign unique ids to footnotes
> if possible
>
> If the entry (or its ancestor) has the CUSTOM_ID property defined, then
> use that as part of the generated footnote references and definitions.
> ---
> lisp/org-html.el | 12
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/lisp/org-html.el b/lisp/org-html.el
> index c9c9d78..8b79c39 100644
> --- a/lisp/org-html.el
> +++ b/lisp/org-html.el
> @@ -1248,6 +1248,9 @@ PUB-DIR is set, use this as the publishing directory."
>(org-export-have-math nil)
>(org-export-footnotes-seen nil)
>(org-export-footnotes-data (org-footnote-all-labels 'with-defs))
> + (custom-id (or (org-entry-get nil "CUSTOM_ID" t) ""))
> + (footnote-def-prefix (format "fn-%s" custom-id))
> + (footnote-ref-prefix (format "fnr-%s" custom-id))
>(lines
> (org-split-string
> (org-export-preprocess-string
> @@ -1685,8 +1688,8 @@ PUB-DIR is set, use this as the publishing directory."
> (format
> (concat "%s"
> (format org-export-html-footnote-format
> -(concat " name=\"fnr.%s%s\" href=\"#fn.%s\">%s")))
> -(or (match-string 1 org-line) "") n extra n n)
> +(concat " name=\"" footnote-ref-prefix ".%s%s\" href=\"#" footnote-def-prefix
> ".%s\">%s")))
> +(or (match-string 1 line) "") n extra n n)
> ;; If another footnote is following the
> ;; current one, add a separator.
> (if (save-match-data
> @@ -1773,8 +1776,9 @@ PUB-DIR is set, use this as the publishing directory."
> (format
> (concat ""
> (format org-export-html-footnote-format
> -" name=\"fn.%s\" href=\"#fnr.%s\">%s"))
> -n n n) t t org-line)
> +(concat
> + " footnote-def-prefix ".%s\" href=\"#" footnote-ref-prefix ".%s\">%s")))
> +n n n) t t line)
> ;; Check if the line break needs to be conserved
> (cond
>((string-match "[ \t]*$" org-line)
> --
> 1.7.10
--
Suhail
Re: [O] Exporting to groff, now in org-export.el ...
In case you were curious how today's updates look like (if you're not, then yeah, I'm showing up :) ), samples of these can be found at: Sources: graph.org - http://ppl.ug/droqQrYmMkw/ todo.org - http://ppl.ug/W6RBCb7gNAs/ PDF results: graph.pdf - http://ppl.ug/YGVUBTwhknY/ todo.org - http://ppl.ug/c1TZGeedv3Y/ I also added a small feature to include groff files if they are placed in links. The groff exporter as it stands has very minimal support for links, these will just be printed as text. However being that groff can include files, I throught that it would be nice if groff files were included instead having their path printed out. Hence [[file:myfile.groff]] Will map to an include call, namely to: .so myfile.groff When the org file is exported, myfile.groff will be included as part of the export process and written in the resultant PDF file. Regards, -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] Exporting to groff, now in org-export.el ...
I should clarify that image files that are supported in groff, get inlined when a link is written. Hence, [[file:image.eps]] or [[file:image.pic]] Will include the image and write the image in the resultant PDF file. Sorry if I confused anybody... :( -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
[O] save-excursion in Org files
Hi List, in elisp code, with point in entry1, I do a save-excursion that inserts another entry2 and does some work there. After existing from the save-excursion form, I add e.g. a global ID with org-id-get-create - and would expect to find it in entry1 when save-excursion did its job right. But I find it in entry2. So when I am in one entry and do some inserting in a save-excursion, I cannot expect to find myself at the same position in the same entry after save-excursion finished? -- cheers, Thorsten
Re: [O] save-excursion in Org files
Thorsten Jolitz writes: > in elisp code, with point in entry1, I do a save-excursion that inserts > another entry2 and does some work there. After existing from the > save-excursion form, I add e.g. a global ID with org-id-get-create - and > would expect to find it in entry1 when save-excursion did its job right. > But I find it in entry2. > > So when I am in one entry and do some inserting in a save-excursion, I > cannot expect to find myself at the same position in the same entry > after save-excursion finished? save-excursion does seem to work better than human reception: ,--- | before save excusion1: 271 | before save excusion2: 271 | after save excursion2: 271 | before end save excusion1: 455 | after save excusion1: 271 | after postprocess: 271 `--- I enclosed the whole thing in another save-excursion, an found out that there was some point movement after the original save-excursion that I had overlooked. Sorry for the noise. -- cheers, Thorsten
Re: [O] Exporting to groff, now in org-export.el ...
Hi Luis, The outputs look great. However I have a question; I see all the PDFs have the content pages at the end instead of the front. Is there any particular reason for that? Keep up the good work. :) Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] Functions in SBE blocks
Hi Nick,
Nick Dokos wrote:
> Viktor Rosenfeld wrote:
>
> > Hi,
> >
> > I can't get SBE blocks called from a table to work, if they use
> > functions like org-parse-time-string.
> >
> > Suppose I have the following table:
> >
> > | Start| Ende | |
> > |--+--+-|
> > | [2011-06-29 Wed] | [2012-02-29 Wed] | |
> > #+TBLFM: $3='(sbe "billable-month" (start $1) (end $2))
> >
> > and the following source block:
> >
> > #+NAME: billable-month(start="[2011-06-29 Wed]", end="[2012-02-29 Wed]")
> > #+BEGIN_SRC emacs-lisp
> > (let* ((start-date start))
> >(message "%s" start-date))
> > #+END_SRC
> >
> > If I evaluate the table, the start date is put into the last column.
> > However, if I change the code to the following:
> >
> > #+NAME: billable-month(start="[2011-06-29 Wed]", end="[2012-02-29 Wed]")
> > #+BEGIN_SRC emacs-lisp
> > (let* ((start-date (org-parse-time-string start)))
> >(message "%s" (nth 4 start-date)))
> > #+END_SRC
> >
> > then the string #ERROR is inserted into the table. Evaluating the source
> > block directly yields the correct result.
> >
> > What's going on here?
> >
>
> Finicky type matching: if you evaluate the second code block in the buffer
> with
>
>ESC ESC : (sbe "billable-month" (start "[2011-06-29 Wed]") (end
> "[2012-02-29 Wed]")) RET
>
> you get a backtrace similar to this:
>
> ,
> | Debugger entered--Lisp error: (wrong-type-argument stringp [2011-06-29 Wed])
> |
> string-match("\\(\\([0-9]\\{4\\}\\)-\\([0-9]\\{2\\}\\)-\\([0-9]\\{2\\}\\)\\(
> +[^]+0-9>
> \n -]+\\)?\\( +\\([0-9]\\{1,2\\}\\):\\([0-9]\\{2\\}\\)\\)?\\)" [2011-06-29
> Wed])
> | (if (string-match org-ts-regexp0 s) (list 0 (if (or (match-beginning 8)
> (not nodefault)) (string-to-number (or (match-string 8 s) "0"))) (if (or
> (match-beginning 7) (not nodefault)) (string-to-number (or (match-string 7 s)
> "0"))) (string-to-number (match-string 4 s)) (string-to-number (match-string
> 3 s)) (string-to-number (match-string 2 s)) nil nil nil) (error "Not a
> standard Org-mode time string: %s" s))
> | org-parse-time-string([2011-06-29 Wed])
> | (let* ((start-date (org-parse-time-string start))) (format "%d" (nth 4
> start-date)))
> | ...
> `
>
> Somewhere, the string becomes not a string. Try modifying the block to this:
>
> #+BEGIN_SRC emacs-lisp
> (let* ((start-date (org-parse-time-string (format "%s" start
>(message "%s" (nth 4 start-date)))
> #+END_SRC
>
> Nick
Thanks, that does the trick. The double ESC evaluation is helpful, too.
Cheers,
Viktor
Re: [O] Exporting to groff, now in org-export.el ...
suvayu ali writes: Hi Sevayu! > > have the content pages at the end instead of the front. Is there any > particular reason for that? Yes there is a reason. The MM implementation of table of contents collects all the headers and captions that have read up to the point of execution of the table of content command. If you want to collect all the headers, the table of content command must be placed at the end. The idea was that you placed those pages in the right order before "shipping" the document after printing. Now in the day of PDF files, it may look weird to have it there but being that the implementation of the macro has not changed, it still needs to be the last command in the document. -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] Exporting to groff, now in org-export.el ...
Hi Luis, On Sun, Jul 8, 2012 at 3:49 AM, Luis Anaya wrote: > suvayu ali writes: > > Hi Sevayu! > >> >> have the content pages at the end instead of the front. Is there any >> particular reason for that? > > Yes there is a reason. > > The MM implementation of table of contents collects all the headers and > captions that have read up to the point of execution of the table of > content command. > > If you want to collect all the headers, the table of content command > must be placed at the end. The idea was that you placed those pages in > the right order before "shipping" the document after printing. Now in > the day of PDF files, it may look weird to have it there but being > that the implementation of the macro has not changed, it still needs > to be the last command in the document. Ah, so it's a legacy reason. It is always great to learn about history. :) Maybe this information would be worth mentioning in the future documentation for the groff exporter. Thanks, -- Suvayu Open source is the future. It sets us free.
[O] Output of R babel blocks with quotes is mangled/truncated
Hi, if a value outputted by R in a Babel block contains quotes only the quoted parted is exported. Consider this: #+BEGIN_SRC R q = 'cat="S"' q #+END_SRC #+RESULTS: : S The expected result would be entire string, i.e. 'cat="S"' (without single quotes). Is there a workaround? I've tried escaping with backslashes to no avail. Cheers, Viktor
