Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update “OS X” to “macOS” #53

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update “OS X” to “macOS” #53

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 14 additions & 14 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -245,16 +245,16 @@ <h3 class="callout"><a href="https://www.apple.com"><img class="logo" src="macos
<div class="prelike">Binary package: <a href="https://mosh.org/mosh-1.3.2.pkg"><img src="dmg.png" alt=""> mosh-1.3.2.pkg</a>.</div>
<!-- <br />
<div class="prelike">OS X 10.5&ndash;10.9: <a href="https://mosh.org/mosh-1.2.5-leopard.pkg"><img src="dmg.png" alt=""> mosh-1.2.5-leopard.pkg</a>.</div> -->
<p><small>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.</small></p>
<p><small>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.</small></p>
</div>

<div class="span4" style="vertical-align: top;">
<h3 class="callout"><a href="https://mxcl.github.io/homebrew/"><img class="logo" src="homebrew2.png" alt=""></a>Homebrew <small>OS X 10.5 or later</small></h3>
<h3 class="callout"><a href="https://mxcl.github.io/homebrew/"><img class="logo" src="homebrew2.png" alt=""></a>Homebrew <small>macOS 10.5 or later</small></h3>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new name only applies to new versions of the operating system. The correct name would be Mac OS X Leopard according to Apple.

<pre>$ brew install mosh</pre>
<br />
</div>
<div class="span4" style="vertical-align: top;">
<h3 class="callout"><a href="https://www.macports.org"><img class="logo" src="macports.png" alt=""></a>MacPorts <small>OS X 10.5 or later</small></h3>
<h3 class="callout"><a href="https://www.macports.org"><img class="logo" src="macports.png" alt=""></a>MacPorts <small>macOS 10.5 or later</small></h3>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same issue as line 252. The correct name would be Mac OS X Leopard.

<pre>$ sudo port install mosh</pre>
<br />
</div>
Expand Down Expand Up @@ -456,7 +456,7 @@ <h3 class="callout">Security on new operating systems</h3><br>
Note that <code>mosh-client</code> 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.
</p>
</div>
</div>
Expand Down Expand Up @@ -661,14 +661,14 @@ <h3 class="callout">Careful terminal emulation</h3>
<dl>
<dt>Tricky unicode</dt>

<dd><p>Only Mosh and the OS X Terminal correctly handle a Unicode combining character in the first column.</p>
<dd><p>Only Mosh and the macOS Terminal correctly handle a Unicode combining character in the first column.</p>
<div class="thumbs">
<div class="row">
<div class="span4"><img src="terminal-shots/firstcol-xterm.png.2.png" alt=""><br>xterm: circumflex on wrong letter.</div>
<div class="span4"><img src="terminal-shots/firstcol-gnome.png.2.png" alt=""><br>GNOME Terminal: no circumflex at all.</div>
</div>
<div class="row">
<div class="span4"><img src="terminal-shots/firstcol-osx.png.2.png" alt=""><br>OS X Terminal.app gets it right.</div>
<div class="span4"><img src="terminal-shots/firstcol-osx.png.2.png" alt=""><br>macOS Terminal.app gets it right.</div>
<div class="span4"><img src="terminal-shots/firstcol-mosh.png.2.png" alt=""><br>Mosh gets it right too.</div>
</div>
</div>
Expand All @@ -685,7 +685,7 @@ <h3 class="callout">Careful terminal emulation</h3>
<div class="span4"><img src="terminal-shots/acs-gnome.png.2.png" alt=""><br>GNOME Terminal</div>
</div>
<div class="row">
<div class="span4"><img src="terminal-shots/acs-osx.png.2.png" alt=""><br>OS X Terminal.app</div>
<div class="span4"><img src="terminal-shots/acs-osx.png.2.png" alt=""><br>macOS Terminal.app</div>
<div class="span4"><img src="terminal-shots/acs-mosh.png.2.png" alt=""><br>Mosh</div>
</div>
</div>
Expand All @@ -694,16 +694,16 @@ <h3 class="callout">Careful terminal emulation</h3>
<dt>Evil escape sequences</dt>

<dd><p>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 <strong>varies</strong> depending on how
the incoming octets are split across TCP segments, because the
normalization only looks ahead to available bytes.)</p>

<p><small>* We earlier wrote that this misbehaving sequence "crashes"
the OS X Terminal.app. This was mistaken&mdash;instead, Terminal.app
the macOS Terminal.app. This was mistaken&mdash;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
Expand All @@ -715,7 +715,7 @@ <h3 class="callout">Careful terminal emulation</h3>
<div class="span4"><img src="terminal-shots/unicode-and-escape-gnome.png.2.png" alt=""><br>GNOME Terminal's circumflex placement is defensible.</div>
</div>
<div class="row">
<div class="span4"><img src="terminal-shots/unicode-and-escape-osx.png.2.png" alt=""><br>OS X Terminal.app applies circumflex to part of escape sequence, then irretrievably shuts off keyboard input.</div>
<div class="span4"><img src="terminal-shots/unicode-and-escape-osx.png.2.png" alt=""><br>macOS Terminal.app applies circumflex to part of escape sequence, then irretrievably shuts off keyboard input.</div>
<div class="span4"><img src="terminal-shots/unicode-and-escape-mosh.png.2.png" alt=""><br>Mosh gets this one right.</div>
</div>
</div>
Expand All @@ -727,7 +727,7 @@ <h3 class="callout">Careful terminal emulation</h3>
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 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665757">diagnostic
explaining the need for this flag.</a>)</p>
Expand Down Expand Up @@ -953,7 +953,7 @@ <h1>Frequently Asked Questions</h1>
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 <code>PATH</code>, 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.</p></dd>
Expand Down Expand Up @@ -1124,7 +1124,7 @@ <h1>Frequently Asked Questions</h1>

<p>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.</p>

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

<dd><p>This <a href="https://github.com/keithw/mosh/pull/129">bug</a> is fixed in Mosh 1.2. Thanks to Ed Schouten and Peter Jeremy for tracking this down.</p></dd>

Expand Down