From: Jorgen Grahn <grahn+nntp@snipabacken.dyndns.org>
To: help-gnu-emacs@gnu.org
Subject: Re: writing Python in Emacs
Date: 20 Jan 2008 14:35:26 GMT [thread overview]
Message-ID: <slrnfp6n1u.c76.grahn+nntp__45965.3838225224$1200840171$gmane$org@frailea.sa.invalid> (raw)
In-Reply-To: mailman.817.1200761534.896.python-list@python.org
["Followup-To:" header set to comp.lang.python.]
On Sat, 19 Jan 2008 17:51:50 +0100, Terry Jones <terry@jon.es> wrote:
>>>>>> "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.
Also known as dabbrev-expand, and tied to Ctrl-TAB.
I like it *a lot*, and I like it even more because it *isn't* Python
aware. I can use the same function no matter what I am typing, often
with files noone would dream of writing a mode for.
...
>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?
Tags works fine, or at least as well as can be expected. I use the
'etags' which comes with 'ctags', apparently.
> If you have the time, please summarize your findings. The emacs/python
> world has always seemed quite amorphous to me too.
I don't know; python-mode colorizes well and it knows how to help me
keep the indentation sane. The Eclipse users I have seen seem to have
more problems than I have, for example.
/Jorgen
--
// Jorgen Grahn <grahn@ Ph'nglui mglw'nafh Cthulhu
\X/ snipabacken.se> R'lyeh wgah'nagl fhtagn!
next prev parent reply other threads:[~2008-01-20 14:35 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 ` writing Python in Emacs Terry Jones
2008-01-19 20:41 ` Thierry Volpiatto
2008-01-20 14:35 ` Jorgen Grahn [this message]
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
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='slrnfp6n1u.c76.grahn+nntp__45965.3838225224$1200840171$gmane$org@frailea.sa.invalid' \
--to=grahn+nntp@snipabacken.dyndns.org \
--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).