Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Eric Sherman <sup-bugs@masanjin.net>
To: sup-devel@rubyforge.org
Subject: [sup-devel] [issue45] BufferManager.ask truncates responses to (terminal width -	question length)
Date: Sun, 17 Jan 2010 22:02:54 +0000	[thread overview]
Message-ID: <1263765774.58.0.0728242048264.issue45@masanjin.net> (raw)
In-Reply-To: <1263765774.58.0.0728242048264.issue45@masanjin.net>


New submission from Eric Sherman <hyperbolist@gmail.com>:

BufferManager.ask truncates responses to (terminal width - question length).

The easiest way to test if this happens in your environment:
* open a search \ 
* hold down aaaaaaaaaabbbbbbbbbbbcccccccccccc and so on until you've wrapped
across the terminal width a few times
* refine search |
* (you may need to left-arrow a little to see anything)
* the string you are refining should be truncated where your cursor first went
beyond the terminal width in the original search

This does not happen for everyone.

git next
ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10]
ncursesw (1.2.4.1)

----------
messages: 110
nosy: hyperbolist
priority: bug
ruby_version: ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-darwin10]
status: unread
sup_version: git next
title: BufferManager.ask truncates responses to (terminal width - question length)

_________________________________________
Sup issue tracker <sup-bugs@masanjin.net>
<http://masanjin.net/sup-bugs/issue45>
_________________________________________
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


           reply	other threads:[~2010-01-17 22:03 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1263765774.58.0.0728242048264.issue45@masanjin.net>]

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=1263765774.58.0.0728242048264.issue45@masanjin.net \
    --to=sup-bugs@masanjin.net \
    --cc=sup-devel@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