emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dror Atariah <drorata@gmail.com>
To: Ken Mankoff <mankoff@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [Orgmode] Unable to capture the file name generated using matplotlib
Date: Tue, 26 May 2015 15:18:56 +0200	[thread overview]
Message-ID: <CANfRcg2GUuTYscpic2Q3rfjiQN2GsOOr3K1P+j2yV-dcPyg6+w@mail.gmail.com> (raw)
In-Reply-To: <m2k2vwp0ox.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]

On Tue, May 26, 2015 at 3:49 AM, Ken Mankoff <mankoff@gmail.com> wrote:

>
> Nick Dokos removed from Cc.
>
> On 2015-05-25 at 14:22, Dror Atariah <drorata@gmail.com> wrote:
> > I tried to evaluate the problematic file using =emacs -Q= and the problem
> > is the same.
>
> Sorry I can't help much. It works on my system.
>
> The only difference I see is my python version:
>
> #+BEGIN_SRC python :session background :results raw
> import sys
> sys.version
> #+END_SRC
>
> #+RESULTS:
> 2.7.9 |Anaconda 2.2.0 (x86_64)| (default, Dec 15 2014, 10:37:34)
> [GCC 4.2.1 (Apple Inc. build 5577)]
>
I doesn't work also when I try to use the 2.7 version of Python.

>
> > Following is the section of my =init.el= that deals with org-mode (if you
> > need more, let me know):
>
> If the bug exists with "emacs -Q", then sending a large init file is just
> noise and not helpful. A minimum working example would be similar to your
> previous email, but include the necessary Org setup code to execute Python,
> and nothing else.
>
I believe this is the example that John provided; which doesn't work for
me...

How can I make sure that my emacs -Q is really "clean"?

>
>   -k.
>
>


-- 
Dror Atariah, Ph.D.
de.linkedin.com/in/atariah

[-- Attachment #2: Type: text/html, Size: 2251 bytes --]

  reply	other threads:[~2015-05-26 13:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-02  7:48 [Orgmode] Unable to capture the file name generated using matplotlib Dror Atariah
2015-05-02 17:09 ` Nick Dokos
2015-05-02 17:11 ` Nick Dokos
2015-05-05 20:20   ` Dror Atariah
2015-05-23 18:49     ` Dror Atariah
2015-05-25 17:25       ` Dror Atariah
2015-05-25 17:29         ` Ken Mankoff
2015-05-25 18:22           ` Dror Atariah
2015-05-25 18:30             ` John Kitchin
2015-05-26 13:11               ` Dror Atariah
2015-05-26 13:15                 ` Ken Mankoff
2015-05-26 13:19                   ` Dror Atariah
2015-05-26 13:26               ` Dror Atariah
2015-05-26 14:02                 ` Ken Mankoff
2015-05-26 14:37                   ` Dror Atariah
2015-05-26 18:39                   ` Dror Atariah
2015-06-02  5:49                     ` Dror Atariah
2015-06-02 12:21                       ` Ken Mankoff
2015-06-02 18:01                         ` Dror Atariah
2015-05-26  1:49             ` Ken Mankoff
2015-05-26 13:18               ` Dror Atariah [this message]
2015-05-26 14:05                 ` Ken Mankoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANfRcg2GUuTYscpic2Q3rfjiQN2GsOOr3K1P+j2yV-dcPyg6+w@mail.gmail.com \
    --to=drorata@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mankoff@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).