From: Karl Schudt <byzkarl@yahoo.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Crash when I search in buffer
Date: Sat, 19 Dec 2009 14:00:30 -0600 [thread overview]
Message-ID: <1261252732-sup-8065@Vergil> (raw)
In-Reply-To: <1261249855-sup-6929@masanjin.net>
Excerpts from William Morgan's message of Sat Dec 19 13:11:32 -0600 2009:
> Reformatted excerpts from Karl Schudt's message of 2009-12-14:
> > I'm using sup 0.9.1, and it seems to work fine until I try to search in
> > the buffer. Then it crashes.
>
> Hm, another such report. Please submit this to
> http://masanjin.net/sup-bugs with the sup version, ruby version,
> ncurses gem version, and any other system information you think is
> relevant.
I'm sorry--I re-installed linux on my computer, using Fedora instead of
Opensuse. Sup installed and worked fine. It must be some peculiarity of
Opensuse.
.
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-12-19 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 12:41 Karl Schudt
2009-12-19 19:11 ` William Morgan
2009-12-19 20:00 ` Karl Schudt [this message]
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=1261252732-sup-8065@Vergil \
--to=byzkarl@yahoo.com \
--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