[O] Writing microsecond time unit
Dear Orgers,
I would like to do something very simple such as writing microsecond
unit but I fail. I try different way (\mu\nbsp s, $\mu$s, \mu s) but
always get a whitespace between the µ symbol and the second symbol. The
only working version is $\mu\text{s}$ which gives me a pure LaTeX code
which is find for LaTeX to pdf export but is quite annoying when I
export to html. Is there a simple way to use the symbol µ glued to a 's' ?
Thanks in advance,
Xavier
Re: [O] Writing microsecond time unit
Hi Xavier,
· Xavier Garrido xavier.garr...@gmail.com wrote:
Dear Orgers,
I would like to do something very simple such as writing microsecond
unit but I fail. I try different way (\mu\nbsp s, $\mu$s, \mu s) but
always get a whitespace between the µ symbol and the second symbol. The
only working version is $\mu\text{s}$ which gives me a pure LaTeX code
which is find for LaTeX to pdf export but is quite annoying when I
export to html. Is there a simple way to use the symbol µ glued to a 's' ?
what about \mu{}s. It works for HTML:
mu;s
and LaTeX:
$\mu$s
HTH
--
Bis neulich ...
Thomas
Re: [O] Writing microsecond time unit
Thanks a lot Thomas, it works like a charm.
Le 01/07/2013 09:11, Thomas Holst a écrit :
Hi Xavier,
· Xavier Garrido xavier.garr...@gmail.com wrote:
Dear Orgers,
I would like to do something very simple such as writing microsecond
unit but I fail. I try different way (\mu\nbsp s, $\mu$s, \mu s) but
always get a whitespace between the µ symbol and the second symbol. The
only working version is $\mu\text{s}$ which gives me a pure LaTeX code
which is find for LaTeX to pdf export but is quite annoying when I
export to html. Is there a simple way to use the symbol µ glued to a 's' ?
what about \mu{}s. It works for HTML:
mu;s
and LaTeX:
$\mu$s
HTH
Re: [O] Writing microsecond time unit
Xavier Garrido xavier.garr...@gmail.com writes:
Dear Orgers,
I would like to do something very simple such as writing microsecond
unit but I fail. I try different way (\mu\nbsp s, $\mu$s, \mu s) but
always get a whitespace between the µ symbol and the second
symbol. The only working version is $\mu\text{s}$ which gives me a
pure LaTeX code which is find for LaTeX to pdf export but is quite
annoying when I export to html. Is there a simple way to use the
symbol µ glued to a 's' ?
How about
\(\mu s\)
? Should work for both latex and html.
Actually,
\(\mu\text{s}\)
should also work (producing an upright s, rather than the slanted s that
the first example produces - personally I like the first one better).
Not sure if the $ signs are causing problems: imo, it's a better idea
to use the standard latex delimiters
\( ... \) for inline math
\[ ... \] for display math
always.
The html output makes use of MathJax but that should be no problem: by
default, the output references the MathJax installation on orgmode.org.
You might want to install on a local web server if you are going to make
heavy use of it.
See
(info (org) Math formatting in HTML export)
for more details.
--
Nick
Re: [O] [BUG] A typo introduced in '6abc114f188267e4b804a3eca8794900eee66db0'
Hi Vladimir, Vladimir Lomov lomov...@gmail.com writes: a typo introduced in commit '6abc114f188267e4b804a3eca8794900eee66db0' prevents `org-agenda.el' to compile into 'elc' (actually Emacs shows me an error which I don't understand). I compared `org-agenda.el' of '6abc114f188267e4b804a3eca8794900eee66db0' commit with previous commit and made small patch which fixes the problem. Applied, thanks for spotting and reporting this, and sorry for the typo. -- Bastien
Re: [O] Modifying the Beamer Exporter
Josiah Schwab jsch...@gmail.com writes:
For my subtitle example, \subtitle{} is a beamer command so I can make
a patch for that and see what people think.
It should be rather easy. With the old exporter you could get subtitles
with '\\' in beamer headlines, but this seems to have been removed
There is no beamer command for collaborators -- which is why you didn't
find it in the manual. But I almost always have collaborators on my
presentations, so I want to choose once how to render collaborators and
then ever after only have to set the content.
there is \and, though (pp. 93 of the Beamer manual). At least if
implemeting this, it should follow the recommended beamer way, IMO.
--Rasmus
--
. . . It begins of course with The Internet. A Net of Peers.
Re: [O] [BUG] A typo introduced in '6abc114f188267e4b804a3eca8794900eee66db0'
Bastien bzg at gnu.org writes: Applied, thanks for spotting and reporting this, and sorry for the typo. How about merging it into master as well? Regards, Achim.
Re: [O] Ordered List (Alphabetical) and HTML Export
Hello, Bastien b...@gnu.org writes: Josiah Schwab jsch...@gmail.com writes: I am using orgmode 8.0.3 with emacs 24.3. I frequently use ordered lists with alphabetical bullets. I have (setq org-list-allow-alphabetical t) in my .emacs. You should be able to export them to ol type=a lists now (from the maint branch, which will be the next stable release.) I don't think this is a good change. As explained in this thread, alphabetical lists are only a visual clue (and a bad one, IMO) which have no particular meaning wrt export (Org only recognizes `ordered', `unordered' and `description' lists). This is why this feature was never implemented in the last exporter. The OP can probably use CSS to get what he wants without hard coding it in the back-end. Moreover, it introduces an incompatibility with `latex' back-end, since this one won't enforce alphabetical bullets in the same situation. Therefore, I suggest to revert the patch. Regards, -- Nicolas Goaziou
Re: [O] [RFC] Introduce ox-i18n.el
Hello, Rasmus wrote: Nicolas Goaziou n.goaz...@gmail.com writes: I would like to move every variable and function related to internationalization (i.e smart quotes and translations) in a dedicated file (ox-i18n.el) instead of ox.el. Sounds good to me. +1 How about a more informative name where uninformed need not look up the meaning of i18n on Wikipedia? ox-translation(s) or something like that. . . +1 regarding the name i18n. It does not mean much to me. I'd favor ox-international(ization) or ox-strings or ox-translation(s) or ... Now, if i18n is some kind of standard, that's good as well. It then means a lot to people looking for translation strings. Best regards, Seb -- Sebastien Vauban
Re: [O] Ordered List (Alphabetical) and HTML Export
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Therefore, I suggest to revert the patch.
This simple .tex file allows for alphabetical enumeration.
Given that Org allows alphabetical list, the OP question is
natural and will come back. There is no clue in Org that
alphabetical lists are just visual clues.
I see no harm in supporting more flexibility where we can.
E.g. the attached .tex file produces alphabetical lists,
it should be simple enough to implement this in ox-latex.el.
Let me know what you think,
\documentclass[12pt]{article}
\usepackage{enumerate}
\begin{document}
\begin{enumerate}[a.]
\item Item 1
\item Item 2
\end{enumerate}
\end{document}
--
Bastien
Re: [O] [BUG] A typo introduced in '6abc114f188267e4b804a3eca8794900eee66db0'
Achim Gratz strom...@nexgo.de writes: Bastien bzg at gnu.org writes: Applied, thanks for spotting and reporting this, and sorry for the typo. How about merging it into master as well? Done. -- Bastien
Re: [O] [RFC] Introduce ox-i18n.el
Sebastien Vauban sva-news-D0wtAvR13HarG/idocf...@public.gmane.org writes: Sounds good to me. +1 Let's clearly think about what problem it is supposed to solve: if it is just discoverability for potential contributors, I don't think it's worth the split. -- Bastien
Re: [O] Ordered List (Alphabetical) and HTML Export
Bastien b...@altern.org writes: I see no harm in supporting more flexibility where we can. I should add that Org is a way for many LaTeX newbies to discover LaTeX, supporting alphabetical lists in LaTeX (and other backend) goes into this direction IMO. -- Bastien
Re: [O] evaluation context in call statements
Hi Eric On Mon, Jul 1, 2013 at 12:24 AM, Eric Schulte schulte.e...@gmail.com wrote: I've just pushed up a patch which implements this change. Call lines should now work exactly as named code blocks providing clarity, uniformity and the flexibility to run multiple identical call lines. This is very useful for me sometimes, thank you. I am now adapting my recent ERT that you disabled in the meantime due to your changes and therefore have a question. With C-c C-c on this call line #+NAME: src_block_location_shell sect call #+CALL: src_block_location_shell() the result is #+RESULTS: src_block_location_shell sect call : shell a:1, b:0, c:3, d:0, e:0 as expected. With org-test-with-expanded-babel-code I would expect the same but get #+RESULTS: : shell a:1, b:0, c:3, d:0, e:0 Should the behavior of org-test-with-expanded-babel-code not be aligned? Michael
[O] publishing sitemap: xml for google?
Google seems to want sitemap in xml, and with some given specifications. Is there something in orgmode publisher that can produce sitemap.xml instead of sitemap.html? Vikas
Re: [O] Ordered List (Alphabetical) and HTML Export
Hello,
Bastien wrote:
Bastien b...@altern.org writes:
I see no harm in supporting more flexibility where we can.
I should add that Org is a way for many LaTeX newbies to discover LaTeX,
supporting alphabetical lists in LaTeX (and other backend) goes into this
direction IMO.
Speaking of lists, when I showed Org mode this week-end to some hard LaTeX
guy, when he saw that we could choose between -, + and * for itemized
lists and between 1. and 1) for enumerated lists (whichever the depth
level), he suggested (for enumerated lists) that:
- 2nd level items should be:
(a) ...
(b) ...
(c) ...
(d) ...
- 3rd level items should be:
i. ...
ii. ...
iii. ...
iv. ...
or:
i. ...
ii. ...
iii. ...
iv. ...
- 4th level items should be:
A. ...
B. ...
C. ...
D. ...
It is what is implemented (following typographical rules?) for both French and
English (at least) in LaTeX. See:
--8---cut here---start-8---
\documentclass[english,french]{article}
\usepackage[T1]{fontenc}
\usepackage[utf8]{inputenc}
\usepackage{babel}
%
\begin{document}
\newcommand{\test}{%
\begin{enumerate}
\item
\begin{enumerate}
\item
\begin{enumerate}
\item
\begin{enumerate}
\item
\item
\item
\item
\end{enumerate}
\item
\item
\item
\end{enumerate}
\item
\item
\item
\end{enumerate}
\item
\item
\item
\end{enumerate}
}
\test{}
\selectlanguage{english}
\test{}
\end{document}
--8---cut here---end---8---
Dunno what you think about that, dunno if that's feasible and easy... But
wanted to share with you his point of view...
Best regards,
Seb
--
Sebastien Vauban
Re: [O] How do I create an agenda block for entries with a specific tag?
Hi Bastien, b...@gnu.org writes: Hi Alan, Alan Schmitt alan.schm...@polytechnique.org writes: I'm trying to find a way to create an agenda bloc (of type agenda) that is restricted to a set of tags. I tried using a skip function but (as I explained in another mail) I cannot get it to work. If someone has done it before, I'd gladly have a look at how to do it. You can try `org-agenda-tag-filter-preset' but I noticed some quirks with it, so maybe you'll have a change to report more bugs. Thank you for the suggestion, I'll give it a try. Best, Alan
Re: [O] Ordered List (Alphabetical) and HTML Export
Bastien b...@altern.org writes: Given that Org allows alphabetical list, the OP question is natural and will come back. Of course it will. And it had been discussed when the feature was introduced. I don't mind discussing it again, but there's nothing new on the table. I thought it had a FAQ entry: I was wrong. There is no clue in Org that alphabetical lists are just visual clues. The manual is one clue. Quoting section 2.7 Plain lists Org knows ordered lists, unordered lists, and description lists. * _Unordered_ list items start with '-', '+', or '*'(1) as bullets. * _Ordered_ list items start with a numeral followed by either a period or a right parenthesis(2), such as '1.' or '1)'(3). If you want a list to start with a different value (e.g., 20), start the text of the item with '[@20]'(4). Those constructs can be used in any item of the list in order to enforce a particular numbering. * _Description_ list items are unordered list items, and contain the separator ' :: ' to distinguish the description _term_ from the description. Alphabetical list is only a footnote in this paragraph and clearly not a type on its own. Merely a convenience. I see no harm in supporting more flexibility where we can. Only where it makes sense: this is not Org's job to replace CSS. Org is about structure, not appearance. Also, I do see harm. Introducing a feature in one major back-end means updating other major back-ends, for the sake of consistency. LaTeX (as in pdflatex) already does a good job to produce item markers. It is also configurable. Enforcing it is almost certainly a bad idea anyway. Let's think about it. If user has a non-nil `org-list-allow-alphabetical' and don't use them, should we make sure that items are _never_ alphabetical in the output (i.e. always numbers)? Also, what if users start asking for roman numbers as item markers? Greek letters? Of course, Org doesn't provide them in the buffer, but doesn't it sound silly to offer alphabetical lists only when so many other types are supported by the targeted languages? Shouldn't back-ends do the extra step in that direction? We must draw a clear line between what Org should and shouldn't do. IMO, this patch is on the wrong side of the line. Let me know what you think, I think the same as I did way back when we introduced this. I don't like alphabetical lists and I don't think we should offer more support for them. I would be happier if there was less possible bullets in Org syntax. This probably won't happen, but I see no reason to make the situation worse. Regards, -- Nicolas Goaziou
Re: [O] Standalone hyperlinked images in HTML export
Bastien b...@gnu.org writes: Kodi Arfer k...@arfer.net writes: I think I'm going to stop working on this issue for now, but at least what I've done could be helpful for anybody else who wants to go further down the rabbit hole. I can't follow this rabbit right now, but I hope someone can tidy things up a bit here (been there, done that...) I will have a look later today. Regards, -- Nicolas Goaziou
[O] advice needed: how do you guys sync org files between devices?
Hi all I have been using dropbox since i started using orgmode a few weeks ago (yeah im a neewb :)), which kinda works but i find it very annoying as it keeps creating conflicted copies, isnt reliable on my Linux main machine etc etc.. I was wondering what you guys do for syncing org files between PC's, Os's, devices (android etc).. Best Itai
Re: [O] publishing sitemap: xml for google?
Hi Vikas, Vikas Rawal vikasli...@agrarianresearch.org writes: Google seems to want sitemap in xml, and with some given specifications. Is there something in orgmode publisher that can produce sitemap.xml instead of sitemap.html? I don't think there is. You can have a look at contrib/lisp/ox-rss.el which should put you on the right track to code this. -- Bastien
Re: [O] Ordered List (Alphabetical) and HTML Export
(I've removed the feature from maint (and master) so that we can take the time to discuss it.) Nicolas Goaziou n.goaz...@gmail.com writes: Bastien b...@altern.org writes: Given that Org allows alphabetical list, the OP question is natural and will come back. Of course it will. And it had been discussed when the feature was introduced. I don't mind discussing it again, but there's nothing new on the table. I thought it had a FAQ entry: I was wrong. There is no clue in Org that alphabetical lists are just visual clues. The manual is one clue. Quoting section 2.7 Plain lists Org knows ordered lists, unordered lists, and description lists. * _Unordered_ list items start with '-', '+', or '*'(1) as bullets. * _Ordered_ list items start with a numeral followed by either a period or a right parenthesis(2), such as '1.' or '1)'(3). If you want a list to start with a different value (e.g., 20), start the text of the item with '[@20]'(4). Those constructs can be used in any item of the list in order to enforce a particular numbering. * _Description_ list items are unordered list items, and contain the separator ' :: ' to distinguish the description _term_ from the description. Alphabetical list is only a footnote in this paragraph and clearly not a type on its own. Merely a convenience. There is no clue in here. The way it is, the manual seems to suggest that alphabetical lists are supported (including in the export) as long as you have (setq org-list-allow-alphabetical t). We need to make the manual more explicit here. I see no harm in supporting more flexibility where we can. Only where it makes sense: this is not Org's job to replace CSS. Org is about structure, not appearance. Structure vs. appearance is a useful distinction, but very often it is overrated as a way to think about what a tool should/should not do. Also, I do see harm. Introducing a feature in one major back-end means updating other major back-ends, for the sake of consistency. LaTeX (as in pdflatex) already does a good job to produce item markers. It is also configurable. Enforcing it is almost certainly a bad idea anyway. Let's think about it. If user has a non-nil `org-list-allow-alphabetical' and don't use them, should we make sure that items are _never_ alphabetical in the output (i.e. always numbers)? Clearly no. Also, what if users start asking for roman numbers as item markers? ol type=I works fine. There are solutions for LaTeX too. Greek letters? Of course, Org doesn't provide them in the buffer, but doesn't it sound silly to offer alphabetical lists only when so many other types are supported by the targeted languages? Shouldn't back-ends do the extra step in that direction? No. This users can clearly understand: there are (at least human) limits to what we can implement. But this is different that saying him: Exporting a) b) c) as 1. 2. 3. is a feature, not a bug. We must draw a clear line between what Org should and shouldn't do. IMO, this patch is on the wrong side of the line. The patch was too bold, I give you that :) Let me know what you think, I think the same as I did way back when we introduced this. I don't like alphabetical lists and I don't think we should offer more support for them. I would be happier if there was less possible bullets in Org syntax. This probably won't happen, but I see no reason to make the situation worse. I would perfectly understand that it's too much maintainance ahead. This sounds perfectly reasonable to me -- and (perhaps paradoxically) less arbitrary than this does not fit Org's function, this is only aesthetic. Alphabetical lists are aesthetic sugar both in Org and its outputs, and Org is nice because it tries to keep the input and output both structurally and aesthetically similar. For example, horizontal lines in table are purely aesthetic, both in Org and its output. (They may have semantic value within the document, but just as alphabetical bullets.) Users expect Org to do a good job at putting the right horizontal lines in the output because it matters to them. Now: I tend to draw the line between what matters to users and what does not matter, not using the structure vs. aesthetic distinction, which is very relative. IOW, I'd ask the users if then want it or not. Ok, end of rant, back to code :) Thanks, -- Bastien
Re: [O] [PATCH] (update) Add :caption attribute to #+ATTR_LATEX property
Hi Feng, feng shu tuma...@gmail.com writes: Thanks for your help. This is V4 patch. Thanks for the updated patch -- there are more knowledgeable people for this area of the code, I'll let them apply/rework it or not. Best, -- Bastien
Re: [O] evaluation context in call statements
Michael Brand michael.ch.br...@gmail.com writes: Hi Eric On Mon, Jul 1, 2013 at 12:24 AM, Eric Schulte schulte.e...@gmail.com wrote: I've just pushed up a patch which implements this change. Call lines should now work exactly as named code blocks providing clarity, uniformity and the flexibility to run multiple identical call lines. This is very useful for me sometimes, thank you. I am now adapting my recent ERT that you disabled in the meantime due to your changes and therefore have a question. With C-c C-c on this call line #+NAME: src_block_location_shell sect call #+CALL: src_block_location_shell() the result is #+RESULTS: src_block_location_shell sect call : shell a:1, b:0, c:3, d:0, e:0 as expected. With org-test-with-expanded-babel-code I would expect the same but get #+RESULTS: : shell a:1, b:0, c:3, d:0, e:0 Should the behavior of org-test-with-expanded-babel-code not be aligned? Thanks for catching this. The export function (used by `org-test-with-expanded-babel-code') hadn't been updated to use call line names. I've just pushed up a fix. Best, -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Hide empty custom agenda sections
Hi Ken, Ken Mankoff mank...@gmail.com writes: Here is my custom agenda section. I'd like to have the DEADLINE and the REFILE only show up if items exist in those sections, not when they are empty. Actually, I guess I'd like this for all sections. I gave another quick look but this would be too complex to implement, even if I agree this would be nice to have. -- Bastien
Re: [O] org-id should require newcomment?
Hi Samuel, Samuel Wales samolog...@gmail.com writes: Debugger entered--Lisp error: (void-variable comment-region-function) default-value(comment-region-function) org-run-like-in-org-mode(org-insert-link) org-insert-link-global() call-interactively(org-insert-link-global nil nil) We'd need a more complete backtrace as I don't see how org-id is involved here. Thanks, -- Bastien
Re: [O] BUG (?): org capture insist *.org file changed in disk, wipes file each time
Hi Xebar, Xebar Saram zelt...@gmail.com writes: i have tried isolating the exact cause with no success. What if you move your files outside of the Dropbox directory (and update the capture templates accordingly)? -- Bastien
Re: [O] Ordered List (Alphabetical) and HTML Export
Bastien b...@gnu.org writes: (I've removed the feature from maint (and master) so that we can take the time to discuss it.) Fair enough. Let's think about it. If user has a non-nil `org-list-allow-alphabetical' and don't use them, should we make sure that items are _never_ alphabetical in the output (i.e. always numbers)? Clearly no. Interesting. As you know, pdflatex will produce, at some levels, alpha bullets for ordered lists, unless told otherwise. So, a. Item exported to 1. Item is wrong (hence your patch), but 1. Item exported to (a) Item isn't wrong (according to your answer). I just cannot make sense out of it. Either Org controls totally its output (my head hurts just thinking about it) or it doesn't. Your patch stands in-between: it's confusing. Also, what if users start asking for roman numbers as item markers? ol type=I works fine. There are solutions for LaTeX too. Of course there are solutions. For ODT, too. But I certainly don't want to open that can of worms. Greek letters? Of course, Org doesn't provide them in the buffer, but doesn't it sound silly to offer alphabetical lists only when so many other types are supported by the targeted languages? Shouldn't back-ends do the extra step in that direction? No. This users can clearly understand: there are (at least human) limits to what we can implement. But this is different that saying him: Exporting a) b) c) as 1. 2. 3. is a feature, not a bug. That's not what we are telling him. Likewise, we are not promising that exporting a - item will always call for a hyphen in the output: it may be a bullet instead. The only promise wrt bullet type and export is: export will preserve `ordered', `unordered' and `description' status of plain lists. That's all. Supporting this simple thing already requires hundreds lines of code in some export back-ends. Currently, in Org syntax, a) b) c) is an alias for ordered list, as 1) 2) 3). I would perfectly understand that it's too much maintainance ahead. This sounds perfectly reasonable to me -- and (perhaps paradoxically) less arbitrary than this does not fit Org's function, this is only aesthetic. OK. Count me in the too much maintenance ahead, then. Alphabetical lists are aesthetic sugar both in Org and its outputs, I do not agree with and its outputs part, since there was nothing in this direction before your patch. and Org is nice because it tries to keep the input and output both structurally and aesthetically similar. Does it? In Beamer back-end, a block is very different, visually speaking, from a headline. Now: I tend to draw the line between what matters to users and what does not matter, not using the structure vs. aesthetic distinction, which is very relative. IOW, I'd ask the users if then want it or not. There can be no line between what matters to users and what does not, because wherever you may put that line, someone will always be interested in a feature on the other side. Tell me about relative distinctions ;) I'll take structure vs. aesthetics anytime, because you can always argue about it. On the other hand, there's not much to say when someone tells you: this feature is very important in my daily work, let's provide it. Ok, end of rant, back to code :) Whatever the conclusion of this thread is, I hope it will make for a FAQ entry so we do not start it over every now and then. Regards, -- Nicolas Goaziou
Re: [O] evaluation context in call statements
Hi Eric
On Mon, Jul 1, 2013 at 3:11 PM, Eric Schulte schulte.e...@gmail.com wrote:
The export function (used by `org-test-with-expanded-babel-code') hadn't
been updated to use call line names. I've just pushed up a fix.
Thanks, attached the adapted patch to have my ERT again testing.
Michael
From 22633dd583f2a6270bff4e28eed81f1f0d6a36f5 Mon Sep 17 00:00:00 2001
From: Michael Brand michael.ch.br...@gmail.com
Date: Mon, 1 Jul 2013 15:50:15 +0200
Subject: [PATCH] Babel: use NAME for src block calls in ERT
* testing/examples/babel.org(use case of reading entry properties):
Adapt to use the new introduced #+NAME for src block calls.
* testing/lisp/test-ob-exp.el(ob-exp/use-case-of-reading-entry-properties):
Adapt to use the new introduced #+NAME for src block calls.
---
testing/examples/babel.org | 42 --
testing/lisp/test-ob-exp.el | 13 ++---
2 files changed, 34 insertions(+), 21 deletions(-)
diff --git a/testing/examples/babel.org b/testing/examples/babel.org
index de1980e..b1f1702 100644
--- a/testing/examples/babel.org
+++ b/testing/examples/babel.org
@@ -365,7 +365,10 @@ Here is a call line with more than just the results
exported.
:ID: cc5fbc20-bca5-437a-a7b8-2b4d7a03f820
:END:
-If overriden by caller then use :var from header else use entry property.
+Use case checked and documented with this test: During their
+evaluation the source blocks read values from properties from the
+entry where the call has been made unless the value is overridden with
+the optional argument of the caller.
** section
:PROPERTIES:
@@ -375,10 +378,14 @@ If overriden by caller then use :var from header else use
entry property.
Note: Just export of a property can be done with a macro: {{{property(a)}}}.
-#+CALL: src_block_location_shell(dummy_name=sect call)
-#+CALL: src_block_location_elisp[:session sect call]()
-- sect inline call_src_block_location_shell(dummy_name=sect inline)
-- sect inline call_src_block_location_elisp[:session sect inline]()
+#+NAME: src_block_location_shell sect call
+#+CALL: src_block_location_shell()
+
+#+NAME: src_block_location_elisp sect call
+#+CALL: src_block_location_elisp()
+
+- sect inline call_src_block_location_shell()
+- sect inline call_src_block_location_elisp()
*** subsection
:PROPERTIES:
@@ -386,20 +393,27 @@ Note: Just export of a property can be done with a macro:
{{{property(a)}}}.
:c:4
:END:
-#+CALL: src_block_location_shell(dummy_name=sub0 call)
-#+CALL: src_block_location_elisp[:session sub0 call]()
-- sub0 inline call_src_block_location_shell(dummy_name=sub0 inline)
-- sub0 inline call_src_block_location_elisp[:session sub0 inline]()
+#+NAME: src_block_location_shell sub0 call
+#+CALL: src_block_location_shell()
+
+#+NAME: src_block_location_elisp sub0 call
+#+CALL: src_block_location_elisp()
+
+- sub0 inline call_src_block_location_shell()
+- sub0 inline call_src_block_location_elisp()
+
+#+NAME: src_block_location_shell sub1 call
+#+CALL: src_block_location_shell(c=5, e=6)
+
+#+NAME: src_block_location_elisp sub1 call
+#+CALL: src_block_location_elisp(c=5, e=6)
-#+CALL: src_block_location_shell(dummy_name=sub1 call, c=5, e=6)
-#+CALL: src_block_location_elisp[:session sub1 call](c=5, e=6)
-- sub1 inline call_src_block_location_shell(dummy_name=sub1 inline, c=5, e=6)
-- sub1 inline call_src_block_location_elisp[:session sub1 inline](c=5, e=6)
+- sub1 inline call_src_block_location_shell(c=5, e=6)
+- sub1 inline call_src_block_location_elisp(c=5, e=6)
function definition
#+NAME: src_block_location_shell
-#+HEADER: :var dummy_name=workaround to get different result blocks
#+HEADER: :var a=(or (org-entry-get org-babel-current-src-block-location a
t) 0)
#+HEADER: :var b=(or (org-entry-get org-babel-current-src-block-location b
t) 0)
#+HEADER: :var c=(or (org-entry-get org-babel-current-src-block-location c
t) 0)
diff --git a/testing/lisp/test-ob-exp.el b/testing/lisp/test-ob-exp.el
index 416e229..d2541d3 100644
--- a/testing/lisp/test-ob-exp.el
+++ b/testing/lisp/test-ob-exp.el
@@ -217,7 +217,6 @@ Here is one at the end of a line. =2=
(should-not (string-match (regexp-quote i=\10\) result)
(ert-deftest ob-exp/use-case-of-reading-entry-properties ()
- :expected-result :failed ;; TODO: update for new call line result insertion
(org-test-at-id cc5fbc20-bca5-437a-a7b8-2b4d7a03f820
(org-narrow-to-subtree)
(let* ((case-fold-search nil)
@@ -227,27 +226,27 @@ Here is one at the end of a line. =2=
(sub1 a:1, b:2, c:5, d:0, e:6)
(func sub0))
;; entry section
- (should (string-match (concat \sect call\.*)\n: shell sect \n)
+ (should (string-match (concat _shell sect call\n: shell sect \n)
result))
- (should (string-match (concat sect call\\](.*)\n: elisp sect \n)
+ (should (string-match (concat _elisp sect call\n: elisp sect \n)
Re: [O] [PATCH] Append value of #+HTML_LINK_HOME to links relative with paths
Bastien b...@gnu.org writes: the attached patch appends the value of #+HTML_LINK_HOME to links with relative paths in the HTML export. I just pushed a new option `org-html-link-use-abs-url' for this, nil by default. Setting it to `t' will prepend the URL in HTML_LINK_HOME to the relative path in the exported output. -- Bastien
Re: [O] Ordered List (Alphabetical) and HTML Export
The buck stops with the maintainer of the files. It is only polite and good etiquette that any change that is not-trivial or not-routine be discussed beforehand. Sneaking in changes - just because it can be done in 5 minutes - is what a jerk would do.
Re: [O] evaluation context in call statements
Michael Brand michael.ch.br...@gmail.com writes: Hi Eric On Mon, Jul 1, 2013 at 3:11 PM, Eric Schulte schulte.e...@gmail.com wrote: The export function (used by `org-test-with-expanded-babel-code') hadn't been updated to use call line names. I've just pushed up a fix. Thanks, attached the adapted patch to have my ERT again testing. Michael Applied, Thanks -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Ordered List (Alphabetical) and HTML Export
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: Whatever the conclusion of this thread is, I hope it will make for a FAQ entry so we do not start it over every now and then. Here is it: http://orgmode.org/worg/org-faq.html#sec-11-5 -- Bastien
Re: [O] Ordered List (Alphabetical) and HTML Export
On 1.7.2013, at 13:49, Nicolas Goaziou n.goaz...@gmail.com wrote: Bastien b...@altern.org writes: Given that Org allows alphabetical list, the OP question is natural and will come back. Of course it will. And it had been discussed when the feature was introduced. I don't mind discussing it again, but there's nothing new on the table. I thought it had a FAQ entry: I was wrong. There is no clue in Org that alphabetical lists are just visual clues. The manual is one clue. Quoting section 2.7 Plain lists Org knows ordered lists, unordered lists, and description lists. * _Unordered_ list items start with '-', '+', or '*'(1) as bullets. * _Ordered_ list items start with a numeral followed by either a period or a right parenthesis(2), such as '1.' or '1)'(3). If you want a list to start with a different value (e.g., 20), start the text of the item with '[@20]'(4). Those constructs can be used in any item of the list in order to enforce a particular numbering. * _Description_ list items are unordered list items, and contain the separator ' :: ' to distinguish the description _term_ from the description. Alphabetical list is only a footnote in this paragraph and clearly not a type on its own. Merely a convenience. I see no harm in supporting more flexibility where we can. Only where it makes sense: this is not Org's job to replace CSS. Org is about structure, not appearance. Hi, as I have expressed earlier in a different thread, I think Nicolas is right here. The backend should decide how lists (ordered and unordered) are formatted, because this is the right way construct document structure. LaTeX and HTML are really the guide there. Lists are written with enumerate and itemize, and the style sets the bullets for different levels. When I write documents, I often choose only different types of bullets to make it easier for me to remember what level I am on. I think in almost all cases the structure created by a good document formatter will provide the cleanest and most readable output. So I would like to keep the current convention. If we must, we can have something like the [@N] to enforce a particular bullet style. - Carsten Also, I do see harm. Introducing a feature in one major back-end means updating other major back-ends, for the sake of consistency. LaTeX (as in pdflatex) already does a good job to produce item markers. It is also configurable. Enforcing it is almost certainly a bad idea anyway. Let's think about it. If user has a non-nil `org-list-allow-alphabetical' and don't use them, should we make sure that items are _never_ alphabetical in the output (i.e. always numbers)? Also, what if users start asking for roman numbers as item markers? Greek letters? Of course, Org doesn't provide them in the buffer, but doesn't it sound silly to offer alphabetical lists only when so many other types are supported by the targeted languages? Shouldn't back-ends do the extra step in that direction? We must draw a clear line between what Org should and shouldn't do. IMO, this patch is on the wrong side of the line. Let me know what you think, I think the same as I did way back when we introduced this. I don't like alphabetical lists and I don't think we should offer more support for them. I would be happier if there was less possible bullets in Org syntax. This probably won't happen, but I see no reason to make the situation worse. Regards, -- Nicolas Goaziou
Re: [O] Hide empty custom agenda sections
On Mon, Jul 1, 2013 at 9:38 AM, Bastien b...@gnu.org wrote: I gave another quick look but this would be too complex to implement, even if I agree this would be nice to have. Ok. Oh well. Thank you for considering and replying. -k.
Re: [O] Ordered List (Alphabetical) and HTML Export
Nicolas Goaziou n.goaz...@gmail.com writes: Let's think about it. If user has a non-nil `org-list-allow-alphabetical' and don't use them, should we make sure that items are _never_ alphabetical in the output (i.e. always numbers)? Clearly no. Interesting. As you know, pdflatex will produce, at some levels, alpha bullets for ordered lists, unless told otherwise. So, a. Item exported to 1. Item is wrong (hence your patch), but 1. Item exported to (a) Item isn't wrong (according to your answer). I just cannot make sense out of it. Either Org controls totally its output (my head hurts just thinking about it) or it doesn't. Your patch stands in-between: it's confusing. Maybe I misunderstand your question. If a user has (setq org-list-allow-alphabetical t) but don't use alphabetical lists, I don't see where is the problem. The only promise wrt bullet type and export is: export will preserve `ordered', `unordered' and `description' status of plain lists. That's all. Supporting this simple thing already requires hundreds lines of code in some export back-ends. I know. But speaking of structure vs. appearance: ODT has no notion of descriptive lists, this is just a visual emulation of it. So the choice of limiting the syntax to `ordered', `unordered', `description' is fine to me, but has some arbitrary ground too. Currently, in Org syntax, a) b) c) is an alias for ordered list, as 1) 2) 3). I would perfectly understand that it's too much maintainance ahead. This sounds perfectly reasonable to me -- and (perhaps paradoxically) less arbitrary than this does not fit Org's function, this is only aesthetic. OK. Count me in the too much maintenance ahead, then. Fair enough. Alphabetical lists are aesthetic sugar both in Org and its outputs, I do not agree with and its outputs part, since there was nothing in this direction before your patch. I was speaking of alphabetical lists in general: they are aesthetic sugar in HTML as well (i.e. there is no aol tag for alphabetical ordered list.) and Org is nice because it tries to keep the input and output both structurally and aesthetically similar. Does it? In Beamer back-end, a block is very different, visually speaking, from a headline. It does where it can. -- Bastien
[O] Shortkeys for shifting dates in Agenda view?
I often use the agenda view to postpone tasks to future dates, so technically I want to change the SCHEDULED or DEADLINE dates of one or several agenda lines to a future date, e. g. tomorrow. This is possible with the shortkey Shift-right arrow, however this forces me to move my right hand away from the main block of alphanumeric keys (QERTZ...) to the cursor block. As all other navigation commands are available diretctly in the QWERTZ-block (e. g. n for next line), this is disturbing for my typing. Is there a built-in key for that? Sure I could achieve that with CtrlC, Ctrl-S, +1, Ret, but this is 4 keystrokes instead of one... Any suggestions are welcome. It is clear that I could define a custom command, but as there are already that many commands defined by org-mode or other packages, it is difficult for me as a newbie to choose one that makes sense and is not used for something else.. Kind regards Martin
Re: [O] Oorg-export-generic.el and emphasize
Bastien b...@gnu.org writes: Maybe we could write an interactive exporter generator based on ox.el? Something with simple questions that will write the new ox-xxx.el file itself, with no fiddling from the user. Not immediately, at least. That'd be cool too, but why not do it via late binding so that the user doesn't even have to know code is being generated (at startup)? Or why not allow the ox.el code to accept a format string instead of a function? -- Wes Hardaker My Pictures: http://capturedonearth.com/ My Thoughts: http://pontifications.hardakers.net/
Re: [O] advice needed: how do you guys sync org files between devices?
On Jul 1, 2013 8:26 AM, Xebar Saram zelt...@gmail.com wrote: Hi all I have been using dropbox since i started using orgmode a few weeks ago (yeah im a neewb :)), which kinda works but i find it very annoying as it keeps creating conflicted copies, isnt reliable on my Linux main machine etc etc.. I was wondering what you guys do for syncing org files between PC's, Os's, devices (android etc).. Best Itai Hi, For keeping org files in sync between real computers, version control seems to me the obvious way to go. It gets you sync and history. There is perhaps a bit of a learning curve, but time spent learning widely useful tools is time well spent :-) bzr and hg are (superficially?) easier and git is pretty dominant. For Android, mobile org push to android has worked for me (syncing over SD rather than the cloud or WebDAV). Pulling from Android hasn't been reliable enough for me to use it. HTH, Brian vdB
Re: [O] [PATCH] Use geiser for babel scheme evaluation.
Eric Schulte writes: I've just applied this patch. I don't think external dependencies are a problem if they offload language integration work to a dedicated external package. The more babel can re-use existing packages the better, e.g., common lisp code blocks are just thin wrappers around slime, but they work exceedingly well with almost no babel-side coding or maintenance. Would you mind keeping the byte-compile clean? --8---cut here---start-8--- Compiling /home/org-mode/lisp/ob-scheme.el... In org-babel-scheme-get-buffer-impl: ob-scheme.el:81:5:Warning: reference to free variable `geiser-impl--implementation' In org-babel-scheme-execute-with-geiser: ob-scheme.el:130:21:Warning: `message' called with 4 args to fill 3 format field(s) ob-scheme.el:133:15:Warning: assignment to free variable `geiser-repl--repl' ob-scheme.el:134:15:Warning: assignment to free variable `geiser-impl--implementation' In org-babel-execute:scheme: ob-scheme.el:163:25:Warning: reference to free variable `geiser-default-implementation' ob-scheme.el:164:30:Warning: reference to free variable `geiser-active-implementations' In end of data: ob-scheme.el:181:1:Warning: the following functions are not known to be defined: run-geiser, geiser-mode, geiser-eval-region, geiser-repl-exit --8---cut here---end---8--- Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] advice needed: how do you guys sync org files between devices?
On Mon, Jul 1, 2013 at 1:10 PM, Brian van den Broek brian.van.den.br...@gmail.com wrote: On Jul 1, 2013 8:26 AM, Xebar Saram zelt...@gmail.com wrote: Hi all I have been using dropbox since i started using orgmode a few weeks ago (yeah im a neewb :)), which kinda works but i find it very annoying as it keeps creating conflicted copies, isnt reliable on my Linux main machine etc etc.. I was wondering what you guys do for syncing org files between PC's, Os's, devices (android etc).. Best Itai Hi, For keeping org files in sync between real computers, version control seems to me the obvious way to go. It gets you sync and history. There is perhaps a bit of a learning curve, but time spent learning widely useful tools is time well spent :-) bzr and hg are (superficially?) easier and git is pretty dominant. For Android, mobile org push to android has worked for me (syncing over SD rather than the cloud or WebDAV). Pulling from Android hasn't been reliable enough for me to use it. HTH, Brian vdB Hi, To me, a rather reliable way (without version control) has been unison. Easy to set up and learn, fast. Only problem is that it doesn't deal well (actually, at all) with merges (i.e. a file that has been modified in both computers). But I agree with Brian that in the long run, though harder to learn, git is a charm. Tomas
Re: [O] advice needed: how do you guys sync org files between devices?
Hi Itai, zelt...@gmail.com writes: Hi all I have been using dropbox since i started using orgmode a few weeks ago (yeah im a neewb :)), which kinda works but i find it very annoying as it keeps creating conflicted copies, isnt reliable on my Linux main machine etc etc.. I was wondering what you guys do for syncing org files between PC's, Os's, devices (android etc).. Best Itai I use a combination of dropbox (between the computers ---all running Linux) and version control, and for syncing with Android I use mobile org. With Dropbox I've had a some conflicted copy issues; this is annoying (and is the sort of thing that would have been solved much more easily with version control) but happens very rarely. What I like about this is that my frequent changes in org files get propagated without the need for an explicit version control command. However, for safety and for tracking, I run a nightly job with bazaar where I commit all changes (this is done in only one of the machines, of course). This has actually proven extremely useful when, by mistake, I have deleted a complete subtree and only realized maybe a month later. HTH, R. -- Ramon Diaz-Uriarte Department of Biochemistry, Lab B-25 Facultad de Medicina Universidad Autónoma de Madrid Arzobispo Morcillo, 4 28029 Madrid Spain Phone: +34-91-497-2412 Email: rdia...@gmail.com ramon.d...@iib.uam.es http://ligarto.org/rdiaz
Re: [O] org-mode and python pandas
Eric Schulte writes: | |A |B |C | |---+--+--+--| | 0 | 0.827817 | 0.664009 | 0.089161 | | 1 | 0.170031 | 0.729214 | 0.110918 | | 2 | 0.575918 | 0.863924 | 0.757536 | | 3 | 0.682722 | 0.774445 | 0.992041 | What happens if you add :results table to your code block? Would that be sufficient? The problem is that he's trying to consume human-readable output. The alignment in this output is done with spaces, not tabs (as Org would expect). There are more problems considering that the numbers likely lose precision in this format (nota bene: there are other Babel languages that have that same problem). The default value should be to convert multi-line output to tables, the :results table option above will force this conversion in case it is currently not taking place due to the default header arguments in use. Since there are no tabs in there, it is impossible to skip empty cells like the first one (they'd have to be written as instead, as would be cells that should contain literal spaces). 2. Add to pandas the option of globally influencing the text formatting so that it outputs something more parsable by org-mode. This sounds promising, if pandas support csv output that will be correctly parsed by Org-mode. The package already has CSV export, so one could use that. I don't know if you could echo the result directly to the output, all examples revolve around putting the CSV into a file. For Org, TSV output would be more natural. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
[O] Very minor bug in undo applied to org table
Hello, This seems like a very minor bug, but I thought I'd report it anyway in case it has wider ramifications that I'm unaware of. Create an org file with the following lines: | 1 | #+TBLFM: $1=2 Open it and type C-c C-c on the TBLFM line. This replaces the '1' in the table with a '2'. Now type C-_ (for undo). Not only does the '2' revert to a '1', but a second line reading '#+TBLFM: $1=2' is inserted directly under the first. An second C-_ removes this second TBLFM line. Regards, Paul PS. I'm using Emacs 24.2.1 and Org-mode release_8.0.3-331-gf7e6f1 and I tested with the minimal org-mode set-up from http://orgmode.org/manual/Feedback.html.
Re: [O] org-mode and python pandas
Achim Gratz strom...@nexgo.de writes:
2. Add to pandas the option of globally influencing the text
formatting so that it outputs something more parsable by org-mode.
This sounds promising, if pandas support csv output that will be
correctly parsed by Org-mode.
The package already has CSV export, so one could use that. I don't know
if you could echo the result directly to the output, all examples
revolve around putting the CSV into a file. For Org, TSV output would
be more natural.
Something like:
from pandas import DataFrame
from numpy.random import rand
from sys import stdout
df = DataFrame(rand(10,3), columns = list('abc'))
df
df.to_csv(stdout, sep=\t, header = True, cols=(1,2))
I was completely unable to get ob-python working this morning, so I
haven't tested it. I'm using python3, build in python mode and elpy.
In any case, the csv route might be better, as Pandas doesn't print
the table if it's too big (try changing 10 to 1000 above).
--
Powered by magic pixies!
Re: [O] Process diagrams with dot and some glue using Org-mode
* Rick Frankel r...@rickster.com wrote: The solution is to specify the range on the call: #+call: graph-from-table(nodes=example-node-table[2:-1],graph=example-graph[2:-1]) [...] Thank you *very* much for your explanations! You helped me to understand the method that good that I will soon start documenting it on Worg. -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: get Memacs from https://github.com/novoid/Memacs https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
Re: [O] advice needed: how do you guys sync org files between devices?
* Tomas Grigera tgrig...@gmail.com wrote: To me, a rather reliable way (without version control) has been unison. Easy to set up and learn, fast. Only problem is that it doesn't deal well (actually, at all) with merges (i.e. a file that has been modified in both computers). I am using Unison File Synchronizer in a cron-job[1] to sync my Org-mode files with a 24/7-server in the cloud (my *own* server). All computers are being synced with this server. This works as long as I do not forget to save all and exit Emacs before I leave/shut down/hibernate my machines. This way, I do prevent two changes happening on different machines (sync conflict). Unison does not offer any merge functionality. However, you can easily use third party tools to handle merge conflicts (Emacs, vim, ...). But I agree with Brian that in the long run, though harder to learn, git is a charm. Totally agree. I am using gitwatch[2] to automatically commit any changes in my org-mode files. However, I do this only on my main working machine and ignore git information when syncing with Unison (multiple reasons, complicated to explain). In case you want to manage all of your Org-mode files with git (in contrast to me), you can also choose to auto-push/pull those git commits to other machines as well. This should even merge the most simple conflicts without user interaction. I do not have experience with this method by myself. There are several interesting solution candidates out there: Sparkle Share and several script on github. HTH 1. https://en.wikipedia.org/wiki/Crond 2. https://github.com/nevik/gitwatch -- mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode: get Memacs from https://github.com/novoid/Memacs https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
Re: [O] org-id should require newcomment?
Hi Bastien, I require 'org-id, then store the link, then insert the link, and that is the backtrace I get. Please tell me what else I can provide. If nobody else can confirm it, I will require 'newcomment and work around the bug. :) Samuel On 7/1/13, Bastien b...@gnu.org wrote: Hi Samuel, Samuel Wales samolog...@gmail.com writes: Debugger entered--Lisp error: (void-variable comment-region-function) default-value(comment-region-function) org-run-like-in-org-mode(org-insert-link) org-insert-link-global() call-interactively(org-insert-link-global nil nil) We'd need a more complete backtrace as I don't see how org-id is involved here. Thanks, -- Bastien -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
[O] Incorrect sum of times in table
Hello, I noticed a case where the sum of two times in a table does not give the correct answer. To see this, create an org file with the following lines: | 0:00:31 | | 0:00:30 | |-| | | Open it and type C-+ C-y in the empty cell of the table. The answer inserted is 0:01:00 instead of 0:01:01. Regards, Paul PS. I'm using Emacs 24.2.1 and Org-mode release_8.0.3-331-gf7e6f1 and I tested with the minimal org-mode set-up from http://orgmode.org/manual/Feedback.html.
[O] [PATCH] ob-core.el: fix confirm before eval when using a function
* lisp/ob-core.el: (org-babel-check-confirm-evaluate): Fix handling of `org-confirm-babel-evaluate' when it is a function. When `org-confirm-babel-evaluate' is a function, this construct: (or (when (functionp org-confirm-babel-evaluate) (funcall org-confirm-babel-evaluate lang block-body)) org-confirm-babel-evaluate) will always be true -- if the function evaluates to nil, the `or' will evaluate to the value of `org-confirm-babel-evaluate', which is non-nil. Change the `when' to an `if' and move a closing parenthesis so that when `org-confirm-babel-evaluate' is a function its return value will always be used, even if nil. TINYCHANGE --- lisp/ob-core.el | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/lisp/ob-core.el b/lisp/ob-core.el index 16a122e..bde9553 100644 --- a/lisp/ob-core.el +++ b/lisp/ob-core.el @@ -301,10 +301,10 @@ name of the code block. (noeval (or ,eval-no ,eval-no-export)) (query (or (equal ,eval query) (and ,export (equal ,eval query-export)) -(when (functionp org-confirm-babel-evaluate) - (funcall org-confirm-babel-evaluate - ,lang ,block-body)) -org-confirm-babel-evaluate)) +(if (functionp org-confirm-babel-evaluate) +(funcall org-confirm-babel-evaluate + ,lang ,block-body) + org-confirm-babel-evaluate))) (code-block (if ,info (format %s ,lang) )) (block-name (if ,name (format (%s) ,name) ))) ,@body))) -- 1.8.3.1
[O] Using different image format given the export backend
Dear Orgers,
As explain is this forum thread
http://stackoverflow.com/questions/13611837/how-can-i-use-different-image-formats-for-different-exports-in-org-mode,
I'd also like to use different image format given the export backend. I
have used the answer provided in the forum to have something like that
#+CAPTION: Toto figure
#+NAME: fig::toto
#+ATTR_LATEX: :width 0.38\textwidth
#+BEGIN_SRC emacs-lisp :exports results :results value raw
(case (and (boundp 'backend) backend)
(nil )
(latex [[file:./toto.pdf]]
(html [[file:./toto.png]]))
#+END_SRC
While the export is fine with html, when I export to latex-pdf, it
gives me :
\includegraphics[width=.9\linewidth]{./toto.pdf}
not respecting the latex width attribute nor caption. I am using the new
exporter and I wonder if I can get something working in the same way.
Thanks a lot for your help,
Xavier
--
|
|__ GARRIDO Xavier Laboratoire de l'Accélérateur Linéaire
/\ NEMO Université Paris-Sud 11
/--\garr...@lal.in2p3.fr UMR 8607
| garr...@in2p3.fr Batiment 200
|__ +33 1.64.46.84.2891898 Orsay Cedex, France
Re: [O] Using different image format given the export backend
Hello, #+CAPTION: Toto figure #+NAME: fig::toto #+ATTR_LATEX: :width 0.38\textwidth #+BEGIN_SRC emacs-lisp :exports results :results value raw (case (and (boundp 'backend) backend) (nil ) (latex [[file:./toto.pdf]] (html [[file:./toto.png]])) #+END_SRC I do it like this: (defun vb-massage-includegraphics (str backend opts) (replace-regexp-in-string .png} .pdf} str)) (add-hook 'org-export-filter-final-output-functions 'vb-massage-includegraphics) And then, simply refer to the png file in the .org file. Then nothing happens for the html output, but on latex export, the regexp matches the '}' and includes the .pdf file instead. That is extremely ugly, and makes plenty of assumptions, most of all that the .pdf file exists. And it should probably test for the value of 'backend'. But for personal use, it is convenient ... /v -- Vincent Beffara
Re: [O] [PATCH] summarize timestamps in column view
Hi Bastien, Bastien b...@gnu.org writes: It hardly counts as a tiny change, though, as I count 25 lines... I'm afraid the patch is larger than what we can accept without paperwork. Would you mind signing the FSF copyright assignment (or telling me if you did so already for Emacs)? I don't mind assigning copyright to FSF at all. I've not done so until now. http://orgmode.org/cgit.cgi/org-mode.git/plain/request-assign-future.txt That'll leave some time so that someone else can test the patch and report about it :) Sounds good. I'll email ass...@gnu.org after I write this. Should I revive this thread when the assignment is acknowledged? Thanks for looking at the patch, -- Pedro
[O] Help with babel and gnuplot
Hello, I hesitate to ask this question as I feel I should be able to work it out myself, but I don't seem to be able to. I'm trying to get gnuplot working through babel. I'm using Emacs 24.2.1 and I have Org-mode release_8.0.3-331-gf7e6f1 installed in ~/org-mode. I'm running /usr/bin/emacs -Q -l minimal-org.el test.org where minimal-org.el contains just (setq debug-on-error t debug-on-signal nil debug-on-quit nil) (add-to-list 'load-path (expand-file-name ~/org-mode/lisp)) (org-babel-do-load-languages 'org-babel-load-languages '((gnuplot . t))) and test.org contains just #+begin_src gnuplot :results silent plot x #+end_src When I press C-c C-c inside the source block I get Debugger entered--Lisp error: (file-error Cannot open load file gnuplot) require(gnuplot) org-babel-execute:gnuplot(plot x ... org-babel-execute-src-block(nil) org-babel-execute-src-block-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) I've been assuming it's a path issue, but ~/org-mode/lisp/ob-gnuplot.elc is present and I have gnuplot installed in /usr/bin/gnuplot. Also, other languages (eg. python) work okay through babel. Any advice would be greatly appreciated. Kind regards, Paul
Re: [O] [PATCH] ob-core.el: fix confirm before eval when using a function
Richard Hansen writes: When `org-confirm-babel-evaluate' is a function, this construct: (or (when (functionp org-confirm-babel-evaluate) (funcall org-confirm-babel-evaluate lang block-body)) org-confirm-babel-evaluate) will always be true -- if the function evaluates to nil, the `or' will evaluate to the value of `org-confirm-babel-evaluate', which is non-nil. Indeed, thanks for catching it. This had actually been fixed before in exactly the same way, then replaced by a cond form and then replaced again (wrongly) with an or form… I should have looked at the history of that code more closely. Fixed in maint and master. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: [O] Help with babel and gnuplot
Paul Stansell writes: Debugger entered--Lisp error: (file-error Cannot open load file gnuplot) require(gnuplot) This tells you that gnuplot.el is nowhere to be found in your load-path. It usually comes with gnuplot, but either the install didn't put it into the correct place on your system or you no longer have that location in load-path. You can get an up-to-date copy here: https://github.com/bruceravel/gnuplot-mode Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] Incorrect sum of times in table
Paul Stansell paulstans...@gmail.com writes: Hello, I noticed a case where the sum of two times in a table does not give the correct answer. To see this, create an org file with the following lines: | 0:00:31 | | 0:00:30 | |-| | | Open it and type C-+ C-y in the empty cell of the table. The answer inserted is 0:01:00 instead of 0:01:01. I think you mean C-c +. The problem is that these things are calculated as decimal hours, using floating point arithmetic and you get truncation towards 0 when the value is printed out as an integer. The format in org-table-sum is (format %d:%02d:%02d h m s) but s is 0.... and it gets formatted as 0. It might be better to use (format %.0f:%02.0f:%02.0f h m s) i.e. as floating point with no places after the decimal point (in which case the decimal point does not seem to be output). But there may be other problems that I have not thought of. It might be even better to round the floating point number to the nearest integer and use %d formats instead: (format %d:%02d:%02d (round h) (round m) (round s)) -- Nick
[O] Possible bug geiser for scheme evaluation
I just updated from git (previous update on June 30 about 08:00 EDT) and had trouble loading emacs. Attached is a backtrace for the referenced possible bug. My .emacs has the following ; Babel set for when I get around to learning how to use it (org-babel-do-load-languages 'org-babel-load-languages '((awk . t) (calc . t) (C . t) (clojure . t) (emacs-lisp . t) (latex . t) (ledger . t) (lisp . t) (org . t) (scheme . t) (sh . t))) If I comment out (scheme . t) - no problem loading emacs. Set up Windows 7, home premium; c:/emacs/emacs-24.2 GNU Emacs 24.2.1 (i386-mingw-nt6.1.7601) of 2012-08-28 on MARVIN Org mode version Org-mode version 8.0.3 (release_8.0.3-333-g8387b3 @ c:/cygwin/home/Charlie/elisp/Org-Mode/lisp/) at /c/cygwin/home/charlie/.elisp/org-mode which is update using git my .emacs does load the cygwin org-mode version. Charlie Millar Debugger entered--Lisp error: (file-error Cannot open load file geiser-impl) load(geiser-impl) load-library(geiser-impl) byte-code(\300\301!\210\302\303!\207 [require ob load-library geiser-impl] 2) require(ob-scheme) #[(pair) A\303@!\211\203 \304\305\306 P!!\202% \307\305\310 P!!\210\307\305\311 P!!*\207 [pair lang active symbol-name require intern ob- fmakunbound org-babel-execute: org-babel-expand-body:] 5]((scheme . t)) mapc(#[(pair) A\303@!\211\203 \304\305\306 P!!\202% \307\305\310 P!!\210\307\305\311 P!!*\207 [pair lang active symbol-name require intern ob- fmakunbound org-babel-execute: org-babel-expand-body:] 5] ((awk . t) (calc . t) (C . t) (clojure . t) (emacs-lisp . t) (latex . t) (ledger . t) (lisp . t) (org . t) (scheme . t) (sh . t))) org-babel-do-load-languages(org-babel-load-languages ((awk . t) (calc . t) (C . t) (clojure . t) (emacs-lisp . t) (latex . t) (ledger . t) (lisp . t) (org . t) (scheme . t) (sh . t))) eval-buffer(#buffer *load* nil c:/Users/Charlie/AppData/Roaming/.emacs.d/init.el nil t) ; Reading at buffer position 11470 load-with-code-conversion(c:/Users/Charlie/AppData/Roaming/.emacs.d/init.el c:/Users/Charlie/AppData/Roaming/.emacs.d/init.el t t) load(c:/Users/Charlie/AppData/Roaming/.emacs.d/init t t) #[0 \205\262 \306=\203 \307\310Q\202; \311=\204 \307\312Q\202; \313\307\314\315#\203* \316\202; \313\307\314\317#\203: \320\nB\321\202; \316\322\323\322\211#\210 \322=\203a \324\325\326\307\327Q!\\323\322\211#\210 \322=\203` \210 \203\243 \330 !\331\232\203\243 \332 !\211\333P\334!\203} \211\202\210 \334!\203\207 \202\210 \314\262\203\241 \335 \\203\237 \336\337 #\210\340\341!\210\266\f?\205\260 \314 \323\342\322\211#)\262\207 [init-file-user system-type delayed-warnings-list user-init-file inhibit-default-init inhibit-startup-screen ms-dos ~ /_emacs windows-nt /.emacs directory-files nil ^\\.emacs\\(\\.elc?\\)?$ ~/.emacs ^_emacs\\(\\.elc?\\)?$ (initialization `_emacs' init file is deprecated, please use `.emacs') ~/_emacs t load expand-file-name init file-name-as-directory /.emacs.d file-name-extension elc file-name-sans-extension .el file-exists-p file-newer-than-file-p message Warning: %s is newer than %s sit-for 1 default] 7 \n\n(fn)]() command-line() normal-top-level()
Re: [O] Standalone hyperlinked images in HTML export
Hello, Kodi Arfer k...@arfer.net writes: The manual explains in Images in HTML export that you can make an image a hyperlink like this: [[file:highres.jpg][file:thumb.jpg]] where thumb.jpg becomes the img 'src' and highres.jpg becomes the a 'href'. One might infer it should also be possible to link to something other than an image, like this: [[http://gnu.org][http://example.com/gnu-head.jpg]] For example, try exporting this file: #+begin_src org Some initial text. [[http://example.com/a.png]] Some text between images 1 and 2. [[http://eeyup.com][http://example.com/b.png]] Some text between images 2 and 3. http://example.com/c.png Some trailing text. #+end_src You do indeed get a href=http://eeyup.com;img src=http://example.com/b.png; alt=b.png //a in the output, but the exporter doesn't regard the image as standalone, so it doesn't get put in a div (or, in HTML5 mode, figure) like the others, and if you add a #+CAPTION, no caption will be included. Indeed. Would you mind testing the following patch against master? It should fix the issues. Regards, -- Nicolas Goaziou From b20ae9f2cc1af67250af9917541b071ab778f36f Mon Sep 17 00:00:00 2001 From: Nicolas Goaziou n.goaz...@gmail.com Date: Mon, 1 Jul 2013 22:51:26 +0200 Subject: [PATCH] ox-html: Fix standalone hyperlinked images * lisp/ox-html.el (org-html-inline-images): Change default value and remove `maybe'. (org-html-format-inline-image): Remove functions. (org-html--wrap-image, org-html--format-image, org-html-inline-image-p): New functions. (org-html-latex-environment, org-html-latex-fragment): Use new functions. (org-html-standalone-image-p): Use new functions. Also remove an unused optional argument. (org-html-link, org-html-paragraph): Correctly export hyperlinked images. This patch permits the back-end to recognize links like: [[http://orgmode.org][http://orgmode.org/img/org-mode-unicorn-logo.png]] as standalone, so they can get wrapped within a proper environment and get captions. Thanks to Kodi Arfer for reporting it. --- lisp/ox-html.el | 257 +++- 1 file changed, 124 insertions(+), 133 deletions(-) diff --git a/lisp/ox-html.el b/lisp/ox-html.el index 4753e66..b8d927f 100644 --- a/lisp/ox-html.el +++ b/lisp/ox-html.el @@ -713,16 +713,14 @@ When nil, the links still point to the plain `.org' file. Links :: Inline images -(defcustom org-html-inline-images 'maybe +(defcustom org-html-inline-images t Non-nil means inline images into exported HTML pages. This is done using an img tag. When nil, an anchor with href is used to -link to the image. If this option is `maybe', then images in links with -an empty description will be inlined, while images with a description will -be linked only. +link to the image. :group 'org-export-html - :type '(choice (const :tag Never nil) - (const :tag Always t) - (const :tag When there is no description maybe))) + :version 24.4 + :package-version '(Org . 8.1) + :type 'boolean) (defcustom org-html-inline-image-rules '((file . \\.\\(jpeg\\|jpg\\|png\\|gif\\|svg\\)\\') @@ -1326,39 +1324,43 @@ attributes with a nil value will be omitted from the result. \ quot; (org-html-encode-plain-text item (setcar output (format %s=\%s\ key value -(defun org-html-format-inline-image (src info optional - caption label attr standalone-p) - Format an inline image from SRC. -CAPTION, LABEL and ATTR are optional arguments providing the -caption, the label and the attribute of the image. -When STANDALONE-P is t, wrap the img.../ into a div.../div. - (let* ((id (if (not label) - (format id=\%s\ (org-export-solidify-link-text label - (attr (concat attr - (format src=\%s\ src) - (cond - ((string-match \\alt= (or attr )) ) - ((string-match ^ltxpng/ src) - (format alt=\%s\ - (org-html-encode-plain-text - (org-find-text-property-in-string - 'org-latex-src src - (t (format alt=\%s\ - (file-name-nondirectory src)) - (html5-fancy (and (org-html-html5-p info) - (plist-get info :html-html5-fancy -(cond - (standalone-p - (let ((img (org-html-close-tag img attr info))) - (format (if html5-fancy - \nfigure%s%s%s\n/figure - \ndiv%s class=\figure\%s%s\n/div) - id (format \np%s/p img) - (if (and caption (not (string= caption ))) - (format (if html5-fancy -\nfigcaption%s/figcaption - \np%s/p) caption) - (t (org-html-close-tag img (concat attr id) info) +(defun org-html--wrap-image (contents info optional caption label) + Wrap CONTENTS string within an appropriate environment for images. +INFO is a plist used as a communication channel. When optional +arguments CAPTION and LABEL are given, use them for caption and +\id\ attribute. + (let ((html5-fancy (and (org-html-html5-p info) + (plist-get info
[O] Date format when exporting to LaTeX?
Hi all,
I recently upgraded from 7.8.03 to current master (actually
release_8.0.3-299-g1d606c0) and now when I export to LaTeX, the following:
#+DATE: %Y-%m-%d
no longer causes the date to be the current date in ISO 8601 format. It
now simply prints %Y-%m-%d.
I tried:
#+DATE: {{{date(%Y-%m-%d)}}}
but got Circular macro expansion: date. I also tried:
#+BIND: org-export-date-timestamp-format %Y-%m-%d
but that did nothing (no confirmation prompt, nothing).
Setting org-export-date-timestamp-format as a file-local variable didn't
work either.
Any hints?
Thanks,
Richard
Re: [O] Possible bug geiser for scheme evaluation
Hi Charles, Charles mill...@verizon.net writes: If I comment out (scheme . t) - no problem loading emacs. The new ob-scheme.el relies on geiser: http://www.nongnu.org/geiser/ Adding geiser to your load-path should fix the problem. -- Bastien
Re: [O] Incorrect sum of times in table
Hi Nick, Nick Dokos ndo...@gmail.com writes: I think you mean C-c +. The problem is that these things are calculated as decimal hours, using floating point arithmetic and you get truncation towards 0 when the value is printed out as an integer. The format in org-table-sum is (format %d:%02d:%02d h m s) but s is 0.... and it gets formatted as 0. It might be better to use (format %.0f:%02.0f:%02.0f h m s) i.e. as floating point with no places after the decimal point (in which case the decimal point does not seem to be output). But there may be other problems that I have not thought of. It might be even better to round the floating point number to the nearest integer and use %d formats instead: (format %d:%02d:%02d (round h) (round m) (round s)) Both solutions work -- we don't need to fear other problems here, `org-table-sum' is pretty isolated, so I'd say please go ahead! and fix this in maint. Thanks, -- Bastien
Re: [O] Standalone hyperlinked images in HTML export
On 2013 Jul 01 Mon 5:01:46 PM -0400, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Kodi Arfer k...@arfer.net writes: The manual explains in Images in HTML export that you can make an image a hyperlink like this: [[file:highres.jpg][file:thumb.jpg]] where thumb.jpg becomes the img 'src' and highres.jpg becomes the a 'href'. One might infer it should also be possible to link to something other than an image, like this: [[http://gnu.org][http://example.com/gnu-head.jpg]] For example, try exporting this file: #+begin_src org Some initial text. [[http://example.com/a.png]] Some text between images 1 and 2. [[http://eeyup.com][http://example.com/b.png]] Some text between images 2 and 3. http://example.com/c.png Some trailing text. #+end_src You do indeed get a href=http://eeyup.com;img src=http://example.com/b.png; alt=b.png //a in the output, but the exporter doesn't regard the image as standalone, so it doesn't get put in a div (or, in HTML5 mode, figure) like the others, and if you add a #+CAPTION, no caption will be included. Indeed. Would you mind testing the following patch against master? It should fix the issues. I tried it with captions, :html5-fancy, and paths to images as well as path to non-images. All looks good. You're awesome. I see your patch also affects math export somehow, but I haven't tested that.
Re: [O] Refiling list items
On 6/30/13, Bastien b...@gnu.org wrote: I confirm the following bug in git master. Fixed, thanks. Thanks. Does this work for the OP? Now there is a new bug. When the region is not active, I expect an ordinary refile. What happens instead is that the entire entry gets copied to the target location and the line point is on gets deleted. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. Denmark: free Karina Hansen NOW.
Re: [O] [PATCH] (update) Add :caption attribute to #+ATTR_LATEX property
Hello,
feng shu tuma...@gmail.com writes:
Thanks for your help. This is V4 patch.
Thanks for the update. More comments below.
+@item :caption
+By default, you should use @code{#+caption} keyword to add a table caption.
+If you want to add caption with complex or special latex commands, you can
use
+@code{:caption} attribute. It will precedence over @code{#+caption} keyword.
+It should be set with raw latex command and nothing in it will be
+interpreted by Org.
You need to use upper cases for keywords: @code{#+CAPTION}. Also,
sentences are expected to end with two spaces and latex should be typed
@LaTeX{}. Here is a suggestion (note that I'm not a wording expert):
@code{#+CAPTION} keyword is the simplest way to set a caption for
a table (@pxref{Images and tables}). If you need more advanced commands
for that task, you can use @code{:caption} attribute instead. Its value
should be raw @LaTeX{} code. It has precedence over @code{#+CAPTION}.
+When export the below example to latex, the table caption will be set
+with latex command @code{\bicaption@{Heading A@}@{Heading B@}} instead of
+@code{#+CAPTION} keywords.
In the example below, @LaTeX{} command @code{\bicaption@{Heading
A@}@{Heading B@}} will set the caption. (I think you can drop the rest
of the sentence).
-@code{:width} and @code{:height} attributes. It is also possible to add any
-other option with the @code{:options} attribute, as shown in the following
-example:
+@code{:width} and @code{:height} attributes. If you want to set image
+caption with special latex command, you can use @code{:caption} attribute,
+for example:
Besides the missing two spaces at the end of the sentence, I suggest the
following:
You can specify specify image width or height with, respectively,
@code{:width} and @code{:height} attributes. It is also possible to add any
other option with the @code{:options} attribute, as shown in the following
example:
EXAMPLE
If you need a specific command for the caption, use @code{:caption}
attribute. It will override standard @code{#+CAPTION} value, if any.
EXAMPLE?
Also, you don't seem to document the feature for special blocks.
- (short (org-export-get-caption element t)))
-(cond
- ((and (not main) (equal label-str )) )
- ((not main) (concat label-str \n))
- ;; Option caption format with short name.
- (short (format \\caption[%s]{%s%s}\n
- (org-export-data short info)
- label-str
- (org-export-data main info)))
- ;; Standard caption format.
- (t (format \\caption{%s%s}\n label-str (org-export-data main
info))
+ (short (org-export-get-caption element t))
+ (caption-from-attr-latex (org-export-read-attribute :attr_latex
element :caption)))
+(cond ((org-string-nw-p caption-from-attr-latex)
+(concat caption-from-attr-latex \n))
+ ((and (not main) (equal label-str )))
Why do you drop the return value (empty string) here?
Regards,
--
Nicolas Goaziou
Re: [O] fill paragraph: math and latex environments
Nicolas Goaziou n.goaziou at gmail.com writes:
Hello,
azw at fastmail.fm (Albert Z. Wang) writes:
Thanks for the clarification! Is there an easy way to have them be
treated as full-fledged environments? I usually prefer to use the above
for unnumbered display equations since it reduces visual clutter and
looks closer to the intent.
No, there's no easy way.
Making \[...\] an element would mean that \[...\] cannot exist anymore
within a paragraph. I'm not sure it's worth it.
Also, I think it's good, in this case, to have both an inlined and
a non-inlined version for the same thing.
Regards,
Hi Nicolas,
I hope you don't mind me giving my view on this so long after the initial
posts, but I been trying, without success, to get fill-paragraph to
recognise \[...\] as boundaries to it's function.
You say in your post
Making \[...\] an element would mean that \[...\] cannot exist anymore
within a paragraph. I'm not sure it's worth it.
Also, I think it's good, in this case, to have both an inlined and
a non-inlined version for the same thing.
In Lamport's book on Latex he explains that \[...\] is for display style
maths, that is, for maths that is not inside a paragraph but presented on
it's own line. Inside a paragraph one should use $...$ or \(...\) as they
are for inline equations (and Latex treats them the same). For display
style maths Latex uses
\begin{displaymath}
...
\end{displaymath}
and, for less typing,
\[
...
\]
and both are treated the same, ie., both produce the exact same output in
the processed latex document.
This being the case, my wish would be to see org mode treat
\[
...
\]
the same as
\begin{displaymath}
...
\end{displaymath}
and not fill past it's boundaries.
Kind regards,
Paul
Re: [O] Date format when exporting to LaTeX?
Hi Richard,
I recently upgraded from 7.8.03 to current master (actually
release_8.0.3-299-g1d606c0) and now when I export to LaTeX, the following:
#+DATE: %Y-%m-%d
no longer causes the date to be the current date in ISO 8601 format. It
now simply prints %Y-%m-%d.
I tried:
#+DATE: {{{date(%Y-%m-%d)}}}
This also doesn't work for, but I've never used it before. But it
should be {{{time(.)}}} cf.
http://orgmode.org/cgit.cgi/org-mode.git/commit/?h=maint
but got Circular macro expansion: date. I also tried:
#+BIND: org-export-date-timestamp-format %Y-%m-%d
This works for me in Org-mode version 8.0.3
(release_8.0.3-309-gabacff). Is the problem still persistent after
trying from emacs -q or after trying M-x org-reload?
#+BIND: org-export-date-timestamp-format %Y-%m-%d
#+DATE: 2013-07-01 Mon
* test
#+begin_src emacs-lisp
(setq org-export-date-timestamp-format %B %e, %Y)
(set (make-local-variable 'org-export-allow-bind-keywords) t)
#+end_src
–Rasmus
--
The Kids call him Billy the Saint
Re: [O] Possible bug geiser for scheme evaluation
Hi Bastien, On 7/1/2013 5:14 PM, Bastien wrote: Hi Charles, Charles mill...@verizon.net writes: If I comment out (scheme . t) - no problem loading emacs. The new ob-scheme.el relies on geiser: http://www.nongnu.org/geiser/ Adding geiser to your load-path should fix the problem. Worked like a charm. Thank you. Charlie
Re: [O] Date format when exporting to LaTeX?
On 2013-07-01 17:46, Rasmus wrote:
Hi Richard,
I recently upgraded from 7.8.03 to current master (actually
release_8.0.3-299-g1d606c0) and now when I export to LaTeX, the following:
#+DATE: %Y-%m-%d
no longer causes the date to be the current date in ISO 8601 format. It
now simply prints %Y-%m-%d.
I tried:
#+DATE: {{{date(%Y-%m-%d)}}}
This also doesn't work for, but I've never used it before. But it
should be {{{time(.)}}} cf.
http://orgmode.org/cgit.cgi/org-mode.git/commit/?h=maint
I tried:
#+DATE: {{{time(%Y-%m-%d)}}}
and that did work. Thank you!
Unfortunately this does not work quite right with org-mode 7.8.03, so
I'll have to make sure everyone I collaborate with upgrades their
org-mode. :(
but got Circular macro expansion: date. I also tried:
#+BIND: org-export-date-timestamp-format %Y-%m-%d
This works for me in Org-mode version 8.0.3
(release_8.0.3-309-gabacff). Is the problem still persistent after
trying from emacs -q or after trying M-x org-reload?
#+BIND: org-export-date-timestamp-format %Y-%m-%d
#+DATE: 2013-07-01 Mon
* test
#+begin_src emacs-lisp
(setq org-export-date-timestamp-format %B %e, %Y)
(set (make-local-variable 'org-export-allow-bind-keywords) t)
#+end_src
This works for me too, but:
* I must provide a date. If I don't have that #+DATE line then the
LaTeX exporter uses \today, and that ignores
org-export-date-timestamp-format. I don't want to have to specify
a date; I want it to use today's date. (The {{{time()}}} macro
works well for this, but I was unaware of its existence until now.)
* org-export-allow-bind-keywords must be true. Adding it as a
file-local variable is not an acceptable solution in my
circumstance.
I didn't have to set this variable when I was using 7.8.03 --
org-mode simply asked me (once) if it was OK to bind the
variables. I miss that behavior.
Thanks again for letting me know about {{{time(.)}}}.
-Richard
Re: [O] [PATCH] (update) Add :caption attribute to #+ATTR_LATEX property
Thanks all the people! This is V5!
On Tue, Jul 2, 2013 at 5:38 AM, Nicolas Goaziou n.goaz...@gmail.com wrote:
Hello,
feng shu tuma...@gmail.com writes:
Thanks for your help. This is V4 patch.
Thanks for the update. More comments below.
+@item :caption
+By default, you should use @code{#+caption} keyword to add a table
caption.
+If you want to add caption with complex or special latex commands, you
can use
+@code{:caption} attribute. It will precedence over @code{#+caption}
keyword.
+It should be set with raw latex command and nothing in it will be
+interpreted by Org.
You need to use upper cases for keywords: @code{#+CAPTION}. Also,
sentences are expected to end with two spaces and latex should be typed
@LaTeX{}. Here is a suggestion (note that I'm not a wording expert):
@code{#+CAPTION} keyword is the simplest way to set a caption for
a table (@pxref{Images and tables}). If you need more advanced commands
for that task, you can use @code{:caption} attribute instead. Its value
should be raw @LaTeX{} code. It has precedence over @code{#+CAPTION}.
I think it's much good than mine. For me, writing documentation is a painful
thing.
+When export the below example to latex, the table caption will be set
+with latex command @code{\bicaption@{Heading A@}@{Heading B@}} instead
of
+@code{#+CAPTION} keywords.
In the example below, @LaTeX{} command @code{\bicaption@{Heading
A@}@{Heading B@}} will set the caption. (I think you can drop the rest
of the sentence).
-@code{:width} and @code{:height} attributes. It is also possible to
add any
-other option with the @code{:options} attribute, as shown in the
following
-example:
+@code{:width} and @code{:height} attributes. If you want to set image
+caption with special latex command, you can use @code{:caption}
attribute,
+for example:
Besides the missing two spaces at the end of the sentence, I suggest the
following:
You can specify specify image width or height with, respectively,
@code{:width} and @code{:height} attributes. It is also possible to add
any
other option with the @code{:options} attribute, as shown in the
following
example:
EXAMPLE
If you need a specific command for the caption, use @code{:caption}
attribute. It will override standard @code{#+CAPTION} value, if any.
EXAMPLE?
Also, you don't seem to document the feature for special blocks.
- (short (org-export-get-caption element t)))
-(cond
- ((and (not main) (equal label-str )) )
- ((not main) (concat label-str \n))
- ;; Option caption format with short name.
- (short (format \\caption[%s]{%s%s}\n
- (org-export-data short info)
- label-str
- (org-export-data main info)))
- ;; Standard caption format.
- (t (format \\caption{%s%s}\n label-str (org-export-data main
info))
+ (short (org-export-get-caption element t))
+ (caption-from-attr-latex (org-export-read-attribute :attr_latex
element :caption)))
+(cond ((org-string-nw-p caption-from-attr-latex)
+(concat caption-from-attr-latex \n))
+ ((and (not main) (equal label-str )))
Why do you drop the return value (empty string) here?
It's my mistake!
Regards,
--
Nicolas Goaziou
0001-Add-caption-attribute-to-ATTR_LATEX-property.patch
Description: Binary data
[O] [PATCH] Let =`make'= be an option to =`org-latex-pdf-process'=.
0001-Let-make-be-an-option-to-org-latex-pdf-process.patch Description: Binary data
Re: [O] Shortkeys for shifting dates in Agenda view?
Martin elwood...@web.de writes: I often use the agenda view to postpone tasks to future dates, so technically I want to change the SCHEDULED or DEADLINE dates of one or several agenda lines to a future date, e. g. tomorrow. This is possible with the shortkey Shift-right arrow, however this forces me to move my right hand away from the main block of alphanumeric keys (QERTZ...) to the cursor block. As all other navigation commands are available diretctly in the QWERTZ-block (e. g. n for next line), this is disturbing for my typing. Is there a built-in key for that? Sure I could achieve that with CtrlC, Ctrl-S, +1, Ret, but this is 4 keystrokes instead of one... _is_ the built-in key! If you don't like where it's located, you can rebind `org-agenda-date-prompt' to a different key in the agenda map. As you noted, almost the entire keyboard is already bound in agenda mode, but if you hit C-h m and look at the bindings, you'll see a couple of capital letters are free. Then in an eval-after-load block (or org-agenda-mode-hook) you could call: (define-key org-agenda-mode-map (kbd K) org-agenda-date-prompt) Or whatever you pick. That ought to work... Eric Any suggestions are welcome. It is clear that I could define a custom command, but as there are already that many commands defined by org-mode or other packages, it is difficult for me as a newbie to choose one that makes sense and is not used for something else.. Kind regards Martin
[O] Broken Link on worg (org-contribute)
The link to the emacs elisp coding conventions on the page http://orgmode.org/worg/org-contribute.html was incorrect. I have attached a patch which fixes the link. Best, Josiah From a6a3872b0bcf5971dfc9cb51f5562cdff57a723e Mon Sep 17 00:00:00 2001 From: Josiah Schwab jsch...@gmail.com Date: Mon, 1 Jul 2013 22:25:06 -0700 Subject: [PATCH] org-contribute: Fix 404 for elisp coding conventions page --- org-contribute.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/org-contribute.org b/org-contribute.org index 829b1a1..080b1f1 100644 --- a/org-contribute.org +++ b/org-contribute.org @@ -120,7 +120,7 @@ them. ** Coding conventions -Org is part of Emacs, so any contribution should follow the [[http://www.gnu.org/software/emacs/elisp/html_node/Coding-Conventions.html][GNU Emacs Lisp +Org is part of Emacs, so any contribution should follow the [[http://www.gnu.org/software/emacs/manual/html_node/elisp/Coding-Conventions.html][GNU Emacs Lisp coding conventions]] described in Emacs manual. ** Sending patch with git -- 1.8.3.2
