Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: bwalton@artsci.utoronto.ca (Ben Walton)
Subject: [sup-talk] Odd key bug
Date: Mon, 27 Jul 2009 13:52:02 -0400	[thread overview]
Message-ID: <1248717027-sup-9556@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1248715577-sup-4766@utwig>

Excerpts from Alex Vandiver's message of Mon Jul 27 13:27:33 -0400 2009:
> As another data point, I also see this, with emacs as my editor.

And I saw it with vim until I switched to emacs a few months back.  I
wonder if this is anything to do with how these curses apps interact
with the 'alternate' screen buffer or something?  For the record, I've
always run sup inside of screen...

I've just been suffering through it too.  Edward, you've given voice
to this insidious little annoyance! :)

-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20090727/580ec624/attachment.bin>


  reply	other threads:[~2009-07-27 17:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 17:13 Edward Z. Yang
2009-07-27 17:27 ` Alex Vandiver
2009-07-27 17:52   ` Ben Walton [this message]
2009-07-27 17:33 ` William Morgan
2009-07-27 18:13   ` Edward Z. Yang
2009-07-27 18:30     ` Edward Z. Yang
2009-07-27 19:15       ` Edward Z. Yang
2009-07-28 15:17         ` William Morgan
2009-07-28 15:31           ` Ben Walton
2009-07-27 18:47 ` Tarko Tikan
2009-07-27 20:11   ` Andrew Pimlott

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=1248717027-sup-9556@ntdws12.chass.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    /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