Linefeeds should only move the cursor down if it's before the end of
the scroll region.

The "out of bounds" panic was triggered by linefeeds going off the
bottom of the screen when the scroll region end was above the cursor.

Note: https://vt100.net/docs/vt102-ug/chapter5.html
"Characters added outside the scrolling region do not cause the screen to scroll."

Outside of a scroll region, linefeed will still advances the line until
reaching the bottom row in other terminals. Alacritty now matches that.

There were two ref tests that were not being run. Oops!

Useful when requesting more info to help investigating issues.

* Support text cursor color escape codes
* Support reset color index escape code
* Support multiple colors in set color index escape code

…ritty#907)"

This reverts commit a931d69.

Please see alacritty#907 (comment)
for rationale w/ GIF.

> now alacritty starts "in stages". First it paints some small
> rectangle, and in a second in "boots" and fills up the available
> space.

… change to "==".

…tatic_lifetime).

…less_pass_by_value, needless_borrow).

The default cursor can now be configured through the cursor_style field
of the config. Valid options include Block, Underline, and Beam.

The default can be restored by sending \e[0q as in VTE terminals.

Live config reloading is supported for this parameter.

…alacritty#879)

I dug into this and narrowed the issue down to the macOS app bundle
Info.plist file. So, I spun up a native macOS app real quick and tested
it by launching the binary directly and launching it via the app bundle.
When launching from the command line directly, it created multiple
windows & instances of the app. However, when launching via the app
bundle it behaved as I normally expect a macOS app to behave, that is
when launched multiple times to simply focus the already existing window
and instance.

This informed me that it wasn't something in code as much as it was
something in the app bundle configuration. Hence, I reworked the
Info.plist file based on the one that was created by XCode when I made
the native macOS app and it started behaving as expected.

Until winit gives us more capabilities in regard to window decorations
this implements a simple switch that renders the window without any
title bar or border

See 46a1ee7

Move/rename borderless into window_config as decorations

This cleans up a bunch of code.

fixes alacritty#1086

The level of heading were one to high.

Upgrading glutin to the latest version allows building alacritty even
with old XRandr versions.

This is relevant for Debian machines (and other ancient systems).