From me at the-compiler.org Tue Jan 6 07:18:09 2015 From: me at the-compiler.org (Florian Bruhin) Date: Tue, 6 Jan 2015 07:18:09 +0100 Subject: This week's qutebrowser updates Message-ID: <20150106061809.GQ25530@tonks> Heya! Last week I didn't think about sending an update mail because I was at the annual CCC congress in Hamburg and busy with releasing v0.1.1: https://lists.schokokeks.org/pipermail/qutebrowser/2014-December/000029.html If you're still on v0.1 (or older...) you should update! You can check your current version using :open qute:version. A lot has happened in the past two weeks though! Also, it's mind-blowing how many people have contributed lately - you're all awesome! I hope I didn't forget anyone in the logs below. Overview -------- (for the past week, because Github doesn't let me view this for two weeks...) Excluding merges, 7 authors have pushed 28 commits to master and 31 commits to all branches. On master, 147 files have changed and there have been 450 additions and 311 deletions. 6 Pull requests merged by 6 people 1 Pull request proposed by 1 person 16 Issues closed by 2 people 6 Issues created by 1 person https://github.com/The-Compiler/qutebrowser/pulse/weekly Features -------- - User is now asked whether to overwrite an existing file with downloads. Thanks to Joel Torstensson for this contribution! - Add an -f option to :reload to reload without cache. Thanks to HalosGhost for this contribution! - Pass more information (QUTE_MODE, QUTE_SELECTED_TEXT, QUTE_SELECTED_HTML, QUTE_USER_AGENT) to userscripts. Improvements ------------ - Rewrite of the way nested keyboard modes (e.g. clicking an input field while a prompt is active) are handled because the previous behaviour was too complicated and buggy. Now there's only one active mode, and insert mode on click is disabled as long as we're not in normal mode. - Give keyboard focus back to web view after leaving prompt mode. - Set the window icon to the qutebrowser logo. - Disable alias completion for now (not too important and needs more work to work properly) - Add a fullscreen keybinding. Thanks to Joel Torstensson for this contribution! - Remove hosts-file.net from default block lists (too many false-positives). - Add a :search command in addition to "/foo" so it's more visible and can be used from scripts. Thanks to Johannes Altmanninger for this contribution! - Various documentation improvements. Thanks to Regina Hug, Helen Sherwood-Taylor Martin Zimmermann and John ShaggyTwoDope Jenkins for their contributions! - Small crash dialog/log improvements (grey out report button, move debug log to bottom) - Expand ~ to the users home directory with :run-userscript. - Improve the userscript runner on Linux/OS X by using QSocketNotifier. - Don't add debug log to crash reports by default in private browsing mode. - Add luakit-like gt/gT keybindings to cycle through tabs. Thanks to Thiago Barroso Perrotta for this contributon! Bugfixes -------- - Display IPC error as warning instead as exception. - Fix AttributeError on config changes with old Qt versions (e.g. on Ubuntu Trusty) - Fix exception when showing a filename question for an already cancelled download. - Make qutebrowser work even if started with an invalid working directory. - Handle :restart correctly with Python eggs. - Fix an exception in the completion with certain input. - Fix setting of QWebSettings with an empty string. - Fix crash with invalid ShellCommand setting values (e.g. general->editor). - Fix segfault when refreshing/navigating away from pages while a prompt (SSL errors, javascript prompt, etc.) is open. - Fix an invalid value in the default config (ooops!). Thanks to Matthias Lisin for this contribution! - Fix exception when downloading files with chars not encodable in the system's filesystem encoding (e.g. UTF-8 with LANG=C). - Fix hints->uppercase option. Thanks to Error 800 for this contribution! -- http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From edu at thorsten-wissmann.de Sat Jan 10 03:27:15 2015 From: edu at thorsten-wissmann.de (Thorsten =?iso-8859-1?Q?Wi=DFmann?=) Date: Sat, 10 Jan 2015 13:27:15 +1100 Subject: [PATCH] Fix some check_libraries() for arch Message-ID: <20150110022715.GA22319@ghul.anu.edu.au> By now, the python-jinja and python-pygments packages are available in community. The attached patch 0001-Fix-some-check_libraries-for-arch.patch contains the commit, you can apply it with git am 0001-Fix-some-check_libraries-for-arch.patch Cheers, Thorsten -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Fix-some-check_libraries-for-arch.patch Type: text/x-diff Size: 1554 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 213 bytes Desc: not available URL: From me at the-compiler.org Wed Jan 14 21:40:03 2015 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 14 Jan 2015 21:40:03 +0100 Subject: qutebrowser v0.1.2 released! Message-ID: <20150114204003.GD30488@tonks> Hi, this release was already made past Saturday, but I didn't post an annoucement yet as I was sick in bed over the past few days... v0.1.2 is a bugfix-only release, with the bugfixes since v0.1.1 cherry-picked so they get out faster to people using non-git packages. v0.2 will hopefully follow soon with some new features! These are the changes since v0.1.1: * Fix rare exception when a key is pressed shorly after opening a window * Fix exception with certain invalid URLs like http:foo:0 * Work around Qt bug which renders checkboxes on OS X unusable * Fix exception when a local files can't be read in :adblock-update * Hide 2 more Qt warnings. * Add !important to hint CSS so websites don't override the hint look * Make init_venv.py work with multiple sip .so files. * Fix splitting with certain commands with an empty argument (""/''). * Uncheck sending of debug log by default when private browsing is on. * Fix uppercase hints. * Fix segfaults if another page is loaded while a prompt is open (SSL, javascript, ...) * Fix exception with invalid ShellCommand config values. * Add SSL info to version info. * Replace unencodable chars (filesystem encoding) in download filenames. * Remove hosts-file.net from blocker default lists. * Fix user-stylesheet setting with an empty value. Thanks to Error 800 and Matthias Lisin for contributing bugfixes for this release! Florian -- http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From lepperta at gmail.com Tue Jan 20 12:51:34 2015 From: lepperta at gmail.com (Andreas Leppert) Date: Tue, 20 Jan 2015 12:51:34 +0100 Subject: Automatic passthrough mode for certain urls Message-ID: Hello, first of all: great browser, I love it! Some pages like gmail or feedly provide keyboard navigation. Is it possible to have a list of urls so that passthrough mode is enabled automatically for these urls? Thanks in advance! AL -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at the-compiler.org Tue Jan 20 23:56:43 2015 From: me at the-compiler.org (Florian Bruhin) Date: Tue, 20 Jan 2015 23:56:43 +0100 Subject: This week's qutebrowser updates Message-ID: <20150120225643.GN30488@tonks> Hi! Another longer update as I was sick last week. There wasn't that much happening lately, but there were some infrastructure/buildbot-related changes I'll mention at the end. There was also v0.1.2 released on the 7th, which is quite stable. Here I'll just mention the updates since v0.1.2 was released - see https://lists.schokokeks.org/pipermail/qutebrowser/2015-January/000033.html for the rest. Again: If you want bleeding-edge, stay on master. v0.1.2 is just master without the new features basically. There are still 6 pullrequests open - most of them are simple, but I plan to look at them after the WIP-change you see under infrastructure (updating pylint) is done. Sorry for the delay! I was a bit confused by the logs and branches, so I hope I didn't forget anyone! Overview -------- (for the past week, because Github doesn't let me view this for two weeks...) Excluding merges, 4 authors have pushed 17 commits to master and 27 commits to all branches. On master, 16 files have changed and there have been 201 additions and 78 deletions. 3 Pull requests proposed by 3 people 6 Issues closed by 2 people 4 Issues created by 1 person https://github.com/The-Compiler/qutebrowser/pulse/weekly Features -------- - Add possibility to display warnings in the statusbar and to deprecate commands. - Merge :run-userscripts into :spawn (with new --userscript option) and deprecate it. Improvements ------------ - Show default value in the completion. Thanks to Peter Vilim for this contribution! - Various README/documentation improvements. - Save contact address in error report dialog. Bugfixes -------- - Remove old colors->tabs.separator option which was unused. - Fix crash when the config is binary garbage (i.e. invalid unicode) Checks/Infrastructure --------------------- - Added an OS X buildbot. Big thanks to: - Christian Vogler for letting me use his Mac for this for free. - feuermurmel for helping with debugging a nasty OS X virtualenv issue. - The Chaos Computer Club Zurich hackerspace for hosting the Mac for free. - WIP: Updating pylint to a more recent version for the checks. - Make sure the right versio of the checkers run on all platforms when init_venv.py is used with run_checks.py. -- http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From me at the-compiler.org Wed Jan 21 06:46:02 2015 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 21 Jan 2015 06:46:02 +0100 Subject: qutebrowser crash reports In-Reply-To: <20150116095836.GD3081@sw-archsrv> References: <20150116053429.GI30488@tonks> <20150116093135.GB3081@sw-archsrv> <20150116163720.GL30488@tonks> <20150116095836.GD3081@sw-archsrv> Message-ID: <20150121054602.GA27871@tonks> Hi, (Cc-ing this to the list because I'd like some discussion and ideas about this. For people who have already spoken out about the confusing crash dialog issue - I hear you, I just want to hear more opinions an am unsure about what's best) * Doug Stone-Weaver [2015-01-16 01:58:36 -0800]: > Good question - do you generally follow up with ALL crash reports? I'd like to, but maybe one out of twenty has contact information. Let's say the distribution of crash reports looks roughly like this, at least right now with v0.1.2 which is quite stable. - 5% real qutebrowser problems which need to be fixed. Those are usually easy, the exception and debug log gives me all information I need. I'd still like to follow-up with people and at least tell them the github issue link, so they can subscribe. But this is like 1 report by week, and I don't expect it to increase much, unless I fsck up something. - 50% segfaults because of distributions like Debian/Ubuntu which are still on an older Qt version. I'd like to tell people it's not actually a qutebrowser problem, and they should please wait for their distribution to upgrade. - 10% segfaults which could somehow be worked around in qutebrowser, but I don't have any info, so I can't. The debug log on segfaults usually only says "qt_mainloop", so I don't know *anything*, but I'd desperatly like to fix the problem. - 35% issues in qutebrowser which are already fixed, but people didn't upgrade for months. I'd like to tell them to do. > I was expecting my second crash to just get lumped in with the first (if > I'm remembering correctly and the stacks where the same), so I didn't > think you'd need more info, hence I didn't expect the email. > > If you're planning to follow up with everyone who hits a crash and > submits a report (at least for now :))... here are some super subjective > thoughts on what might have made me expect an email. Thanks! I added them to https://github.com/The-Compiler/qutebrowser/issues/447 > 2) It might be worth flipping the order of the > boxes, so people enter their contact information first. It's possible > that this will lower the hit rate of people entering repro steps... but > I imagine it would increase the hit rate of people who give you their > contact information? Maybe some A/B testing :) - just kidding. People usually submit neither, or both. Most of the time neither. Right now, the "OK" button being a report if you don't pay attention kinda tricks them into reporting bugs even if they don't want to - but in case of exceptions those are useful as well. See the first point in the issue above - it'd stop people from accidentally reporting info they don't want to, but I'm afraid I'll also lose many useful reports if users really make a choice between reporting and not. What do you think? Florian -- http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From rikuah1n at gmail.com Wed Jan 21 09:34:53 2015 From: rikuah1n at gmail.com (Riku Ahonen) Date: Wed, 21 Jan 2015 10:34:53 +0200 Subject: qutebrowser crash reports In-Reply-To: <20150121054602.GA27871@tonks> References: <20150116053429.GI30488@tonks> <20150116093135.GB3081@sw-archsrv> <20150116163720.GL30488@tonks> <20150116095836.GD3081@sw-archsrv> <20150121054602.GA27871@tonks> Message-ID: <54BF64AD.2030605@gmail.com> 21.01.2015, 07:46, Florian Bruhin wrote: > Hi, > > (Cc-ing this to the list because I'd like some discussion and ideas > about this. For people who have already spoken out about the confusing > crash dialog issue - I hear you, I just want to hear more opinions > an am unsure about what's best) I think your ideas on bug tracker look good. I have some thoughts which might be useful: "Auto-reject crashes if the stack points to qt_mainloop and Qt version is < Qt 5.4" - I don't know if would be implemented in report dialog or in the paste part, but informing the user about this in the crash dialog would help them. Something like "you seem to have Qt version x.x which is know to cause crashes. Updating to latest Qt might fix this problem." Another thing would be to write a document which describes most common types of crashes and what a user can do about them. Maybe something like you wrote in the cc'd email. And link to this document in crash dialog. When I first sent a crash report with my email address I was a bit surprised it ended up on public web page. I think it would be nice to keep contact information private or tell the user about this in the crash dialog. Riku "rikn00" From me at the-compiler.org Wed Jan 21 09:56:46 2015 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 21 Jan 2015 09:56:46 +0100 Subject: qutebrowser crash reports In-Reply-To: <54BF64AD.2030605@gmail.com> References: <20150116053429.GI30488@tonks> <20150116093135.GB3081@sw-archsrv> <20150116163720.GL30488@tonks> <20150116095836.GD3081@sw-archsrv> <20150121054602.GA27871@tonks> <54BF64AD.2030605@gmail.com> Message-ID: <20150121085646.GQ30488@tonks> * Riku Ahonen [2015-01-21 10:34:53 +0200]: > > 21.01.2015, 07:46, Florian Bruhin wrote: > >Hi, > > > >(Cc-ing this to the list because I'd like some discussion and ideas > >about this. For people who have already spoken out about the confusing > >crash dialog issue - I hear you, I just want to hear more opinions > >an am unsure about what's best) > I think your ideas on bug tracker look good. I have some thoughts which > might be useful: > > "Auto-reject crashes if the stack points to qt_mainloop and Qt version is < > Qt 5.4" > > - I don't know if would be implemented in report dialog or in the paste > part, but informing the user about this in the crash dialog would help them. > Something like "you seem to have Qt version x.x which is know to cause > crashes. Updating to latest Qt might fix this problem." Since "crash is in mainloop AND Qt is out-of-date" is a really good indicator for an useless crash report, I plan to not display the crash report dialog at all. More something like "qutebrowser was restarted after a fatal crash caused by the Qt library. Your distribution is using an outdated version of Qt. Unfortunately, the only way to fix it is to wait until they have updated." or so, without the ability to report. > Another thing would be to write a document which describes most common types > of crashes and what a user can do about them. Maybe something like you wrote > in the cc'd email. And link to this document in crash dialog. Hm, I like that idea. I wonder how many people will read that though, given the big count of reports with *no info at all* at the moment. I guess a surprising crash just isn't the right time for reading a document about how to report crashes. :-/ But it'd probably be useful in general to link people to - I opened a separate issue: https://github.com/The-Compiler/qutebrowser/issues/480 > When I first sent a crash report with my email address I was a bit surprised > it ended up on public web page. I think it would be nice to keep contact > information private or tell the user about this in the crash dialog. Huh, I think the crash dialog mentioned the reports being public. Maybe I'm wrong, or this got lost in the first redesign I did. There are basically two reasons they are public: - I already had the pastebin set up, and didn't think there would be so many reports at the time I set it up, so I just used that. - Sometimes I just dump the URL into an issue without much more information. If someone wants to help fixing the bug, it'd make sense for them to be able to see the report. Or in general, it'd be confusing if reports linked in public issues needed an account :-/ But yeah - given the amount of "real" issues is going down (and hopefully will stay down when more tests are running), maybe I should spend more time opening issues with any *relevant* information from the full report, and making it private. I also opened an issue: https://github.com/The-Compiler/qutebrowser/issues/481 I probably have to set up a separate pastebin for qutebrowser reports. I guess that'd make sense anyways. Florian -- http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From rikuah1n at gmail.com Wed Jan 21 22:03:52 2015 From: rikuah1n at gmail.com (Riku Ahonen) Date: Wed, 21 Jan 2015 23:03:52 +0200 Subject: qutebrowser crash reports In-Reply-To: <20150121085646.GQ30488@tonks> References: <20150116053429.GI30488@tonks> <20150116093135.GB3081@sw-archsrv> <20150116163720.GL30488@tonks> <20150116095836.GD3081@sw-archsrv> <20150121054602.GA27871@tonks> <54BF64AD.2030605@gmail.com> <20150121085646.GQ30488@tonks> Message-ID: <54C01438.9060505@gmail.com> 21.01.2015, 10:56, Florian Bruhin wrote: > > When I first sent a crash report with my email address I was a bit surprised > it ended up on public web page. I think it would be nice to keep contact > information private or tell the user about this in the crash dialog. > Huh, I think the crash dialog mentioned the reports being public. > Maybe I'm wrong, or this got lost in the first redesign I did. > > There are basically two reasons they are public: > > - I already had the pastebin set up, and didn't think there would be > so many reports at the time I set it up, so I just used that. > > - Sometimes I just dump the URL into an issue without much more > information. If someone wants to help fixing the bug, it'd make > sense for them to be able to see the report. Or in general, it'd be > confusing if reports linked in public issues needed an account :-/ > > But yeah - given the amount of "real" issues is going down (and > hopefully will stay down when more tests are running), maybe I should > spend more time opening issues with any *relevant* information from > the full report, and making it private. > > I also opened an issue: > > https://github.com/The-Compiler/qutebrowser/issues/481 > > I probably have to set up a separate pastebin for qutebrowser reports. > I guess that'd make sense anyways. > > Florian > Maybe crash dialog could send the actual crash log into a public pastebin and possible contact information somewhere else? I don't know if I was unclear in my earlier message but I don't oppose public crash logs. I just think email addresses and such would better be kept private. Riku From me at the-compiler.org Wed Jan 21 23:22:49 2015 From: me at the-compiler.org (Florian Bruhin) Date: Wed, 21 Jan 2015 23:22:49 +0100 Subject: qutebrowser crash reports In-Reply-To: <54C01438.9060505@gmail.com> References: <20150116053429.GI30488@tonks> <20150116093135.GB3081@sw-archsrv> <20150116163720.GL30488@tonks> <20150116095836.GD3081@sw-archsrv> <20150121054602.GA27871@tonks> <54BF64AD.2030605@gmail.com> <20150121085646.GQ30488@tonks> <54C01438.9060505@gmail.com> Message-ID: <20150121222249.GA30488@tonks> * Riku Ahonen [2015-01-21 23:03:52 +0200]: > > 21.01.2015, 10:56, Florian Bruhin wrote: > > > >When I first sent a crash report with my email address I was a bit surprised > >it ended up on public web page. I think it would be nice to keep contact > >information private or tell the user about this in the crash dialog. > >Huh, I think the crash dialog mentioned the reports being public. > >Maybe I'm wrong, or this got lost in the first redesign I did. > > > >There are basically two reasons they are public: > > > >- I already had the pastebin set up, and didn't think there would be > > so many reports at the time I set it up, so I just used that. > > > >- Sometimes I just dump the URL into an issue without much more > > information. If someone wants to help fixing the bug, it'd make > > sense for them to be able to see the report. Or in general, it'd be > > confusing if reports linked in public issues needed an account :-/ > > > >But yeah - given the amount of "real" issues is going down (and > >hopefully will stay down when more tests are running), maybe I should > >spend more time opening issues with any *relevant* information from > >the full report, and making it private. > > > >I also opened an issue: > > > >https://github.com/The-Compiler/qutebrowser/issues/481 > > > >I probably have to set up a separate pastebin for qutebrowser reports. > >I guess that'd make sense anyways. > > > >Florian > > > Maybe crash dialog could send the actual crash log into a public pastebin > and possible contact information somewhere else? I don't know if I was > unclear in my earlier message but I don't oppose public crash logs. I just > think email addresses and such would better be kept private. Too hard to implement. Right now I just can use a pastebin. I don't want to implement my own server-side thing, I prefer to work on qutebrowser. And debug logs could have enough sensitive information for them to be private. Florian -- http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From me at the-compiler.org Thu Jan 22 07:03:24 2015 From: me at the-compiler.org (Florian Bruhin) Date: Thu, 22 Jan 2015 07:03:24 +0100 Subject: [PATCH] Fix some check_libraries() for arch In-Reply-To: <20150110022715.GA22319@ghul.anu.edu.au> References: <20150110022715.GA22319@ghul.anu.edu.au> Message-ID: <20150122060324.GC30488@tonks> * Thorsten Wi?mann [2015-01-10 13:27:15 +1100]: > By now, the python-jinja and python-pygments packages are available in > community. > > The attached patch 0001-Fix-some-check_libraries-for-arch.patch contains > the commit, you can apply it with > > git am 0001-Fix-some-check_libraries-for-arch.patch Sorry for the delay, I was quite busy over the past few days :) Merged now: https://github.com/The-Compiler/qutebrowser/compare/5a0a0302df2a...011e398f77f3 I haven't checked, but my guess would be they always were in [community] and I just failed with copy-paste. Thanks! Florian -- http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From me at the-compiler.org Mon Jan 26 22:27:01 2015 From: me at the-compiler.org (Florian Bruhin) Date: Mon, 26 Jan 2015 22:27:01 +0100 Subject: This week's qutebrowser updates Message-ID: <20150126212701.GL11132@tonks> Hi! Back to normal weekly updates hopefully! Some interesting changes and some more infrastructure-related stuff this week. Overview -------- Excluding merges, 4 authors have pushed 77 commits to master and 77 commits to all branches. On master, 32 files have changed and there have been 667 additions and 277 deletions. 3 Pull requests merged by 3 people 11 Issues closed by 1 person 11 Issues created by 1 person https://github.com/The-Compiler/qutebrowser/pulse/weekly Features -------- - Add ability to toggle a value to :set. Thanks to ZDarian for this contribution! - Add new option tabs -> hide-always to hide the tabbar. Thanks to ZDarian for this contribution! - Add new option ui -> hide-statusbar to hide the statusbar. Improvements ------------ - Various crash dialog UI improvements. - Use python3 venv instead of virtualenv for init_venv.py. Thanks to Patric Schmitz for this contribution! - Display error instead of crash dialog if there's a segfault with an old Qt version. - Clone tab icon and text when cloning tabs. - Clone zoom level when cloning tabs. - Show loading percentage in window title. - Add Voidlinux package and install instructions. Thanks to Eivind Uggedal for this contribution! - Fix package output for Arch when checking for dependencies. Thanks to Thorsten Wi?mann for this contribution! Bugfixes -------- - Add quotes to empty default values in completion. Thanks to Peter Vilim for this contribution! - Fix :spawn --userscript with multiple args. - Re-enable qutebrowser.misc tests which accidentally were disabled. - Fix retrying of downloads after the tab in which they were started in is closed. Checks/Infrastructure --------------------- - Updated pylint to a more recent version for the checks. - Added a --print-version argument to run_checks.py. - Run virtualenv library versions in run_checks.py. - Cache virtualenvs between tests. - Various other small improvements in init_venv.py and run_checks.py. -- http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From MAILER-DAEMON at ibw.com Fri Jan 30 15:42:29 2015 From: MAILER-DAEMON at ibw.com (Mail Delivery System) Date: Fri, 30 Jan 2015 09:42:29 -0500 (EST) Subject: Delayed Mail (still being retried) Message-ID: <19740413061513.235C028003FB43C7@xcs3.ibw.com> This is an automated message from the XCS at host xcs3.ibw.com. #################################################################### # THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE. # #################################################################### Your message could not be delivered for 4.0 hours. It will be retried until it is 5.0 days old. For further assistance, please send mail to . Reason: : connect to 190.5.159.197[190.5.159.197]:25: Operation timed out -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/rfc822-headers Size: 688 bytes Desc: Undelivered Message Headers URL: