From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: pymacs
Date: Mon, 10 Jun 2013 11:13:14 +0800 [thread overview]
Message-ID: <877gi27j5h.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CABX3oxaN74WYwwBJBaBCrt9EQuPCs-W1iVXx7Stpr9KH+Xh2NA@mail.gmail.com
daniel <idnael@gmail.com> writes:
> That is interesting. (but doesn't work in my Emacs installation yet...)
>
> Anyway, it is not related to my question!
> """Pymacs is a powerful tool which, once started from Emacs, allows
> both-way communication between Emacs Lisp and Python."""
I use pymacs and rope, and like them quite a bit, but I remember it was
a real pain in the rear to get everything installed and talking
together. I'm on arch, so there are often confusions about python 2 vs 3
(3 is the default), and I think I was trying to install too many things
manually. Arch turned out to have readymade packages for pymacs,
python2-rope and python2-ropemode, and it all worked better.
Depending on your system, I'd definitely look for packages. Pymacs is
also available through Emacs' package manager, which might be the safest
option: install it from there, and do the usual initialization dance in
a python-mode load hook:
(autoload 'pymacs-apply "pymacs")
(autoload 'pymacs-call "pymacs")
(autoload 'pymacs-eval "pymacs" nil t)
(autoload 'pymacs-exec "pymacs" nil t)
(autoload 'pymacs-load "pymacs" nil t)
What else do you need to know?
Eric
next prev parent reply other threads:[~2013-06-10 3:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-09 19:35 pymacs daniel
2013-06-09 22:19 ` pymacs andrea crotti
2013-06-09 22:37 ` pymacs daniel
2013-06-10 3:13 ` Eric Abrahamsen [this message]
2013-06-10 10:54 ` pymacs daniel
2013-06-10 13:12 ` pymacs daniel
2013-06-10 13:37 ` pymacs Eric Abrahamsen
2013-06-10 17:50 ` pymacs daniel
2013-06-10 18:03 ` pymacs Andreas Röhler
2013-06-10 22:43 ` pymacs Kyle Machulis
2013-06-16 20:38 ` pymacs daniel
2013-06-10 5:20 ` pymacs Andreas Röhler
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877gi27j5h.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@gnu.org \
/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.
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).