From 564952cca3fc4786036270a0e664f13b66eed898 Mon Sep 17 00:00:00 2001 From: Jakob Krigovsky Date: Mon, 26 Nov 2018 05:50:09 +0100 Subject: [PATCH] =?UTF-8?q?Update=20=E2=80=9COS=20X=E2=80=9D=20to=20?= =?UTF-8?q?=E2=80=9CmacOS=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- index.html | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/index.html b/index.html index e3ec040..572ece8 100644 --- a/index.html +++ b/index.html @@ -245,16 +245,16 @@

Binary package: mosh-1.3.2.pkg. -

This is a standalone OS X package that will work on any supported Macintosh. However, if you are using a package manager such as Homebrew or MacPorts, we suggest using it to get Mosh, for better compatibility and automatic updates.

+

This is a standalone macOS package that will work on any supported Macintosh. However, if you are using a package manager such as Homebrew or MacPorts, we suggest using it to get Mosh, for better compatibility and automatic updates.

-

Homebrew OS X 10.5 or later

+

Homebrew macOS 10.5 or later

$ brew install mosh

-

MacPorts OS X 10.5 or later

+

MacPorts macOS 10.5 or later

$ sudo port install mosh

@@ -456,7 +456,7 @@

Security on new operating systems


Note that mosh-client receives an AES session key as an environment variable. If you are porting Mosh to a new operating system, please make sure that a running process's environment variables are not readable by other users. We have - confirmed that this is the case on GNU/Linux, OS X, and FreeBSD. + confirmed that this is the case on GNU/Linux, macOS, and FreeBSD.

@@ -661,14 +661,14 @@

Careful terminal emulation

Tricky unicode
-

Only Mosh and the OS X Terminal correctly handle a Unicode combining character in the first column.

+

Only Mosh and the macOS Terminal correctly handle a Unicode combining character in the first column.


xterm: circumflex on wrong letter.

GNOME Terminal: no circumflex at all.
-

OS X Terminal.app gets it right.
+

macOS Terminal.app gets it right.

Mosh gets it right too.
@@ -685,7 +685,7 @@

Careful terminal emulation


GNOME Terminal
-

OS X Terminal.app
+

macOS Terminal.app

Mosh
@@ -694,16 +694,16 @@

Careful terminal emulation

Evil escape sequences

Only Mosh and GNOME Terminal have a defensible rendering when -Unicode mixes with an ECMA-48/ANSI escape sequence. The OS X Terminal +Unicode mixes with an ECMA-48/ANSI escape sequence. The macOS Terminal unwisely tries to normalize its input before the vt500 state machine, causing it to misinterpret and become unusable after receiving the -following input!* (This also means the OS X Terminal's interpretation +following input!* (This also means the macOS Terminal's interpretation of the incoming octet stream varies depending on how the incoming octets are split across TCP segments, because the normalization only looks ahead to available bytes.)

* We earlier wrote that this misbehaving sequence "crashes" -the OS X Terminal.app. This was mistaken—instead, Terminal.app +the macOS Terminal.app. This was mistaken—instead, Terminal.app interprets the escape sequence as shutting off keyboard input, and because of an unrelated bug in Terminal.app, it is not possible for the user to restore keyboard input by resetting the terminal from the @@ -715,7 +715,7 @@

Careful terminal emulation


GNOME Terminal's circumflex placement is defensible.
-

OS X Terminal.app applies circumflex to part of escape sequence, then irretrievably shuts off keyboard input.
+

macOS Terminal.app applies circumflex to part of escape sequence, then irretrievably shuts off keyboard input.

Mosh gets this one right.
@@ -727,7 +727,7 @@

Careful terminal emulation

the user is typing in an 8-bit character set or in UTF-8, because in canonical mode (i.e. "cooked" mode), the kernel needs to be able to delete a typed multibyte character - sequence from an input buffer. On OS X and Linux, this is + sequence from an input buffer. On macOS and Linux, this is done with the "IUTF8" termios flag.) (See diagnostic explaining the need for this flag.)

@@ -953,7 +953,7 @@

Frequently Asked Questions

mosh (or at least mosh-server) is installed on the server you are trying to connect to. Also, the server is expected to be available on your server's default login PATH, which is not - usually true on OS X and BSD servers, or if you install mosh-server + usually true on macOS and BSD servers, or if you install mosh-server in your home directory. In these cases please see the "Server binary outside path" instructions in the Usage section, above.

@@ -1124,7 +1124,7 @@

Frequently Asked Questions

3. If all goes well, you should have a working Mosh connection. Information about where the process fails can help us debug why Mosh isn't working for you.

-
Q: With the mosh-server on FreeBSD or OS X, I sometimes get weird color problems. What's wrong?
+
Q: With the mosh-server on FreeBSD or macOS, I sometimes get weird color problems. What's wrong?

This bug is fixed in Mosh 1.2. Thanks to Ed Schouten and Peter Jeremy for tracking this down.