Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: ezyang@MIT.EDU (Edward Z. Yang)
Subject: [sup-talk] Odd key bug
Date: Mon, 27 Jul 2009 14:13:12 -0400	[thread overview]
Message-ID: <1248718344-sup-1931@javelin> (raw)
In-Reply-To: <1248715911-sup-4656@masanjin.net>

Excerpts from William Morgan's message of Mon Jul 27 13:33:57 -0400 2009:
> This happens to me too. Maybe there's some more curses weirdness that
> needs to happen when shelling out---you can see the current magic spell
> at buffer.rb circa line 724, in BufferManager#shell_out. I've just
> suffered through it for the past three years.

I tried cargo culting a few extra function calls from the web, to no
avail.  Man, where's an ncurses expert when you need them...

Cheers,
Edward


  reply	other threads:[~2009-07-27 18:13 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
2009-07-27 17:33 ` William Morgan
2009-07-27 18:13   ` Edward Z. Yang [this message]
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=1248718344-sup-1931@javelin \
    --to=ezyang@mit.edu \
    /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