Re: [O] Custom formatting during export
Hi Gabe,
Macro replacements [[http://orgmode.org/manual/Macro-replacement.html]]
should be what you are looking for.
For example, the macro
#+MACRO: pkg $1
would be called by
{{{pkg(PkgName)}}}
You can also use this to format your input for one or multiple backends
#+MACRO: M @@latex:\$1{@@$2@@latex:}@@
Let me know if this helps.
Best
Julian
On 03.09.2014 06:36, Gabe Becker wrote:
orgmode developers and power-users,
I'd like to be able to declare custom entities (apologies if I'm using
that term incorrectly) within the text of an orgmode document which I
can specify custom formatting for when my .org is exported, e.g. to PDF
or HTML.
I have a background in Docbook, so the analogue there would be defining
a custom xml tag and then extending the XSL files to handle it as
desired. Please see the following snippet:
* section title
Here is some text, but I want [specialthing: this bit here] to be
formatted differently than [newanddifferent: this other big over here].
Where I would have defined specific custom formatting rules for
"specialthing" and "newanddifferent" type entities.
Is there a way to do this in orgmode? If not, it seems like it would be
a very useful feature (at least to me:) ). Note: I don't care about the
syntax as long as the result is the same.
Thanks for your help,
~G
--
Computational Biologist
Genentech Research
Re: [O] Title of org files in github not recognized
Hi Waldemar,
Thanks, I'm looking forward to see all these improvements also in github.
Best wishes
Julian
On 02.05.2014 07:44, Waldemar Quevedo wrote:
Hi, yes this issue would be fixed once Github upgrades the Ruby
implementation of the parser.
To upgrade the version it takes making a pull request to the
github/markup repository so that they bump the version and do the
release, but it takes some time before the upgrade is validated
(security checks, etc...)
There another couple of issues that I would like it that they make it to
Github, so once having those tackled I'll see if I can ask one of the
maintainers to help out planning for an update soon.
Cheers
On Fri, May 2, 2014 at 12:21 AM, Sebastien Vauban
mailto:sva-n...@mygooglest.com>> wrote:
Julian Gehring wrote:
> On 01.05.2014 14:17, Sebastien Vauban wrote:
>> Julian Gehring wrote:
>>> How I can convince github to recognize the '#+TITLE:' field of an
>>> org-file? This should be a 'h1' heading, while it is currently
>>> treated as normal text (for example, see
>>>
https://github.com/julian-gehring/vignettes/blob/master/README.org).
>>> I know that this is a problem of the parsing on github's site, but
>>> is anyone aware of a good solution?
>>
>> That was supposed to be solved.
>>
>> See https://github.com/wallyqs/org-ruby/issues/3
>
> Nice. So it seems that github is using an older version of
org-ruby. Is it
> clear what the update policy/cycle of github for softwares like
org-ruby is?
Unfortunately, not to me... ;-)
Best regards,
Seb
--
Sebastien Vauban
Re: [O] Title of org files in github not recognized
Hi Seb, Nice. So it seems that github is using an older version of org-ruby. Is it clear what the update policy/cycle of github for softwares like org-ruby is? Best wishes Julian On 01.05.2014 14:17, Sebastien Vauban wrote: Julian Gehring wrote: How I can convince github to recognize the '#+TITLE:' field of an org-file? This should be a 'h1' heading, while it is currently treated as normal text (for example, see https://github.com/julian-gehring/vignettes/blob/master/README.org). I know that this is a problem of the parsing on github's site, but is anyone aware of a good solution? That was supposed to be solved. See https://github.com/wallyqs/org-ruby/issues/3 Best regards, Seb
[O] Title of org files in github not recognized
Hi, How I can convince github to recognize the '#+TITLE:' field of an org-file? This should be a 'h1' heading, while it is currently treated as normal text (for example, see https://github.com/julian-gehring/vignettes/blob/master/README.org). I know that this is a problem of the parsing on github's site, but is anyone aware of a good solution? Best wishes Julian
[O] [PATCH] German localization of sections (was: Re: ox-bibtex: Customization of HTML heading)
Hi Batien,
Thank you for extending this!
I have attached the patch for translating the section heading into German.
Best wishes
Julian
On 17.04.2014 17:26, Bastien wrote:
Hi Julian,
Julian Gehring writes:
Would it be reasonable to have an additional option for customizing the
HTML heading of the reference section for ox-bibtex?
Yes -- I added the word "References" to `org-export-dictionary',
and ox-bibtex.el is now using it.
Can you provide a patch to translate it into german?
Thanks!
>From c4d4ef97f7a61703936386fc446307686a96d89b Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Sun, 20 Apr 2014 10:48:07 +0200
Subject: [PATCH] ox.el: German localization of 'References' section
* lisp/ox.el: Add German localization of the 'References' section
Suggested by Batien Guerry
---
lisp/ox.el | 1 +
1 file changed, 1 insertion(+)
diff --git a/lisp/ox.el b/lisp/ox.el
index 35f4972..7c6a96d 100644
--- a/lisp/ox.el
+++ b/lisp/ox.el
@@ -5488,6 +5488,7 @@ them."
("zh-CN" :html "代码%d " :utf-8 "代ç %d "))
("References"
("fr" :ascii "References" :default "Références"))
+ ("de" :default "Quellen"))
("See section %s"
("da" :default "jævnfør afsnit %s")
("de" :default "siehe Abschnitt %s")
--
1.9.1
Re: [O] babel and long-running computations
Hi Christoph, Generally, org-babel is suited for long running computations. Its caching can help you avoid rerunning code chunks. And long runtime does not conflict with the idea of reproducible research, it just may be not very comfortable for the user. In my experience, one can avoid your problems best by structuring your code and analysis in small, logical steps and save intermediate results, such that you can restart in the middle of your analysis. Otherwise, all other frameworks for reproducible research I know have the same "limitations". Best wishes Julian On 17/04/14 10:45, Christoph Groth wrote: > Dear all, > > I’m considering the use of org-babel for “reproducible science”. Is > anyone successfully using org-babel for research that involves > calculations that typically take a few minutes up to several hours on a > single CPU (i.e. up to a few minutes on a cluster)? It seems to me that > currently org-babel is not well suited for such an usage profile, but > I’d love to be taught otherwise. > > Many thanks, > Christoph > > >
[O] ox-bibtex: Customization of HTML heading
Hi, Would it be reasonable to have an additional option for customizing the HTML heading of the reference section for ox-bibtex? By default, a 'References' gets inserted in the HTML file. I would suggest to include an option for omitting the heading complete (and letting the user define the context in which it occurs). Optionally, one could also think about an option for changing the heading text, instead of hardcoding it. Any thoughts regarding this? Best wishes Julian
Re: [O] [bug] Tangling a LaTeX code block creates a .latex file
Hi,
This seems to be more general, since it also occurs for e.g. python
source blocks. Tangling a python source code block with the argument
=:tangle yes= produces a '.python' instead of a '.py' file (at least
with 8.2.5c).
Best wishes
Julian
On 01/29/2014 09:19 PM, Sebastien Vauban wrote:
Hello,
This one is quite new: tangling a code block in `latex' language now
produces a file with a `.latex' extension, instead of the common `.tex'
extension.
Example:
--8<---cut here---start->8---
* Letter composition
#+begin_src latex :noweb yes :tangle yes
\documentclass{article}
\usepackage[utf8x]{inputenc}
\usepackage[T1]{fontenc}
% ...
#+end_src
--8<---cut here---end--->8---
Best regards,
Seb
PS- Org-mode version 8.2.5e (release_8.2.5e-111-g72ad52)
Re: [O] ox-bibtex: Allow for missing bibtex style
Hi Nicolas, Please excuse the late reply. The patch works great, can't find anything that would need further tweaking. Best wishes Julian On 12/21/2013 04:15 PM, Nicolas Goaziou wrote: Hello, Julian Gehring writes: I would like to add this feature, if I knew how to program in lisp... Would you like to work on this together? I could contribute on the side of documenting and testing, if this helps. Fair enough. Here is a patch for you to test. Regards,
Re: [O] problem of path in using ox-bibtex
Hi Joseph, Have you tried to specify the full path without the expansion of '~' (i.e. replacing the "~" with "/home/USER/" or equivalent)? At least, this seems to eliminate the error message of bibtex2html failing. Best wishes Julian On 01/05/2014 09:35 AM, Joseph Vidal-Rosset wrote: Hello the list, Is it possible to define a single and unique path by default when one use ox-bibtex? I meet the following problem. At the end of an org file, in order to use ox-bibtex to get bibliographical references , I have this line: #+BIBLIOGRAPHY: references plain option:-a limit:t It means that I need to have the file references.bib in the same folder of this paper.org's . I have tried to write to give the path of the default folder of my references.bib: #+BIBLIOGRAPHY: ~/Dropbox/Bibliographiers/references plain option:-a limit:t but in this case biblatex2html fails. It means that I have to copy the references.bib from folder to folder and I do not like this solution. I do not doubt that there is a better solution, but I do not see it. Your help is welcome, Best wishes, Jo.
Re: [O] ox-bibtex: Allow for missing bibtex style
Hi Nicolas, It sounds interesting. Would you want to provide a patch for that? I would like to add this feature, if I knew how to program in lisp... Would you like to work on this together? I could contribute on the side of documenting and testing, if this helps. Best wishes Julian
[O] ox-bibtex: Allow for missing bibtex style
Hi,
I recently started using ox-bibtex, and was impressed by the nice and
simple functionality.
Currently, it is required to specify a bibtex style when defining the
bibliography:
#+BIBLIOGRAPHY: bibfilebasename stylename optional-options
Would it be reasonable to allow for a missing 'stylename'? Such that if
'stylename' is missing or 'nil', that:
a) 'stylename' is passed with the '-s' argument to 'bibtex2html' and
b) the line '\bibliographystyle{stylename}' is not added to the latex
output? Then, the bibtex style can be overwritten by default settings
of the latex document. At the moment, this results in a warning about
two conflicting styles.
Would be happy to hear your opinion about this suggestion.
Best wishes
Julian
[O] Publish setup in file
Hi, Is there a way to specify publishing options (e.g. the location) at the level of the file to be published, instead doing this globally in the =.emacs= file? I have many projects in orgmode which consist of a single file. I have been looking at #+SETUPFILE (which seems to deal only with org files) and publishing templates (which seem not to be able to change all project options, as the target location). Does anyone of you have an idea on how to do this? Best wishes Julian
Re: [O] Converting Org to Sweave (*.Rnw)
Hi Chuck,
thanks, what you describe seems to me like a already quite elaborated
solution. I would be very interested in your existing implementation
for this.
As you mentioned, there will probably have to be a trade-off between the
syntax/functionality of Org-mode/babel and Sweave. But already a
solution being able to handle to obvious cases of header argumnets would
be step forward in bringing Org-mode even closer to R Sweave.
Best
Julian
On 07/17/2012 06:05 PM, cbe...@tajo.ucsd.edu wrote:
Julian Gehring writes:
Hi,
is there a way to convert Org-mode files with R code blocks to the
Sweave ('*.Rnw') [1] file format or has anyone planned to work on
this?
First, there is this thread:
http://comments.gmane.org/gmane.emacs.orgmode/7931
and then there is this
http://yihui.name/knitr/demo/org/
But I wanted more, and I think the new exporter provides some awesome
possibilities, so...
I have put together a rudimentary exporter for Sweave and for brew style
chunks and hope to have several of the knitr chunk flavors supported
soon. I've not looked closely, but I think pander can be supported, too.
The basic idea is to use the new export engine. See
http://orgmode.org/worg/dev/org-export-reference.html
for background.
The e-latex, e-html, and other modes are used as parent backends and
e-latex-rnw, e-html-brew, etc are *derived* backends. It is pretty easy
to hitch a ride on the work done to make a parent backend and then add a
minimal definition of the chunk formatting.
The only tricky bit is getting Babel to help in the process, but not
interfere. I want Babel to porcess non-R src blocks and clean out R
#+RESULTS blocks, but not strip out the header args, as these may be
wanted (as you suggest below) to inform the chunk arguments. I've
managed this by advise'ing org-babel-exp-do-export to do special
handling of R src blocks.
I've not yet delved into translating the headers into code chunk
arguments. Some like 'width' seem pretty obvious. Others like the
:exports + :results translation may take some thought. And there are
some idioms in Sweave and kntir that have not corresponding idiom in org
(which is a strong motive for doing this work) like 'dev' in knitr as
well as ':cache yes' versus 'cache=T', which are false cognates, so to
speak
So far, what I've done is do add a header arg like this:
Here is an inline chunk: src_R{ rnorm(1) } which the brew export
renders as <%= rnorm(1) -%> (i.e. print the result, but do not place
a line break after the result), making a non-printing version of this
is done by using this src_R[ :ravel <% -%> ]{ rnorm(1) }, which
renders as <% rnorm(1) -%>.
or this
: #+name: aCachedChunk
: #+begin_src R :ravel cache=T
: x <- rnorm(1e7)
: #+end_src
which is rendered as
<>=
x <- rnorm(1e7)
@ %def
when using the Sweave style exporters.
However, Nicolas *just* added support for #+ATTR_SOMETHING, where
SOMETHING is a user defined key. And I incline to the view that using
something like
: #+attr_ravel: cache=T
: #+name: aCachedChunk
: #+begin_src R
: x <- rnorm(1e7)
: #+end_src
might be preferred.
Anyway, I'll try to get a version up where you can have a look at it
sometime today.
I am keen to collaborate on this.
Chuck
Sweave is heavily used in the R community in terms of literate
programming, and has a tight integration into current package building
workflows. Essentially, the file format is a latex document, with
designated code chunks.
Since Org/Org-babel offers a very similar feature set, and already
covers the export to latex, I was wondering whether anyone is working
on some code that would rewrite the code block headers in the export?
In the R community, I have seen a lot of interest in such an exporter,
that would allow to write the documentation in Org itself and later
export it to several backends, including Sweave to integrate it in the
R package.
If anyone has some comments regarding this or is interested in working
on this, please let me know. My colleagues and I would be very
interested in contributing in projects in this direction.
Best
Julian
[1] http://en.wikipedia.org/wiki/Sweave
[O] Converting Org to Sweave (*.Rnw)
Hi,
is there a way to convert Org-mode files with R code blocks to the
Sweave ('*.Rnw') [1] file format or has anyone planned to work on this?
Sweave is heavily used in the R community in terms of literate
programming, and has a tight integration into current package building
workflows. Essentially, the file format is a latex document, with
designated code chunks.
Since Org/Org-babel offers a very similar feature set, and already
covers the export to latex, I was wondering whether anyone is working on
some code that would rewrite the code block headers in the export? In
the R community, I have seen a lot of interest in such an exporter, that
would allow to write the documentation in Org itself and later export it
to several backends, including Sweave to integrate it in the R package.
If anyone has some comments regarding this or is interested in working
on this, please let me know. My colleagues and I would be very
interested in contributing in projects in this direction.
Best
Julian
[1] http://en.wikipedia.org/wiki/Sweave
Re: [O] orgweb/Changes: broken formatting of code blocks
Hi Bastien, thanks, the formatting of the code block example looks fine now. Best Julian On 04/11/2012 12:19 PM, Bastien wrote: Hi Julian, Julian Gehring writes: at the changes page of the orgmode website, some of the code block formatting seems to be broken (see http://orgmode.org/Changes.html#sec-3). I recently pushed a fix for this. It looks okay to me know. Can you check again? Can anyone please check if the attached patch would fix this? With my local setup, this yields a proper display of the code blocks. Or do the commas in front of the code lines have a meaning that I am simply missing? The content of the #+begin_src block is inserted as an example, which looks the right thing to do to me. Thanks,
[O] orgweb/Changes: broken formatting of code blocks
Hi, at the changes page of the orgmode website, some of the code block formatting seems to be broken (see http://orgmode.org/Changes.html#sec-3). Can anyone please check if the attached patch would fix this? With my local setup, this yields a proper display of the code blocks. Or do the commas in front of the code lines have a meaning that I am simply missing? Best Julian >From 72e27909e8a01bdd44a85f05826a052e1dbe698a Mon Sep 17 00:00:00 2001 From: Julian Gehring Date: Tue, 10 Apr 2012 21:44:35 +0200 Subject: [PATCH] Changes.org: fix code block formatting --- Changes.org | 80 +-- 1 file changed, 40 insertions(+), 40 deletions(-) diff --git a/Changes.org b/Changes.org index 409fa95..adc1438 100644 --- a/Changes.org +++ b/Changes.org @@ -241,60 +241,60 @@ combines with =visual-line-mode=. This results in the following behavior. #+begin_src org - ,#+property: var foo=1 - ,#+property: var+ bar=2 + #+property: var foo=1 + #+property: var+ bar=2 - ,#+begin_src emacs-lisp - , (+ foo bar) - ,#+end_src + #+begin_src emacs-lisp +(+ foo bar) + #+end_src - ,#+results: - ,: 3 + #+results: + : 3 - ,#+begin_src emacs-lisp - , (org-entry-get (point) "var" t) - ,#+end_src + #+begin_src emacs-lisp +(org-entry-get (point) "var" t) + #+end_src - ,#+results: - ,: foo=1 bar=2 + #+results: + : foo=1 bar=2 - ,* overwriting a file-wide property - , :PROPERTIES: - , :var: foo=7 - , :END: + * overwriting a file-wide property +:PROPERTIES: +:var: foo=7 +:END: - ,#+begin_src emacs-lisp - , foo - ,#+end_src + #+begin_src emacs-lisp +foo + #+end_src - ,#+results: - ,: 7 + #+results: + : 7 - ,#+begin_src emacs-lisp - , (org-entry-get (point) "var" t) - ,#+end_src + #+begin_src emacs-lisp +(org-entry-get (point) "var" t) + #+end_src - ,#+results: - ,: foo=7 + #+results: + : foo=7 - ,* appending to a file-wide property - , :PROPERTIES: - , :var+: baz=3 - , :END: + * appending to a file-wide property +:PROPERTIES: +:var+: baz=3 +:END: - ,#+begin_src emacs-lisp - , (+ foo bar baz) - ,#+end_src + #+begin_src emacs-lisp +(+ foo bar baz) + #+end_src - ,#+results: - ,: 6 + #+results: + : 6 - ,#+begin_src emacs-lisp - , (org-entry-get (point) "var" t) - ,#+end_src + #+begin_src emacs-lisp +(org-entry-get (point) "var" t) + #+end_src - ,#+results: - ,: foo=1 bar=2 baz=3 + #+results: + : foo=1 bar=2 baz=3 #+end_src *** =org-agenda-custom-commands= has a default value ([[git:b3de2dbb953dcadacafeb179899ab9df184da4ff][git]]) -- 1.7.10
Re: [O] [PATCH] org.texi: Fix missing links and formatting in 'Exporting' section
Hi Bernt,
thank you for spotting this. This hunk is really not doing anything useful.
Best
Julian
On 04/08/2012 04:43 PM, Bernt Hansen wrote:
Julian Gehring writes:
From 40344d3dd27af520ba09516b72e6cbb06a37e780 Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Sun, 8 Apr 2012 15:24:47 +0200
Subject: [PATCH] org.texi: Fix missing links and formatting in 'Exporting'
section
Hi Julian,
Why is the last hunk in this patch useful? Doesn't it just add a
trailing blank?
@@ -11588,7 +11587,7 @@ two table styles with the names
@samp{TableWithHeaderRowAndColumn} and
@samp{TableWithFirstRowandLastRow}. (@strong{Important:} The OpenDocument
styles needed for producing the above template have been pre-defined for you.
These styles are available under the section marked @samp{Custom Table
-Template} in @file{OrgOdtContentTemplate.xml}
+Template} in @file{OrgOdtContentTemplate.xml}
(@pxref{x-orgodtcontenttemplate-xml,,Factory styles}). If you need
additional templates you have to define these styles yourselves.
I think this hunk should probably be dropped.
Bernt
[O] [PATCH] org.texi: Fix missing links and formatting in 'Exporting' section
>From 40344d3dd27af520ba09516b72e6cbb06a37e780 Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Sun, 8 Apr 2012 15:24:47 +0200
Subject: [PATCH] org.texi: Fix missing links and formatting in 'Exporting'
section
---
doc/org.texi | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index b16adf8..5e51843 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -9565,12 +9565,12 @@ the web, while the XOXO format provides a solid base for exchange with a
broad range of other applications. @LaTeX{} export lets you use Org mode and
its structured editing functions to easily create @LaTeX{} files. DocBook
export makes it possible to convert Org files to many other formats using
-DocBook tools. OpenDocument Text(ODT) export allows seamless
+DocBook tools. OpenDocument Text (ODT) export allows seamless
collaboration across organizational boundaries. For project management you
can create gantt and resource charts by using TaskJuggler export. To
incorporate entries with associated times like deadlines or appointments into
a desktop calendar program like iCal, Org mode can also produce extracts in
-the iCalendar format. Currently Org mode only supports export, not import of
+the iCalendar format. Currently, Org mode only supports export, not import of
these different formats.
Org supports export of selected regions when @code{transient-mark-mode} is
@@ -10906,10 +10906,10 @@ one format (say @samp{csv}) to another format (say @samp{ods} or @samp{xls}).
If you have a working installation of LibreOffice, a document converter is
pre-configured for you and you can use it right away. If you would like to
use @file{unoconv} as your preferred converter, customize the variable
-@code{org-export-odt-convert-process} to point to @code{unoconv}. If you
-would like to use a converter of your own choosing or tweak the default
-settings of the default @file{LibreOffice} and @samp{unoconv} converters
-@xref{Configuring a document converter}.
+@code{org-export-odt-convert-process} to point to @code{unoconv}. You can also
+use a converter of your own choice or tweak the default settings of the default
+@file{LibreOffice} and @samp{unoconv} converters
+(@xref{Configuring a document converter}).
@subsubsection Automatically exporting to other formats
@anchor{x-export-to-other-formats}
@@ -11243,7 +11243,7 @@ that the @file{dvipng} program be available on your system.
For various reasons, you may find embedding @LaTeX{} math snippets in an
ODT document less than reliable. In that case, you can embed a
-math equation by linking to its MathML(@file{.mml}) source or its
+math equation by linking to its MathML (@file{.mml}) source or its
OpenDocument formula (@file{.odf}) file as shown below:
@example
@@ -11306,7 +11306,7 @@ Illustration 2: Bell curve
Export of literal examples (@pxref{Literal examples}) with full fontification
is supported. Internally, the exporter relies on @file{htmlfontify.el} to
generate all style definitions needed for a fancy listing.@footnote{Your
-@file{htmlfontify.el} library must atleast be at Emacs 24.1 levels for
+@file{htmlfontify.el} library must at least be at Emacs 24.1 levels for
fontification to be turned on.} The auto-generated styles have @samp{OrgSrc}
as prefix and inherit their color from the faces used by Emacs
@code{font-lock} library for the source language.
@@ -11355,10 +11355,9 @@ the variable @code{org-export-odt-convert-processes}. Also specify how the
converter can be invoked via command-line to effect the conversion.
@item Configure its capabilities
-@vindex org-export-odt-convert-capabilities
+@vindex org-export-odt-convert-capabilities
@anchor{x-odt-converter-capabilities}
-
Specify the set of formats the converter can handle by customizing the
variable @code{org-export-odt-convert-capabilities}. Use the default value
for this variable as a guide for configuring your converter. As suggested by
@@ -11497,7 +11496,7 @@ regular text.
@end example
@strong{Hint:} To see the above example in action, edit your
-@file{styles.xml}(@pxref{x-orgodtstyles-xml,,Factory styles}) and add a
+@file{styles.xml} (@pxref{x-orgodtstyles-xml,,Factory styles}) and add a
custom @samp{Highlight} style as shown below.
@example
@@ -11516,7 +11515,7 @@ directive. For example, to force a page break do the following:
@end example
@strong{Hint:} To see the above example in action, edit your
-@file{styles.xml}(@pxref{x-orgodtstyles-xml,,Factory styles}) and add a
+@file{styles.xml} (@pxref{x-orgodtstyles-xml,,Factory styles}) and add a
custom @samp{PageBreak} style as shown below.
@example
@@ -11588,7 +11587,7 @@ two table styles with the names @samp{TableWithHeaderRowAndColumn} and
@samp{TableWithFirstRowandLastRow}. (@strong{Important:} The OpenDocument
styles needed for producing the above template have been pre-defined for you.
These styles are availa
[O] [PATCH] doc/org.texi: add tiny stylistic improvements
>From e640d3e9fe99c4cb2f2282bf355d0a1d28c33414 Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Sun, 26 Feb 2012 14:10:05 +0100
Subject: [PATCH] doc/org.texi: add tiny stylistic improvements
---
doc/org.texi |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 7e4bbb0..593bca6 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -9827,13 +9827,13 @@ at a different level, specify it with a prefix argument. For example,
@end example
@noindent
-creates only top level headlines and does the rest as items. When
+creates only top level headlines and exports the rest as items. When
headlines are converted to items, the indentation of the text following
the headline is changed to fit nicely under the item. This is done with
the assumption that the first body line indicates the base indentation of
the body text. Any indentation larger than this is adjusted to preserve
the layout relative to the first line. Should there be lines with less
-indentation than the first, these are left alone.
+indentation than the first one, these are left alone.
@vindex org-export-ascii-links-to-notes
Links will be exported in a footnote-like style, with the descriptive part in
@@ -10224,7 +10224,7 @@ viewing options:
path:@r{The path to the script. The default is to grab the script from}
@r{@url{http://orgmode.org/org-info.js}, but you might want to have}
@r{a local copy and use a path like @samp{../scripts/org-info.js}.}
-view:@r{Initial view when website is first shown. Possible values are:}
+view:@r{Initial view when the website is first shown. Possible values are:}
info @r{Info-like interface with one section per page.}
overview @r{Folding interface, initially showing only top-level.}
content @r{Folding interface, starting with all headlines visible.}
--
1.7.9
[O] [PATCH] doc/org.texi: remove duplicated keybinding for 'org-refile-cache-clear'
>From e56f7f204014ce6e2b83a75caeb248dd63a6c74f Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Sun, 26 Feb 2012 13:51:22 +0100
Subject: [PATCH] doc/org.texi: remove duplicated keybinding for
'org-refile-cache-clear'
---
doc/org.texi |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 7e4bbb0..79342fd 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6919,10 +6919,7 @@ Use the refile interface to jump to a heading.
Jump to the location where @code{org-refile} last moved a tree to.
@item C-2 C-c C-w
Refile as the child of the item currently being clocked.
-@item C-0 C-c C-w @ @r{or} @ C-u C-u C-u C-c C-w
-
@orgcmdtkc{C-0 C-c C-w @ @r{or} @ C-u C-u C-u C-c C-w,C-0 C-c C-w,org-refile-cache-clear}
-
Clear the target cache. Caching of refile targets can be turned on by
setting @code{org-refile-use-cache}. To make the command see new possible
targets, you have to clear the cache with this command.
--
1.7.9
[O] [PATCH] Org manual: Fix double-spaces at the end of sentences
Org manual: Fix double-spaces at the end of sentences
* doc/org.texi: End sentences with two spaces.
>From 19e39b67f4a8dbee3f1015f636fac4f77e59d3c2 Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Mon, 12 Dec 2011 19:19:20 +0100
Subject: [PATCH] Org manual: Fix double-spaces at the end of sentences
* doc/org.texi: End sentences with two spaces.
---
doc/org.texi | 36 ++--
1 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index ff9bb7e..2cbb7d1 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6023,7 +6023,7 @@ Insert a dynamic block (@pxref{Dynamic blocks}) containing a clock
report as an Org-mode table into the current file. When the cursor is
at an existing clock table, just update it. When called with a prefix
argument, jump to the first clock report in the current document and
-update it. The clock table always includes also trees with
+update it. The clock table always includes also trees with
@code{:ARCHIVE:} tag.
@orgcmdkkc{C-c C-c,C-c C-x C-u,org-dblock-update}
Update dynamic block at point. The cursor needs to be in the
@@ -6642,7 +6642,7 @@ buffer again after capture is completed.
In the template itself, special @kbd{%}-escapes@footnote{If you need one of
these sequences literally, escape the @kbd{%} with a backslash.} allow
-dynamic insertion of content. The templates are expanded in the order given here:
+dynamic insertion of content. The templates are expanded in the order given here:
@smallexample
%[@var{file}] @r{insert the contents of the file given by @var{file}.}
@@ -10896,7 +10896,7 @@ newly created file. For additional configuration options
@pxref{x-overriding-factory-styles,,Overriding factory styles}.
If you would like to choose a style on a per-file basis, you can use the
-@code{#+ODT_STYLES_FILE} option. A typical setting will look like
+@code{#+ODT_STYLES_FILE} option. A typical setting will look like
@example
#+ODT_STYLES_FILE: "/path/to/example.ott"
@@ -10932,7 +10932,7 @@ internal links. It creates Internet-style links for all other links.
Export of native Org-mode tables (@pxref{Tables}) and simple @file{table.el}
tables is supported. However, export of complex @file{table.el} tables -
-tables that have column or row spans - is not supported. Such tables are
+tables that have column or row spans - is not supported. Such tables are
stripped from the exported document.
By default, a table is exported with top and bottom frames and with
@@ -10944,7 +10944,7 @@ are interpreted as weighted ratios with the default weight being 1}
@cindex #+ATTR_ODT
If you are not satisfied with the default formatting of tables, you can
create custom table styles and associate them with a table using
-the @code{#+ATTR_ODT} line. @xref{Customizing tables in @acronym{ODT} export}.
+the @code{#+ATTR_ODT} line. @xref{Customizing tables in @acronym{ODT} export}.
@node Images in @acronym{ODT} export, Math formatting in @acronym{ODT} export, Tables in @acronym{ODT} export, OpenDocument Text export
@subsection Images in @acronym{ODT} export
@@ -11171,11 +11171,11 @@ that would be of interest to power users.
@cindex doc, docx
The @acronym{ODT} exporter adds support for exporting Org outlines to formats
-that are not supported natively by Org. It also adds support to convert
+that are not supported natively by Org. It also adds support to convert
document from one format to another. To use these features, you need to
configure a command-line converter. Once a command-line converter is
configured you can use it to extend the list of formats to which Org can
-export. @xref{x-export-to-other-formats,,Automatically exporting to other
+export. @xref{x-export-to-other-formats,,Automatically exporting to other
formats}. You can also use it to perform one-off document conversion as
detailed below.
@@ -11186,7 +11186,7 @@ detailed below.
Convert an existing document from one format to another as determined by the
variable @code{org-export-odt-convert-capabilities}
(@pxref{x-odt-converter-capabilities,,Configure converter
-capabilities}). @strong{Please note} that you can use this command to even
+capabilities}). @strong{Please note} that you can use this command to even
convert documents that are produced outside of Org and in other formats than
@acronym{ODT} format.
@end table
@@ -11209,7 +11209,7 @@ distribution.
@vindex org-odt-data-dir
This converter is distributed as a LibreOffice extension and can be found in
-your Org distribution. See the subdirectory pointed to by the variable
+your Org distribution. See the subdirectory pointed to by the variable
@code{org-odt-data-dir}.
@end enumerate
@@ -11360,11 +11360,11 @@ file. The use of this feature is better illustrated with couple of examples.
@item Embedding ODT tags as part of regular text
You can include simple OpenDocument tags by prefixing them with
-@samp{@@}. For example, t
[O] [PATCH] Orgcard: Correct markup in 'Timestamps' section
Orgcard: Correct markup in 'Timestamps' section
* doc/orgcard.tex: Correct one markup in 'Timestamps' section
>From 756e4eb6aca0e1b72f8fa55537005d2b617b83f8 Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Mon, 12 Dec 2011 12:29:46 +0100
Subject: [PATCH] Orgcard: Correct markup in 'Timestamps' section
* doc/orgcard.tex: Correct one markup in 'Timestamps' section
---
doc/orgcard.tex |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/doc/orgcard.tex b/doc/orgcard.tex
index 38df521..f543e91 100644
--- a/doc/orgcard.tex
+++ b/doc/orgcard.tex
@@ -526,7 +526,7 @@ after ``{\tt :}'', and dictionary words elsewhere.
\section{Timestamps}
\key{prompt for date and insert timestamp}{C-c .}
-\key{like \kbd{C-c} . but insert date and time format}{C-u C-c .}
+\key{like \kbd{C-c .} but insert date and time format}{C-u C-c .}
\key{like \kbd{C-c .} but make stamp inactive}{C-c !} % FIXME
\key{insert DEADLINE timestamp}{C-c C-d}
\key{insert SCHEDULED timestamp}{C-c C-s}
--
1.7.4.1
Re: [O] bug: export of results in babel/R prevents export
Hi Eric, thank you for the fast response. Everything is working fine now. Best Julian
[O] bug: export of results in babel/R prevents export
Hi, when trying to export a file (example see below) with R code and the parameter ":exports" set to "both" or "results" Test babel #+BABEL: :exports both :session #+begin_src R 1:10 #+end_src to html or pdf, export fails with "Symbol's function definition is void: copy-seq". This worked fine with release 7.5, and appeared first with the commit "6ddad0a: ob: not including export-variable headers in cache sha1" (and is still present with the latest version). Can anyone confirm this behavior? Best Julian
[O] [PATCH] orgcard: correct reference to manual
'orgcard.tex' refers to the 'Installation' section of the manual for
defining key bindings, while this is now covered in the 'Activation'
section.
-- Julian
>From b4cb03931c8834626ffa61b0b48157849966002d Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Sat, 30 Jul 2011 14:52:46 +0200
Subject: [PATCH] orgcard: correct reference to manual
---
doc/orgcard.tex |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/doc/orgcard.tex b/doc/orgcard.tex
index be8cbef..2561879 100644
--- a/doc/orgcard.tex
+++ b/doc/orgcard.tex
@@ -674,7 +674,7 @@ never exported.
\section{Notes}
[1] This is only a suggestion for a binding of this command. Choose
-your own key as shown under INSTALLATION.
+your own key as shown under ACTIVATION.
[2] Keybinding affected by {\tt org-support-shift-select} and also
{\tt org-replace-disputed-keys}.
--
1.7.4.1
[O] [PATCH] org-html: fix typo in doc
Hi, this patch fixes a typo in the documentation of org-html. Best Julian>From 40483bb63d236595d6982dca26a2a3d80bfd39bc Mon Sep 17 00:00:00 2001 From: Julian Gehring Date: Wed, 29 Jun 2011 10:31:21 +0200 Subject: [PATCH] org-html: fix typo in doc --- lisp/org-html.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org-html.el b/lisp/org-html.el index f6108fc..fd43bbf 100644 --- a/lisp/org-html.el +++ b/lisp/org-html.el @@ -196,7 +196,7 @@ For example, a valid value would be: ]]> -If you'd like to refer to en external style file, use something like +If you'd like to refer to an external style file, use something like -- 1.7.4.1
Re: [O] Corrections for org mode manual
Hi Bastien,
thank you for including the patches.
> Also note that the convention is to use a double-space at the ending
> of each sentence. There are a lot of fixes needed to this regard...
This patch should take care of (I hope all) the double spaces at the
ending of the sentences (and a few other formatting issues).
Best
Julian
>From ac31b86b5a3be0cfa2e994fef42e777ed1a3f115 Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Sat, 25 Jun 2011 10:50:40 +0200
Subject: [PATCH] fix double spacing at the end of sentences in whole org mode manual
---
doc/org.texi | 260 +-
1 files changed, 130 insertions(+), 130 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 7614b1a..721fe78 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -1426,7 +1426,7 @@ commands can be accessed through a dispatcher:
This prompts for an extra key to select a sparse-tree creating command.
@orgcmd{C-c / r,org-occur}
@vindex org-remove-highlights-with-change
-Occur. Prompts for a regexp and shows a sparse tree with all matches. If
+Prompts for a regexp and shows a sparse tree with all matches. If
the match is in a headline, the headline is made visible. If the match is in
the body of an entry, headline and body are made visible. In order to
provide minimal context, also the full hierarchy of headlines above the match
@@ -1658,7 +1658,7 @@ converted into a list item.
@kindex C-c *
@item C-c *
Turn a plain list item into a headline (so that it becomes a subheading at
-its location). @xref{Structure editing}, for a detailed explanation.
+its location). @xref{Structure editing}, for a detailed explanation.
@kindex C-c C-*
@item C-c C-*
Turn the whole plain list into a subtree of the current heading. Checkboxes
@@ -1940,7 +1940,7 @@ unpredictable for you, configure the variables
@table @kbd
@tsubheading{Creation and conversion}
@orgcmd{C-c |,org-table-create-or-convert-from-region}
-Convert the active region to table. If every line contains at least one
+Convert the active region to table. If every line contains at least one
TAB character, the function assumes that the material is tab separated.
If every line contains a comma, comma-separated values (CSV) are assumed.
If not, lines are split at whitespace into fields. You can use a prefix
@@ -2520,7 +2520,7 @@ a Lisp string (in double-quotes) containing the field. If you provide the
@samp{N} mode switch, all referenced elements will be numbers (non-number
fields will be zero) and interpolated as Lisp numbers, without quotes. If
you provide the @samp{L} flag, all fields will be interpolated literally,
-without quotes. i.e., if you want a reference to be interpreted as a string
+without quotes. I.e., if you want a reference to be interpreted as a string
by the Lisp form, enclose the reference operator itself in double-quotes,
like @code{"$3"}. Ranges are inserted as space-separated fields, so you can
embed them in list or vector syntax. Here are a few examples---note how the
@@ -3027,7 +3027,7 @@ or with a mouse click (@pxref{Handling links}). Links to custom IDs will
point to the corresponding headline. The preferred match for a text link is
a @i{dedicated target}: the same string in double angular brackets. Targets
may be located anywhere; sometimes it is convenient to put them into a
-comment line. For example
+comment line. For example
@example
# <>
@@ -3323,7 +3323,7 @@ displayed at startup by configuring the variable
@orgcmd{C-c %,org-mark-ring-push}
@cindex mark ring
Push the current position onto the mark ring, to be able to return
-easily. Commands following an internal link do this automatically.
+easily. Commands following an internal link do this automatically.
@c
@orgcmd{C-c &,org-mark-ring-goto}
@cindex links, returning to
@@ -3428,7 +3428,7 @@ not accept any arguments, and return the full link with prefix.
File links can contain additional information to make Emacs jump to a
particular location in the file when following a link. This can be a
line number or a search option after a double@footnote{For backward
-compatibility, line numbers can also follow a single colon.} colon. For
+compatibility, line numbers can also follow a single colon.} colon. For
example, when the command @kbd{C-c l} creates a link (@pxref{Handling
links}) to a file, it encodes the words in the current line as a search
string that can be used to find this line back later when following the
@@ -4239,7 +4239,7 @@ large number of subtasks (@pxref{Checkboxes}).
@vindex org-list-automatic-rules
Every item in a plain list@footnote{With the exception of description
-lists. But you can allow it by modifying @code{org-list-automatic-rules}
+lists. But you can allow it by modifying @code{org-list-automatic-rules}
accordingly.} (@pxref{Plain lists}) can be made into a checkbox by starting
it with the string @samp{[ ]}. This feature is simila
Re: [O] Corrections for org mode manual
Hey,
here is a patch with four small corrections for the org mode manual. I
hope it helps.
Best
Julian>From ace6614d8a95bbaca5dfd2f6596f1a1554fb53c5 Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Fri, 24 Jun 2011 10:56:43 +0200
Subject: [PATCH] correct manual
---
doc/org.texi | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 936416d..a9159d5 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -265,7 +265,7 @@
@copying
This manual is for Org version @value{VERSION}.
-Copyright @copyright{} 2004, 2005, 2006, 2007, 2008, 2009, 2010
+Copyright @copyright{} 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011
Free Software Foundation, Inc.
@quotation
@@ -6243,7 +6243,7 @@ prefix commands:
@table @kbd
@orgkey{C-u C-c c}
-Visit the target location of a cpature template. You get to select the
+Visit the target location of a capture template. You get to select the
template in the usual way.
@orgkey{C-u C-u C-c c}
Visit the last stored capture item in its buffer.
@@ -9818,7 +9818,7 @@ support text viewers and accessibility, and align it to the right.
@end example
@noindent
-and you could use @code{http} addresses just as well.
+You could use @code{http} addresses just as well.
@node Math formatting in HTML export, Text areas in HTML export, Images in HTML export, HTML export
@subsection Math formatting in HTML export
@@ -10058,7 +10058,7 @@ sections.
@orgcmd{C-c C-e l,org-export-as-latex}
@cindex property EXPORT_FILE_NAME
Export as @LaTeX{} file. For an Org file
-@file{myfile.org}, the ASCII file will be @file{myfile.tex}. The file will
+@file{myfile.org}, the @LaTeX{} file will be @file{myfile.tex}. The file will
be overwritten without warning. If there is an active region@footnote{This
requires @code{transient-mark-mode} be turned on.}, only the region will be
exported. If the selected region is a single tree@footnote{To select the
@@ -11426,8 +11426,8 @@ Optional switches controlling exportation of the code block (see switches discus
@ref{Literal examples})
@item
Optional header arguments control many aspects of evaluation, export and
-tangling of code blocks. See the @ref{Header arguments}
-section. Header arguments can also be set on a per-buffer or per-subtree
+tangling of code blocks. See the @ref{Header arguments}.
+Header arguments can also be set on a per-buffer or per-subtree
basis using properties.
@item
The source code.
--
1.7.4.1
[O] Corrections for org mode manual
Hey,
while reading through the org mode manual I found some lines that could
require minor corrections.
I attached a patch file with corrections
('0001-add-corrections-to-org-manual.patch'), as well as one with
suggestions ('0001-add-suggestions-to-org-manual.patch') that are more
of a matter of style.
If there are any questions or comments, please let me know. I will have
a look at the remaining chapters as soon as possible.
Best
Julian
>From 18eb49c49439c7664e4179e28f4213954c5e7c8c Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Sat, 4 Jun 2011 23:07:41 +0200
Subject: [PATCH] add corrections to org manual
---
doc/org.texi | 32 +---
1 files changed, 17 insertions(+), 15 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index eb97759..182219e 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -4025,7 +4025,7 @@ called ``habits''. A habit has the following properties:
You have enabled the @code{habits} module by customizing the variable
@code{org-modules}.
@item
-The habit is a TODO, with a TODO keyword representing an open state.
+The habit is a TODO item, with a TODO keyword representing an open state.
@item
The property @code{STYLE} is set to the value @code{habit}.
@item
@@ -4941,7 +4941,7 @@ optional. The individual parts have the following meaning:
@var{property}@r{The property that should be edited in this column.}
@r{Special properties representing meta data are allowed here}
@r{as well (@pxref{Special properties})}
-@var{title} @r{The header text for the column. If omitted, the property}
+@var{title} @r{The header text for the column. If omitted, the property}
@r{name is used.}
@{@var{summary-type}@} @r{The summary type. If specified, the column values for}
@r{parent nodes are computed from the children.}
@@ -6131,7 +6131,7 @@ not started at exactly the right moment.
@kindex ;
Calling @code{org-timer-set-timer} from an Org-mode buffer runs a countdown
-timer. Use @key{;} from agenda buffers, @key{C-c C-x ;} everwhere else.
+timer. Use @kbd{;} from agenda buffers, @kbd{C-c C-x ;} everwhere else.
@code{org-timer-set-timer} prompts the user for a duration and displays a
countdown timer in the modeline. @code{org-timer-default-timer} sets the
@@ -6999,7 +6999,7 @@ Lift the restriction.
@cindex agenda dispatcher
@cindex dispatching agenda commands
The views are created through a dispatcher, which should be bound to a
-global key---for example @kbd{C-c a} (@pxref{Installation}). In the
+global key---for example @kbd{C-c a} (@pxref{Activation}). In the
following we will assume that @kbd{C-c a} is indeed how the dispatcher
is accessed and list keyboard access to commands accordingly. After
pressing @kbd{C-c a}, an additional letter is required to execute a
@@ -8396,7 +8396,7 @@ version of some agenda views to carry around. Org-mode can export custom
agenda views as plain text, HTML@footnote{You need to install Hrvoje Niksic's
@file{htmlize.el}.}, Postscript, PDF@footnote{To create PDF output, the
ghostscript @file{ps2pdf} utility must be installed on the system. Selecting
-a PDF file with also create the postscript file.}, and iCalendar files. If
+a PDF file will also create the postscript file.}, and iCalendar files. If
you want to do this only occasionally, use the command
@table @kbd
@@ -8940,8 +8940,8 @@ If the syntax for the label format conflicts with the language syntax, use a
@code{-l} switch to change the format, for example @samp{#+BEGIN_SRC pascal
-n -r -l "((%s))"}. See also the variable @code{org-coderef-label-format}.
-HTML export also allows examples to be published as text areas, @xref{Text
-areas in HTML export}.
+HTML export also allows examples to be published as text areas (@xref{Text
+areas in HTML export}).
Because the @code{#+BEGIN_...} and @code{#+END_...} patterns need to be added
so often, shortcuts are provided using the Easy Templates facility
@@ -9641,8 +9641,8 @@ language, but with additional support for tables.
@table @kbd
@orgcmd{C-c C-e h,org-export-as-html}
@cindex property, EXPORT_FILE_NAME
-Export as HTML file @file{myfile.html}. For an Org file @file{myfile.org},
-the ASCII file will be @file{myfile.html}. The file will be overwritten
+Export as HTML file. For an Org file @file{myfile.org},
+the HTML file will be @file{myfile.html}. The file will be overwritten
without warning. If there is an active region@footnote{This requires
@code{transient-mark-mode} be turned on.}, only the region will be
exported. If the selected region is a single tree@footnote{To select the
@@ -10057,8 +10057,8 @@ sections.
@table @kbd
@orgcmd{C-c C-e l,org-export-as-latex}
@cindex property EXPORT_FILE_NAME
-Export as @LaTeX{} file @file{myfile.tex}. For an Org file
-@file{myfile.org}, the ASCII file will be @file{myfile.tex}. The file will
+
[Orgmode] incorrect key binding for org-attach-open in manual
Hi, In section 9.2 of the current org manual, "org-attach-open" is associated with the key binding "C-c C-a p". However, this seems to be a typo and the correct key binding should be "C-c C-a o". Best Julian ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
