<feed xmlns='http://www.w3.org/2005/Atom'>
<title>r-alacritty-vte.git/src/utf8, branch rahm</title>
<subtitle>Alacritty's VTE library with Rahm's extra hacks.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.josher.dev/cgit/r-alacritty-vte.git/'/>
<entry>
<title>Move utf8 parsing into separate crate</title>
<updated>2016-09-18T00:03:25+00:00</updated>
<author>
<name>Joe Wilm</name>
<email>joe@jwilm.com</email>
</author>
<published>2016-09-18T00:02:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.josher.dev/cgit/r-alacritty-vte.git/commit/?id=917080a5c27b3310daab135f9bfdbc531cb54186'/>
<id>917080a5c27b3310daab135f9bfdbc531cb54186</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Add support for UTF-8</title>
<updated>2016-09-18T00:03:20+00:00</updated>
<author>
<name>Joe Wilm</name>
<email>joe@jwilm.com</email>
</author>
<published>2016-09-17T22:51:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.josher.dev/cgit/r-alacritty-vte.git/commit/?id=cffdb6de59ceb3fd9983a1c19476e5109da8db97'/>
<id>cffdb6de59ceb3fd9983a1c19476e5109da8db97</id>
<content type='text'>
This adds a table-driven UTF-8 parser which only has a single branch for
the entire parser. UTF-8 support is essentially bolted onto the VTE
parser. Not the most elegant, but it does prevent the transition tables
from blowing up.

Instead of refactoring the syntax extension to handle both table
definitions, I've opted to copy/paste now for both simplicities sake and
because I can't see a clear path to a minimal shared solution.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This adds a table-driven UTF-8 parser which only has a single branch for
the entire parser. UTF-8 support is essentially bolted onto the VTE
parser. Not the most elegant, but it does prevent the transition tables
from blowing up.

Instead of refactoring the syntax extension to handle both table
definitions, I've opted to copy/paste now for both simplicities sake and
because I can't see a clear path to a minimal shared solution.
</pre>
</div>
</content>
</entry>
</feed>
