tangus

Well, I spent 5 minutes laboriously building a query for the whole thing to hang on me when I reached the ORDER BY clause.

I actually don't see how this is better than a cheat sheet with SQL keywords and autocompletion of tables/fields.

Deferred actions are not explicit at the exit points.

That's quite implicit. You can no longer reason about a local piece of code; you now have to know its lexical nesting up to top level to see if it's inside a guard block that might trigger hidden behavior.

It's documented.

>A Date object can be created with an optional argument, the day of calendar reform as a Julian day number, which should be 2298874 to 2426355 or negative/positive infinity. The default value is Date::ITALY (2299161=1582-10-15).

A heads up: if you use a dark theme in your phone, this webpage is recognizes it and changes its background to dark grey. This makes the grey words in the diagrams illegible.

The standard says "bold or increased intensity". I see brighter colors on dark background (what everybody does) more in line with it than darker colors on dark background (what Kitty does).

Good choice. CTWM and Sawfish are two of the best and more configurable window managers there are.

Unfortunately I had to give up on both years ago when they got unmaintained on Debian and not even compiling them from source would make them avoid visual glitches that made them unusable (especially after running Firefox (!)).

Now I use KDE (also quite configurable, at least keyboard-wise) and my life is a little simpler in some ways and my experience a little more annoying in others.

So if A says something incorrect, B can't set the record straight because that's unfortunate and shuts down any respectful discussion?

I'm thinking that reactions to this maintainer's answers probably align to which side of the discussion one often find themselves.

Yeah, that was a silly year we'll never get back, but they seem to be on track again now.

It's your responsibility to buy a car you can operate without causing an accident. If you can't use its wiper interface without losing control, don't buy it.

The same as when people buy power cars which are difficult to drive without training and then oversteer and crash.

You probably turn the 6 upside down.

On the other hand, it makes the move to protect him more commendable. It wasn't just out of self-interest.

They made the multiline field value format incompatible with the email/HTTP/etc headers one...

Why?

I would have tried sshd. What's the catch?

Nice nostalgia. Unfortunately most of the ones that deal with text are from before the 8bit to utf-8 move, which makes them unusable nowadays (unless you restrict yourself to ASCII).

Burning it, actually. It's a legend about how Seymour Cray would design and build a sailboat every year only to burn it afterward, so he could design a better one, or something like that.

It's a subjective question, but given that A68's slices are already burdened with carrying their lower bound wherever they go, not much is lost with adding another piece of data to them. They are already quite fat, and more with each dimension. I think the ability of taking a column and just apply any sequence function to it is well worth it.

I don't think you could use OS APIs without boxing and unboxing data, but I think that's the case with every language except C.

(In the same vein of other comments...)

Algol 68 slices are also fat pointers. Only they also carry a `stride` field, since in Algol 68 you can slice multidimensional arrays in any direction.

Civic honesty x civic duty, actually. One of the variables you measured was whether that unknown guy's problem is worth my effort to contact them.

I'd guess (out of my ass, of course) that many people didn't steal it but also didn't bother. They just left it there for someone to come and pick it up. And I'd also guess they didn't trust they co-workers not to steal the money if they left the wallet there at the end of their shift, that's why more wallets with money were reported.

But he's perfectly right. I don't know if he can arrive to that conclusion from his experiment, nevertheless he's right.

Spanish is full of ambiguous words. Just looking around at my desk, I can find...

papel - paper/role

monitor - monitor/supervisor (in Arg, also the student in charge of class materials)

factura - invoice/a kind of pastry (Arg)

caja - box/till/case/drum/soundbox

revista - magazine/review

And let's not start with the verbs...

sonreír - smirk/grin/smile

arrancar - pull out / pull up / pluck / tear out / rip out / blow off / snatch / wrench / start / start a vehicle or machine / boot / set sail...

Did he just basically copy Joe Allen's Text Editor Performance Comparison[1] (which is already somewhat obsolete) without attribution? Wow.

1: https://github.com/jhallen/joes-sandbox/tree/master/editor-p...

---- EDIT: I'm sorry, there's a mention at the end of the article. Either I didn't noticed it before or he added it after this comment.

Does anybody know how does undo work with this feature?

But in fact it does not seek to mirror _any_ of find's powerful functionality.

Maybe advertize it as "a better ls -R | grep -i"?

You are so strict with your definition of democracy and so loose with your definition of war declaration...

"All problems in computer science can be solved by another level of indirection" --David Wheeler or Butler Lampson

Come on. The spouse in this case is a woman. Ok, OP already said s/he wasn't referring to this case, it "just made him/her think about divorce generally". Let's leave it already.

Here is a great explanation of parser combinators, not tied to any specific implementation:

https://qntm.org/combinators

The answer is no, we all know this. It's an unfortunate title that provokes useless knee-jerk reactions. The author's main point is in the last three paragraphs:

>Three centuries before the ancestors of Mr. Trump landed on United States soil, there were Mexicans in that northern territory known as New Spain and Mexico. But neither they nor their descendants are even symbolically part of American national pride; rather they are objects of stereotyping or emblems of a disgraceful past that has remained, to a great extent, in obscurity. It is time for it to come fully into the light, to be recognized and vindicated.

>For us Mexicans, this is the chance for a kind of reconquest. Surely not the physical reconquest of the territories that once were ours. Nor an indemnification that should have been much greater than the feeble amount of $15 million that the American government paid, in installments, for the stolen land. We need a reconquest of the memory of that war so prodigal in atrocities inspired by racial prejudices and greed for territorial gain.

>But the best and most just reparation would be American immigration reform that could open the road to citizenship for the descendants of those Mexicans who suffered the unjust loss of half their territory.

A long time ago, working for a BBS, I wrote a nice interactive utility to review and change user configurations. I named it uc ("user configure"). After some testing, I installed it in /usr/local/bin.

Time to use it!

    # uc /bbs/users/*

Nothing happens. It needs some time to read all users' configuration files before displaying the user interface, but it's taking too long. What's happening? I decide to interrupt it. Shortly after, we find out all user accounts starting with A, B, and C are wiped out.

Apparently, unbeknown to me, somebody had previously written a utility to delete user accounts. It was named uc (user clear), and was installed in /usr/bin. Fortunately we had fairly recent backups.

That day I learned about hash -r.

You simply use it to wait for the appropriate prompt before sending anything. If the expected prompt never arrives, something is wrong (CLI changed), so abort. The snippet for this particular case could be something like

    set timeout=1
    expect {
      "enter \"p\" for pre-configured paranoia mode"  { puts p\n }
      timeout     abort
      eof         abort
    }

I agree, but if a script is going to use the CLI then it's the script's responsibility to parse the prompts and not to blindly send strings to the program. `expect` exists since 1990, use it or reinvent it.