From: Dmitry Gutov <dgutov@yandex.ru>
To: npostavs@users.sourceforge.net
Cc: Evgeniy Sharapov <evgeniy.sharapov@gmail.com>, 28051@debbugs.gnu.org
Subject: bug#28051: Multiline Statement Indentation Error in Inferior Python Mode
Date: Sun, 27 Aug 2017 19:42:43 +0300 [thread overview]
Message-ID: <2e36c178-b365-cc6e-402e-ffc4f01e9c86@yandex.ru> (raw)
In-Reply-To: <87fuckbcyz.fsf@users.sourceforge.net>
On 8/22/17 4:36 AM, npostavs@users.sourceforge.net wrote:
> Hmm, when using company-mode the error message is sent repeatedly, which
> seems pretty annoying. But silently returning no matches could be
> confusing. Dimitri, any advice?
Use a python-specific global variable and only show the warning one
time? Or at most once in XX seconds?
There's no existing diagnostic UI for this in company-mode. And the idea
for completion-at-point-functions is to not signal errors during normal
operation (an error means there's a bug to be fixed, and bugging the
user in that case seems okay).
In this particular case, though, I'd simply return no completions. We do
the same in inf-ruby anyway (no completion on continuation lines). Add a
warning message once a session, if you prefer.
next prev parent reply other threads:[~2017-08-27 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 17:24 bug#28051: 25.2; Multiline Statement Indentation Error in Inferior Python Mode evgeniy.sharapov
2017-08-11 18:19 ` bug#28051: " Evgeniy Sharapov
2017-08-12 17:50 ` Glenn Morris
2017-08-14 23:59 ` npostavs
2017-08-21 12:17 ` npostavs
2017-08-22 1:36 ` npostavs
2017-08-27 16:42 ` Dmitry Gutov [this message]
2017-08-27 18:28 ` npostavs
2017-08-19 14:45 ` bug#28051: 25.2; " npostavs
2017-08-25 2:50 ` Evgeniy Sharapov
2017-08-25 12:20 ` npostavs
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=2e36c178-b365-cc6e-402e-ffc4f01e9c86@yandex.ru \
--to=dgutov@yandex.ru \
--cc=28051@debbugs.gnu.org \
--cc=evgeniy.sharapov@gmail.com \
--cc=npostavs@users.sourceforge.net \
/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.