all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Terry Jones <terry@jon.es>
To: help-gnu-emacs@gnu.org
Cc: python-list@python.org
Subject: Re: writing Python in Emacs
Date: Sat, 19 Jan 2008 17:51:50 +0100	[thread overview]
Message-ID: <mailman.817.1200761534.896.python-list@python.org> (raw)
In-Reply-To: Your message at 04:01:48 on Saturday, 19 January 2008

>>>>> "Richard" == Richard Szopa <ryszard.szopa@gmail.com> writes:

Richard> I am a devoted Emacs user and I write a lot in Python.

Me too.

Richard> I need the following features:

Richard> 1) Tab completion, ideally Slime like. That is, when there's not
Richard> enough letters to unambiguously complete a symbol, I want it to
Richard> show a buffer (w/o taking the focus) w/ the possible
Richard> completions. In an ideal world, it would be able to complete
Richard> fo.ba<TAB> to foo.bar. I imagine this would require quite tight
Richard> Emacs-Python integration.

I know this is not what you want, but I use hippie expand (M-/) to cycle
through possible completions. It's not Python aware, but it is of some use.

Richard> 2) Sending the toplevel definition (class or function) to the Python
Richard> buffer.

I switched to IPython to have better interaction with a spawned Python.

To use IPython you need to use the Python mode that is NOT the one from
(endorsed?) by the FSF. It gives you some completion (at least in the
*Python* buffer) and you can send pieces of the buffer to the python
process, via py-send-region (C-c |), py-execute-def-or-class (M-C-x), etc.

Richard> 3) Hints on function/method arguments. IDLE has this done nearly
Richard> right, but the hints are a bit too intrusive for me. I would like to
Richard> see them in the minibuffer.

I don't have this.

Richard> 4) (optional) I would like to see the definition of a function
Richard> function or class by hitting M-. on its name. (I understand that
Richard> this may be impossible for methods, as Emacs would have to
Richard> automagically infer the type of the object).

This is just an emacs tag file need. Have you googled for something like
emacs tags python? The issue of methods might be overcome by just moving
through tags with the same name. Yes, that requires _you_ to know when
you've hit the right thing. That's not optimal, but it's better than
nothing. Ideally you could send the definition to IPython, ask it for the
class info, and use that to jump to the right tag.

Richard> I have tried a couple of times both python-modes (the one shipped w/
Richard> Python and the one shipped w/ Emacs), pymacs and stuff like that...
Richard> And, as I said, never got it right. But, maybe I just cannot find the
Richard> way to configure it, and some configuration hints will be enough...

If you have the time, please summarize your findings. The emacs/python
world has always seemed quite amorphous to me too.

Terry

       reply	other threads:[~2008-01-19 16:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <160ed936-c8c0-432e-81c8-c62b8f164136@s13g2000prd.googlegroups.com>
2008-01-19 16:51 ` Terry Jones [this message]
2008-01-19 20:41   ` writing Python in Emacs Thierry Volpiatto
2008-01-20 14:35   ` Jorgen Grahn
2008-01-20 15:42   ` Rob Wolfe
     [not found]   ` <87r6gc5wr5.fsf@merkury.smsnet.pl>
2008-01-20 22:35     ` Thierry Volpiatto
2008-01-21  7:59     ` Thierry Volpiatto
2008-01-31  0:03     ` Ryszard Szopa
2008-01-31  3:28     ` alitosis
2008-01-19 18:08 ` Thierry Volpiatto
2008-01-19 18:18   ` Lennart Borgman (gmail)
2008-01-19 20:29     ` Thierry Volpiatto
     [not found] <mailman.6346.1200859328.18990.help-gnu-emacs@gnu.org>
2008-01-21 10:22 ` Richard G Riley
     [not found] <slrnfp6n1u.c76.grahn+nntp@frailea.sa.invalid>
2008-01-20 19:28 ` Drew Adams
2008-01-20 20:01   ` Drew Adams
2008-01-19 12:01 Richard Szopa

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

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

  git send-email \
    --in-reply-to=mailman.817.1200761534.896.python-list@python.org \
    --to=terry@jon.es \
    --cc=help-gnu-emacs@gnu.org \
    --cc=python-list@python.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.