From: Carlos Pita <carlosjosepita@gmail.com>
To: 19755@debbugs.gnu.org
Subject: bug#19755: python.el: native completion: more problems (and solutions)
Date: Thu, 5 Feb 2015 11:25:31 -0300 [thread overview]
Message-ID: <CAELgYhdmXMBCVEMcUGqebmgZrGpWSy5H3oU+JsYsyf+UYYBcNw@mail.gmail.com> (raw)
In-Reply-To: <CAELgYheghNU85Q21ERQdkhg_rywFgWtaO5aeREjVR71PiUfFWw@mail.gmail.com>
Ok, after a conversation with Fabian I understood which are the
shortcomings of the legacy mechanism:
1) While inside a block of code asking a completion to the shell makes
it believe that you're not inside the block anymore.
2) Spurious prompt number increments take place each time a completion
is requested to the shell.
So it's not just a matter of the completer being the preinstalled by
the shell or some other one that python.el instantiates itself during
the setup phase.
Another solution could be to open a simple python helper thread that
listens on a socket. This thread could provide documentation for eldoc
or for help buffers (I'm about to post a RFE for this feature),
besides the completions. Another adventage is that it will be possible
to unify the completion mechanisms again.
What do you think?
Cheers
--
Carlos
next prev parent reply other threads:[~2015-02-05 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 12:40 bug#19755: python.el: native completion: more problems (and solutions) Carlos Pita
[not found] ` <handler.19755.B.142296725921901.ack@debbugs.gnu.org>
2015-02-03 16:50 ` bug#19755: Acknowledgement (python.el: native completion: more problems (and solutions)) Carlos Pita
2015-02-05 14:25 ` Carlos Pita [this message]
2015-02-06 2:22 ` bug#19755: python.el: native completion: more problems (and solutions) Carlos Pita
2015-04-09 3:55 ` Fabián Ezequiel Gallina
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=CAELgYhdmXMBCVEMcUGqebmgZrGpWSy5H3oU+JsYsyf+UYYBcNw@mail.gmail.com \
--to=carlosjosepita@gmail.com \
--cc=19755@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).