From: Lele Gaifax <lele@metapensiero.it>
To: emacs-devel@gnu.org
Subject: Two issues with the new Flymake
Date: Fri, 03 Nov 2017 10:50:49 +0100 [thread overview]
Message-ID: <87k1z7adxi.fsf@metapensiero.it> (raw)
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) #<killed buffer> (#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.
next reply other threads:[~2017-11-03 9:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 9:50 Lele Gaifax [this message]
2017-11-03 12:33 ` Two issues with the new Flymake Stefan Monnier
2017-11-03 14:07 ` Lele Gaifax
2017-11-03 16:59 ` João Távora
2017-11-03 17:15 ` Stefan Monnier
2017-11-03 20:17 ` Three Flymake backends Was " João Távora
2017-11-04 15:30 ` Stefan Monnier
2017-11-04 23:17 ` João Távora
2017-11-05 12:50 ` Dmitry Gutov
2017-11-05 12:59 ` João Távora
2017-11-05 13:04 ` Dmitry Gutov
2017-11-05 13:22 ` João Távora
2017-11-05 20:14 ` Dmitry Gutov
2017-11-05 21:05 ` João Távora
2017-11-05 23:56 ` Dmitry Gutov
2017-11-06 9:48 ` João Távora
2017-11-06 10:35 ` Dmitry Gutov
2017-11-06 11:08 ` João Távora
2017-11-13 0:23 ` Dmitry Gutov
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=87k1z7adxi.fsf@metapensiero.it \
--to=lele@metapensiero.it \
--cc=emacs-devel@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).