From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Subject: Re: Python interactive navigation around nested functions
Date: Sun, 26 Jun 2016 21:29:04 +0200 [thread overview]
Message-ID: <cab27267-1122-045c-cf91-4ca6fcf94c60@online.de> (raw)
In-Reply-To: <576DC0D4.5060304@gmail.com>
On 25.06.2016 01:23, Clément Pit--Claudel wrote:
> On 2016-06-24 18:10, Dima Kogan wrote:
>> Yeah, I'd rather not proliferate multiple similar-yet-slightly-different
>> behaviors, so I'll simply use my own python nav functions in my work if
>> this gets rejected.
> That would be too bad
Not that much, as it displays another basic strength of Emacs.
For me a major reason for preferring it over other tools, which might be
smarter in detail.
> ;.I think you're making a good point; and still the frustrating part with a python-specific fix is that C-M-a will have a different meaning depending on the programming language :/
>
Nope. A function definition as displayed here is pretty comparable with
its role in Emacs Lisp.
A case would be def/class distinction - which is not at stake.
next prev parent reply other threads:[~2016-06-26 19:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 4:52 Python interactive navigation around nested functions Dima Kogan
2016-06-20 2:43 ` Stefan Monnier
2016-06-20 7:14 ` Andreas Röhler
2016-06-20 7:34 ` Stefan Monnier
2016-06-20 8:28 ` Andreas Röhler
2016-06-20 13:57 ` Clément Pit--Claudel
2016-06-20 16:23 ` Andreas Röhler
2016-06-21 5:45 ` Dima Kogan
2016-06-21 6:05 ` Dima Kogan
2016-06-21 6:21 ` Stefan Monnier
2016-06-24 22:10 ` Dima Kogan
2016-06-24 23:23 ` Clément Pit--Claudel
2016-06-26 19:29 ` Andreas Röhler [this message]
2016-06-27 0:39 ` Clément Pit--Claudel
2016-06-27 6:02 ` Andreas Röhler
2016-06-25 0:18 ` Stefan Monnier
2016-06-26 19:37 ` Andreas Röhler
2016-06-21 6:32 ` Andreas Röhler
2016-06-21 6:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cab27267-1122-045c-cf91-4ca6fcf94c60@online.de \
--to=andreas.roehler@online.de \
--cc=emacs-devel@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.
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.