Looks interesting indeed. You're using many more LaTeX features than I
ever do and I can see how your configuration would be useful in those
cases. More examples will help in understanding when it will be useful.
--
: Eric S Fraga via Emacs 28.0.50, Org release_9.4.4-254-g37749c
Eric S Fraga writes:
> On Wednesday, 31 Mar 2021 at 20:28, Martin Steffen wrote:
>> And there is a final thing which (for me) seem to work better in
>> latex-mode compared to org. That's jumping to the ``next error'' with
>> some key stroke. That's important, LaTeX's own error output it quite
>>
Eric S Fraga writes:
> On Thursday, 1 Apr 2021 at 16:50, Timothy wrote:
>> I think in part this works for me because of a particular system I
>> have in place (that IMHO works *wonderfully* with Org) which I plan on
>> submitting patches to upstream (to Org) in the not-to-distant future.
>
>
On Thursday, 1 Apr 2021 at 16:50, Timothy wrote:
> I think in part this works for me because of a particular system I
> have in place (that IMHO works *wonderfully* with Org) which I plan on
> submitting patches to upstream (to Org) in the not-to-distant future.
Interesting. Look forward to
Eric S Fraga writes:
> On Wednesday, 31 Mar 2021 at 20:28, Martin Steffen wrote:
>> And there is a final thing which (for me) seem to work better in
>> latex-mode compared to org. That's jumping to the ``next error'' with
>> some key stroke. That's important, LaTeX's own error output it quite
On Thursday, 1 Apr 2021 at 18:00, Tim Cross wrote:
> the only small bit of help I've found is org-lint, which has helped me
org-lint is very helpful indeed.
> Having said that, I find the most common cause of errors in the *.tex
> export is due to in-line Latex in my org file. I rarely run into
Eric S Fraga writes:
> On Wednesday, 31 Mar 2021 at 20:28, Martin Steffen wrote:
>> And there is a final thing which (for me) seem to work better in
>> latex-mode compared to org. That's jumping to the ``next error'' with
>> some key stroke. That's important, LaTeX's own error output it quite
On Wednesday, 31 Mar 2021 at 20:28, Martin Steffen wrote:
> And there is a final thing which (for me) seem to work better in
> latex-mode compared to org. That's jumping to the ``next error'' with
> some key stroke. That's important, LaTeX's own error output it quite
> poor, but jumping to error
Martin Steffen writes:
> [...] And last not least; if I ``compile'' the document (firing off latex,
> bibtex, or index or whatever), the compilation runs in the background.
> As far as I do that in org (exporting to pdf), it blocks emacs. Not
> that it's a huge delay even, at least for smaller
> "Eric" == Eric S Fraga writes:
Eric> On Tuesday, 30 Mar 2021 at 17:44, Juan Manuel Macías wrote:
>> However, *I would not recommend anyone to use LaTeX for
>> writing*. A light markup language is more comfortable and
>> efficient for me.
Eric> Totally agree! Although,
On Tuesday, 30 Mar 2021 at 17:44, Juan Manuel Macías wrote:
> However, *I would not recommend anyone to use LaTeX for writing*. A
> light markup language is more comfortable and efficient for me.
Totally agree! Although, over the years, I have written many papers in
LaTeX directly, in the past
Martin Steffen writes:
>
> There is one case where I do _NOT_ use org for such documents (though I
> use org basically most things I do), and that is
>
> collaborative editing,
>
> working together on a document (maybe shared by git), at least with a
> document of some amount of
Martin Steffen writes:
> In my experience, ith latex, it's possible to write text together for
> well-intended people. Publishing houses tell you ``these are the classes
> and style files (among perhaps others) that you _have_ to use, and also
> do the following...'' (same possible for
Martin Steffen wrote:
> I cannot imagine
> that publishers would prescibe ``this is the org-settings and features
> you as author must to use to publish with us''.
If anyone, then the IEEE. In the late 80s, their instructions to authors
included a mindboggling number of allowable DTP-program
> "autofrettage" == autofrettage writes:
autofrettage> Hi,
autofrettage> Not even the most streamlined DTP-wysiwyg-program is
I agree. I did not want to imply that.
autofrettage> safe from this. Far from. I even doubt typewritten
autofrettage> documents can be written
Hi,
Just a remark about what Martin Steffen wrote:
> There is one case where I do NOT use org for such documents (though I
> use org basically most things I do), and that is
>
> collaborative editing,
>
> /.../ one can easily
> mess it up (typically for novices, who start changing layout or
>
Hi, here's my angle (which works for myself) how I use org-exporting in
connection with doing documents (I use in the meantime also org to
export as input for jekyll to produce HTML, but that's a different use,
the heavy lifting there is done in jekyll).
I am a LaTeX user since quite some
On Tue, Mar 30 2021, Eric S Fraga wrote:
> On Tuesday, 30 Mar 2021 at 10:13, Detlef Steuer wrote:
>> Btw. I had do deliver rtf recently. Is there any documented way to generate
>> rtf from org?
>
> Two routes that I know of:
> 1. org -> LaTeX -> rtf using latex2rtf
> 2. org -> odt -> rtf by
Eric S Fraga writes:
> On Tuesday, 30 Mar 2021 at 09:06, Tim Cross wrote:
>> The trick with Latex is to go with the flow, not against it.
>
> +1
>
> This is the first thing I tell my students. LaTeX knows much much more
> about how to make documents look good than any of us ever will.
If you
On Tuesday, 30 Mar 2021 at 10:13, Detlef Steuer wrote:
> Btw. I had do deliver rtf recently. Is there any documented way to generate
> rtf from org?
Two routes that I know of:
1. org -> LaTeX -> rtf using latex2rtf
2. org -> odt -> rtf by saving as that format in LibreOffice.
Pandoc may have
On Tuesday, 30 Mar 2021 at 09:01, Colin Baxter wrote:
> Very true. Unfortunately, you also have to "go with the flow" with the
> publishers who insist on receiving a docx file.
I'm lucky in that the vast majority of the journals I deal with accept
(and prefer) LaTeX.
> Thankfully there's
Am Tue, 30 Mar 2021 09:01:33 +0100
schrieb Colin Baxter :
> Very true. Unfortunately, you also have to "go with the flow" with the
> publishers who insist on receiving a docx file. Thankfully there's
> pandoc, but it's an annoying waste of time having to convert from
> LaTeX to some dreadful
> Eric S Fraga writes:
> On Tuesday, 30 Mar 2021 at 09:06, Tim Cross wrote:
>> The trick with Latex is to go with the flow, not against it.
> +1
> This is the first thing I tell my students. LaTeX knows much much
> more about how to make documents look good than any of
On Tuesday, 30 Mar 2021 at 09:06, Tim Cross wrote:
> The trick with Latex is to go with the flow, not against it.
+1
This is the first thing I tell my students. LaTeX knows much much more
about how to make documents look good than any of us ever will.
--
: Eric S Fraga via Emacs 28.0.50, Org
i tend to be situational. some things i export to html, some to pdf,
some to both. it just depends on the need of whatever small project i'm
working on.
Ypo writes:
> Hi
>
> After some years of using orgmode, and exporting using its defaults, I would
> like to take a quality leap and find a way of exporting for life. My options:
> LaTeX, ODT, HTML.
>
Forget your goal. Technology and user expectations moves too fast and you will
never find a
Aloha Ypo,
"Exporting for life" is a vague target, so it is difficult to give
precise recommendations.
It is usually the case that export to LaTeX doesn't require
subsequent modification of the tex file. In most cases for my
work, I am exporting to a LaTeX document style/class provided by
is org ootb mma? for those of us who woul dlike to spend, like, zero
time exporting, and then, like, less than a half hour fixing htat one
thing that is irritating about hte output, with no errors? i can
dream.
On 3/29/21, autofrettage wrote:
> Hi Ypo and the rest of you all,
>
>> After some
Hi,
Ypo writes:
> LaTeX: I can see some masters here that make professional books, and I
> have some friends that publish scientific papers using LaTeX. But, it
> looks like a like a rabbit hole to me, since even the masters seem to
> have to modify the tex file directly (is this correct?), not
Hi Ypo and the rest of you all,
> After some years of using orgmode, and exporting using its defaults, I would
> like to take a quality leap and find a way of exporting for life. My options:
> LaTeX, ODT, HTML.
/.../
> How do you think I should spend some hundreds (or thousands) of hours to
>
On 29 March 2021, Ypo wrote:
How do you think I should spend some hundreds (or thousands) of hours to
achieve maestry exporting my documents?
I think the key question is: Do you want to preserve them as web pages or
page-based documents? If the web, then it's HTML; if documents, I'd use
Hi
After some years of using orgmode, and exporting using its defaults, I
would like to take a quality leap and find a way of exporting for life.
My options: LaTeX, ODT, HTML.
LaTeX: I can see some masters here that make professional books, and I
have some friends that publish scientific
On 2015-07-29, at 21:32, Xiha x...@laposte.net wrote:
Hi John,
Yes, highlight-regexp looks good and simple, when I apply it manually to
the buffer. No need even to define a new face as the default hi-yellow
is what I want.
But: (how) can I call highlight-regexp from my .emacs file so
Hi John,
Yes, highlight-regexp looks good and simple, when I apply it manually to
the buffer. No need even to define a new face as the default hi-yellow
is what I want.
But: (how) can I call highlight-regexp from my .emacs file so that it
automatically applies to every Org buffer? Or must
Eric S Fraga e.fr...@ucl.ac.uk writes:
3) Custom highlight markers error
No idea about this. It could be a bug anywhere.
Could you maybe post a small example file? I have no idea what you are
describing unfortunately.
I retrieved what I did, from here
On Tuesday, 28 Jul 2015 at 09:24, Sebastien Vauban wrote:
Eric S Fraga e.fr...@ucl.ac.uk writes:
[...]
You can always use macros instead?
Or the `font-lock-add-keywords' mechanism?
Best regards,
Seb
I think the OP wanted markers that would export, not just stand out in
the emacs
You need to differentiate between two aspects: highlighting of text
within a org buffer and what happens to text when exported. In the new
exporter, I don't think you can implement anything that covers both use
cases.
I am not entirely sure what it is you want. If you want just one of
these,
Thanks guys. Getting closer - but please don't overestimate my backgound
knowledge :)
On 07/28/2015 02:05 PM, Eric S Fraga wrote:
You need to differentiate between two aspects: highlighting of text
within a org buffer and what happens to text when exported.
Yes. Principally, I want the
You may find this post on highlighting text helpful:
http://kitchingroup.cheme.cmu.edu/blog/2015/07/28/A-highlight-annotation-mode-for-Emacs-using-font-lock/
I think it also lays the foundation for thinking about how to get it to
export, although you would need to do this as a preprocessing step
Thanks Sebastien and Eric,
On Tuesday, 28 Jul 2015 at 09:24, Sebastien Vauban wrote:
Eric S Fraga e.fraga at ucl.ac.uk writes:
[...]
You can always use macros instead?
Maybe, if I knew how. I haven't used macros before. I read this
http://orgmode.org/manual/Macro-replacement.html and
Xiha x...@laposte.net writes:
Thanks Sebastien and Eric,
On Tuesday, 28 Jul 2015 at 09:24, Sebastien Vauban wrote:
Eric S Fraga e.fraga at ucl.ac.uk writes:
[...]
You can always use macros instead?
Maybe, if I knew how. I haven't used macros before. I read
Thanks Rasmus and Eric!
1) subtitle
The git version has a #+subtitle keyword. See the git version of the
manual for supported backends (most).
Where the git install instructions say you should edit local.mk to
point to the appropriate install location, how do I find out where this
is?
On Monday, 27 Jul 2015 at 15:55, Xiha wrote:
Thanks Rasmus and Eric!
1) subtitle
The git version has a #+subtitle keyword. See the git version of the
manual for supported backends (most).
Where the git install instructions say you should edit local.mk to
point to the appropriate install
On Sunday, 26 Jul 2015 at 15:04, Xiha wrote:
2) I have #+OPTIONS: H:9 num:9 because explicit level structure is
important for this document. I would like to have more control over
For LaTeX export, this will not work (AFAIK) as LaTeX only supports 4 or
so levels of headings.
how this is
Hello,
I am writing a paper-like document in Org-mode, and experimenting with
export to HTML and PDF (via LaTeX) in order to share drafts. Not sure
yet what the final formatting will be. I am quite new to Emacs/Org-mode,
know little about css and nothing about LaTeX. Using Emacs 24.5.1 and
Xiha x...@laposte.net writes:
1) I would like the exported document to have a subtitle under the
title in a smaller and/or lighter font. The latter requirement makes
splitting the title with a newline not quite a solution. I believe I
saw discussion somewhere about a #+SUBTITLE keyword for
On Jul 5, 2009, at 6:40 PM, Nick Dokos wrote:
Spike Spiegel fsm...@gmail.com wrote:
...
Also, given a variable like org-export-latex-image-default-option, is
there any way to override it per file or per document class?
...
Well, yes and no (mostly no - but see below):
o You can of course
Hi Nicholas,
On Sun, Jul 5, 2009 at 4:40 AM, Nick Dokosnicholas.do...@hp.com wrote:
Spike Spiegel fsm...@gmail.com wrote:
...
- I also need to include an image in the titlepage but I don't see any
way to override \maketitle other than maybe renewcommand'ing it, which
I tried with
Spike Spiegel fsm...@gmail.com wrote:
#+LaTeX_HEADER: \titlegraphic{\includegraphics{foo.png}}
Both answers spot on, thanks, with just a minor problem: adding
\titlegraphic won't make the spacing between \title \author \data as
produced by \maketitle shrink so the entire slide is pretty
Spike Spiegel fsm...@gmail.com wrote:
...
I did some more work last night and came across another issues:
- #BEGIN_VERBATIM won't work because to use the \begin{verbatim}
environment the \being{frame} requires [fragile]
I worked around this when working on my presentation by putting
Spike Spiegel fsm...@gmail.com wrote:
...
Also, given a variable like org-export-latex-image-default-option, is
there any way to override it per file or per document class?
...
Well, yes and no (mostly no - but see below):
o You can of course customize this variable, but that's a global
] questions about exporting to latex using beamer document
class
Spike Spiegel fsm...@gmail.com wrote:
...
- I'm in the situation that I need to pass options to an image
(\includegraphics) in a frame's title (frames are beamer's idea of
slide). Based on the docs it seems I should
Here's how I use prosper, follow the examples below. After exporting
to tex, you must use the latex command (not pdflatex), followed by dvipdf.
Enjoy!
~/.emacs:
(setq org-export-latex-classes (cons '(prosper
% BEGIN Prosper Defaults
\\documentclass[pdf, contemporain]{prosper}
Spike Spiegel fsm...@gmail.com wrote:
...
On a side note, a little feature request: would it be possible to
produce an indented tex file? post editing is otherwise quite painful
Try
C-x h C-M-\
or equivalently
M-x mark-whole-buffer
M-x indent-region
when
Spike Spiegel fsm...@gmail.com wrote:
...
- I also need to include an image in the titlepage but I don't see any
way to override \maketitle other than maybe renewcommand'ing it, which
I tried with #+LaTeX_HEADER, but kept getting errors, altho that might
have been me. While poking around I
55 matches
Mail list logo
