Alex Knauth
Alex Knauth
I have removed the event, and moved `SetCustomVariable` from `LiveSplitState` to `RunMetadata`.
Bump, can this be merged soon?
Bump? The `==` entry in the grammar is within a giant string. It doesn't seem possible to insert a `@racket[==]` into that string, because this string is passed to the...
Oh, okay. Do you mean the `fixup-sexp` function here? https://github.com/racket/racket/blob/2637cf451925f105f5bf489db59a5ecb9cae11aa/pkgs/racket-doc/scribblings/reference/match-parse.rkt#L65-L85
> It isn't a good idea to put the call to `contract` inside the guard So is it better to put the `contract` call outside, even when the guard calls...
I'm still wondering about the blame information. The old `positive-blame-expr` was the `(current-contract-region)` within the `with-contract #:region struct struct-name` form, which in the old error message example was `(struct s)`....
Closed by https://github.com/LiveSplit/LiveSplit/commit/2df95ecad320e02feffb1affed4519e0b5f840f2 with https://github.com/LiveSplit/LiveSplit.Splits/pull/28 and https://github.com/LiveSplit/LiveSplit.Subsplits/pull/23
On regular LiveSplit, there's a setting for this: "Lock Last Split to Bottom", which is only activated as a choice if "Fill with Blank Space" is True. If "Fill with...
I have a suspicion that this might be related to https://github.com/LiveSplit/livesplit-core/issues/815
I see 2 possible solutions. Either fix `set_config` so that it doesn't do this bad-merging thing, or avoid calling `set_config` in LiveSplitOne entirely: create the hotkey system with the correct...