Just remember to run cargo fmt --all.

and remove Cargo.lock
:))

and remove Cargo.lock

Don't remove it if you're adding deps.
If it doesn't conflict, then it's fine.

and remove Cargo.lock

Don't remove it if you're adding deps.
If it doesn't conflict, then it's fine.

Did the Cargo.lock ci check get removed?

Did the Cargo.lock ci check get removed?

It did because Cargo.lock exists for some reason.
Just don't push a deleated and re-cleanbuilded Cargo.lock if not neccessary. - That's the idea here.

Just don't push a deleated and re-cleanbuilded Cargo.lock if not neccessary

makes sense

Please take a look at the check.

Please take a look at the check.

already on it

This causes a reversion by removing functionality added in #202.

Yeah, that'll have to get sorted out. I'll have to take a deeper look into breaking up the lines on overflow, since it gets a little complicated with the unrendered ansi sequences in the raw strings

Just perusing the docs a bit, this shouldn't be too hard. I'd probably still use a flat map, just over the constructed lines rather than the raw text to preserve the styling and accurately determine the width of the actually rendered text

@lj3954 why are we looking at wrapping rather than side scrolling?

@lj3954 why are we looking at wrapping rather than side scrolling?

Oh I like side scrolling a lot better.

Oh I like side scrolling a lot better.

Me 2, but there's also the issue of altered semantics of a mid line break without also inserting a trailing* backslash, and even then I'm not sure that backslashes are valid at any arbitrary location*

@ChrisTitusTech @lj3954 just implemented side scrolling to fix regression

get_lines should not take in an owned String, the split method is implemented for str instead. The lines() method also is more idiomatic than split("\n").

get_lines should not take in an owned String, the split method is implemented for str instead. The lines() method also is more idiomatic than split("\n").

good catch, that was pretty sloppy