all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 31409@debbugs.gnu.org, "Sébastien Gendre" <seb@k-7.ch>
Subject: bug#31409: 25.3; Python.el: getting function signature with eldoc is not automatic
Date: Thu, 04 Feb 2021 11:18:31 +0100	[thread overview]
Message-ID: <874kist9u0.fsf@gnus.org> (raw)
In-Reply-To: <875zqllmcy.fsf@gmail.com> (Noam Postavsky's message of "Tue, 07 May 2019 22:18:53 -0400")

Noam Postavsky <npostavs@gmail.com> writes:

>> In python-mode, to get a Python function signature in minibuffer, an
>> user need to:
>> - Start the Python shell (M-x run-python)
>
> You can use C-c C-p.
>
>> - Enable eldoc (M-x eldoc-mode)
>
> This step is no longer needed, global-eldoc-mode is on by default.
>
>> - Send function definition or import to the shell (C-M-x or M-x
>> python-shell-send-defun)
>>
>> It's too much steps and less efficient than what we have for Emacs
>> Lisp. :(
>
> The last step (loading function) is needed for Emacs Lisp too.  So I
> guess just auto-starting Python shell would be needed.

I don't think auto-starting a Python shell would be generally
appreciated?  Bug I guess people who want this can just put run-python
into python-mode-hook?

So I'm not sure whether there's anything to do in this bug report?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-02-04 10:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10 16:41 bug#31409: 25.3; Python.el: getting function signature with eldoc is not automatic Sébastien Gendre
2019-05-08  2:18 ` Noam Postavsky
2021-02-04 10:18   ` Lars Ingebrigtsen [this message]
2021-03-12  1:54     ` Lars Ingebrigtsen

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=874kist9u0.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=31409@debbugs.gnu.org \
    --cc=npostavs@gmail.com \
    --cc=seb@k-7.ch \
    /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.