[#64210] Asking for clarification for exception handling usage — Rodrigo Rosenfeld Rosas <rr.rosas@...>
I've created a ticket for that but didn't get any feedback so I decided
5 messages
2014/08/05
[#64517] Fw: Re: Ruby and Rails to become Apache Incubator Project — Tetsuya Kitahata <kitahata@99.alumni.u-tokyo.ac.jp>
What do you think? >> Ruby developers
13 messages
2014/08/23
[#64524] Re: Fw: Re: Ruby and Rails to become Apache Incubator Project
— Henry Maddocks <hmaddocks@...>
2014/08/24
[#64525] Re: Fw: Re: Ruby and Rails to become Apache Incubator Project
— Brandon Weaver <keystonelemur@...>
2014/08/24
What benefits are there to this? I have a feeling that adding unnecessary
[#64526] Re: Fw: Re: Ruby and Rails to become Apache Incubator Project
— Tetsuya Kitahata <kitahata@99.alumni.u-tokyo.ac.jp>
2014/08/24
On Sat, 23 Aug 2014 22:43:46 -0700
[#64527] Re: Fw: Re: Ruby and Rails to become Apache Incubator Project
— Urabe Shyouhei <shyouhei@...>
2014/08/24
Here I am a Japanese. Before moving anywhere else answer to our question first: what benefits?
[#64528] Re: Fw: Re: Ruby and Rails to become Apache Incubator Project
— Tetsuya Kitahata <kitahata@99.alumni.u-tokyo.ac.jp>
2014/08/24
tax issue with each other.
[#64531] Re: Fw: Re: Ruby and Rails to become Apache Incubator Project
— Urabe Shyouhei <shyouhei@...>
2014/08/24
Forgot to assert my opinions:
[#64614] cowspace (work-in-progress) — Eric Wong <normalperson@...>
Hi all, I started working on a cowspace branch. Based on the mspace API
4 messages
2014/08/28
[#64615] [ruby-trunk - Feature #10181] [Open] New method File.openat() — oss-ruby-lang@...
Issue #10181 has been reported by Technorama Ltd..
10 messages
2014/08/28
[#64616] Re: [ruby-trunk - Feature #10181] [Open] New method File.openat()
— Eric Wong <normalperson@...>
2014/08/28
I like this feature.
[#64623] Re: [ruby-trunk - Feature #10181] [Open] New method File.openat()
— Joel VanderWerf <joelvanderwerf@...>
2014/08/29
On 08/28/2014 02:53 PM, Eric Wong wrote:
[#64634] Re: [ruby-trunk - Feature #10181] [Open] New method File.openat()
— Eric Wong <normalperson@...>
2014/08/29
Joel VanderWerf <joelvanderwerf@gmail.com> wrote:
[#64635] Re: [ruby-trunk - Feature #10181] [Open] New method File.openat()
— Joel VanderWerf <joelvanderwerf@...>
2014/08/29
On 08/29/2014 12:55 AM, Eric Wong wrote:
[#64638] Re: [ruby-trunk - Feature #10181] [Open] New method File.openat()
— Eric Wong <normalperson@...>
2014/08/29
Joel VanderWerf <joelvanderwerf@gmail.com> wrote:
[#64627] [ruby-trunk - Feature #10182] [PATCH] string.c: move frozen_strings table to rb_vm_t — ko1@...
Issue #10182 has been updated by Koichi Sasada.
3 messages
2014/08/29
[#64671] Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object — SASADA Koichi <ko1@...>
Why this fix solve your problem?
9 messages
2014/08/30
[#64672] Re: Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object
— SASADA Koichi <ko1@...>
2014/08/30
(2014/08/30 8:50), SASADA Koichi wrote:
[#64676] Re: Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object
— Eric Wong <normalperson@...>
2014/08/30
SASADA Koichi <ko1@atdot.net> wrote:
[#64684] Re: Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object
— Eric Wong <normalperson@...>
2014/08/31
Eric Wong <normalperson@yhbt.net> wrote:
[#64692] Re: Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object
— SASADA Koichi <ko1@...>
2014/08/31
(2014/08/31 0:18), Eric Wong wrote:
[ruby-core:64381] [ruby-trunk - Feature #8515] [Feedback] don't allow irb to dump output for forever and ever
From:
shibata.hiroshi@...
Date:
2014-08-15 02:34:11 UTC
List:
ruby-core #64381
Issue #8515 has been updated by Hiroshi SHIBATA. Status changed from Open to Feedback ---------------------------------------- Feature #8515: don't allow irb to dump output for forever and ever https://bugs.ruby-lang.org/issues/8515#change-48349 * Author: Josh Sharpe * Status: Feedback * Priority: Normal * Assignee: * Category: * Target version: ---------------------------------------- You've done this before, I know you have. You were screwing around in IRB and you ran something stupid and IRB just started dumping output. LOTS of output. Output that would scroll by for an hour if you don't go kill it. Output going by so fast that it's useless. So much output that your lappy laptop starts burning your knees. (That much output!) Then, to compound problems, Crtl-C doesn't work here. Maybe you're in some weird context, or on a low-mem server and everything is just... What, Bam, UNRESPONSIVE. Ugh, the troubles! Now you gotta gotta bust out the 'kill -9' (if you can even get another terminal open) and lose any progress you may have been working on.... OH MAN! Wouldn't it be nice if IRB limited its output, much the way psql/less do? That is, at some point if enough output has scrolled by, Stop, and let me have the option to continue or not. That'd be cool. <3 -- https://bugs.ruby-lang.org/