From: Gaute Hope <eg@gaute.vetsj.com>
To: Ruthard Baudach <ruthard.baudach@web.de>,
"supmua@googlegroups.com" <supmua@googlegroups.com>
Subject: Re: Re: [sup] ncursesw segmentation fault after update
Date: Tue, 29 Jul 2014 15:15:30 +0200 [thread overview]
Message-ID: <CABKe4MuFHY5KH7fEANeU9Y6gDRkTBQcFWs5P0YOpgVoPPqBkbQ@mail.gmail.com> (raw)
In-Reply-To: <trinity-40c4ba6a-e23f-44b6-9d87-63061d4b9b29-1406638933924@3capp-webde-bs49>
On Tue, Jul 29, 2014 at 3:02 PM, Ruthard Baudach <ruthard.baudach@web.de> wrote:
>
>
> Yes,
> I tried:
> ruby 1.9.1 => sup 0.19 needs >= 1.9.3
> ruby 1.9.3 with ncursesw 1.4.9 and 1.4.2 => segfault
> ruby 2.1.2 with ncursesw >= 1.4.2 => segfault.
>
> By the way, im using sup in byobu (ubuntu's enhanced gnu screen) over sup. Shoudn't make a difference though.
>
Does this happen with a completely clean setup as well (empty .sup
directory)? Could you try it without byobu as well?
- gaute
prev parent reply other threads:[~2014-07-29 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 18:26 ruthard.baudach
2014-07-28 10:33 ` [sup] " Gaute Hope
[not found] ` <trinity-40c4ba6a-e23f-44b6-9d87-63061d4b9b29-1406638933924@3capp-webde-bs49>
2014-07-29 13:15 ` Gaute Hope [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=CABKe4MuFHY5KH7fEANeU9Y6gDRkTBQcFWs5P0YOpgVoPPqBkbQ@mail.gmail.com \
--to=eg@gaute.vetsj.com \
--cc=ruthard.baudach@web.de \
--cc=supmua@googlegroups.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