Wrapping comments

[Lawrence D'Oliveiro]

You could have that ten years ago with AppleScript. Gets annoying
quickly...

To me, the annoying thing about the AppleScript Script Editor wasn't the
tokenization, it was its insistence on overriding my decisions about where
to continue a line.

 

[Lawrence D'Oliveiro]

(still not gonna use software that doesn't let me type # because it's
alt+3 on a UK layout; having to re-learn or configure that is just sick)

Tried typing compose-plus-plus?

 

[Lawrence D'Oliveiro]

You probably haven't used MAC OS X then!

I tried using Emacs via SSH from a Mac once. Made me run screaming for the
nearest Windows box
<http://groups.google.co.nz/group/comp.sys.mac.advocacy/msg/dfad8bff6942e749>.

 

[Tobias Weber]

[OT]

I tried using Emacs via SSH from a Mac once. Made me run screaming

Indeed the terminal application that ships with Mac OS is not by default
set up for elaborate text mode user interfaces like emacs, because Apple
correctly assumes that their typical customer will use a native GUI
instead. Terminal is optimized for casual bash use.

Complaining about that is about as useful as hating your toaster for its
bad coffee. Just use a different terminal. Or, if you're restricted to
included software and its default configuration, a different OS.

My complaint about Aquamacs is (slightly) more substantial, since its
whole point is to make emacs more accessible. To then exlude the
standard keyboard by default is, um, detrimental.

 

[Piet van Oostrum]

LD> In message <[email protected]>, Nick Craig-
LD> Wood wrote:

LD> I tried using Emacs via SSH from a Mac once. Made me run screaming for the
LD> nearest Windows box

The standard Windows box doesn't even have SSH AFAIK.

I edit remote files on my local Emacs on Mac OS X with tramp,
certainly when they are on a SSH-accessible machine.
Works like a charm.

 

[Michael Torrie]

I tried using Emacs via SSH from a Mac once. Made me run screaming for the
nearest Windows box
<http://groups.google.co.nz/group/comp.sys.mac.advocacy/msg/dfad8bff6942e749>.

Interesting rant, but the problem is with the key bindings they chose to
use in Terminal.app program. Fortunately in leopard most of the problems
are now fixed, or can be configured to work in a non-broken fashion.
The rest of us, in the meantime, all switched to iTerm which, although
had some performance issues, behaved like we all expected terminals to
behave.

As far as terminal hell goes, I regularly find that when ssh-ing to
remote boxes that backspace doesn't work. Or does in bash (because it's
smart enough to play games) but not in vim. Somehow sometimes over ssh
the key bindings for backspace get lost of messed up.

 

[Lawrence D'Oliveiro]

Interesting rant, but the problem is with the key bindings they chose to
use in Terminal.app program.

Except for control-space, which was defined systemwide to bring up
Spotlight. So you can't blame the Terminal app for that. The brain damage
was more widespread than just one program.