org-babel-python-mode
was python3
Hi all,
Takaaki ISHIKAWA writes:
> Dear Julian,
>
> Sorry, the code is an old setting for the previous org.
> Please try org-odt-preferred-output-format.
>
> #+BEGIN_SRC emacs-lisp
> (setq org-odt-preferred-output-format "pdf")
> (setq org-odt-convert-processes
>'(("LibreOffic
Am 08.05.2013 09:12, schrieb Andreas Röhler:
org-babel-python-mode
was python3
e, org-babel-python-command
Hello,
Cameron Desautels writes:
> I'm having a bit of trouble with exports. My understanding is that I should
> be able to create a sparse tree from a tag (C-c / m tag-name RET) and then
> export only the visible items (C-c C-e C-v t A) to get an export of just
> the items with that tag. What I
Am 07.05.2013 18:41, schrieb Eric Schulte:
#+NAME: test2
#+begin_src python :results value :preamble # -*- coding: utf-8 -*- :return
a
a = ( ( "é", "a" ), ( "a", "à" ) )
b = "é"
#+end_src
#+RESULTS: test2
| \303\251 | a|
| a| \303\240 |
Maybe this isn't an execution problem, b
Guido Van Hoecke writes:
> Hi,
>
> Thank you guys for your help.
>
> Got gawk from macports.
Glad you got it. I did make use of whatever GNU awk provided and did
not try to keep to vanilla awk. Sorry about that!
> Hitting data error now:
>
> gawk: ./importGoogleCalendar.awk:143: (FILENAME=- F
All,
I just upgraded to 8.02, so I am trying out the new exporter. Nice.
A little nit. When I export a minimal org file, it should use the
name of the file or buffer as the title if I set nothing in #+TITLE:,
but it seems not to.
Here it a minimal Org file named 'Junk.org':
===
>> "rasmus" == rasmus writes:
> Uwe Brauer writes:
>> Look the following examples
>>
>> \begin{displaymath}
>> Xs,δ:=Hs,δ× Hs,δ+1× Hs,δ+1×
>> Hs+1,δ+2
>> \end{displaymath}
>> org-preview-latex-fragment does not work, change displaymath for
>> equation, again org-preview-latex-f
Andreas Röhler writes:
> Am 08.05.2013 09:12, schrieb Andreas Röhler:
>> org-babel-python-mode
>>
>> was python3
>>
>>
>
> e, org-babel-python-command
>
I can't reproduce this problem. After evaluating the following
(setq org-babel-python-command "python3")
The utf-8 example works per
Paul Stansell writes:
> Hi Eric,
>
> If I change your example org file a little by adding row and column
> names to the table as in the attached file I get the following
> behaviour that I don't understand: if I execute C-c on the shell
> function the file /tmp/data.gnuplot has the format that g
Paul Stansell writes:
> Hi Eric,
>
> My view is that the removal of '""'s will always be preferable for
> gnuplot as it uses what it calls datablocks which are delimited by
> blank lines (see, for example,
> http://gnuplot.sourceforge.net/docs_4.2/node121.html and
> http://gnuplot.sourceforge.net
Hi Dan,
On Wed, May 8, 2013 at 6:06 AM, Daniel E. Doherty wrote:
> All,
>
> I just upgraded to 8.02, so I am trying out the new exporter. Nice.
>
> A little nit. When I export a minimal org file, it should use the
> name of the file or buffer as the title if I set nothing in #+TITLE:,
> but it
Am 08.05.2013 14:40, schrieb Eric Schulte:
Andreas Röhler writes:
Am 08.05.2013 09:12, schrieb Andreas Röhler:
org-babel-python-mode
was python3
e, org-babel-python-command
I can't reproduce this problem. After evaluating the following
(setq org-babel-python-command "python
>
> hmm, indeed, shows up nicely now.
> Please close, cheers,
>
> Andreas
>
>
That's right, it works with python3 but that is not the case with python2...
Cheers,
Roland.
Am 08.05.2013 15:20, schrieb Roland Donat:
hmm, indeed, shows up nicely now.
Please close, cheers,
Andreas
That's right, it works with python3 but that is not the case with python2...
Cheers,
Roland.
python2 fails here already with a common shell, independently from Emacs.
OTOH that
Andreas Röhler easy-emacs.de> writes:
>
> Am 08.05.2013 15:20, schrieb Roland Donat:
> >
> >>
> >> hmm, indeed, shows up nicely now.
> >> Please close, cheers,
> >>
> >> Andreas
> >>
> >>
> >
> > That's right, it works with python3 but that is not the case with
python2...
> >
> > Cheers,
> >
>
Hello,
Daniel E. Doherty writes:
> A little nit. When I export a minimal org file, it should use the
> name of the file or buffer as the title if I set nothing in #+TITLE:,
> but it seems not to.
It should be fixed in maint. Thank you for reporting this.
Regards,
--
Nicolas Goaziou
Am 08.05.2013 16:02, schrieb Roland Donat:
Andreas Röhler easy-emacs.de> writes:
Am 08.05.2013 15:20, schrieb Roland Donat:
hmm, indeed, shows up nicely now.
Please close, cheers,
Andreas
That's right, it works with python3 but that is not the case with
python2...
Cheers,
Roland.
Hi Eric,
It seems to be the first "hline" that causes the problem. For
example, if the table data in splot.org is replaced by
#+name: data
|| x |
|+---|
| r1 | 1 |
it gets exported correctly as
x
r1 1
by both the shell and gnuplot commands.
However, if the data is repla
Am 08.05.2013 16:02, schrieb Roland Donat:
Andreas Röhler easy-emacs.de> writes:
Am 08.05.2013 15:20, schrieb Roland Donat:
hmm, indeed, shows up nicely now.
Please close, cheers,
Andreas
That's right, it works with python3 but that is not the case with
python2...
Cheers,
Roland.
Hi Eric,
In your last example are you illustrating the case of a data file with
missing data? Replacing ""s with blank space in your example doesn't
really break the plot, it's just that gnuplot interprets the first
column of data as
1
2
3
16
6
7
4
9
and the second as
2
4
8
16
8
4
2
Gnuplo
Eric S Fraga writes:
> Guido Van Hoecke writes:
>
>> Hi,
>>
>> Thank you guys for your help.
>>
>> Got gawk from macports.
>
> Glad you got it. I did make use of whatever GNU awk provided and did
> not try to keep to vanilla awk. Sorry about that!
No prob at all!
>> Hitting data error now:
>
On Tue May 07 2013 at 07:23, "Sebastien Vauban" wrote:
> Christian Moe wrote:
>> Bill White writes:
>>> Is there a simple way to disable tangling for an entire section's code
>>> blocks? Or to put it a different way, can tangling be toggled at the
>>> section level and not just the code-block lev
I'd like to change the title of my report, and the exported pdf filename,
based on a value I can change in the org-mode source.
I have a source block like this:
#+NAME: reporttype
#+BEGIN_SRC elisp :results value silent :exports results
"Foo"
#+END_SRC
I figured out how to do the title:
#+TITLE
> > Yes, you're right Andreas. It "fails" to show the accented characters if
you
> > try to print the entire tuple.
> > It fails too if you evaluate a[0][0] in your interpreter. You should see
:
> a[0][0]
> > '\xc3\xa9'
> > But print a[0][0] gives the expected answer 'é'
> >
> > So, based on
The following clocktable line:
#+BEGIN: clocktable :tstart "<-7d>" :tend ""
#+END:
errors out on the tstart & tend times
According to all the documentation I can find, these are both valid
'special' time strings.
Attempts to evaluate the clocktable with C-c C-c give the error:
Updating dynamic b
>> #+INCLUDE: date.org
I changed this to #+INCLUDE: "date.org"
>>
>>
>> * this is a test
>>
>> --- date.org
>> {{{date(%d %b %Y)}}}
>
>You want:
>
> {{{time(%d %b %Y)}}}
I made this change as well, however the same results. Any thing in the
included file is copied verbatim...
-Tim
At Tue, 07 May 2013 16:14:19 +0200,
Nicolas Goaziou wrote:
>
> Hello,
>
> Wiskey 5 Alpha writes:
>
> >I am trying to use the #+INCLUDE directives to have template information
> > for a series of orgmode files that I want to export. Prior to upgrading to
> > v8, the below minimal example wa
Package: org-mode
cus-test.el suggests the following variables may have incorrect
custom :types. (There may be some false positives.)
This refers to Org mode in current Emacs trunk.
Eg, org-footnote-auto-adjust does not have "nil" as an option.
org-refile-target-verify-function
org-icalendar-com
Hello,
Tim writes:
> At Tue, 07 May 2013 16:14:19 +0200,
> Nicolas Goaziou wrote:
>>
>> Hello,
>>
>> Wiskey 5 Alpha writes:
>>
>> >I am trying to use the #+INCLUDE directives to have template information
>> > for a series of orgmode files that I want to export. Prior to upgrading to
>>
> I was hoping that a higher-level setting would override all tangle
> settings under it, no matter what they might be. This would make it
> possible to change an entire section's tangling without fussing with
> each code block's setting.
The status quo makes more sense, I think. It allows you t
31 matches
Mail list logo
