From: benoit.pierre@gmail.com (Benoît PIERRE)
Subject: [sup-talk] ncurses hack
Date: Tue, 18 Aug 2009 20:24:45 +0200 [thread overview]
Message-ID: <1250619721-sup-91@localdomain> (raw)
In-Reply-To: <1250580593-sup-1346@archpc>
Excerpts from Dusan's message of Tue Aug 18 09:42:48 +0200 2009:
>
> [...]
>
> Not being able to fix search/save and other edits is huge show-stopper.
> I do what I read somewhere:
>
> -start search, get garbage results
> -kill that buffer with 'x'
> -start another search but instead of typing search term again first
> repeat: press up, delete search garbage, press up, delete search
> garbage, repeat until there is nothing to delete
> -type another search term and search now works 100%
>
> This works for searches but edits like save still fail (or save X((%^1X file
> so if you can find it you can rename it).
>
> Looks like fixable bug to simulate what I did for searches? Repeat in
> code ten times 'up arrow', '50 x delete char'? Sorry if I am wrong.
>
> Using sup and not being able to properly search or save is too wrong.
>
> If there is any config/version I should report to get this fixed just
> let me know. Without waiting for new ruby of course -- I do have proper
> results when I repeat deleting ritual.
Hi, can you try the following patch and tell me if it fix the problem?
diff --git a/lib/sup/textfield.rb b/lib/sup/textfield.rb
index b8dec59..ccc8533 100644
--- a/lib/sup/textfield.rb
+++ b/lib/sup/textfield.rb
@@ -36,8 +36,9 @@ class TextField
@field = Ncurses::Form.new_field 1, @width - question.length, @y,
@x + question.length, 256, 0
@form = Ncurses::Form.new_form [@field]
@value = default
+ @value ||= ''
Ncurses::Form.post_form @form
- set_cursed_value default if default
+ set_cursed_value @value
end
def position_cursor
--
A: Because it destroys the flow of conversation.
Q: Why is top posting dumb?
next prev parent reply other threads:[~2009-08-18 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 19:54 Edward Z. Yang
2009-08-18 2:43 ` William Morgan
2009-08-18 7:42 ` Dusan
2009-08-18 18:24 ` Benoît PIERRE [this message]
2009-08-18 18:46 ` Dusan
2009-08-18 18:59 ` Benoît PIERRE
2009-08-18 19:04 ` Dusan
2009-08-18 19:24 ` Dusan
2009-08-18 19:31 ` Jörg-Hendrik Bach
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=1250619721-sup-91@localdomain \
--to=benoit.pierre@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox