Re: [O] Different set of packages for LaTeX export
Hi Fabrice, Hope you are well. Last time I saw you was in Pont-à-Mousson in 2005. On Fri, 2 Oct 2015 06:50:03 +0200 Fabrice Popineau <fabrice.popin...@supelec.fr> wrote: > 2015-10-02 5:30 GMT+02:00 Manfred Lotz <manfred.l...@arcor.de>: > > > On Thu, 01 Oct 2015 21:21:42 +0200 > > Rasmus <ras...@gmx.us> wrote: > > > > > Hi Manfred, > > > > > > Manfred Lotz <manfred.l...@arcor.de> writes: > > > > > > > When creating slides, i.e using beamer I get an option clash > > > > during compiling the tex file because beamer did already load > > > > hyperref. > > > > > > > > How can I solve it? > > > > > > > > Could I have a different package list if the class is beamer? > > > > > > No you can only discriminate based on the compiler version (and > > > actually only in ox-latex, not ox-beamer). > > > > > > > Hm, I think it would be great if a package list could be mapped to a > > certain LaTeX class. > > > > > To solve this, I set up my own LaTeX class. I find it at least as > good as to rely > on Org configuration. Actually, I removed the list of packages that > Org is exporting. > My LaTeX class can produce slides, course notes, exams and so on. > Based on options, I can chose which kind of document and a few things > like the style (font, etc.). > You are right, of course. Using my own class I have the full control to do what I like. Thanks for the idea. -- Manfred
[O] Different set of packages for LaTeX export
Hi all, I have configured LaTeX export for using xelatex. For this I have defined a list of packages in org-latex-default-packages-alist. One of those packages is hyperref with certain options. When creating a normal document, e.g. using class article that works fine. When creating slides, i.e using beamer I get an option clash during compiling the tex file because beamer did already load hyperref. How can I solve it? Could I have a different package list if the class is beamer? -- Manfred
Re: [O] Different set of packages for LaTeX export
On Thu, 01 Oct 2015 21:21:42 +0200
Rasmus <ras...@gmx.us> wrote:
> Hi Manfred,
>
> Manfred Lotz <manfred.l...@arcor.de> writes:
>
> > When creating slides, i.e using beamer I get an option clash
> > during compiling the tex file because beamer did already load
> > hyperref.
> >
> > How can I solve it?
> >
> > Could I have a different package list if the class is beamer?
>
> No you can only discriminate based on the compiler version (and
> actually only in ox-latex, not ox-beamer).
>
Hm, I think it would be great if a package list could be mapped to a
certain LaTeX class.
> You can use a filter to remove hyperref. AFAIK, there's only issues
> if you use funny options for hyperref, e.g. I use
>
> ("unicode, psdextra,hidelinks" "hyperref" nil).
>
I have this
("colorlinks=true, urlcolor=FireBrick, plainpages=false,
pdfpagelabels, bookmarksnumbered" "hyperref" nil)
which IMHO doesn't look to exotic.
> Last I checked there was an open bug report for this, so it might have
> been fixed in upstream beamer.
>
> I use this filter to remove hyperref in beamer exports:
>
>(defun rasmus/org-beamer-filter-remove-hyperref (text backend
> info) "Remove hyperref from beamer tex files.
>
> My default values are incompatible with beamer."
> ;; TODO: make better solution; check if still necessary
> (when (org-export-derived-backend-p backend 'beamer)
>(replace-regexp-in-string
> "usepackage\\[\\(.*?\\)\\]{hyperref}\n"
> ""
> text)))
>
>(add-to-list 'org-export-filter-final-output-functions
> 'rasmus/org-beamer-filter-remove-hyperref)
>
>
Yep, this works fine.
Thanks a lot for your help.
--
Best, Manfred
[O] line width in html export
Hi there,
When exporting to html text lines get as long as the browser window is
wide which could look pretty ugly.
If I add something like this into the exported html file
body {
color: #888;
font: 300 16px/22px Open Sans, Helvetica Neue, Helvetica, Arial,
sans-serif; }
then the line width gets under control. I'm not an html expert, and
thus don't know if this is the way to go. If there is anything better
please tell me.
Question: How would I tell org-mode to insert this into the exported
html in order to extend the CSS?
--
Manfred
Re: [O] beamer and changing font size for example environment
On Mon, 13 Oct 2014 08:50:09 +0100
Eric S Fraga e.fr...@ucl.ac.uk wrote:
On Saturday, 11 Oct 2014 at 10:42, Manfred Lotz wrote:
Maybe a stupid question.
How could I change font size (in my case to smaller) for an example
environment in org-mode? Needed in export to Beamer pdf.
Not sure what exactly you are asking but IIUC maybe something along
these lines will work for you:
--8---cut here---start-8---
#+latex: {\footnotesize
org stuff here
#+latex: }
--8---cut here---end---8---
Choose the font size you want.
You can also /shrink/ individual frames in beamer.
Thanks, that is what I was looking for.
--
Manfred
[O] beamer and changing font size for example environment
Maybe a stupid question. How could I change font size (in my case to smaller) for an example environment in org-mode? Needed in export to Beamer pdf. -- Thanks, Manfred
[O] Syntaxhighlighing in headers
Hi there, If have something like this * Information (Local) because of the parenthesis the line will not be highlighted. Is there a customization knob to get ( and ) added to the list of valid characters? -- Thanks, Manfred
[O] export to man page problem
Hi there, When exporting to a man page an underscore will be translated to nothing. Any idea what I could do? -- Manfred
Re: [O] export to man page problem
Hi Nicolas, Thanks for answering. On Sun, 07 Sep 2014 09:12:21 +0200 Nicolas Goaziou m...@nicolasgoaziou.fr wrote: Hello, Manfred Lotz manfred.l...@arcor.de writes: When exporting to a man page an underscore will be translated to nothing. Any idea what I could do? Because I know close to nothing about Groff, could you give an example illustrating 1. what you wrote, 2. what you expected to have in the .man file, 3. what you actually got. Take this --snip #+TITLE: mycmd * NAME mycmd - does very important things * SYNOPSIS mycmd.pl -u bla [-R] [-A] [-n] [-a] * DESCRIPTION mycmd could be configured by setting environment variable MYCMD_OPT --snap The man page looks like this: mycmd(1) General Commands Manual mycmd(1) NAME mycmd - does very important things SYNOPSIS mycmd.pl -u bla [-R] [-A] [-n] [-a] DESCRIPTION mycmd could be configured by setting environment variable MYCMDOPT As you can see the _ (underscore) in MYCMD_OPT vanished. -- Manfred
Re: [O] export to man page problem
On Sun, 07 Sep 2014 10:14:59 +0200
Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
Manfred Lotz manfred.l...@arcor.de writes:
Take this
--snip
#+TITLE: mycmd
* NAME
mycmd - does very important things
* SYNOPSIS
mycmd.pl -u bla [-R] [-A] [-n] [-a]
* DESCRIPTION
mycmd could be configured by setting environment variable MYCMD_OPT
--snap
The man page looks like this:
mycmd(1) General Commands
Manual mycmd(1)
NAME
mycmd - does very important things
SYNOPSIS
mycmd.pl -u bla [-R] [-A] [-n] [-a]
DESCRIPTION
mycmd could be configured by setting environment variable
MYCMDOPT
As you can see the _ (underscore) in MYCMD_OPT vanished.
In this case, _OPT is a subscript, which is translated into
MYCMD\d\s-2OPT\s+2\u. For some reason, groff doesn't recognize this
markup.
Anyway, you probably don't want a subscript here. Locally, you can use
a macro instead:
MYCMD\under{}OPT
or simply disable subscript (and superscript) for the whole document:
#+OPTIONS: ^:nil
In this case I prefer the OPTINS version. However, it is good to know I
just could use \under.
Thanks a lot for your help.
--
Manfred
Re: [O] minted question
Hi Tom,
On Mon, 21 Jul 2014 10:48:14 -1000
t...@tsdye.com (Thomas S. Dye) wrote:
Hi Manfred,
Manfred Lotz manfred.l...@arcor.de writes:
Hi Tom,
On Mon, 21 Jul 2014 09:53:41 -1000
t...@tsdye.com (Thomas S. Dye) wrote:
Aloha Manfred,
You should be able to use attr_latex (untested).
Manfred Lotz manfred.l...@arcor.de writes:
#+ATTR_LATEX: :options linenos=true frame=single
#+BEGIN_SRC perl
#! /usr/bin/perl
use strict;
use warnings;
use 5.010;
say 'hey';
#+END_SRC
Unfortunately, that doesn't work.
Yes, when I tried a slightly modified version here I got incorrect
LaTeX output:
\begin{minted}[,linenos=true, frame=single]{perl}
#! /usr/bin/perl
use strict;
use warnings;
use 5.010;
say 'hey';
\end{minted}
Note the extraneous comma in the optional argument before linenos.
I get what looks to be correct LaTeX export if I set options in the
variable org-latex-minted-options, as shown in the emacs-lisp code
block below.
#+ATTR_LATEX: :options linenos=true, frame=single
#+BEGIN_SRC perl
#! /usr/bin/perl
use strict;
use warnings;
use 5.010;
say 'hey';
#+END_SRC
#+begin_src emacs-lisp
(require 'ox-latex)
(add-to-list 'org-latex-packages-alist '( minted))
(setq org-latex-listings 'minted)
(setq org-latex-minted-options
'((linenos true) (frame single)))
#+end_SEC
In the end I did put the code into the .emacs file which isn't too bad
as I usually like to have those minted settings globally.
--
Best, Manfred
[O] How to get results into export?
I have this minimal example using minted:
#+TITLE: Minimal example
#+LaTeX_HEADER: \usemintedstyle{emacs}
* Example
- some code
#+BEGIN_SRC sh :results values code
echo # of items
echo \# of items
echo # of items
#+END_SRC
#+RESULTS:
#+BEGIN_SRC sh
# of items
# of items
#+END_SRC
I evaluated the source code block and got the results. Now, when
exporting the file to say PDF the results won't appear in the PDF.
Is there a possibility to make this happen?
--
Thanks, Manfred
From owner-freebsd-pkg-fall...@freebsd.org Thu Jul 24 23:41:20 2014
Return-path: owner-freebsd-pkg-fall...@freebsd.org
Envelope-to: arch...@mail-archive.com
Delivery-date: Thu, 24 Jul 2014 23:41:20 -0700
Received: from bolt10a.mxthunder.net ([209.105.224.168])
by mail-archive.com with esmtp (Exim 4.76)
(envelope-from owner-freebsd-pkg-fall...@freebsd.org)
id 1XAZBw-0002DA-87
for arch...@mail-archive.com; Thu, 24 Jul 2014 23:41:20 -0700
Received: by bolt10a.mxthunder.net (Postfix, from userid 12345)
id 3hKLQy0kgzz16gsl; Thu, 24 Jul 2014 23:40:48 -0700 (PDT)
Received: from mx2.freebsd.org (mx2.freebsd.org [8.8.178.116])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by bolt10a.mxthunder.net (Postfix) with ESMTPS id 3hKLQR1xm5z1S5P2
for arch...@mail-archive.com; Thu, 24 Jul 2014 23:40:47 -0700 (PDT)
Received: from hub.freebsd.org (hub.freebsd.org [8.8.178.136])
(using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
(No client certificate requested)
by mx2.freebsd.org (Postfix) with ESMTPS id BADED71E;
Fri, 25 Jul 2014 06:40:46 + (UTC)
Received: from hub.freebsd.org (hub.freebsd.org
[IPv6:2001:1900:2254:206c::16:88])
by hub.freebsd.org (Postfix) with ESMTP id B6A575AC;
Fri, 25 Jul 2014 06:40:46 + (UTC)
Delivered-To: pkg-fall...@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 8117459E
for pkg-fall...@freebsd.org; Fri, 25 Jul 2014 06:40:41 + (UTC)
Received: from beefy1.isc.freebsd.org (beefy1.isc.freebsd.org
[IPv6:2001:4f8:3:ffe0:4072:0:16:38])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 6D7D92986;
Fri, 25 Jul 2014 06:40:41 + (UTC)
Received: from beefy1.isc.freebsd.org (localhost [127.0.0.1])
by beefy1.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id s6P6efPX029213;
Fri, 25 Jul 2014 06:40:41 GMT (envelope-from pkg-fall...@freebsd.org)
Received: (from root@localhost)
by beefy1.isc.freebsd.org (8.14.9/8.14.9/Submit) id s6P6efjC029157;
Fri, 25 Jul 2014 06:40:41 GMT (envelope-from pkg-fall...@freebsd.org)
Date: Fri, 25 Jul 2014 06:40:41 GMT
From: pkg-fall...@freebsd.org
Message-Id: 201407250640.s6p6efjc029...@beefy1.isc.freebsd.org
To: ross...@gmail.com
Subject: [package - 10i386-default][graphics/] Failed for -323_5 in
build
Cc: pkg-fall...@freebsd.org
X-BeenThere: freebsd-pkg-fall...@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Fallout logs from package building freebsd-pkg-fallout.freebsd.org
List-Unsubscribe:
https://lists.freebsd.org/mailman/options/freebsd-pkg-fallout,
mailto:freebsd-pkg-fallout-requ...@freebsd.org?subject=unsubscribe
List-Archive: http://lists.freebsd.org/pipermail/freebsd-pkg-fallout/
List-Post: mailto:freebsd-pkg-fall...@freebsd.org
List-Help: mailto:freebsd-pkg-fallout-requ...@freebsd.org?subject=help
List-Subscribe:
https://lists.freebsd.org/mailman/listinfo/freebsd-pkg-fallout,
mailto:freebsd-pkg-fallout-requ...@freebsd.org?subject=subscribe
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-freebsd-pkg-fall...@freebsd.org
Sender: owner-freebsd-pkg-fall...@freebsd.org
X-MXTHUNDER-Identifier: 201407250640.s6p6efjc029...@beefy1.isc.freebsd.org
X-MXTHUNDER-IP-Rating: 0, 8.8.178.116, Ugly c=0 p=0 Source New
X-MXTHUNDER-Scan-Result: 100
X-MXTHUNDER-Rules:
100-5946975-2143-2162-m
100-5946975-0-30815-f
X-MXTHUNDER-Group: Bulk Mail
You are receiving this mail as a port that you maintain
is failing to build on the FreeBSD package build server.
Please investigate the failure and submit a PR to fix
build.
Maintainer: ross...@gmail.com
Last committer: zeis...@freebsd.org
Ident: $FreeBSD: head/graphics//Makefile 351411 2014-04-16
18:28:47Z zeising $
Log URL:
http://beefy1.isc.freebsd.org/data/10i386-default/2014-07-24_17h59m28s/logs/-323_5.log
Build URL:
http://beefy1.isc.freebsd.org/build.html?mastername=10i386-defaultbuild=2014-07-24_17h59m28s
Log:
Building graphics/
build started at Fri Jul 25 06:40:37 UTC 2014
port directory: /usr/ports/graphics/
building for: FreeBSD
Re: [O] How to get results into export?
On Fri, 25 Jul 2014 10:03:14 +0200
Thorsten Jolitz tjol...@gmail.com wrote:
Manfred Lotz manfred.l...@arcor.de writes:
I have this minimal example using minted:
#+TITLE: Minimal example
#+LaTeX_HEADER: \usemintedstyle{emacs}
* Example
- some code
#+BEGIN_SRC sh :results values code
echo # of items
echo \# of items
echo # of items
#+END_SRC
#+RESULTS:
#+BEGIN_SRC sh
# of items
# of items
#+END_SRC
I evaluated the source code block and got the results. Now, when
exporting the file to say PDF the results won't appear in the PDF.
Is there a possibility to make this happen?
Try header arg
,
| :exports results
`
(untested)
Oops yes, it is such easy. In my case :results both is what I want.
--
Thanks a lot, Manfred
Re: [O] How to get results into export?
On Fri, 25 Jul 2014 11:11:23 +0200
Manfred Lotz manfred.l...@arcor.de wrote:
On Fri, 25 Jul 2014 10:03:14 +0200
Thorsten Jolitz tjol...@gmail.com wrote:
Manfred Lotz manfred.l...@arcor.de writes:
I have this minimal example using minted:
#+TITLE: Minimal example
#+LaTeX_HEADER: \usemintedstyle{emacs}
* Example
- some code
#+BEGIN_SRC sh :results values code
echo # of items
echo \# of items
echo # of items
#+END_SRC
#+RESULTS:
#+BEGIN_SRC sh
# of items
# of items
#+END_SRC
I evaluated the source code block and got the results. Now, when
exporting the file to say PDF the results won't appear in the PDF.
Is there a possibility to make this happen?
Try header arg
,
| :exports results
`
(untested)
Oops yes, it is such easy. In my case :results both is what I want.
Sorry, I wanted to say: :exports both
-- Manfred
[O] minted question
Hi there,
I have a an org file which gets exported to beamer. The following
example (although I do not know if there are errors) works fine.
Now I would like to get a frame around the perl code, and also line
numbers. How can I define this in the org file?
--
Thanks,
Manfred
Minimal example:
#+TITLE: My slides
#+AUTHOR: Manfred Lotz
#+EMAIL: manfred.l...@yahoo.de
#+DATE: 2014-07-21
#+LaTeX_CLASS_options: [bigger, allowframebreaks]
#+LaTeX_HEADER: \usepackage{minted}
#+LaTeX_HEADER: \usemintedstyle{emacs}
#+OPTIONS: H:2 toc:t num:t
#+TOC: headlines [currentsection]
#+startup: beamer
#+BEAMER_THEME: CambridgeUS
#+BEAMER_COLOR_THEME: dolphin
* Introduction
** A simple slide
The following contains some perl code
- a minimal perl example
#+BEGIN_SRC perl
#! /usr/bin/perl
use strict;
use warnings;
use 5.010;
say 'hey';
#+END_SRC
- the previous point shows the use of the minted environment
Re: [O] minted question
Hi Tom, On Mon, 21 Jul 2014 09:53:41 -1000 t...@tsdye.com (Thomas S. Dye) wrote: Aloha Manfred, You should be able to use attr_latex (untested). Manfred Lotz manfred.l...@arcor.de writes: #+ATTR_LATEX: :options linenos=true frame=single #+BEGIN_SRC perl #! /usr/bin/perl use strict; use warnings; use 5.010; say 'hey'; #+END_SRC Unfortunately, that doesn't work. I also tried #+ATTR_LaTeX: :environment minted :linenos true :frame single which didn't do it either. -- Manfred
Re: [O] minted question
Hi Thomas,
On Mon, 21 Jul 2014 10:48:14 -1000
t...@tsdye.com (Thomas S. Dye) wrote:
Hi Manfred,
Manfred Lotz manfred.l...@arcor.de writes:
Hi Tom,
On Mon, 21 Jul 2014 09:53:41 -1000
t...@tsdye.com (Thomas S. Dye) wrote:
Aloha Manfred,
You should be able to use attr_latex (untested).
Manfred Lotz manfred.l...@arcor.de writes:
#+ATTR_LATEX: :options linenos=true frame=single
#+BEGIN_SRC perl
#! /usr/bin/perl
use strict;
use warnings;
use 5.010;
say 'hey';
#+END_SRC
Unfortunately, that doesn't work.
Yes, when I tried a slightly modified version here I got incorrect
LaTeX output:
\begin{minted}[,linenos=true, frame=single]{perl}
#! /usr/bin/perl
use strict;
use warnings;
use 5.010;
say 'hey';
\end{minted}
Note the extraneous comma in the optional argument before linenos.
I get what looks to be correct LaTeX export if I set options in the
variable org-latex-minted-options, as shown in the emacs-lisp code
block below.
#+ATTR_LATEX: :options linenos=true, frame=single
#+BEGIN_SRC perl
#! /usr/bin/perl
use strict;
use warnings;
use 5.010;
say 'hey';
#+END_SRC
#+begin_src emacs-lisp
(require 'ox-latex)
(add-to-list 'org-latex-packages-alist '( minted))
(setq org-latex-listings 'minted)
(setq org-latex-minted-options
'((linenos true) (frame single)))
#+end_SEC
Are you getting an extraneous comma with the #+attr_latex line?
All the best,
Tom
I do not get any extraneous comma. When using the #+attr_latex line
there is just nothing in the latex output.
I'm also confused about the emacs-lisp code snippet. I only get it
working if I either put it into my .emacs or evaluate it in the scratch
buffer. The way you wrote it the lisp code shows up in my document.
I messed around with :results but to no avail.
--
Best, Manfred
Re: [O] #+TEXT: disappeared
On Thu, 19 Dec 2013 21:42:47 +0100 Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Manfred Lotz manfred.l...@arcor.de writes: Actually I want to have an abstract between title/author and the first chapter. Isn't the following sufficient? #+title: My title #+author: Me #+begin_abstract ... #+end_abstract * First section Contents Yes, this works. I simply didn't know about #+BEGIN_ABSTACT aso. -- Thanks, Manfred
Re: [O] #+TEXT: disappeared
Hi Bastien, On Mon, 23 Dec 2013 00:05:39 +0100 Bastien b...@gnu.org wrote: Hi Manfred, Manfred Lotz manfred.l...@arcor.de writes: Yes, this works. I simply didn't know about #+BEGIN_ABSTACT aso. I guess this is a quite common need for the LaTeX exporter, so I explicitely used #+BEGIN_ABSTACT as an example of special block in the manual. This will be in the next release. Yes, it is good to have #+BEGIN_ABSTACT available. I discovered that even a #+BEGIN_BLABLA would work if I only would export to LaTeX (if there is an environment blabla is LaTeX). Other exporters wouldn't know blabla, of course. -- Manfred
Re: [O] #+TEXT: disappeared
On Wed, 18 Dec 2013 19:39:39 +0100 Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Manfred Lotz manfred.l...@arcor.de writes: On Tue, 17 Dec 2013 15:53:25 +0100 Sebastien Vauban sva-n...@mygooglest.com wrote: Manfred Lotz wrote: I just found that #+TEXT: from pre 8 org-mode has disappeared. Does anybody know how this is done with org-mode 8? IIUC, it became `#+ascii:'. Best regards, Seb Hm, when I try this it won't even appear in the .tex file. TEXT keywords were removed in Org 8 because we do not need them anymore. Would you mind providing your use case, or, better, an example, so we can help you? Regards, Actually I want to have an abstract between title/author and the first chapter. -- Manfred
Re: [O] #+TEXT: disappeared
On Wed, 18 Dec 2013 08:40:31 -1000 t...@tsdye.com (Thomas S. Dye) wrote: Manfred Lotz manfred.l...@arcor.de writes: On Tue, 17 Dec 2013 15:53:25 +0100 Sebastien Vauban sva-n...@mygooglest.com wrote: Manfred Lotz wrote: I just found that #+TEXT: from pre 8 org-mode has disappeared. Does anybody know how this is done with org-mode 8? IIUC, it became `#+ascii:'. Best regards, Seb Hm, when I try this it won't even appear in the .tex file. I'm not sure what your expectations might be, but if you want to add special code to a .tex file, Section 12.7.3 of the manual, Quoting LaTeX code, describes how to do that. I know about this but I didn't want to do this. I just said if #+ASCII: had any effect I would have seen it in the resulting tex file when exporting to LaTeX file. -- Manfred
Re: [O] #+TEXT: disappeared
On Tue, 17 Dec 2013 15:53:25 +0100 Sebastien Vauban sva-n...@mygooglest.com wrote: Manfred Lotz wrote: I just found that #+TEXT: from pre 8 org-mode has disappeared. Does anybody know how this is done with org-mode 8? IIUC, it became `#+ascii:'. Best regards, Seb Hm, when I try this it won't even appear in the .tex file. -- Manfred
[O] #+TEXT: disappeared
Hi there, I just found that #+TEXT: from pre 8 org-mode has disappeared. Does anybody know how this is done with org-mode 8? -- Thanks, Manfred
Re: [O] export question
On Sun, 1 Sep 2013 20:50:07 +0200 Suvayu Ali fatkasuvayu+li...@gmail.com wrote: On Sun, Sep 01, 2013 at 06:49:01PM +0200, Manfred Lotz wrote: Now I want to export the file to an ascii buffer/file where show the content as a table. I want to omit certain p lines. So I would like to have something like this where I would like to show only certain columns. val p1 p14 -- item 1 something bla item n hm more more bla [...chomp...chomp...chomp...] I guess 1. makes much sense. In this case I like to know if there is a tutorial showing how to do my own exporter or where to find specific documentation how to do this? ox-odt.el has a feature like this, list to tables. You can take a look there for hints. Thanks for the pointer. I'll look at it. -- Manfred
[O] export question
Hi all, I have an org file which looks like this: * My list ** item1 - p1 :: something - p2 :: 23232 ... - p14 :: bla ** item2 - p1 :: another valu - p2 :: 21 ... - p14 :: more bla ... ** itemn - p1 :: hm - p2 :: 3842 ... - p14 :: more more bla ... in the p list means there are also p3 till p13 ... in the item list indicates there are n items actually. Now I want to export the file to an ascii buffer/file where show the content as a table. I want to omit certain p lines. So I would like to have something like this where I would like to show only certain columns. val p1 p14 -- item 1 something bla item n hm more more bla How do I achieve this? I see basically two possibilities like follows: 1. write my own special exporter 2. write an external program which does it I guess 1. makes much sense. In this case I like to know if there is a tutorial showing how to do my own exporter or where to find specific documentation how to do this? Perhaps there is something very simple I do not even think of? Any hints appreciated. -- Thanks a lot in advance, Manfred
Re: [O] export to odt
On Fri, 14 Jun 2013 09:07:26 +0200 Christian Moe m...@christianmoe.com wrote: Manfred Lotz writes: On Thu, 13 Jun 2013 08:37:55 +0100 Eric S Fraga e.fr...@ucl.ac.uk wrote: Manfred Lotz manfred.l...@arcor.de writes: [...] This is really weird or it is because just my knowledge about Libreoffice is limited. At least, I'm happy to be able to use LaTeX in most cases instead of an office product. I'm with you on this! I use LaTeX almost exclusively. Every now and again, unfortunately, I have to share an editable document with others and LibreOffice/MSWord is the only easy way. For simple dissemination, LaTeX - PDF is better. Yep, exactly. I'm grateful that the export to odt was implemented in org-mode so that we have an option to give a finalized document away if needed. Note, however, that what you've been discussing is a feature, not a requirement. LibreOffice allows you to put the title of the document in a field code that mirrors the document metadata; it doesn't force you to, and I imagine 95% of users aren't even aware of the option. As I recall, this was a solution Jambunathan opted for at some late point in the development of the org-odt exporter. Before that, the exporter just wrote the title in as ordinary, editable text. I sort of preferred the old approach, but not enough to bother to ask to have it back. Yes I'm aware that this is due to the way how org-mode export to odt is coded. But if many users are baffled why they can't just edit a document title on the page itself after exporting to ODT -- and that seems likely -- maybe this feature is ripe for a change. Hm, I do not have any requirements to later change title and author in the odt document as I would change it in the org file directly. Thus I don't care how the title and author is set in the odt document. -- Manfred
Re: [O] export to odt
On Thu, 13 Jun 2013 08:37:55 +0100 Eric S Fraga e.fr...@ucl.ac.uk wrote: Manfred Lotz manfred.l...@arcor.de writes: [...] This is really weird or it is because just my knowledge about Libreoffice is limited. At least, I'm happy to be able to use LaTeX in most cases instead of an office product. I'm with you on this! I use LaTeX almost exclusively. Every now and again, unfortunately, I have to share an editable document with others and LibreOffice/MSWord is the only easy way. For simple dissemination, LaTeX - PDF is better. Yep, exactly. I'm grateful that the export to odt was implemented in org-mode so that we have an option to give a finalized document away if needed. -- Manfred
Re: [O] export to odt
On Wed, 12 Jun 2013 08:33:55 +0100 Eric S Fraga e.fr...@ucl.ac.uk wrote: Manfred Lotz manfred.l...@arcor.de writes: On Tue, 11 Jun 2013 11:33:56 +0100 Eric S Fraga e.fr...@ucl.ac.uk wrote: [...] 2. The title and author fields in the exported document are protected in some way and I cannot figure out how to enable editing on them. I can change the style for these just fine but I cannot change the text. You easily can setup both title and author in your org document like this: #+TITLE: My Important Documentation #+AUTHOR: Manfred Lotz Is this what you mean? No. I know I can set the title and author in org. However, sometimes, I need to tweak the title or author information *only* in the exported document. Aah, ok. Now I see what your are after. GO to menu entry File/Properties and then you click tab Description. There you can edit Title. It seems that you can edit author via menu Tools/Options. Then choose LibreOffice/User Data and edit First/Last Name. Finally, you have to go to File/Properties and click on Reset (Please note, that there 'Apply user data' must be clicked on). This is really weird or it is because just my knowledge about Libreoffice is limited. At least, I'm happy to be able to use LaTeX in most cases instead of an office product. -- Manfred
Re: [O] export to odt
On Tue, 11 Jun 2013 11:33:56 +0100 Eric S Fraga e.fr...@ucl.ac.uk wrote: Manfred Lotz manfred.l...@arcor.de writes: [...] The following worked fine: I loaded the exported odt document, changed the Heading 1 style to do a page break before the heading and saved the template as my.ott (I copied it into the ~/org directory). Thanks. Very helpful. I have two different questions about exporting to ODT, one related to style and other not: 1. Description lists are indented somehow, both the item and the description. I would like to change the indentation but the LibreOffice sytle dialogue doesn't show any indentation. I cannot find where the indentation is specified. Hm, not quite sure about this as I am no expert regarding Libreoffice. I will have a look if I find anything about this. 2. The title and author fields in the exported document are protected in some way and I cannot figure out how to enable editing on them. I can change the style for these just fine but I cannot change the text. You easily can setup both title and author in your org document like this: #+TITLE: My Important Documentation #+AUTHOR: Manfred Lotz Is this what you mean? -- Manfred
Re: [O] export to odt
Hi Eric, On Tue, 11 Jun 2013 11:33:56 +0100 Eric S Fraga e.fr...@ucl.ac.uk wrote: Manfred Lotz manfred.l...@arcor.de writes: [...] The following worked fine: I loaded the exported odt document, changed the Heading 1 style to do a page break before the heading and saved the template as my.ott (I copied it into the ~/org directory). Thanks. Very helpful. I have two different questions about exporting to ODT, one related to style and other not: 1. Description lists are indented somehow, both the item and the description. I would like to change the indentation but the LibreOffice sytle dialogue doesn't show any indentation. I cannot find where the indentation is specified. I found the following. You open the Modify Dialog for style OrgDescriptionList. Here you choose tab Position. Then you can modify indentation for level 1 and 2. Example: org mode: - dog :: is an animal In odt document dog is an animal Then dog is level 1 and 'is an animal' is level 2. Then as previously described the style could be saved in an .ott file and be specified in the org file itself. Hope this helps. -- Manfred
Re: [O] Tbl: precision for cells
On Sat, 18 May 2013 17:07:36 +0200 Suvayu Ali fatkasuvayu+li...@gmail.com wrote: On Fri, May 17, 2013 at 10:18:08PM +0200, Manfred Lotz wrote: [...chomp...chomp...chomp...] As the numeric fields are currency fields could I specify somehow for the whole table that there are exactly 2 decimals after the dot? Have you looked at the Chapter on tables in the manual? http://orgmode.org/manual/Formula-syntax-for-Calc.html#Formula-syntax-for-Calc Hope this helps, Yes, I had checked this out. However, didn't find anything on this page helping me. I know that I could add ;%.2f to each formula in the table. However, I would like to specify %.2f only one time for the whole table. -- Manfred
[O] Tbl: precision for cells
I have a table like this | Item |F1 | F2 | F3 | |--++--+--| | w| 579.12 | 110.0328 | 689.1528 | | x| 28.8 |5.472 | 34.272 | | y| 13.2 |2.508 | 15.708 | | z|24. | 4.56 |28.56 | |--++--+--| | Sum | 513.12 | 97.4928 | 610.6128 | As the numeric fields are currency fields could I specify somehow for the whole table that there are exactly 2 decimals after the dot? So that I have this: | Item |F1 | F2 | F3 | |--++--+--| | w| 579.12 | 110.03 | 689.15 | | x| 28.80 | 5.47 |34.27 | | y| 13.20 | 2.51 |15.71 | | z| 24.00 | 4.56 |28.56 | |--++--+--| | Sum | 513.12 |97.49 | 610.61 | -- Thanks, Manfred
Re: [O] How could I configure an export directory?
On Thu, 25 Apr 2013 11:53:16 -0500 John Hendy jw.he...@gmail.com wrote: On Thu, Apr 25, 2013 at 10:51 AM, Manfred Lotz manfred.l...@arcor.de wrote: Hi there, When I export to pdf (involving LaTeX), odt or whatever I would like all those files (including temporary files) to reside in a special directory, say ~/org/exportdir Looks like this has come up before: - http://stackoverflow.com/questions/9559753/emacs-org-mode-export-to-another-directory - http://lists.gnu.org/archive/html/emacs-orgmode/2012-03/msg00264.html I tried both (for pdf and html) but to no avail. Looking into ox-latex.el it seems that this is just not possible at this point in time as pdflatex's --output-directory parameter has a value %o which is just the base directory of the file. -- Manfred
[O] How could I configure an export directory?
Hi there, When I export to pdf (involving LaTeX), odt or whatever I would like all those files (including temporary files) to reside in a special directory, say ~/org/exportdir How can I configure this? -- Thanks, Manfred
[O] odt export not working
Hi there, Using org-mode 8.0-2-g77476c (fedora 18 system) exporting to odt doesn't work. zip program is available. When I do =C-c C-e= the *Org Export Dispatcher* buffer pops up but showing nothing related to odt. When now typing =o o= I get =Invalid Key=. Any idea what's going wrong. -- Thanks, Manfred
Re: [O] odt export not working
On Sun, 21 Apr 2013 22:29:10 +0800 Eric Abrahamsen e...@ericabrahamsen.net wrote: Manfred Lotz manfred.l...@arcor.de writes: Hi there, Using org-mode 8.0-2-g77476c (fedora 18 system) exporting to odt doesn't work. zip program is available. When I do =C-c C-e= the *Org Export Dispatcher* buffer pops up but showing nothing related to odt. When now typing =o o= I get =Invalid Key=. Any idea what's going wrong. Are you calling (require 'ox-odt) somewhere in your config? Or configuring `org-export-backends'? ODT export isn't loaded by default, you'll have to load it explicitly by one of those two methods. Hope that's the extent of the problem, Eric Yep, that was it. I didn't know that. Thanks a lot, Eric. -- Manfred
