jerch

Thats related to this line: https://github.com/xtermjs/xterm.js/blob/f701d073d15f7b312a9d051e719f748665701cef/src/browser/CoreBrowserTerminal.ts#L813 As far as I can see with git blame, it has always been like that in the last 6 years. > File scrolls the...

I checked the xterm sources - thats basically linked there to `alternateScroll` or `DECSET 1007`. For some reason thats disabled on my system (ubuntu here). > Perhaps that sequence should...

@a-p-f Thx for reporting. To be honest, `ForeignKey` fields as CFs were never officially supported (and thus not tested), as they would screw up the dependency tree and make the...

@nnseva Sure, feel free to look into that issue 👍

@nnseva Oh wow - the change from `field.attname` to `field.name` already fixed things here? I cannot really remember, why I went with _attname_ here in the first place, but originally...

@nnseva I've added your PR, thx alot, it solves a long standing issue with computed fk fields. I also was able to find the reason for the _attname_ usage from...

@JestemStefan You are right - in retrospection this change would be better on the 0.3.0 release. By the time the fix was applied, it looked more like a bug getting...

Oh weird, this `|| 0` looks like some testing remnant. Note that the encoder part of this lib is alpha and almost untested. It has serious performance issues, so I...