Re: Great SWT Program

On Nov 30, 9:18 am, b...@xxxxxxxxxxx (Bent C Dalager) wrote:
Emacs doesn't generally handle anything in a sensible manner, but this
is irrelevant anyway. The point is that undo is a poor "delete last
sentence" thing because it might delete only the last word or the
whole last paragraph. Undo after typing deleting all the typing since
the last non-typing input, as it does, this must necessarily be the
case.

Undo after typing might do that in the editors you use, but emacs
[apparently violates standards by deleting some random amount instead]

Oh, great, MORE random standards-violating behavior, and again deeply
embedded enough to be unfixable by merely rebinding keys. Can't really
say I'm surprised, though.

Bull***. Would you argue that having safety rails on a catwalk
"reduces efficiency"?
[proceeds to argue that having safety rails on a catwalk reduces
efficiency]

I hope to Christ you don't code anything mission critical, like
software used to control nuclear power plants or medical equipment or
something. Or design workplace environments or anything like that.

Because that is the equivalent of what I'm
discussing here. Your tools easily do irrevocable things without
confirmation, and encourage working blind by requiring extra, explicit
commands just to show you the context of what you're doing.

The blindness is your invention again, of course [snip]

Baloney. It's evident to anyone who so much as touches any of the
cruftware you're pushing. If I go file-save in Windows I see a list of
existing files. Plus it prompts me whether to overwrite one if I pick
a colliding name. If I go file-save in just about any old text-mode
app I get a "Enter filename here:" prompt with no indication of the
existing contents of the save directory, or even what directory it's
figuring to save it in. If I type a name that happens to collide with
an existing file, fifty-fifty odds it just quietly overwrites the old
file without a peep of warning or even a notice after the fact that it
did so.

This is the sort of "blind without extra, explicit commands" I'm
talking about, in a context where it can cause catastrophic data loss
that no amount of control-Z hammering will ever undo.

All that ranting just to arrive at [complete bollocks]

STOP PUTTING WORDS IN MY MOUTH you miserable piece of ***!

Emacs sucks and you can't do a thing to change that. You can't argue
all of its glaring flaws into magically disappearing, nor baffle any
reasonably intelligent human being into becoming so confused as to no
longer recognize the flaws. You waste your time even trying. And I
suspect you lack the programming skills to actually fix the flaws for
real.

The niche you depend on for your daily professional needs is "elitist
old-skool-unix geek"? Because that's all emacs proficiency is required
for. That and "emacs training" anyway.

[Bent tacitly admits that his professional needs include an elitist
attitude]

That's nice to know. Thanks. :P

No, because in that case I've won; end of thread.

You keep saying that. Has it ever done you any good?

Since you're too stubborn and brain-damaged to recognize defeat and
give up, unfortunately it hasn't done all that it should have.
.