They can't justify building something because my time doing the work around costs less that the web programmer writing something easier.

But they'd only have to do it once and it would save your time year after year. It sounds more like lazy and/or incompetent.

Sophia, I feel your Pain. I was at a uni for 10 years and had to deal with stupid crap like that all of the tIme. I actually ended up bulidIng my own pages using Contribute.

I despise regular expressions with a passion.

I bow to their power, but they cause me tears. I learn Unix standard regex every time from scratch. And it hurts every time. I'm looking to, if not learn it forever this time, find a good tutorial that encourages me to remember, rather than get me to the regex I need to solve my problem this time and ignore anything else.

So if you were going to show someone who's giving up and giving in the best I-can-actually-already-code introduction to regex, what link would that be?

Hah, I cannot help, because I totally always just look up the one regex I need at the moment.

I feel bad. I worked out three different regexes, when technically there is one that will do it, and...I'm gonna forget that shit. But I recorded it, so at least that's not last.

And you want to know what it was for? To extract every link to a JPG in the SPN thread, because I needed to find the right one, and paging through was just not working, and search was fruitless.

So...great power.

But I must practice. Good text editors will encourage that.

Bwah.

Make that into a sellable product, and you will have millions.

Assuming you've saved the thread in a file called "Supernatural.html", this will work:

$ perl -0777 -ne '@x = /href=.(.*?\\.jpg)/g; print join("\\n", @x)' Supernatural.html

That's not precisely what I did--I didn't just grab the http string, I grabbed the entire <a href=" link so it would be clickable html in the output (I did a regexp find all, copy then paste), I just didn't realise that some people used single quotes and some used none at all, so I ended up going back for more. And then the resulting file was pretty illegible onscreen, so I had to insert t li in there tidy it up and make it followable.

But your command line is a good example of the one liners I've been avoiding paying enough attention to in order to remember--it's not like it's a physical pain, or anything.

The Apple v Samsung verdict is being read now: [link]

Given the complexity of the task, a verdict back this soon is shocking. Some 700 individual decisions needed to be made for the jury to finish its job.

To recap, this jury hasn't asked a single question since Wednesday. It hasn't asked for clarification on a single element of jury instructions, it hasn't asked to have any testimony re-read.... nothing.