toofar

Results 182 comments of toofar

The fixups I did for black were just for [line too long](https://github.com/qutebrowser/qutebrowser/commit/ddf40ac903244b4f54617f5a37afd544248686c8) and [moving](https://github.com/qutebrowser/qutebrowser/commit/180da6eb6229cce75876b9f5116f3471561a8467) type ignore comments up inside new parenthesised blocks. And for isort it was just one [circular...

> set: NoOptionError - No option 'qt.chromium.sandboxing' Your version output says you are running on `f11cdd0bf on HEAD (2021-02-04 10:19:33 +0100)`, that option was only added this year. Any reason...

It looks like the redirectableResources map got moved from redirect-engine.js to a new redirect-resources.js in https://github.com/gorhill/uBlock/commit/985ea24e826d62dc1f05fb09c95603780d47fbf6

I realize that the X11BypassWindowManagerHint flag was added to solve [an issue](https://github.com/flameshot-org/flameshot/pull/2520) but it would be nice if it was a configuration option at least (to make pinned windows "normal"...

Here you go: ```javascript // ==UserScript== // @name Twitch-HLS-AdBlock // @namespace github.com/instance01 // @description Block advertisements that are inserted in Twitch streams directly. // @match *://*.twitch.tv/* // @run-at document-start //...

Haha, I just looked into this recently (haven't actually done it though). Mostly from this post http://blog.spreedlycom/2014/06/24/merge-pull-request-considered-harmful/. You just add the pr as a new branch (origin pull/ID/head:new-local-branch [1](https://help.github.com/articles/checking-out-pull-requests-locally) [3](https://gist.github.com/piscisaureus/3342247))...

@DrTobe @hpfmn put a workaround here: https://github.com/qutebrowser/qutebrowser/issues/7859 Hopefully that gets you going for now, not really sure what's going on there but hopefully someone figures it out before the next...

Apparently the `macos-14` runner (which is available for public repos too) runs on an M1 CPU now: https://github.com/actions/runner-images/issues/9254 I guess that means if we want to support older macOS releases...

Hi @bitraid . I'm planning on looking at this after we get the 3.0 release out. Mostly because you are maintaining the prior version already so if you say it...

> maybe open a PR with an update for the current version? Maybe? https://github.com/qutebrowser/qutebrowser/pull/7804 mentions something about NSIS changes, so they would be welcome. But if we aren't building 32bit...