Age | Commit message (Collapse) | Author |
|
|
|
|
|
This will break things as there's no PyQt 5.9.1 Linux wheel available yet, but
it'll make it possible to release a new qutebrowser release for macOS and
Windows with Qt 5.9.2 at least.
|
|
|
|
When doing :unbind with a default keybinding the first time, it gets inserted
into bindings.commands with None as value.
When then doing :unbind a second time, instead of just leaving that None value
as-is, we removed it again (because it got treated as a custom binding).
Fixes #3162
(cherry picked from commit 5689a3c0dc9aecae425a9a43602823418a0927f9)
|
|
We really just need to check that the row exists here, the date doesn't
matter. Checking the date here is actually flaky with regards to time.
When running locally at 11:50 EST, it failed with:
```
assert self._model.data(self._model.index(row, col)) == item
AssertionError: assert '1969-12-31' == '1970-01-01'
- 1969-12-31
+ 1970-01-01
```
It was wrong to assume that an atime of 0 would always format to
1970-01-01.
(cherry picked from commit a9926e44f0b2f88a4ffd772be8b41d82f5b9afd5)
|
|
I previously removed the sorting logic from SortFilter thinking it was
unnecessary if we construct the model with a sorted list. However, this
only worked when no pattern was set, and the items are misordered as
soon as a pattern is input.
This patch reintroduces alpha-sorting, which can be disabled by passing
sort=False to the ListCategory constructor. The session completion test
had to be tweaked as it simulated the incorrect assumption that the
session list is not alpha-ordered; sessions come out of the
session-manager pre-sorted so we may as well use alpha-sorting in the
session completion model.
Resolves #3156.
(cherry picked from commit 47447c047ad7374e2b7ec4bb4775eb74f7f5f6a8)
|
|
It can be used in normal mode as well, and it's nice to have it discoverable.
Fixes #3235.
(cherry picked from commit bb208f4e7736312aa8bfc1763f166b84f2259169)
|
|
(cherry picked from commit 1c39715267c9dd242a06fe5478b1e9cbe831c1f6)
|
|
Looks like npm doesn't work with Node v9:
https://github.com/nodejs/node/issues/16649
(cherry picked from commit 385337eb90966706960c618b75c9e6854fea1bcf)
|
|
Closes #3223
(cherry picked from commit cb7e6ab02d22995bff0728ee5ee78820221f2d2e)
|
|
(cherry picked from commit 64b6852ae34929659f2376c4fd02545a012007bd)
|
|
See #3209
(cherry picked from commit 2a4163b2c7b3e8bb321ba92e01e73af2957288dc)
|
|
(cherry picked from commit 97d719b1792e419aa53e36467d9e0186d71bbf75)
|
|
(cherry picked from commit cb6f4313d7e74d1cf8ab7152958b617fad34c882)
|
|
(cherry picked from commit 49daa7aab88fca09034eae4dae36176587641125)
|
|
(cherry picked from commit b49947459918269189a8d633923dd9a9cd612567)
|
|
(cherry picked from commit caae1c70085d61413c760af0861a3f79e840179d)
|
|
(cherry picked from commit fde4495bc795699aa413892fe30b5390b8592f99)
|
|
(cherry picked from commit e705ea7e568535528c8cf8200684214bf9364687)
|
|
(cherry picked from commit 08b562ea0c52e6dfa496055371ed668777adc418)
|
|
[ci skip]
(cherry picked from commit 17e0f6d23c8e472e4eaea59e967554284cbb810c)
|
|
See #2930
(cherry picked from commit 96bec9f9d7139264488dbaeb700dbed36986b5f6)
|
|
|
|
(cherry picked from commit 1a7612e559560e8b1a1fb95ebaf9151a3643e9c4)
|
|
(cherry picked from commit d8384ced0a958e9841dfbb7f7b0d75f1f8c92f19)
|
|
(cherry picked from commit e766fe14fcde6769f50e02f822b0d788266acc3f)
|
|
Fixes #3130
(cherry picked from commit 2a65cadb67ec8ec1792e5e6f90b770ae82e6b221)
|
|
(cherry picked from commit fa4a66f7b38ed038e11f74011c796e2577b3f005)
|
|
|
|
|
|
|
|
While the old values meant the same thing, they weren't mutable, so the config
couldn't modify them with a simple .append().
Fixes #3104
|
|
[ci skip]
|
|
We don't support Qt < 5.4 anymore anyways.
|
|
We need to do it before utils.opengl_vendor(), and it fits better there anyway.
This was a regression in v1.0.
See #2554, #3106
|
|
|
|
For some reason, this hangs a lot on AppVeyor
|
|
|
|
This happens on Travis from time to time.
|
|
[ci skip]
|
|
|
|
|
|
|
|
[ci skip]
|
|
With the previous commit, we also checked that PyQt was >= 5.7.1, but we want to
support PyQt 5.7.0. Instead, we now check the individual components by hand.
Also, the previous check accidentally allowed PyQt >= 5.2.0 instead of 5.7.0.
|
|
With an older PyQt built against a newer Qt, we still don't have its features
available.
This also drops support for exact=True with compiled=True as the semantics for
that are unclear, and it's not used.
|
|
See #3096
|
|
|
|
|