From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Lele Gaifax Newsgroups: gmane.emacs.devel Subject: Two issues with the new Flymake Date: Fri, 03 Nov 2017 10:50:49 +0100 Organization: Nautilus Entertainments Message-ID: <87k1z7adxi.fsf@metapensiero.it> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1509702677 11868 195.159.176.226 (3 Nov 2017 09:51:17 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 3 Nov 2017 09:51:17 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 03 10:51:13 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eAYd5-0002Ty-HZ for ged-emacs-devel@m.gmane.org; Fri, 03 Nov 2017 10:51:11 +0100 Original-Received: from localhost ([::1]:35641 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eAYdA-0005Wq-1W for ged-emacs-devel@m.gmane.org; Fri, 03 Nov 2017 05:51:16 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33828) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eAYd3-0005WM-F4 for emacs-devel@gnu.org; Fri, 03 Nov 2017 05:51:10 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eAYd0-0003lL-BG for emacs-devel@gnu.org; Fri, 03 Nov 2017 05:51:09 -0400 Original-Received: from [195.159.176.226] (port=47789 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eAYd0-0003kJ-4N for emacs-devel@gnu.org; Fri, 03 Nov 2017 05:51:06 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1eAYcm-0001RW-Qo for emacs-devel@gnu.org; Fri, 03 Nov 2017 10:50:52 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 41 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:jgXfjteOmG9WtCubLfGXwHeFxvU= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:219880 Archived-At: Hi all, I'm happily using the new Flymake implementation coupled with the Python backend (that I'm still hoping it could be merged into Emacs 26, see bug #28808). I have two "minor" issues with it, one I think should be corrected in Flymake, the other by any chance related to my configuration, but was not able to identify its source yet. The first problem is something that happens when I add new code at the end of the source: if I write something and then quickly enough partially delete it with `delete-backward-char' and replace it with something else, at times Flymake reports an error message about unexpected report from the backend; I think it's due to the external checker reporting a problem in a region of the buffer that isn't there anymore at the time Flymake receives/processes that annotation. This is at worst a little annoyance, because at that time Emacs "hangs" for a noticeable interval of time, enough to disrupt my (re)writing. The second one is a strange interaction with the `python-shell-send-region' (a feature that I use very seldom): when I execute that, I get the following error message Error in post-command-hook (#[0 "\304\305\303\242\306#\210r\302q\210\307\310\311\301\"\300\")\207" [nil (post-command on-display) # (#0) remove-hook post-command-hook nil flymake-start remove post-command] 4]): (error "Selecting deleted buffer") This does not happen in a `emacs -Q' session, so I bet it must be something related to the activation of flymake-mode and/or with the python-flymake backend, but as said despite my efforts I was not able to better understand what's going on (toggle-debug-on-error didn't help). Do you have any advice on how to investigate further? Thanks in advance for any hint, ciao, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. lele@metapensiero.it | -- Fortunato Depero, 1929.