[O] Last org-lparse.el changes make swriter not to open after org-export-as-odt-and-open
Last org-lparse.el changes make swriter not to open after org-export-as-odt-and-open This refers to commit Tue, 2 Oct 2012 08:03:15 + (10:03 +0200) and, I think, the problems is only in org-lparse.el changes. Version 7.9.2-50-g1fb3cc works as expected if org-lparse.el is reverted to its previous version.
Re: [O] [New exporter] Wrong export to LaTeX
Hi Nicolas, Nicolas Goaziou wrote: Sebastien Vauban writes: Suvayu Ali wrote: However, I thought that LaTeX_CLASS had been renamed EXPORT_LaTeX_CLASS, but when using the latter, I get frames inside an `article' documentclass type of document -- while using `C-c E l O' (for Beamer)? That results in a weird document... I believe that is the property name only for subtree export. So when exporting a file, use: #+LaTeX_CLASS: beamer for subtree export use: * Beamer presentation :PROPERTIES: :EXPORT_LaTeX_CLASS: beamer :END: Nicolas, do you confirm the fact that keywords differ whether they apply to the file or to a subtree? Yes. If yes, wouldn't make sense to remove such a distinction, or (at the other extreme of the spectrum) to make all keywords share that same feature (prefixing with EXPORT_ for subtrees)? Note that it isn't a new feature from the new export engine, merely a generalization from the old exporter, which already distinguished #+DATE: and :EXPORT_DATE:, #+TITLE: and :EXPORT_TITLE:... There's little incentive for users to create new keywords on the fly. On the other hand, they may want to add node properties. That's why export keywords should be made as simple as possible and export properties should pollute as little namespace as possible. Therefore, I think the current state is good. It will be properly documented once the new exporter becomes mainstream (but the rule is simple anyway). I'm glad that such a rule exists: #+KEYWORD: for *file* export properties | v #+EXPORT_KEYWORD: for *subtree* export properties #+LaTeX_CLASS follows a rule which escaped me. Your explanation does make a lot of sense. No change! Best regards, Seb -- Sebastien Vauban
[O] [BUG] [ODT] ODT export (old) fails with wrong-type-argument
Hi, When I try to export to ODT (without invoking the new exporter or anything), I get: OpenDocument export failed: Wrong type argument: stringp, (org-export-odt-preprocess-latex-fragments) This also happens in a document with no latex fragments. I'm running Org-mode version 7.9.2 (release_7.9.2-458-ged698d @ /Applications/Emacs.app/Contents/Resources/site-lisp/org/) on GNU Emacs 24.1.1. Is it just me? Yours, Christian
Re: [O] [BUG] [ODT] ODT export (old) fails with wrong-type-argument
Backtrace attached. The previous message wouldn't go through as long as I included the backtrace in the message body. No idea why. Christian Debugger entered--Lisp error: (wrong-type-argument stringp (org-export-odt-preprocess-latex-fragments)) file-exists-p((org-export-odt-preprocess-latex-fragments)) org-lparse-and-open(odt odt nil) #[nil \303\206 \304\304#\n \210\207 [org-export-odt-preferred-output-format arg --cleanup-xml-buffers org-lparse-and-open odt] 4]() org-export-as-odt-and-open(nil) call-interactively(org-export-as-odt-and-open) org-export(nil) call-interactively(org-export nil nil)
[O] #+LATEX_CLASS: IEEEtran
Hi, I want to latex export my paper which has to use the document class IEEEtran With the following in the preamble #+LATEX_CLASS: IEEEtran I am getting following error org-export-latex-set-initial-vars: No definition for class `IEEEtran' in `org-export-latex-classes' Can anybody guide me please ? Thanks - *Sanjib Sikder *Ph.D. Fellow Chemical Engineering IIT Bombay* *
Re: [O] #+LATEX_CLASS: IEEEtran
Sanjib Sikder sanjibju2...@gmail.com wrote:
Hi,
I want to latex export my paper which has to use the document class IEEEtran
With the following in the preamble
#+LATEX_CLASS: IEEEtran
I am getting following error
org-export-latex-set-initial-vars: No definition for class `IEEEtran' in
`org-export-latex-classes'
As it says, you need to add a definition for the class `IEEEtran' to
the variable org-export-latex-classes (for the old exporter - the
corresponding variable for the new exporter is org-e-latex-classes).
You should read the docs for these variables: they do a few different
things and they are somewhat complicated.
Here is a trivial example to start with:
--8---cut here---start-8---
;;;
;;; latex export
(setq ieeetran-class
'(IEEEtran \\documentclass[11pt]{IEEEtran}
(\\section{%s} . \\section*{%s})
(\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})
(\\paragraph{%s} . \\paragraph*{%s})
(\\subparagraph{%s} . \\subparagraph*{%s})))
(require 'org-latex)
(add-to-list 'org-export-latex-classes ieeetran-class t)
(require 'org-e-latex)
(add-to-list 'org-e-latex-classes ieeetran-class t)
--8---cut here---end---8---
It's basically the article class spec with a different name.
You should add the code above to your .emacs (or similar init file).
You can then elaborate it as necessary.
Nick
Re: [O] #+LATEX_CLASS: IEEEtran
Hi, Dokos,
Thanks again.
After incorporating those lines, I am getting following error.
File error: Cannot open load file, org-e-latex
If it is complex (as I am new in orgmode), then I will go for normal latex
instead of orgmode for this particular task as I have a template for
IEEEtran but I would love to do the job in orgmode.
Eagerly waiting for your comments
Thanks.
-
*Sanjib Sikder
*Ph.D. Fellow
Chemical Engineering
IIT Bombay*
*
On Tue, Oct 16, 2012 at 3:08 PM, Nick Dokos nicholas.do...@hp.com wrote:
Sanjib Sikder sanjibju2...@gmail.com wrote:
Hi,
I want to latex export my paper which has to use the document class
IEEEtran
With the following in the preamble
#+LATEX_CLASS: IEEEtran
I am getting following error
org-export-latex-set-initial-vars: No definition for class `IEEEtran'
in `org-export-latex-classes'
As it says, you need to add a definition for the class `IEEEtran' to
the variable org-export-latex-classes (for the old exporter - the
corresponding variable for the new exporter is org-e-latex-classes).
You should read the docs for these variables: they do a few different
things and they are somewhat complicated.
Here is a trivial example to start with:
--8---cut here---start-8---
;;;
;;; latex export
(setq ieeetran-class
'(IEEEtran \\documentclass[11pt]{IEEEtran}
(\\section{%s} . \\section*{%s})
(\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})
(\\paragraph{%s} . \\paragraph*{%s})
(\\subparagraph{%s} . \\subparagraph*{%s})))
(require 'org-latex)
(add-to-list 'org-export-latex-classes ieeetran-class t)
(require 'org-e-latex)
(add-to-list 'org-e-latex-classes ieeetran-class t)
--8---cut here---end---8---
It's basically the article class spec with a different name.
You should add the code above to your .emacs (or similar init file).
You can then elaborate it as necessary.
Nick
Re: [O] #+LATEX_CLASS: IEEEtran
Sanjib Sikder sanjibju2...@gmail.com wrote: Hi, Dokos, Thanks again. After incorporating those lines, I am getting following error. File error: Cannot open load file, org-e-latex If it is complex (as I am new in orgmode), then I will go for normal latex instead of orgmode for this particular task as I have a template for IEEEtran but I would love to do the job in orgmode. Eagerly waiting for your comments Two options: o if you are not going to use the new exporter, just delete the two lines: (require 'org-e-latex) (add-to-list 'org-e-latex-classes ieeetran-class t) o alternatively, teach emacs where to find org-e-latex by augmenting the load-path: (add-to-list 'load-path /path/to/org/mode/contrib/lisp) This needs to be done before the (require 'org-e-latex) and of course, the path needs to be modified for your particular setup. Nick
[O] org-export-expand-include-keyword doesn't handle inline tasks well
Hi, When a tree includes another file tree by using the #+INCLUDE keyword, the imported headlines are demoted by appending an appropriate number of asterisks. The problem is when an inline task is included, the number of asterisks seems to make it unrecognisable as an inline task. Can someone confirm this as a bug? This has two problems that I can see: 1) if the resulting file is subsequently included again in another file, the inline tasks are thought to be headings so anything coming after it is demoted beneath it, 2) some functions seem to expect a maximum number of asterisks (I'll leave this bit a little vague; it was something to do with dynamic blocks). Org-mode version 7.9.2 (release_7.9.2-441-gf287ab @ /home/myles/.emacs.d/plugins/org-mode/lisp/) Herewith a minimum example: Start with emacs -Q -l [your_minimal.el] _ file: a.org __ #+BEGIN_SRC emacs-lisp (require 'org-inlinetask) #+END_SRC * A heading ** Another heading *** Here is an inline task *** END #+BEGIN_SRC emacs-lisp (require 'org-export) (org-export-with-current-buffer-copy (org-export-expand-include-keyword) (clipboard-kill-ring-save (point-min) (point-max))) (find-file ./results.org) (clipboard-yank) #+END_SRC __ _ file: b.org __ * A Heading in b.org *** An inline task in b.org *** END #+BEGIN_SRC emacs-lisp (require 'org-inlinetask) #+END_SRC Buffer results.org contains inline tasks of different levels: ** Another heading *** Here is an inline task *** END *** A Heading in b.org * An inline task in b.org * END Thanks, Myles
[O] [new exporter] latex: why does {{}} become \{\{\}\} ?
Hi,
Org-mode version 7.9.2 (release_7.9.2-441-gf287ab @
/home/myles/.emacs.d/plugins/org-mode/lisp/)
Can anyone tell me please why (in the examples below) {} exports fine
but {{}} exports as \{\{\}\} ? Am I meant to wrap these in
#+begin_latex blocks?
In my .org file:
\tikzset{help lines/.style=very thin}
\tikzset{help grid/.style={help lines,color=blue!50}}
In the resulting .tex file
\tikzset{help lines/.style=very thin}
\tikzset\{help grid/.style=\{help lines,color=blue!50\}\}
Thanks,
Myles
Re: [O] new exporter: too many blank lines in .org results in missing images from src blocks
Hello, On 10/15/2012 10:35 PM, Nicolas Goaziou wrote: Hello, Robert Klein klein...@mpip-mainz.mpg.de writes: The export of the file below doesn't always include the image in the export (that is, no image, not even a missing image). When there is only one blank line after #+end_src, the image in included. Two or more blank lines, and there is no image. in tex files there is no \includegraphics, in html exports img src... is missing. Same happens when the org file ends after #+end_src and there are more than two blank lines. (That happened with the file I encountered the issue first. And, of course, didn't see any difference to a org file where exporting worked... :-) It should be fixed now. Thanks again for the report. Regards, yes, it works. Thank you very much! Best regards Robert
[O] publish one org-file as many html files
Dear list, Is there a way to publish a huge org file, typically containing a single date-tree, into one html file per day / per leaf of the tree ? That would be a neat tool to blog using org-mode (org-capture a post into the tree, export, you're done). Cheers, /vincent -- Vincent Beffara
Re: [O] Publishing one org-file as many html files
o-blog should be able to do that, see: http://renard.github.com/o-blog/tips/2012/01/07_creating-a-blog.html On 16 October 2012 18:23, Vincent Beffara vbeffara...@gmail.com wrote: Dear list, Is there a way to publish a huge org file, typically containing a single date-tree, into one html file per day / per leaf of the tree ? That would be a neat tool to blog using org-mode (org-capture a post into the tree, export, you're done). Cheers, /vincent -- Vincent Beffara
Re: [O] BIBINPUT in .bashrc not recognized by Emacs
Hello Sanjib, Since Myles has already answered your question to some extent, I would like to take the liberty to point out that your current issue is off-topic on this list. I would advise you try to ask this on the Ubuntu list (since you use Ubuntu), or post on help-b...@gnu.org (a dedicated bash help list). Apart from this, if you prefer web interfaces over email, you could post your question on superuser.com, a member of the stackexchange network. Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] Publishing one org-file as many html files
Hi, This looks very promising! Quite a bit more sophisticated than what I had in mind though, and it is not immediately clear how to customize it, but I will look into it. Thanks for the link ! /v -- Vincent Beffara On Tuesday, October 16, 2012 at 18:35 , Christopher Witte wrote: o-blog should be able to do that, see: http://renard.github.com/o-blog/tips/2012/01/07_creating-a-blog.html On 16 October 2012 18:23, Vincent Beffara vbeffara...@gmail.com (mailto:vbeffara...@gmail.com) wrote: Dear list, Is there a way to publish a huge org file, typically containing a single date-tree, into one html file per day / per leaf of the tree ? That would be a neat tool to blog using org-mode (org-capture a post into the tree, export, you're done). Cheers, /vincent -- Vincent Beffara
Re: [O] [new exporter] latex: why does {{}} become \{\{\}\} ?
Hello,
Myles English mylesengl...@gmail.com writes:
Can anyone tell me please why (in the examples below) {} exports fine
but {{}} exports as \{\{\}\} ? Am I meant to wrap these in
#+begin_latex blocks?
You're writing LaTeX code in an Org buffer. This is only possible to
a limited extent. In particular, these lines should indeed go within
a LaTeX block. Otherwise, they will be protected to appear as-is in the
output.
Regards,
--
Nicolas Goaziou
Re: [O] org-export-expand-include-keyword doesn't handle inline tasks well
Hello, Myles English mylesengl...@gmail.com writes: When a tree includes another file tree by using the #+INCLUDE keyword, the imported headlines are demoted by appending an appropriate number of asterisks. The problem is when an inline task is included, the number of asterisks seems to make it unrecognisable as an inline task. Can someone confirm this as a bug? I can. It should be fixed now. Thanks for the report. Regards, -- Nicolas Goaziou
Re: [O] nbsp and /italics/
t...@tsdye.com (Thomas S. Dye) writes:
#+name: ngz-nbsp
#+begin_src emacs-lisp
(defun ngz-latex-filter-nobreaks (text backend info)
Ensure \_\ are properly handled in Beamer/LaTeX export.
(when (memq backend '(e-beamer e-latex))
(replace-regexp-in-string ~ text)))
(add-to-list 'org-export-filter-plain-text-functions
'ngz-latex-filter-nobreaks)
#+end_src
Hmm, I'm intrigued by this and it could solve one of my long standing
issue with Org LaTeX export.
I write all new sentences with , and for stuff like fig. I use
one space. Pretty consistently. I would love to modify the function
to recognize point one space as .~ and point double space as
. . (i.e. no translation).
Can anyone think of a clever regexp that recognizes the above pattern?
I tried, \\.[ ]\{1\} but it didn't work. And without the \{1\} it's
too strong. . .
Thanks in advance,
Rasmus
--
I almost cut my hair, it was happened just the other day
Re: [O] Bug: Org column view, property edit bug [7.8.11]
Hello, Teemu Likonen tliko...@iki.fi writes: Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. Org's column view has e key for editing fields such as property values. Properties are messed up if user tries to clear the property's value with e. See the following example. Start emacs -Q and load this org file: #+COLUMNS: %9ITEM %5foo * heading :PROPERTIES: :foo: value :END: Turn on the column view with C-c C-x C-c. The buffer should look like this: ITEM__|_foo___|_ #+COLUMNS: %9ITEM %5foo * heading | value | :PROPERTIES: :foo: value :END: Now move the point to the value column and edit it with e. Clear all the text from the minibuffer prompt and press enter. The buffer looks like this: ITEM__|_foo___|_ #+COLUMNS: %9ITEM %5foo * heading | | :PROPERTIES: :foo: :END: Don't move the point. Press e again to edit the same value again. Insert xxx to the minibuffer prompt. The buffer looks like this: ITEM__|_foo___|_ #+COLUMNS: %9ITEM %5foo * heading | | :PROPERTIES: :foo: :foo: xxx :END: See, there are now two foo properties: one with empty value and one with the value xxx. The column view will always show the empty value but the edit command e will edit the latter value (currently xxx). I think the last e command in my example shouldn't create new foo property line; it should edit the empty foo instead. Emacs : GNU Emacs 24.2.3 (x86_64-unknown-linux-gnu, GTK+ Version 2.20.1) of 2012-10-14 on mithlond Package: Org-mode version 7.8.11 Thanks for the report. For what it's worth, though, I cannot reproduce it on Org mode 7.9.2. Regards, -- Nicolas Goaziou
Re: [O] [new exporter] latex: why does {{}} become \{\{\}\} ?
Nicolas Goaziou writes:
You're writing LaTeX code in an Org buffer. This is only possible to
a limited extent. In particular, these lines should indeed go within
a LaTeX block. Otherwise, they will be protected to appear as-is in the
output.
Thanks, just confirming that was helpful, me and my emacs were confused
somehow and #+begin_latex was coming out as \begin{latex}, it may have
been a missing bracket.
Myles
Re: [O] [new exporter] latex: why does {{}} become \{\{\}\} ?
Hello Nicolas,
Nicolas Goaziou wrote:
Myles English mylesengl...@gmail.com writes:
Can anyone tell me please why (in the examples below) {} exports fine
but {{}} exports as \{\{\}\} ? Am I meant to wrap these in
#+begin_latex blocks?
You're writing LaTeX code in an Org buffer. This is only possible to
a limited extent. In particular, these lines should indeed go within
a LaTeX block.
Within a LaTeX block (#+begin_latex) or within a Babel block for LaTeX
language (#+begin_src latex)? Do you make a difference?
Best regards,
Seb
--
Sebastien Vauban
Re: [O] nbsp and /italics/
Rasmus ras...@gmx.us writes:
Can anyone think of a clever regexp that recognizes the above pattern?
I tried, \\.[ ]\{1\} but it didn't work. And without the \{1\} it's
too strong. . .
Here's one that seems to work in the primitive cases, but not when
there's a link.
Tested on
test of tilde. small space fig. [[latex:ref][test]]. But here's a large
space.
the regexp recognizes both small spaces, but does not insert the
tilde between fig. and [[.
Could I add it to an earlier hook or something similar to make it
work?
#+begin_src emacs-lisp
(defun ngz-latex-filter-nobreaks-double-space (text backend info)
Tries to export \S1. S2\ as \S1.~S2\ while letting \S1. S2\ be
exported without tilde
(when (memq backend '(e-beamer e-latex))
(replace-regexp-in-string \\.[ ]\\{1\\}\\([^ ]\\) .~\\1 text)))
(add-to-list 'org-export-filter-plain-text-functions
'ngz-latex-filter-nobreaks-double-space)
#+end_src
Thanks,
Rasmus
--
I almost cut my hair, it was happened just the other day
Re: [O] org-export-expand-include-keyword doesn't handle inline tasks well
Nicolas Goaziou writes: Hello, Myles English mylesengl...@gmail.com writes: When a tree includes another file tree by using the #+INCLUDE keyword, the imported headlines are demoted by appending an appropriate number of asterisks. The problem is when an inline task is included, the number of asterisks seems to make it unrecognisable as an inline task. Can someone confirm this as a bug? I can. It should be fixed now. Thanks for the report. Thanks for fixing it, works great. Now I just have to remember to (require 'org-inlinetask) if I am going to #+INCLUDE a file that uses them. Myles
[O] latex export: document fails to compile
create a new empty org-mode file containing this text
* test
$\text{asdf}$
export to latex, build pdf from tex
error
ERROR: Undefined control sequence.
--- TeX said ---
recently read \text
l.38 $\text
{asdf}$
--- HELP ---
TeX encountered an unknown command name. You probably misspelled the
name. If this message occurs when a LaTeX command is being processed,
the command is probably in the wrong place---for example, the error
can be produced by an \item command that's not inside a list-making
environment. The error can also be caused by a missing \documentclass
command.
This is a bug?
Re: [O] org-end-of-line
Hello, Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: When pressing `C-e' to go to the last char of a looong sentence, such as: azroiu zrouz eruzepr ozeioru zoepru zoeruozieuriozerusdjflsdfjsdksjfsdfs df sdjf sdf sdsd fklsdjf sdj sdjlksdjf sqfjsdjf sdfklsjdjsdsdjlkmskfjsldkjfsdjfoizeoi xcsdf zerfze ze rrz zer ze sdf sd d g erg ry er fscvf dsr yh yt re gfsd f er gt z'y reg er fsd cf,sk jfshfsdc kle eozifsdnc sslk kzdjf dsl jfsdljf sdilkj fzefoizejfsdlkf sklqjfoiezrfoi it goes up to the last char of the visual line, would that line be truncated. In every other mode I've looked at (Message, Emacs Lisp, etc.), `C-e' does go to the end of the physical line, _with the same untouched settings_ for `line-move-visual' (set to `t' in `simple.el'). Why does Org behave differently? See line 21613 in org.el: It should be fixed. Thanks for the report. Regards, -- Nicolas Goaziou
