Re: [O] Is there an easy way converting html -> orgmode?
Thanks a lot, Roger and Eric, in the mean time, I have found the ancient command line "html2text" that even replaces html section headers etc. by the appropriate orgmode star prefices. Kind regards Martin Am Sonntag, 24. April 2016, 11:10:00 schrieb Roger Mason: > Hello, > > Martin Weigele writes: > > Hi, the subject line says it all, is there an easy way converting html to > > orgmode (not the other way round). > > I think pandoc (http://pandoc.org/) can do that. > > Cheers, > Roger
[O] Is there an easy way converting html -> orgmode?
Hi, the subject line says it all, is there an easy way converting html to orgmode (not the other way round). Thanks, Martin
Re: [O] How to create synopsis output of versioned text?
Thanks Ken, your wording "side-by-side-options" helped me now tracking down emacs "ediff" (M-x ediff-files). But this probably won't do the trick of side- by-side output other than on screen. Am Mittwoch, 20. Mai 2015, 16:21:55 schrieben Sie: > I use 'latexdiff' for this, but it does not have a side-by-side option. > > -k. > > On 2015-05-20 at 14:13, Martin Weigele wrote: > > When dealing with different versions of text, e.g. old and new (law) code, > > it is sometimes nice to be able to create a synopsis of the versions of > > the text in tabular form. > > > > Any suggestions how to do this in emacs orgmode? Yes I know you can > > manually do tables, and you could call unix diff, but something that does > > it automatically from the individual text versions with a tabular output > > - old version left, new version right column, with similar sections or > > code pieces matching in the same row would be cool. As a last resort, > > even outside orgmode. :) > > > > Martin
[O] How to create synopsis output of versioned text?
When dealing with different versions of text, e.g. old and new (law) code, it is sometimes nice to be able to create a synopsis of the versions of the text in tabular form. Any suggestions how to do this in emacs orgmode? Yes I know you can manually do tables, and you could call unix diff, but something that does it automatically from the individual text versions with a tabular output - old version left, new version right column, with similar sections or code pieces matching in the same row would be cool. As a last resort, even outside orgmode. :) Martin
Re: [O] Solution for very long hyperlinks when exporting to latex?
Problem solved by uncommenting the "[NO-DEFAULT-PACKAGES]" and "[EXTRA]"
parts (see elisp part below) in the emacs lisp initialisation of .emacs.
Am Mittwoch, 1. Oktober 2014, 02:29:23 schrieb Martin Weigele:
> That is exactly the problem, Rasmus... I am lost in the complexity of object
> and metalevels and don't really know where to start reducing it. Except for
> the naughty monster urls everything else works fine. Thanks anyway. :)
>
> Good night, Martin
>
> Am Mittwoch, 1. Oktober 2014, 02:20:45 schrieb Rasmus:
> > Martin Weigele writes:
> > > There you go. Thx.
> >
> > Please send a minimal example that displays the undesired behavior :)
> >
> > > #+TITLE: Blah
> > > #+AUTHOR: Me und Du
> > >
> > > #+OPTIONS: H:20
> > > #+LATEX_CLASS: scrbook
> > >
> > > #+LATEX_CLASS_OPTIONS:
> > > [paper=17cm:22cm,DIV=calc,BCOR=12mm,titlepage,11pt,scrhack]
> > >
> > > #+LATEX_HEADER: \usepackage[english,ngerman]{babel}
> > > #+LATEX_HEADER:\usepackage{
> > > #+LATEX_HEADER: fixltx2e % Verbessert einige Kernkompetenzen von
> > > LaTeX2e
> > > #+LATEX_HEADER:}
> > > #+LATEX_HEADER:\usepackage{%
> > > #+LATEX_HEADER: ellipsis, % Korrigiert den Weißraum um
> > > Auslassungspunkte
> > > #+LATEX_HEADER: ragged2e, % Ermöglicht Flattersatz mit Silbentrennung
> > > #+LATEX_HEADER: marginnote,% Für bessere Randnotizen mit \marginnote
> > > statt
> > > #+LATEX_HEADER:% \marginline
> > > #+LATEX_HEADER:}
> > > #+LATEX_HEADER:\usepackage[tracking=true]{microtype}%
> > > #+LATEX_HEADER:% Microtype ist einfach super, aber lesen Sie
> > > #+LATEX_HEADER:% unbedingt die Anleitung um das Folgende zu
> > > #+LATEX_HEADER:% verstehen.
> > > #+LATEX_HEADER: \usepackage{mathptmx, enumerate,
> > > setspace,alnumsec}\alnumsecstyle{LRald}
> > > #+LATEX_HEADER: \pagenumbering{roman}
> > > #+LATEX_HEADER: \usepackage[hyphens]{url}
> > > #+LATEX_HEADER: \usepackage{pdfpages}
> > > #+LATEX_HEADER: \usepackage{graphics, color}
> > > #+LATEX_HEADER: \usepackage{xcolor}
> > > #+LATEX_HEADER: \usepackage{graphicx, latexsym, keyval, ifthen,
> > > moreverb}
> > > #+LATEX_HEADER: \usepackage{gnuplottex}
> > > #+LATEX_HEADER: \usepackage{tikz}
> > > #+LATEX_HEADER: \usepackage{gnuplot-lua-tikz}
> > > #+LATEX_HEADER: \hypersetup{
> > > #+LATEX_HEADER: breaklinks=true,
> > > #+LATEX_HEADER: pdfkeywords={},
> > > #+LATEX_HEADER: pdfsubject={},
> > > #+LATEX_HEADER: pdfcreator={Emacs Org-mode version }}
> > >
> > > #+TEXT: [TABLE-OF-CONTENTS]
> > >
> > > -
> > >
> > > (require 'package)
> > > (add-to-list 'package-archives '("org" . "http://orgmode.org/elpa/";) t)
> > > (require 'ox-odt)
> > > (require 'org-latex)
> > > (setq org-export-latex-listings t)
> > > (add-to-list 'org-latex-classes
> > >
> > > '("scrartcl"
> > >
> > >"\\documentclass{scrartcl}"
> > >
> > > ;; [NO-DEFAULT-PACKAGES]
> > > ;; [EXTRA]"
> > >
> > >("\\section{%s}" . "\\section*{%s}")
> > >("\\subsection{%s}" . "\\subsection*{%s}")
> > >("\\subsubsection{%s}" . "\\subsubsection*{%s}")
> > >("\\paragraph{%s}" . "\\paragraph*{%s}")
> > >("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
> > >
> > > (add-to-list 'org-latex-classes
> > >
> > >'("scrbook"
> > >
> > >"\\documentclass{scrbook}"
> > >
> > > ;; [NO-DEFAULT-PACKAGES]
> > > ;; [EXTRA]"
> > >
> > > ("\\chapter{%s}" . "\\chapter*{%s}")
> > >
> > >("\\section{%s}" . "\\section*{%s}")
> > >("\\subsection{%s}" . "\\subsection*{%s}")
> > >("\\subsubsection{%s}" . "\\subsubsection*{%s}")
> > >("\\paragraph{%s}" . "\\p
Re: [O] Solution for very long hyperlinks when exporting to latex?
That is exactly the problem, Rasmus... I am lost in the complexity of object
and metalevels and don't really know where to start reducing it. Except for
the naughty monster urls everything else works fine. Thanks anyway. :)
Good night, Martin
Am Mittwoch, 1. Oktober 2014, 02:20:45 schrieb Rasmus:
> Martin Weigele writes:
> > There you go. Thx.
>
> Please send a minimal example that displays the undesired behavior :)
>
> > #+TITLE: Blah
> > #+AUTHOR: Me und Du
> >
> > #+OPTIONS: H:20
> > #+LATEX_CLASS: scrbook
> >
> > #+LATEX_CLASS_OPTIONS:
> > [paper=17cm:22cm,DIV=calc,BCOR=12mm,titlepage,11pt,scrhack]
> >
> > #+LATEX_HEADER: \usepackage[english,ngerman]{babel}
> > #+LATEX_HEADER:\usepackage{
> > #+LATEX_HEADER: fixltx2e % Verbessert einige Kernkompetenzen von LaTeX2e
> > #+LATEX_HEADER:}
> > #+LATEX_HEADER:\usepackage{%
> > #+LATEX_HEADER: ellipsis, % Korrigiert den Weißraum um Auslassungspunkte
> > #+LATEX_HEADER: ragged2e, % Ermöglicht Flattersatz mit Silbentrennung
> > #+LATEX_HEADER: marginnote,% Für bessere Randnotizen mit \marginnote statt
> > #+LATEX_HEADER:% \marginline
> > #+LATEX_HEADER:}
> > #+LATEX_HEADER:\usepackage[tracking=true]{microtype}%
> > #+LATEX_HEADER:% Microtype ist einfach super, aber lesen Sie
> > #+LATEX_HEADER:% unbedingt die Anleitung um das Folgende zu
> > #+LATEX_HEADER:% verstehen.
> > #+LATEX_HEADER: \usepackage{mathptmx, enumerate,
> > setspace,alnumsec}\alnumsecstyle{LRald}
> > #+LATEX_HEADER: \pagenumbering{roman}
> > #+LATEX_HEADER: \usepackage[hyphens]{url}
> > #+LATEX_HEADER: \usepackage{pdfpages}
> > #+LATEX_HEADER: \usepackage{graphics, color}
> > #+LATEX_HEADER: \usepackage{xcolor}
> > #+LATEX_HEADER: \usepackage{graphicx, latexsym, keyval, ifthen, moreverb}
> > #+LATEX_HEADER: \usepackage{gnuplottex}
> > #+LATEX_HEADER: \usepackage{tikz}
> > #+LATEX_HEADER: \usepackage{gnuplot-lua-tikz}
> > #+LATEX_HEADER: \hypersetup{
> > #+LATEX_HEADER: breaklinks=true,
> > #+LATEX_HEADER: pdfkeywords={},
> > #+LATEX_HEADER: pdfsubject={},
> > #+LATEX_HEADER: pdfcreator={Emacs Org-mode version }}
> >
> > #+TEXT: [TABLE-OF-CONTENTS]
> >
> > -
> >
> > (require 'package)
> > (add-to-list 'package-archives '("org" . "http://orgmode.org/elpa/";) t)
> > (require 'ox-odt)
> > (require 'org-latex)
> > (setq org-export-latex-listings t)
> > (add-to-list 'org-latex-classes
> >
> > '("scrartcl"
> >
> >"\\documentclass{scrartcl}"
> >
> > ;; [NO-DEFAULT-PACKAGES]
> > ;; [EXTRA]"
> >
> >("\\section{%s}" . "\\section*{%s}")
> >("\\subsection{%s}" . "\\subsection*{%s}")
> >("\\subsubsection{%s}" . "\\subsubsection*{%s}")
> >("\\paragraph{%s}" . "\\paragraph*{%s}")
> >("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
> >
> > (add-to-list 'org-latex-classes
> >
> > '("scrbook"
> >
> >"\\documentclass{scrbook}"
> >
> > ;; [NO-DEFAULT-PACKAGES]
> > ;; [EXTRA]"
> >
> >("\\chapter{%s}" . "\\chapter*{%s}")
> >
> >("\\section{%s}" . "\\section*{%s}")
> >("\\subsection{%s}" . "\\subsection*{%s}")
> >("\\subsubsection{%s}" . "\\subsubsection*{%s}")
> >("\\paragraph{%s}" . "\\paragraph*{%s}")
> >("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
> >
> > ;; active Babel languages
> > (org-babel-do-load-languages
> >
> > 'org-babel-load-languages
> > '((gnuplot . t)))
> >
> > ;; add additional languages with '((language . t)))
> > (custom-set-variables
> >
> > ;; custom-set-variables was added by Custom.
> > ;; If you edit it by hand, you could mess it up, so be careful.
> > ;; Your init file should contain only one such instance.
> > ;; If there is more than one, they won't work right.
> > '(org-latex-with-hyperref nil))
> >
&
Re: [O] Solution for very long hyperlinks when exporting to latex?
There you go. Thx.
#+TITLE: Blah
#+AUTHOR: Me und Du
#+OPTIONS: H:20
#+LATEX_CLASS: scrbook
#+LATEX_CLASS_OPTIONS:
[paper=17cm:22cm,DIV=calc,BCOR=12mm,titlepage,11pt,scrhack]
#+LATEX_HEADER: \usepackage[english,ngerman]{babel}
#+LATEX_HEADER:\usepackage{
#+LATEX_HEADER: fixltx2e % Verbessert einige Kernkompetenzen von LaTeX2e
#+LATEX_HEADER:}
#+LATEX_HEADER:\usepackage{%
#+LATEX_HEADER: ellipsis, % Korrigiert den Weißraum um Auslassungspunkte
#+LATEX_HEADER: ragged2e, % Ermöglicht Flattersatz mit Silbentrennung
#+LATEX_HEADER: marginnote,% Für bessere Randnotizen mit \marginnote statt
#+LATEX_HEADER:% \marginline
#+LATEX_HEADER:}
#+LATEX_HEADER:\usepackage[tracking=true]{microtype}%
#+LATEX_HEADER:% Microtype ist einfach super, aber lesen Sie
#+LATEX_HEADER:% unbedingt die Anleitung um das Folgende zu
#+LATEX_HEADER:% verstehen.
#+LATEX_HEADER: \usepackage{mathptmx, enumerate,
setspace,alnumsec}\alnumsecstyle{LRald}
#+LATEX_HEADER: \pagenumbering{roman}
#+LATEX_HEADER: \usepackage[hyphens]{url}
#+LATEX_HEADER: \usepackage{pdfpages}
#+LATEX_HEADER: \usepackage{graphics, color}
#+LATEX_HEADER: \usepackage{xcolor}
#+LATEX_HEADER: \usepackage{graphicx, latexsym, keyval, ifthen, moreverb}
#+LATEX_HEADER: \usepackage{gnuplottex}
#+LATEX_HEADER: \usepackage{tikz}
#+LATEX_HEADER: \usepackage{gnuplot-lua-tikz}
#+LATEX_HEADER: \hypersetup{
#+LATEX_HEADER: breaklinks=true,
#+LATEX_HEADER: pdfkeywords={},
#+LATEX_HEADER: pdfsubject={},
#+LATEX_HEADER: pdfcreator={Emacs Org-mode version }}
#+TEXT: [TABLE-OF-CONTENTS]
-
(require 'package)
(add-to-list 'package-archives '("org" . "http://orgmode.org/elpa/";) t)
(require 'ox-odt)
(require 'org-latex)
(setq org-export-latex-listings t)
(add-to-list 'org-latex-classes
'("scrartcl"
"\\documentclass{scrartcl}"
;; [NO-DEFAULT-PACKAGES]
;; [EXTRA]"
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
(add-to-list 'org-latex-classes
'("scrbook"
"\\documentclass{scrbook}"
;; [NO-DEFAULT-PACKAGES]
;; [EXTRA]"
("\\chapter{%s}" . "\\chapter*{%s}")
("\\section{%s}" . "\\section*{%s}")
("\\subsection{%s}" . "\\subsection*{%s}")
("\\subsubsection{%s}" . "\\subsubsection*{%s}")
("\\paragraph{%s}" . "\\paragraph*{%s}")
("\\subparagraph{%s}" . "\\subparagraph*{%s}")))
;; active Babel languages
(org-babel-do-load-languages
'org-babel-load-languages
'((gnuplot . t)))
;; add additional languages with '((language . t)))
(custom-set-variables
;; custom-set-variables was added by Custom.
;; If you edit it by hand, you could mess it up, so be careful.
;; Your init file should contain only one such instance.
;; If there is more than one, they won't work right.
'(org-latex-with-hyperref nil))
(custom-set-faces
;; custom-set-faces was added by Custom.
;; If you edit it by hand, you could mess it up, so be careful.
;; Your init file should contain only one such instance.
;; If there is more than one, they won't work right.
)
Am Mittwoch, 1. Oktober 2014, 02:04:34 schrieb Rasmus:
> Martin Weigele writes:
> > Hi Rasmus, thank you very much, Wasn't really aware of texdoc
> > this is great. A lot improvement since the old days... :)
>
> TL is astonishing software.
>
> > Yes \url{...} is being produced by the exporter in the footnotes. However,
> > when I try to set the values by means of #+LATEX_HEADER:
> > \usepackage[hyphens] {url} I get an option clash with pdfpages, and if
> > removed, with graphics.
> >
> > Also I found the information that hyperref calls the package url, but it
> > is
> > not clear to me how to influence this behaviour in time in the exporter.
> > The story is similar if I try to modify hyperref with option breaklinks
> > (which is perhaps just passed on to url as 'hyphens').
>
> Please share a complete example as org (that produces the quirk from
> emacs -q) or as tex.
>
> A unsatisfactory solution is url shortener.
>
> —Rasmus
Re: [O] Solution for very long hyperlinks when exporting to latex?
Hi Rasmus, thank you very much, Wasn't really aware of texdoc this
is great. A lot improvement since the old days... :)
Yes \url{...} is being produced by the exporter in the footnotes. However,
when I try to set the values by means of #+LATEX_HEADER: \usepackage[hyphens]
{url} I get an option clash with pdfpages, and if removed, with graphics.
Also I found the information that hyperref calls the package url, but it is
not clear to me how to influence this behaviour in time in the exporter. The
story is similar if I try to modify hyperref with option breaklinks (which is
perhaps just passed on to url as 'hyphens').
Thx anyway,
Martin
Am Mittwoch, 1. Oktober 2014, 01:02:07 schrieb Rasmus:
> Hi Martin,
>
> Martin Weigele writes:
> > very happy with orgmode but rather desperate these days trying to get very
> > long url hyperlinks in footnotes to typeset as line-broken-up links after
> > latex export. I have tried the hints available on texstack etc., but none
> > of the proposed latex methods work. Not even manual \- produces a
> > reasonable result. I have tried with hyperref switched on and off in the
> > emacs org exporter configuration, and with the "linebreak" option of
> > hyperref which is not even accepted depending on the exporter setting.
> >
> > I am using org-version 8.2.4, emacs 24.3.1, texlive 2014, scrbook (added
> > this style to .emacs which works fine otherwise). I am not sure if it has
> > to do with the exporter or with latex/koma script only, or maybe all
> > three of them.
> >
> > Surely someone must have come across this problem and may be able to
> > provide a hint?
>
> url.sy is usually pretty good a breaking urls. Is the url wrapped in
> \url{·} in your .tex file? If no, you probably did something wrong.
> If yes you should consult the url manual ("texdoc url" in your
> terminal if you have TeXLive). Section 5.2 and maybe section 6 could
> be helpful.
>
> Hope it helps,
> Rasmus
--
Dr. Martin Weigele, Kapellenweg 32, 53179 Bonn, Germany
ph. (+49)(0)228 2894468 office - fax (+49)(0)228 2894446
ph. (+49)(0)228 2893997 privat - mobil (+49)(0)177 4196 515
mailto:mar...@weigele.de - http://www.weigele.de
[O] Solution for very long hyperlinks when exporting to latex?
Hi, very happy with orgmode but rather desperate these days trying to get very long url hyperlinks in footnotes to typeset as line-broken-up links after latex export. I have tried the hints available on texstack etc., but none of the proposed latex methods work. Not even manual \- produces a reasonable result. I have tried with hyperref switched on and off in the emacs org exporter configuration, and with the "linebreak" option of hyperref which is not even accepted depending on the exporter setting. I am using org-version 8.2.4, emacs 24.3.1, texlive 2014, scrbook (added this style to .emacs which works fine otherwise). I am not sure if it has to do with the exporter or with latex/koma script only, or maybe all three of them. Surely someone must have come across this problem and may be able to provide a hint? Thanks, Martin
Re: [O] How to include pre-existing pdf files/pages into orgmode pdf or other export output
Hey Skip and Suvayu, this is so cool. Thank you! says Martin
[O] How to include pre-existing pdf files/pages into orgmode pdf or other export output
Hi, is there an easy way to do this (rather than to fiddle around with resulting pdfs)? Thanks, Martin
Re: [O] gnowsys-mode update?
Thank you very much Nagarjuna G - Am Samstag, 19. März 2011, 12:19:46 schrieb Nagarjuna G: > On Fri, Mar 18, 2011 at 8:25 PM, Martin Weigele wrote: > > Hi all, > > > > I've run into some texts about "gnowsys" as a major mode extending org, > > >... >... > Yes. We use the gnowsys-mode interface for sites running using > gnowsys. So far this is the only complete interface for gnowsys. > Mostly used by the developers and those who maintain the sites, such > as atlas.gnowledge.org > OK I understand now the starting point to understand gnowsys, and, hence, for gnowsys on top of orgmode is http://www.gnu.org/software/gnowsys . This is so great. > I am glad that somewhere some one is interested in this project. It > is very encouraging. Let me know what kind of usecase you have > thought about for using gnowsys-mode. > The project is even in pre-infancy state, but it is about using such modelling to understand and learn structures in humanities (for me coming from a CS background). Martin
[O] gnowsys-mode update?
Hi all, I've run into some texts about "gnowsys" as a major mode extending org, e.g. - http://sunsite.informatik.rwth-aachen.de/Publications/CEUR-WS/Vol-514/paper12.pdf - http://lab.gnowledge.org/documentation which seems to be about linking org-mode to semantic web ideas like OWL. But it seems also there is nothing much to be found after 2009. Is this still an active thing going on on top of orgmode? If not what happened to it? Any hints greatly appreciated. Martin
Re: [Orgmode] Strange behaviour of produced latex-pdf
OK the disappearing subtree seems to have been caused by my declaration of a non-existant "a5" latex (style) package. Works now fine with "a4". Thanks for your help. Took me a while to find out where to look for the latex log file. :-) Am Mittwoch, 2. Februar 2011, um 23:53:05 schrieb Martin Weigele: > Am Mittwoch, 2. Februar 2011, um 23:26:05 schrieb Eric S Fraga: > > "Thomas S. Dye" writes: > > > On Feb 2, 2011, at 1:30 AM, Martin Weigele wrote: > > >> Dear all, have encountered the following strange behaviour in > > >> producing latex- > > >> pdf from a standard outline, C-c C-e d . One of many top nodes is > > >> seemingly > > >> arbitrarily not broken down into subnodes. It works fine, however, > > >> when > > >> producing html. Emacs 23.1.1; org-7.4 manually installed; ubuntu > > >> 10.04 LTS. > > > > [...] > > > > >> Like others, the unrefined chapter contains only (sub)headlines, no > > >> text yet. > > >> Any ideas? > > > > > > Aloha Martin, > > > > > > I don't understand what you mean by "not broken down." Could you > > > provide an example of the LaTeX output? > > > > I also do not necessarily understand what is meant by that but I can say > > that I recently had some problems with the latex exporter, especially > > over the weekend, not exporting the full document the way I would have > > expected: whole sub-trees did not get exported to the latex although > > they did come out in an HTML export, for instance. > > > > Unfortunately, I was unable to reproduce this problem with a small > > example and the document where it was exhibited is large and > > definitely not distributable. > > > > Fortunately, the problem seems to have disappeared and my latex export > > works just fine now -- and the document has not changed (it's under > > revision control). > > > > So, I can suggest to Martin: upgrade to the latest git version of org > > and see if that helps? > > > > eric > > Thanks Eric, it appears that the fact that a whole subtree indeed > disappeared from the latex output had left me kind of "speechless" :-) . > No the problem does not go away with latest git sources. > Martin > > ___ > 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 ___ 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
Re: [Orgmode] Strange behaviour of produced latex-pdf
Am Mittwoch, 2. Februar 2011, um 23:26:05 schrieb Eric S Fraga: > "Thomas S. Dye" writes: > > On Feb 2, 2011, at 1:30 AM, Martin Weigele wrote: > >> Dear all, have encountered the following strange behaviour in > >> producing latex- > >> pdf from a standard outline, C-c C-e d . One of many top nodes is > >> seemingly > >> arbitrarily not broken down into subnodes. It works fine, however, > >> when > >> producing html. Emacs 23.1.1; org-7.4 manually installed; ubuntu > >> 10.04 LTS. > > [...] > > >> Like others, the unrefined chapter contains only (sub)headlines, no > >> text yet. > >> Any ideas? > > > > Aloha Martin, > > > > I don't understand what you mean by "not broken down." Could you > > provide an example of the LaTeX output? > > I also do not necessarily understand what is meant by that but I can say > that I recently had some problems with the latex exporter, especially > over the weekend, not exporting the full document the way I would have > expected: whole sub-trees did not get exported to the latex although > they did come out in an HTML export, for instance. > > Unfortunately, I was unable to reproduce this problem with a small > example and the document where it was exhibited is large and > definitely not distributable. > > Fortunately, the problem seems to have disappeared and my latex export > works just fine now -- and the document has not changed (it's under > revision control). > > So, I can suggest to Martin: upgrade to the latest git version of org > and see if that helps? > > eric Thanks Eric, it appears that the fact that a whole subtree indeed disappeared from the latex output had left me kind of "speechless" :-) . No the problem does not go away with latest git sources. Martin ___ 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
[Orgmode] Strange behaviour of produced latex-pdf
Dear all, have encountered the following strange behaviour in producing latex-
pdf from a standard outline, C-c C-e d . One of many top nodes is seemingly
arbitrarily not broken down into subnodes. It works fine, however, when
producing html. Emacs 23.1.1; org-7.4 manually installed; ubuntu 10.04 LTS.
The following declarations are used:
#+TITLE: Blah
#+LaTeX_CLASS: book
#+LATEX_HEADER: \usepackage{a5}\usepackage{german}
#+LANGUAGE: DE
#+TEXT: Blah
While most top nodes are broken down like
\chapter{blah}
\section{blah}
etc..
...one chapter is simply not broken down. I have checked the org file with vi,
there is no evidence that anything is wrong in the orgfile structure. All go
*chapter
**section
***subsection
etc.
Like others, the unrefined chapter contains only (sub)headlines, no text yet.
Any ideas?
___
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
Re: [Orgmode] Re: [OT] Have you also got hooked by Vim?
Am Donnerstag, 20. Januar 2011, um 01:02:51 schrieb Dan Davison: > Matt Lundin writes: >... > > > > FWIW, Org-mode has its own "modal" editing feature: org speed keys. This > > enables one to edit and reorganize the structure of org files with > > single keystrokes. > > > >> So, how many of you here also use Vim? :) > > > > For quick editing (e.g., config files), I use vi(m). For anything else, > > I use emacs. Both are fantastic tools. > > Doesn't emacsclient make emacs just as quick for editing of random files > encountered at the command line? If emacsclient is aliased to, say, 'e', > and if the WM automatically shifts focus to the running emacs, then that > should be pretty quick. > Can't believe I'm seeing this debate 30 yrs. after. :-DDD Martin ___ 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
