I'm using xelatex org-latex-to-pdf-process to convert org-mode to PDF.
I wanted a page break after the Table of Contents so I modified my
org-export-latex-classes and added:
\\makeatletter
\\g@addto@macro\\@cfttocfinish{\\clearpage}
\\makeatother
But now I have lots of extra whitespace on the pa
text-mode-hook and c-mode-hook do NOT have this bug.
and the org-mode-hook of orgmode shipped within emacs 23.3 does NOT have
this bug.
On Wed, Mar 14, 2012 at 1:41 PM, David Maus wrote:
> Hi,
>
> At Tue, 13 Mar 2012 14:49:41 +0800,
> Du Yanning wrote:
> > org-mode 7.8.03
> > emacs 23.3, 23.4,
Hey Nick,
On Wed, Mar 14, 2012 at 04:11, Nick Dokos wrote:
> suvayu ali wrote:
>
>
>> >> There was a discussion of this topic recently, I had and still have my q=
>> uote source
>> >> blocks in artists (picture) mode and thought this was strange behaviour.
>> >
>> > BTW, artist-mode is *not* the
I use a formula like this in my org table:
#+TBLFM: $>=vmean($<<..$>>);%.3f
However, when I export the org table to a latex file, there appears a line
in the tex file like this:
<<..\$>>(INVISIBLE)
If I use #+TBLFM: $>=vmean($2..$>>);%.3f, the problem will disappear. I
think this is caused by
Sorry the quoting was all wrong! Gmail was behaving weirdly. I wanted to
quote the other message.
On Wed, Mar 14, 2012 at 03:59, Nick Dokos wrote:
> The case-fold-search problem is in
> org-src.el:org-edit-src-code. case-fold-search is let-bound to t, but
> the let form evaluates all the VARLIST
Dear Alan,
dear Nick,
many thanks for your help. Installing minted and pygments and then putting the
emacs-lisp snippet from
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
into my .emacs file did work. Now my code snippets are syntax-highlighted! Do
you have any suggestio
Hi!
> I wanted a page break after the Table of Contents so I modified my org-
> export-latex-classes and added:
Have you tried using \newpage instead of \clearpage?
When I want a page break after the TOC, I'll usually just drop a \newpage in
just before the first heading like this:
#+ORG_E
Attempting to send a bug report using org-submit-bug-report results in the
following backtrace:
(expand-file-name "scripts" (file-name-as-directory (expand-file-name
"../contrib" ...)))
(file-name-as-directory (expand-file-name "scripts" (file-name-as-directory
...)))
(expand-file-name
Suvayu Ali wrote:
> On Wed, Mar 14, 2012 at 09:41, suvayu ali wrote:
> > Yup, your analysis was spot on. :) Changing the let to let* and
> > reevaluating the defun fixed the issue.
> >
> > I hadn't grasped this subtlety about let*, dependencies on preceding
> > bindings hidden behind function ca
I am opening up org-e-html for wider usage. This is an alpha release.
Start with
M-x org-export-dispatch RET
etc etc.
I will *NOT* be prompt with resolving open issues. I can integrate
patches much faster though.
--
On 08/03/2012 22:33, Ilya Shlyakhter wrote:
attached.
Having just run into this same problem (being unable to create
and store a code reference link using C-l in a source block edit
buffer) I would like to second the inclusion of this or an
equivalent patch. Ilya's patch can be seen on the patc
Hi,
Thanks for the new possibility!
It works as described.
I have a few functions based on the org-agenda-buffer-name, which now is no
more available,
as all the agenda buffers are named differently:
..
(if (get-buffer org-agenda-buffer-name)
..
will no more work.
I hope that the current ag
Hi!
I was writing some documentation about how to use a Python function, so I
decided to try the tangling feature. However, the result, when exported to PDF,
is unsatisfactory because the referenced code block is included twice -- first
in the original location, then again where I referenced it
At Wed, 14 Mar 2012 16:54:17 +0100,
Rainer Stengele wrote:
>
> I have a few functions based on the org-agenda-buffer-name, which now is no
> more available,
> as all the agenda buffers are named differently:
>
> ..
> (if (get-buffer org-agenda-buffer-name)
> ..
> will no more work.
If you don
Nick Dokos writes:
> François Pinard wrote:
>> [...] in an Org table, a column is made up of numbers, each of which
>> is immediately followed by a percent sign [...]
> It's of course possible (even probable) that the latex exporter
> behaves differently from the html exporter in this case (an
Jos'h Fuller writes:
> Hi!
>
> I was writing some documentation about how to use a Python function, so I
> decided to try the tangling feature. However, the result, when exported to
> PDF, is unsatisfactory because the referenced code block is included twice --
> first in the original location
1) I see from http://orgmode.org/Changes.html, section "Incompatible changes",
that I have to change my #+BABEL: lines to something else, in order to upgrade
from 7.7 to 7.8.03. But I can't figure out to what.
I previously had:
#+BABEL: :session *R* :results output :exports both
#+begin_src R
Hi Ken,
Did you press C-c C-c on each property line after it was written?
Property lines only take effect either with C-c C-c, or when the file is
first opened.
Best,
Ken Williams writes:
> 1) I see from http://orgmode.org/Changes.html, section "Incompatible
> changes", that I have to change m
Aha! That was the trick, thanks.
How about a translation of the text for question 2)?
-Ken
> -Original Message-
> From: Eric Schulte [mailto:eric.schu...@gmx.com]
> Sent: Wednesday, March 14, 2012 1:29 PM
> To: Ken Williams
> Cc: emacs-orgmode@gnu.org
> Subject: Re: [O] I'm tripping ov
> How about a translation of the text for question 2)?
[...]
>> > 2) In the same list of "Incompatible changes", it says "code blocks
>> > are named with - results are named with code block may still be
>> > labeled with named with #+tblname: will be considered to be named
>> > results". What on e
Hi!
> Does the :no-expand header argument do what you want? See
> http://orgmode.org/manual/no_002dexpand.html#no_002dexpand.
I tried using it like this:
#+name: function-demo
#+begin_src python :exports both :noweb yes :results output :no-expand
<>
print entable([["One", 2, 59
> -Original Message-
> From: Eric Schulte [mailto:eric.schu...@gmx.com]
> Sent: Wednesday, March 14, 2012 1:40 PM
> To: Ken Williams
> Cc: emacs-orgmode@gnu.org
> Subject: Re: [O] I'm tripping over #+BABEL: vs. #+PROPERTY:
>
> > How about a translation of the text for question 2)?
> [...]
Jos'h Fuller writes:
> Hi!
>
>> Does the :no-expand header argument do what you want? See
>> http://orgmode.org/manual/no_002dexpand.html#no_002dexpand.
>
> I tried using it like this:
>
> #+name: function-demo
> #+begin_src python :exports both :noweb yes :results output :no-expand
> <>
Hi!
> > It seems like I almost need some variant of the "tangle" argument to
> > :noweb where syntax references are expanded for evaluation, but not
> > for anything else.
> >
>
> Why would you want to tangle out a python src file with an un-expanded
> noweb reference? Either way, who am I to ju
I find Icicles useful in most areas of emacs, but it gets in the way
when I'm trying to complete tags. This is probably as much of an Icicles
question as an Org one.
I do C-c C-q and see the existing tag for a heading e.g. ":boring:". I
type "comp" and press TAB, hoping for completion to ":bor
I find Icicles useful in most areas of emacs, but it gets in the way
when I'm trying to complete tags. This is probably as much of an Icicles
question as an Org one.
I do C-c C-q and see the existing tag for a heading e.g. ":boring:". I
type "comp" and press TAB, hoping for completion to ":bor
Nick Dokos writes:
> Thorsten wrote:
>
>> suvayu ali writes:
>>
>> Hi,
>>
>> > I am having problems editing blocks with C-c '. If the blocks are
>> > marked
>> > with upper case letters Emacs brings up the temporary buffer in
>> > picture-mode.
>> >
>> >#+BEGIN_SRC latex
>> >
>> >#+EN
Jos'h Fuller writes:
> Hi!
>
>> > It seems like I almost need some variant of the "tangle" argument to
>> > :noweb where syntax references are expanded for evaluation, but not
>> > for anything else.
>> >
>>
>> Why would you want to tangle out a python src file with an un-expanded
>> noweb refer
Eric Schulte wrote:
>
> Did you press C-c C-c on each property line after it was written?
Just to clarify: do I really have to C-c C-c on each line? If I add a
bunch of them and then do C-c C-c on one of them, shouldn't that be
enough to refresh the setup?
Thanks,
Nick
Hi!
> Yes, although it seems that the existing "no-export" or "strip-export"
> options to the :noweb header argument may better suit your purposes.
> These are described in the Org-mode manual, however, they are not
> mentioned in the online version of the manual which is out of date.
I thought I
Jos'h Fuller writes:
> Hi!
>
>> Yes, although it seems that the existing "no-export" or "strip-export"
>> options to the :noweb header argument may better suit your purposes.
>> These are described in the Org-mode manual, however, they are not
>> mentioned in the online version of the manual whic
Sorry for the confusing title.
Here is what I would like to do:-
1. I have a multiple column table, one of which has time stamp and another
one has an entry in multiple lines, because of better visibility. Therefore
the table looks something like this:-
|+|
| DATE 1 | line 1 |
|
Hi Debaditya,
On Thu, Mar 15, 2012 at 01:47, Debaditya Mukhopadhyay
wrote:
> 2. I would like to sort the table based on date, but instead of sorting each
> line is it possible to sort by block (defined by the horizontal lines.)?
What you are asking about is a table.el table. You can use those wi
Nick Dokos writes:
> Part of my frustration with these things (gnome things in particular) is
> the sparse-to-non-existent documentation,
But Nick, the GUI is everything now. Who needs documentation! ? :-(
Anecdote. A big, complex translation system was demonstrated to a few
governmental pos
org-odt, org-e-html, org-e-odt needs new maintainers.
Wrt, org-odt the only thing that has remained uncleard for a long time
is this feature: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9914.
There has been some progress on this the last few days.
I believe org-odt is stable enough to hit Emacs-
Hi Jos'h,
have you looked at the :session header argument? I use it to define
environment variables in bash that are used in later code blocks.
Something like this:
#+BEGIN_SRC sh :session foo
export W="world."
#+END_SRC
#+RESULTS:
#+BEGIN_SRC sh :session foo
echo Hello $W
#+END_SRC
If these
36 matches
Mail list logo
