unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Sean McLaughlin <seanmcl@gmail.com>
Cc: 11099@debbugs.gnu.org
Subject: bug#11099: 23.2; Filter function causes flickering in minibuffer
Date: Sat, 17 Aug 2019 16:25:55 -0700	[thread overview]
Message-ID: <87r25j8jcs.fsf@mouse.gnus.org> (raw)
In-Reply-To: <CAO4dZbe6LxZi1WtSf5kvYjQdu=8vNj6ff-ZnhXgD6kdJb31Y=A@mail.gmail.com> (Sean McLaughlin's message of "Mon, 26 Mar 2012 13:43:03 -0700")

Sean McLaughlin <seanmcl@gmail.com> writes:

> 1) Create a file count.sh
>
> #!/bin/bash
>
> ctr=0
>
> while true; do
>     sleep 1
>     echo "ctr = $ctr"
>     ctr=$(( ctr + 1 ))
> done
>
> 2) Create a buffer called *count*
>
> 3) Start count asyncronously from a clean emacs (-q)
>
> (defun Tmp.filter-fun (proc s)
>   (with-current-buffer "*count*"
>     (insert s)))
>
> (defun Tmp.count ()
>   (interactive)
>   (let ((process
>          (start-process
>           "count"
>           "*count*"
>           "/home/seanmcl/bin/count")))
>     (set-process-filter process 'Tmp.filter-fun)))
>
> 4) Type C-x
>
> This will cause C-x to show up in the minibuffer.  Every time a
> line is filtered from count, the C-x flickers in the minibuffer,
> sometimes moving a character to the right and then back to the
> left.

(I'm going through old bug reports that unfortunately have gotten no
responses yet.)

It looks like this has been fixed in the intervening years -- now you
won't get a "C-x" in the echo area because it's not displayed when
filters are running, apparently.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2019-08-17 23:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-26 20:43 bug#11099: 23.2; Filter function causes flickering in minibuffer Sean McLaughlin
2019-08-17 23:25 ` Lars Ingebrigtsen [this message]

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=87r25j8jcs.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=11099@debbugs.gnu.org \
    --cc=seanmcl@gmail.com \
    /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).