@derobert awesome!

I feel kind of bad bugging you all given that I haven't been on here in ages

swamped by the end of the school year

@strugee The pool opens Saturday. Got to have the last bits of that software done by then.

don't we have a "why bash do X but zsh no?" kind of question? unix.stackexchange.com/q/131588/41104

@derobert ?

github.com/derobert/Westerley-Pool ... I'm writing the software for our community to use to issue/check pool passes

@derobert oooo, fancy

Hello guys!!

Hrm, interesting. Docker recommends using SO for asking questions instead of U&L. I would have figured that'd be off topic for SO and on topic for us :-/

@Patrick I remember seeing that on their site as well too. Had a similar thought.

@Patrick - I don't see why it wouldn't be here either. Seems to make more sense to be targetted here. They're probably just not as knowledgeable about this community vs. SO. I'd like to see more of the virtualization Q's brought here as well. LXC, KVM, etc. I've noticed that these are also present on SF too.

Pinging them should be easy, probably have to coordinate w/ whomever is fielding the tags to do so here vs. there or doing it here in addition.

@slm Yeah, with as tightly tied to the Linux kernel as Docker is, it just makes sense. Now that you mention it, virtualization is something we don't see much of. And that surprises me.

@Patrick - yeah I think those technologies are viewed as server techs primarily. Looking at just kvm and lxc on SF returns 2,862 and 376 respectively

@Patrick - for UL kvm (581) lxc (163)

@slm I see SF lxc=125 and UL lxc=57

@Patrick - those were just raw searches not the tags

oohh

How can I find a substring on a string using regex?

The tagging is unreliable, IMO, so I'd take the raw search over tags for that. There are false positives, likely, but for strings like lxc there are probably zero, and kvm would be a mix of virt. + kvm switches

@Lucio - ask actual Q's on main site

I thought this has been asked previously :D

thanks, I will

I think I found it here :)

Oh that definitely worked

This is how to replace an old string with a new one:

sed -r "s#$OLD#$NEW#g" "$SOURCEFILE"

late here, later there! g night

I'm out as well. G'night

ha ha

modern.ie/en-us/virtualization-tools#escape-from-xp

Quick Q for the terminal gurus here; anyone have any ideas what might cause terminal input corruption?

I have tried to answer a question on Stack Overflow where it turns out the Cyrillic input (in UTF-8) in a terminal is being corrupted.

Extra D0 bytes have been inserted (in one instance with a space as well), effectively doubling those bytes, apparently randomly.

Perhaps this rings a bell somewhere to someone?

See stackoverflow.com/a/23823715 for the context.

@MartijnPieters is a virtual terminal right? which one? gnome, konsole, something else?

Where's the twitter bot when you need it? That's the type of things it should tweet out.

@derobert Ha! Yes, I saw that too :). But surely script -a'Hello * all' would also work wouldn't it?

@terdon Huh? The problem is inside script...

script being the OP's shell script, not the script command

@derobert That's what confuses me. If you run script.sh -a"foo*bar" the * should be expanded before it's passed to the script. So, however you echo it inside the script shouldn't make any difference.

Seeing as this is POSIXman we're talking about I'm sure I'm missing something but what?

var="hello * world"
echo $var

that's all...

$var is being set fine. Setting it as var='hello * world' makes no difference.

hmm, hang on.

Νο. Νοt if the wildcard actually matches anything:

 ./a.sh "/etc/a*b"
/etc/auto.smb
/etc/a*b

umm

never mind blush. I should read my own output

Damn. So, parameters passed to a script are not expanded before they're passed?

Not when they're quoted.

Huh. Only variables then?

@terdon mu

@terdon No. Quoting stops glob expansion.

wildcards in unquoted words are expanded

anthony@Zia:/tmp/test$ touch a b c d
anthony@Zia:/tmp/test$ var="hello *"
anthony@Zia:/tmp/test$ echo "$var"
hello *
anthony@Zia:/tmp/test$ echo $var
hello a b c d

Exactly. OK, so variables are expanded before being passed but globs aren't?

it doesn't matter where the word is (apart from single-word contexts that suppress globbing and splitting, such as in an assignment)

@terdon in double-quoted strings, yeah, $foo is expanded. Globs are not.

@terdon what do you mean by “variables are expanded”? If you mean variable substitutions, then that happens when unquoted or in double quotes.

@terdon in single-quoted strings, $foo is not expanded. Neither are globs.

Huh. I always thought that both globs and variables are expanded in double quotes.

@Gilles Yes, that's what I meant.

That when running ls "$foo", ls never sees $foo but only whatever $foo evaluates to.

I was under the impression that globs were treated the same way.

Damn, I thought I knew all these little details after hanging out with you guys here. Thanks for clearing that up, both of you.

Anyway, we should gather more #stephanefacts then we can start our own version of meta.stackexchange.com/questions/9134/jon-skeet-facts

Heh

@derobert why nobody has answered that?

@Braiam probably we're all waiting for Stephane to do so, since he figured it out.

whoops unix.stackexchange.com/review/close

@Braiam ?

there are/were 7 post in the review D:

I think I'm missing the joke :-(

@Braiam Sorry I took a late lunch 8-)

@slm meh, don't worry, we still need 5 of us

WE ARE SCREWED! Someone is thinking we are the Linux kernel bug tracker

@Braiam Uh? The question is asking where to file a bug, I don't see anyone thinking SE is the place to do that

> Isn't this site for reporting kernel's bugs ?

and the comment you link to is asking about bugzilla.kernel.org

@Braiam no: “this site” links to bugzilla.kernel.org

I linked to the guides, not directly to the bug trackers in some kind of click trough

I swear it looks black on my screen

clearly blue

I don't know.... maybe anti-slashing or some other stuff broke