> On 2021-12-22, at 10:10 AM, Thiede, Christoph <Christoph.Thiede at student.hpi.uni-potsdam.de> wrote:
> 
> Or do you actually hit *command* + [ rather than just [? If yes, why? On Windows, command + bracket does not show any effect at all for me.


Err, yeah; it's only the way we old farts have been doing it for about 40 years. The idea of simply hitting '[' and not getting an actual [ on its own is horrifying. If I want to enclose a block of text I expect to do cmd-[. If I want to remove the [] from an enclosed block I expect to select the text inside the [] and hit cmd-[ ; I'll admit that the idea of using cmd-] to remove has some possible merit and might be enough to make me remember it.

An important point that seems to get forgotten too often is that *typing* some text is a small fraction of the job. *Editing* it will usually occupy much more time, and is typically more fiddly because you have to fairly precisely select text and then operate on it. I'll take improvements to *editing* over improvements on *typing afresh* any day. Anyone that doesn't pretend they get it perfectly correct first time (and they are lying) should prefer it.

And surely any cmd-T to make an ifTrue should actually insert
ifTrue:
	[
anyway? And then maybe cmd-ctl-shift-t with a selection should make it
ifTrue:
	[previous selection]
??
And then clearly cmd-shift-ctl-meta-t should do
ifTrue:
	[previous selection]
ifFalse:
	[]
?

I mean, let's go the whole emacs while we're at it...

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
Strange OpCodes: RBR: Remove Bits Randomly