00:10 <havenwood> v0n: You can just `super` or `super(...)` to pass everything along or `super()` to pass nothing or a combination of `super(*args, **kwargs, &block)` if you want to pick and choose.

00:41 <v0n> havenwood: my question was more about the syntax for passing the variable arguments to super, but I guess from your answer that the syntax is super(*args)

01:37 <ih8u> johnjaye: depends on the conf

01:37 <ih8u> you get to learn some neat stuff from some neat people, and socialise with a lot of other neat people

01:37 <ih8u> the rest kind of depends on you

01:57 <johnjaye> ih8u: what are the big linux conferences? the ones based around specific distros?

02:26 <havenwood> johnjaye: SCALE is what I think of, or OSCON but that's not specifically Linux.

02:26 <havenwood> Lots of Linux distro folk at OSCON though.

02:26 <havenwood> Pretty big conf.

02:27 <havenwood> v0n: If you want to pass on all arguments, just `super` alone. If you're trying to _only_ pass regular arguments and ditch the kwargs and block, a `*` is fine.

02:28 <havenwood> But yeah, if `*args` is different that what the method was called with and what you want, it's totally fair game.

03:02 <havenwood> v0n: Ruby's `super` has some little-known aspects. A `super` will pass both args and block, as long as it has no parens. Most folk aren't aware that `super()` _will_ explicitly _not_ pass arguments or kwargs but _will_ indeed pass a block. You need to `super(&nil)` to not pass a block along.

03:03 <havenwood> I think `&nil` is fairly obscure.

03:03 <havenwood> These days I'd prefer to `super(...)` to signify passing args, kwargs and block.

03:04 <havenwood> The ellipsis means "everything"

03:05 <havenwood> A `super(&nil)` on the other hand means "nothing"

03:05 <havenwood> But will likely confuse many readers

03:08 <havenwood> There are extremely rare cases where you might even `super(*, **, &nil)` to pass args, kwargs but no block.

05:18 <v0n> thank you

09:14 <isene> weaksauce: Comments to your messages above; I want rcurses to be system-wide as my other programs will rely on it - especially important for rtfm. Also since I'm aiming to have it included in Debian/Ubuntu. As for lsblk; ls is already shown in the left pane, and I thought disk usage would be a nice display. lsblk is very common, methinks. What OS are you on? What do you mean when you say "drop the

09:14 <isene> extensions from the gemspec and add the lib/rcurses.rb file to the file"? Making a more fleshed-out example is a good idea. Will think of something nice or cool.

20:25 <weaksauce> isene as it stands it's a brittle install for only a small subset of users

20:25 <weaksauce> sudo gem install would install it system wide the normal way

20:25 <weaksauce> adding the file to files of course

20:26 <weaksauce> i'm on a mac

20:27 <weaksauce> do ls or some other program that exists on 100% of the linux like computers out there would be my suggestion