This reverts commit 8dcf3cb21e.
My experience with even getting in the door with snaps was sub-par.
The submission/review process seems under specified and under staffed.
The tools for producing snaps were also rather broken in the case
that your PATH doesn't match a blessed configuration. This was
hard to discover and expensive to iterate on.
My conclusion is that snaps are not for me.
When enabled, the windows version will use winpty rather than conpty.
This potentially allows running on older windows versions but has
a few caveats:
* Requires winpty.dll and winpty-agent.exe be in the PATH
* The initial screen / cursor position looks funky for me with the
latest release of winpty, but that is from a couple of years ago
* Mouse reporting doesn't work, perhaps for the same reasons that
it isn't working in conpty.
I want to make this into a runtime selectable feature before tidying
up the installation aspects; we need that plumbing anyway to be
able to select between local and remote mux'd tabs.
conpty, while it may be the best native API available for consoles
built in to Windows 10, currently swallows mouse escape sequences
(https://github.com/Microsoft/console/issues/376) so we need an
alternative for a better windows experience.
winpty appears to be a reasonably mature pty implementation, so
let's try that!
I tried to use winpty-sys from crates.io but it requires the
installation of an external clang compiler so I used bindgen
on my linux box to convert the small header file to rust and
then tweaked it a bit.
This commit includes that basic wrapper plus a type safe layer
on top.
This will require distributing the dll and an agent helper along
with the wezterm.exe.
This commit doesn't implement the wezterm side of the pty interface;
that will be in a follow up commit.
Streamline the travis deploy builds; when TRAVIS_TAG is set
we'll run `--release` builds.
Don't error out in fontconfig/build.rs if fontconfig is not
installed. This makes it possible to `cargo test --all` again
on the mac at the cost of potentially making it harder to troubleshoot
problems with not having fontconfig installed on linux.
However: the get-deps script is responsible for installing that.
Now that we have it running build and test, let's keep it green.
Let's take the nightly channel off; it does tend to fail and I
don't care particularly about it, and there's no need to take
up CI resources for it.
The icon comes from "Smoothicons 7" by Corey Marion which I found
as a royalty free icon searching the internet. I would love to
have a purpose built icon, but this is sufficient for now.
The install script sets up a macOS application bundle that references
the generated wezterm binary and the icon. The same technique could
be used to generate a .desktop file for linux.
I've changed the default-prog on macos to be `login -pf $USER` as
that is a better default experience on macOS.
A big paste could saturate the input/output of the pty and
lead to an effective deadlock; the application wants to send
output to us but we are busy trying to write the paste to it.
Break up large pastes into chunks and send them piece by piece.
This does mean that a large bracketed paste is not an atomic
unit any longer, but it seems to work out ok when pasting into
vim.
