Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Michael Stapelberg <michael+sup@stapelberg.de>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] flicker on poll for new messages
Date: Thu, 11 Mar 2010 13:26:58 +0100	[thread overview]
Message-ID: <1268310352-sup-1631@midna.zekjur.net> (raw)
In-Reply-To: <1268309031-sup-2088@khjk.org>

Hi Sven,

Excerpts from Sven Moritz Hallberg's message of Do Mär 11 13:03:55 +0100 2010:
> Just a quick question, when polling for new messages, sup seems to blank the
> screen and just immediately repaint it. Is this necessary?
Do you maybe receive new mails which are GPG signed/encrypted? In this case
the flickering might be caused by leaving the ncurses mode, running the gpg
command and re-entering ncurses mode. This is necessary to allow programs
such as pinentry-curses to work correctly.

Best regards,
Michael
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

  reply	other threads:[~2010-03-11 12:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 12:03 Sven Moritz Hallberg
2010-03-11 12:26 ` Michael Stapelberg [this message]
2010-03-11 12:35   ` Sven Moritz Hallberg

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=1268310352-sup-1631@midna.zekjur.net \
    --to=michael+sup@stapelberg.de \
    --cc=sup-talk@rubyforge.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox