GNU bug report logs - #28051
[w32 / python "legacy" completion] Multiline Statement Indentation Error

Previous Next

Package: emacs;

Reported by: evgeniy.sharapov <at> gmail.com

Date: Fri, 11 Aug 2017 17:55:02 UTC

Severity: normal

Tags: confirmed, patch

Found in version 25.2

Fixed in version 26.1

Done: npostavs <at> users.sourceforge.net

Bug is archived. No further changes may be made.

Full log


Message #38 received at 28051 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: npostavs <at> users.sourceforge.net
Cc: Glenn Morris <rgm <at> gnu.org>, Evgeniy Sharapov <evgeniy.sharapov <at> gmail.com>,
 28051 <at> debbugs.gnu.org
Subject: Re: bug#28051: Multiline Statement Indentation Error in Inferior
 Python Mode
Date: Sun, 27 Aug 2017 19:42:43 +0300
On 8/22/17 4:36 AM, npostavs <at> 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.




This bug report was last modified 7 years and 269 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.