Re: Gmane vs. Mail Archive notmuch-report config

On Thu, Feb 15, 2018 at 03:02:58PM -0500, Daniel Kahn Gillmor wrote: > On Thu 2018-02-15 10:56:29 -0800, W. Trevor King wrote: > > On Thu, Feb 15, 2018 at 11:01:40AM -0500, Daniel Kahn Gillmor wrote: > >> - "message-url": "http://mid.gmane.org/{message-id};

Gmane vs. Mail Archive notmuch-report config (was: [PATCH] move more http -> https)

On Thu, Feb 15, 2018 at 11:01:40AM -0500, Daniel Kahn Gillmor wrote: > - "message-url": "http://mid.gmane.org/{message-id}; > + "message-url": "https://mid.gmane.org/{message-id}; I was wondering whether it made sense to change these to something else with Gmane down. But it appears

Re: [PATCH] nmbug: explicitly prefer python3

On Thu, Feb 15, 2018 at 07:37:53AM +0200, Tomi Ollila wrote: > In this case I value Trevor as valid notmuch maintainer as anyone > else who has done significant work for nmbug. Thanks, but I don't think that should impact the decision for this patch. I'm just sharing my take, but the eventual

Re: [PATCH] nmbug: explicitly prefer python3

On Sun, Feb 11, 2018 at 10:56:36PM -0500, Daniel Kahn Gillmor wrote: > On Fri 2018-02-09 12:46:24 -0800, W. Trevor King wrote: > > From later on in PEP 394 [1]: > > > > It is anticipated that there will eventually come a time where > > the third party eco

Re: [PATCH] nmbug: explicitly prefer python3

On Fri, Feb 09, 2018 at 01:36:48PM -0500, Daniel Kahn Gillmor wrote: > > Is there something using python3 gets you for nmbug that you miss > > with python2? > > Yep, i get to remove python 2 from my operating system :) > > Smaller installed codebase, fewer bugs. There are only two > outstanding

Re: [PATCH] nmbug: explicitly prefer python3

On Thu, Feb 08, 2018 at 11:32:11PM -0500, Daniel Kahn Gillmor wrote: > nmbug and notmuch-report are developer tools. It's 2018, and all > developers should have python3 available. From PEP 394 [1]: One exception to this is scripts that are deliberately written to be source compatible with

[PATCH 1/2] nmbug: Bump to version 0.3

Changes since 0.2: * Accept failures to unset core.worktree in clone (0a155847, 2017-10-10, unreleased). * Use --no-renames in log (f9189a06, 2016-09-26, v0.24). * Auto-checkout in clone if it wouldn't clobber (7ef3b653, 2017-10-10, unreleased). * Add a 'help' command for folks who don't like

[PATCH 2/2] NEWS: Add nmbug 0.3 release notes to the notmuch 0.26 section

--- NEWS | 13 + 1 file changed, 13 insertions(+) diff --git a/NEWS b/NEWS index 6d2bf138..3b6404e7 100644 --- a/NEWS +++ b/NEWS @@ -41,6 +41,19 @@ Indexing cleartext of encrypted e-mails that the notmuch index itself is adequately protected. DO NOT USE this feature without

[PATCH 0/2] nmbug: Bump to 0.3 and document in NEWS

if it wouldn't clobber Date: Mon, 11 Dec 2017 16:51:38 -0400 W. Trevor King (2): nmbug: Bump to version 0.3 NEWS: Add nmbug 0.3 release notes to the notmuch 0.26 section NEWS | 13 + devel/nmbug/nmbug | 2 +- 2 files changed, 14 insertions(+), 1 deletion

Re: [PATCH 3/4] nmbug: Auto-checkout in clone if it wouldn't clobber

On Mon, Dec 11, 2017 at 09:10:47AM -0400, David Bremner wrote: > Not sure what happened to patch 4/4? Ah sorry. My local branch has a commit to bump nmbug's internal version to 0.3 (see my comments in [1]), but I ended up deciding to punt that until before the next notmuch release (in case other

Re: web interface to notmuch

I haven't looked at the backing code in a while, but I really like the public-inbox [1] approach to archival. Since Gmane died, Git (and a few other projects [2]) have also been using the author's hosted version. I haven't looked at the backing code in a while, but it's live Perl, not a static

Re: nmbug backtrace due to .mailmap

On Mon, Oct 16, 2017 at 02:08:17PM -0700, W. Trevor King wrote: > So I've pushed bce5a55c removing .mailmap, and folks without [1] > should be back in business. > … > [1]: > id:4487e001b350aa8e343a1201d869cceca2a03ab6.1508176853.git.wk...@tremily.us But Jani reports still being s

Re: nmbug backtrace due to .mailmap

On Mon, Oct 16, 2017 at 05:37:32PM -0300, David Bremner wrote: > W. Trevor King writes: > > On Mon, Oct 16, 2017 at 10:14:40PM +0300, Jani Nikula wrote: > >> I also didn't see any discussion about adding a .mailmap prior to it > >> being pushed. > > > &g

Re: nmbug backtrace due to .mailmap

On Mon, Oct 16, 2017 at 12:21:15PM -0700, W. Trevor King wrote: > Until then, you can work around the current master by applying this > patch locally. I'd thought this thread was in response to my patch, but it turns out my local nullmailer was off when I sent the patch. Se

[PATCH] nmbug: Only error for invalid diff lines in tags/

Avoid: Traceback (most recent call last): File "/home/nmbug/bin/nmbug", line 834, in args.func(**kwargs) File "/home/nmbug/bin/nmbug", line 385, in checkout status = get_status() File "/home/nmbug/bin/nmbug", line 580, in get_status maybe_deleted =

Re: nmbug backtrace due to .mailmap

On Mon, Oct 16, 2017 at 10:14:40PM +0300, Jani Nikula wrote: > Presumably because of the .mailmap added in nmbug repository: Yup. > I also didn't see any discussion about adding a .mailmap prior to it > being pushed. Sorry :/. I didn't realize it would be an issue until I pushed it. I can't

[PATCH 0/3] nmbug: clone core.worktree and auto-checkout (was: [PATCH 0/3] nmbug:)

On Sat, Oct 14, 2017 at 03:51:08PM +0300, Jani Nikula wrote: > Could we add a "nmbug required version" metadata to the repository… I'm not sure what you mean. The wiki page will mention the minimum nmbug version with which the wiki instructions are compatible (as it already does, [1]). But

Public notmuch.mbox missing some messages which are tagged in nmbug

I was dusting off my local nmbug repository today, and noticed that some messages are tagged in the nmbug repository [1] but missing from our mbox archive [2]. Here's a list: $ nmbug status U 20170509021719.13086-2-da...@tethera.netobsolete U

[PATCH 1/4] nmbug: Respect 'expect' in _spawn(..., wait=True)

Fixing a bug from 7f2cb3be (nmbug: Translate to Python, 2014-10-03). The bug had no direct impact though, because none of the wait=True callers were setting expect. Also add expected codes to the debug messages, to help log readers understand why nonzero exits are occasionally accepted. ---

[PATCH 3/4] nmbug: Auto-checkout in clone if it wouldn't clobber

We currently auto-checkout after pull and merge to make those more convenient. They're guarded against data-loss with a leading _insist_committed(). This commit adds the same convenience to clone, since in most cases users will have no NMBPREFIX-prefixed tags in their database when they clone.

[PATCH 2/4] nmbug: Accept failures to unset core.worktree in clone

Since 6311cfaf (init: do not set unnecessary core.worktree, 2016-09-25, 2.11.0 [1]), Git has no longer set core.worktree when --separate-git-dir is used. This broke clone with: $ nmbug clone http://nmbug.notmuchmail.org/git/nmbug-tags.git Cloning into '/tmp/nmbug-clone.33gg442e'...

[PATCH 0/3] nmbug:

is just before we cut our next notmuch release. Once we do, we can update the wiki page [1] to suggest nmbug 0.3+ and remove the checkout step from “Getting started”. Cheers, Trevor [1]: https://notmuchmail.org/nmbug/ W. Trevor King (3): nmbug: Respect 'expect' in _spawn(..., wait=True) nmbug

Re: [PATCH] nmbug: allow excluded messages

On Sat, Oct 22, 2016 at 08:59:40AM +0100, Mark Walters wrote: > This makes nmbug work even if the notmuch mailing list messages are > excluded (i.e., have a tag in the excluded tags list). > … > (I think this is the only place it is needed, but I don't use nmbug > much so I haven't tested

[PATCH] nmbug: Add --no-renames to default log options

Git has supported this since b68ea12e (diff.c: respect diff.renames config option, 2006-07-07, v1.4.2). All of our information is in the paths (the files are empty), so we don't want rename detection. By using --no-renames, we get entries like: $ nmbug log -- e473b453a2 commit

Re: Mail archives in Git using ssoma

On Sun, Aug 21, 2016 at 06:37:04PM +, Eric Wong wrote: > "W. Trevor King" <wk...@tremily.us> wrote: > > On Fri, Nov 07, 2014 at 11:03:21AM -0800, W. Trevor King wrote: > > > Eric Wong has been working on some tools to store email in a Git > > > repos

Re: Mail archives in Git using ssoma (Docker image)

On Sun, Aug 21, 2016 at 12:08:52PM +, Eric Wong wrote: > "W. Trevor King" <wk...@tremily.us> wrote: > > This is the ssoma archive (with the data in it). I just set up a > > basic HTTP archive (following [1]) based on a Docker image [2] (Gentoo > > does

Re: Mail archives in Git using ssoma (Docker image)

On Sat, Aug 20, 2016 at 09:36:31PM -0700, W. Trevor King wrote: > [2]: git://tremily.us/notmuch-archives.git This is the ssoma archive (with the data in it). I just set up a basic HTTP archive (following [1]) based on a Docker image [2] (Gentoo doesn't package all the Perl dependencies pub

Re: [feature request] emacs: use `notmuch insert` for FCC

On Sat, Aug 20, 2016 at 02:14:38AM -0400, Steven Allen wrote: > Tomi Ollila writes: > > PS: do we have an alternative to mid.gmane.org for > > http://nmbug.tethera.net/status/ > > https://notmuchmail.org/pipermail/notmuch/? However, it's not > indexed by id. The Git folks

Re: syncing tags across machines

On Sat, Jul 09, 2016 at 07:54:05AM +0100, Stephen Eglen wrote: > is there any robust solution yet to sharing/syncing tags across > machines. (e.g. a desktop and a laptop). nmbug [1] is another way to version and share tags. Set NMBPREFIX to the empty string if you want to version all your tags

Re: [PATCH] nmbug: ignore # comments

On Sun, Mar 27, 2016 at 05:25:11PM -0300, David Bremner wrote: > for line in notmuch.stdout: > +if line.strip().startswith('#'): > +continue Looks good to me. Cheers, Trevor -- This email may be signed or encrypted with GnuPG

[PATCH] NEWS: Consolidate nmbug-status and notmuch-report sections

These are the same tool; the nmbug-status text just landed before the name change. We can also drop the message-url details from NEWS, since they're already in the man page. --- The integration fixes requested in [1]. Cheers, Trevor [1]: id:87r3f0jgg1.fsf@zancas.localnet

Re: [PATCH v2 2/4] nmbug-status: Add meta.message-url config setting

On Wed, Mar 23, 2016 at 08:19:34AM -0300, David Bremner wrote: > W. Trevor King writes: > > from __future__ import print_function > > @@ -232,6 +232,10 @@ class Page (object): > > class HtmlPage (Page): > > _slug_regexp = re.compile('\W+') >

Re: encoding of message-ids

On Wed, Feb 17, 2016 at 09:34:29AM -0400, David Bremner wrote: > Daniel Kahn Gillmor writes: > > That said, RFC 2047 suggest that its encodings are only relevant > > in places where a "text" token would be used. Message-ID (and > > References and In-Reply-To) are intended to only contain > >

[PATCH] nmbug: Allow Unicode tags and IDs in Python 2

W. Trevor King <wk...@tremily.us> # # This program is free software: you can redistribute it and/or modify @@ -95,7 +95,7 @@ except AttributeError: # Python < 3.2 _tempfile.TemporaryDirectory = _TemporaryDirectory -def _hex_quote(string, safe='+@=:,'): +def _h

Re: problems with nmbug and empty prefix (UnicodeWarning and broken pipe)

On Sun, Feb 14, 2016 at 08:22:24AM -0400, David Bremner wrote: > W. Trevor King writes: > > for tag in tags: > > _LOG.debug('building a quoted path for {!r} / {!r}'.format(id, tag)) > > path = 'tags/{id}/{tag}'.format( > > id=_hex_quote(string=id)

Re: problems with nmbug and empty prefix (UnicodeWarning and broken pipe)

On Sat, Feb 13, 2016 at 10:41:40PM -0400, David Bremner wrote: > Traceback (most recent call last): > File "/home/bremner/.config/scripts/nmbug.real", line 834, in > args.func(**kwargs) > File "/home/bremner/.config/scripts/nmbug.real", line 324, in commit > status = get_status() >

Re: [PATCH] test/README: have matching test script file names

On Fri, Feb 12, 2016 at 09:17:00PM +0200, Tomi Ollila wrote: > +The test system itself requires: > + > + - bash(1) version 4.0 or newer > + > +Without bash 4.0+ the tests just refuse to run. This was surprising to me (obviously I haven't looked at the test library closely ;), because Git tries

Re: nmbug in the Debian packages?

On Mon, Feb 08, 2016 at 07:33:10AM -0400, David Bremner wrote: > We can include it in /usr/bin along and install a proper man page… I'm happy to write up a man page. Do you want it in a separate directory from nmbug-status / notmuch-report [1]? Do you want to rename nmbug to something notmuch-*

Re: Binding access to ~/.notmuch-config

On Wed, Jan 13, 2016 at 08:25:10AM -0400, David Bremner wrote: > Konrad Hinsen writes: > > I agree. I see notmuch as a collection of CLI tools, some of which > > are part of the distribution and others are written by myself for > > my specific needs. I'd like them all to share a single > >

Re: Crash with Python bindings

On Tue, Jan 12, 2016 at 03:23:46PM +0100, Konrad Hinsen wrote: > Hi Justus, > > > So I guess what happens is that Python3 changed how the > > interpreter environment is torn down and they actually destroy the > > 'q' object. If that is so, then your data is indeed safe. > > That reminds me of a

Re: Crash with Python bindings

On Tue, Jan 12, 2016 at 10:41:57AM +0100, Konrad Hinsen wrote: > -- > from notmuch import Query, Database > > def foo(bar): > pass > > db = Database() > q = Query(db, "*") > db.close() > -- > >

Binding access to ~/.notmuch-config (was: Crash with Python bindings)

On Tue, Jan 12, 2016 at 03:03:15PM -0400, David Bremner wrote: > Nothing to do with Konrad's crash, but I consider the fact that the > python bindings read ~/.notmuch-config to be a kind of layering > violation, since that file belongs to the CLI, while the bindings > are supposed to provide

[PATCH] nmbug-status: Style headers with smaller fonts

http://article.gmane.org/gmane.mail.notmuch.general/21595 [2]: http://www.w3.org/TR/html-markup/h2.html [3]: http://www.w3.org/TR/html-markup/h3.html [4]: http://www.w3.org/TR/html-markup/h4.html --- On Thu, Jan 07, 2016 at 09:20:59AM -0400, David Bremner wrote: > W. Trevor King writes: > &g

[PATCH 1/5] nmbug-status: Avoid hard-coded filename in error message

We already have a 'filename' variable with the name, so stay DRY and use that variable here. Also fix a missing-whitespace error from bed8b674 (nmbug-status: Clarify errors for illegible configs, 2014-05-10), wrapping on the sentence to match similar error-generation earlier in this function. ---

[PATCH 4/5] notmuch-report: Add notmuch-report(1) and notmuch-report.json(5) man pages

To describe the script and config file format, so folks don't have to dig through NEWS or the script's source to get that information. The Makefile and conf.py are excerpted from the main doc/ directory with minor simplifications and adjustments. The devel/nmbug/ scripts are largely independent

[PATCH 2/5] notmuch-report: Rename from nmbug-status

This script generates reports based on notmuch queries, and doesn't really have anything to do with nmbug, except for sharing the NMBGIT environment variable. --- devel/nmbug/nmbug-status | 419 - devel/nmbug/notmuch-report | 419

[PATCH v2 3/4] nmbug-status: Wrap query phrases in parentheses when and-ing together

For example: "query": ["tag:a", "tag:b or tag:c"] is now converted to: ( tag:a ) and ( tag:b or tag:c ) instead of the old: tag:a and tag:b or tag:c This helps us avoid confusion due to Xapian's higher-precedence AND [1], where the old query would be interpreted as: ( tag:a and

[PATCH 5/5] NEWS: Document the notmuch-report branch

--- NEWS | 26 ++ 1 file changed, 26 insertions(+) diff --git a/NEWS b/NEWS index 6681699..3535614 100644 --- a/NEWS +++ b/NEWS @@ -1,3 +1,29 @@ +Notmuch 0.22 (UNRELEASED) += + +Documentation +- + +New `notmuch-report(1)` and

[PATCH v2 2/4] nmbug-status: Add meta.message-url config setting

So you can link to archives other than Gmane. For example, I'm doing this in [1]. [1]: https://github.com/wking/nmbug-oci --- NEWS | 20 devel/nmbug/nmbug-status | 13 ++--- 2 files changed, 30 insertions(+), 3 deletions(-) diff --git a/NEWS

[PATCH v2 4/4] status-config.json: Remove parens from query entry

These are now added by nmbug-status. --- devel/nmbug/status-config.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devel/nmbug/status-config.json b/devel/nmbug/status-config.json index b926946..48b6f19 100644 --- a/devel/nmbug/status-config.json +++

[PATCH 3/5] notmuch-report.json: Rename from status-config.json

status-config.json wasn't obviously associated with the old nmubg-status, now notmuch-report. The new name is ${CONFIGURED_SCRIPT}.json, so the association should be clear. --- devel/nmbug/notmuch-report | 2 +- devel/nmbug/notmuch-report.json | 70 +

[PATCH 0/5] notmuch-report: Rename from nmbug-status and add man pages

-report.json, I can add that in a v2. Cheers, Trevor [1]: id:m2twmxbl1i@guru.guru-group.fi http://thread.gmane.org/gmane.mail.notmuch.general/21535/focus=21539 W. Trevor King (5): nmbug-status: Avoid hard-coded filename in error message notmuch-report: Rename from nmbug-status notmuch

[PATCH v2 0/4] nmbug-status: meta.message-url and query parens

://thread.gmane.org/gmane.mail.notmuch.general/21523 http://thread.gmane.org/gmane.mail.notmuch.general/21535 [2]: id:20151231164719.ga20...@odin.tremily.us http://thread.gmane.org/gmane.mail.notmuch.general/21523/focus=21534 W. Trevor King (4): NEWS: Remove trailing comma from an old

[PATCH v2 1/4] NEWS: Remove trailing comma from an old nmbug-status config

That closing brace is the end of the config JSON; there won't be anything coming after it. --- NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 6681699..0a7a0e0 100644 --- a/NEWS +++ b/NEWS @@ -409,7 +409,7 @@ from the config file. Use something like:

Re: [PATCH 3/5] nmbug-status: Add an nmbug-status(5) man page

On Fri, Jan 01, 2016 at 01:23:37PM +0200, Tomi Ollila wrote: > What we could simply have at the time being: > > devel/nmbug/nmbug > devel/nmbug/nmbug.rst (or .1) > devel/nmbug/nmbug-status > devel/nmbug/nmbug-status.rst (or .1) > devel/nmbug/nmbug-status-config >

Re: [PATCH 4/5] nmbug-status: Wrap query phrases in parentheses when and-ing together

On Wed, Dec 30, 2015 at 11:16:59AM -0800, W. Trevor King wrote: > @@ -167,7 +167,8 @@ class Page (object): > view['title'], sort_key)) > if 'query-string' not in view: > query = view['query'] > -view['query-string'] = ' a

Re: [PATCH 0/2] nmbug-status: h1 title and unbalanced fixups to default templates

On Thu, Dec 31, 2015 at 03:46:50PM +0200, Tomi Ollila wrote: > This series LGTM. (html) tidy complains about imo irrelevant things > -- or I just did not know how to use it correctly -- as `| tidy > -eq`. That doesn't complain about anything with the current tidy 5.1.25 [1] with output built by

Re: [PATCH 3/5] nmbug-status: Add an nmbug-status(5) man page

On Thu, Dec 31, 2015 at 06:11:34PM -0400, David Bremner wrote: > W. Trevor King writes: > > On Thu, Dec 31, 2015 at 01:39:21PM -0400, David Bremner wrote: > >> For me it's a bit odd to have a man page for a tool we don't > >> install by default. Is it maybe tim

Re: [PATCH 3/5] nmbug-status: Add an nmbug-status(5) man page

On Thu, Dec 31, 2015 at 01:39:21PM -0400, David Bremner wrote: > Jani Nikula writes: > > I am wondering about the man page though. I find it slightly > > confusing there would be a man page named after the tool > > describing just the config, but not the tool itself. Yeah, a man page about the

[PATCH 4/5] nmbug-status: Wrap query phrases in parentheses when and-ing together

For example: "query": ["tag:a", "tag:b or tag:c"] is now converted to: ( tag:a ) and ( tag:b or tag:c ) instead of the old: tag:a and tag:b or tag:c This helps us avoid confusion due to Xapian's higher-precedence AND [1], where the old query would be interpreted as: ( tag:a and

[PATCH 5/5] status-config.json: Remove parens from query entry

These are now added by nmbug-status. --- devel/nmbug/status-config.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devel/nmbug/status-config.json b/devel/nmbug/status-config.json index b926946..48b6f19 100644 --- a/devel/nmbug/status-config.json +++

[PATCH 3/5] nmbug-status: Add an nmbug-status(5) man page

To describe the config file format, so folks don't have to dig through NEWS or the nmbug-status source to get that information. --- NEWS | 5 ++ devel/nmbug/nmbug-status | 19 --- doc/conf.py | 6 ++ doc/index.rst | 1 +

[PATCH 2/5] nmbug-status: Add meta.message-url config setting

So you can link to archives other than Gmane. For example, I'm doing this in [1]. [1]: https://github.com/wking/nmbug-oci --- NEWS | 20 devel/nmbug/nmbug-status | 13 ++--- 2 files changed, 30 insertions(+), 3 deletions(-) diff --git a/NEWS

[PATCH 1/5] NEWS: Remove trailing comma from an old nmbug-status config

That closing brace is the end of the config JSON; there won't be anything coming after it. --- NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 6681699..0a7a0e0 100644 --- a/NEWS +++ b/NEWS @@ -409,7 +409,7 @@ from the config file. Use something like:

[PATCH 0/5] nmbug-status: meta.message-url, man page, and query parens

out of this series as each patch passes review. The only strict dependency is that the man page has to land after the meta.message-url patch, because it documents that field. Cheers, Trevor [1]: https://github.com/wking/nmbug-oci W. Trevor King (5): NEWS: Remove trailing comma from an old nmbug

[PATCH 1/2] nmbug-status: Adjust headers to start with h1

We've been leading off with h2s since 3e5fb88f (contrib/nmbug: add nmbug-status script, 2012-07-07), but the semantically-correct headers are: {title} ... Views ... View 1 ... View 2 ... We can always add additional CSS if the default h1 formatting is too intense. ---

[PATCH 2/2] nmbug-status: Fix unbalanced tags in default header/footer

These were broken by b70386a4 (Move the generated date from the top of the page to the footer, 2014-05-31), which moved 'Generated ...' to the footer with the opening tag, but didn't replace the blurb opening tag or add a closing tag after 'Generated ...'. --- devel/nmbug/nmbug-status | 3 ++- 1

[PATCH 0/2] nmbug-status: h1 title and unbalanced fixups to default templates

Polishing the templates a bit. Details in the individual patches. Cheers, Trevor W. Trevor King (2): nmbug-status: Adjust headers to start with h1 nmbug-status: Fix unbalanced tags in default header/footer devel/nmbug/nmbug-status | 7 --- 1 file changed, 4 insertions(+), 3 deletions

Re: [PATCH] nmbug-status: print config errors to stderr

On Sat, Oct 03, 2015 at 12:08:05PM +0300, Tomi Ollila wrote: > On Sat, Oct 03 2015, Jani Nikula wrote: > > Particularly scripted usage with stdout redirection can be > > confusing if errors are printed to stdout instead of stderr. > > LGTM Me too. Cheers, Trevor -- This email may be signed or

[PATCH] nmbug-status: add support for specifying sort order for each view

On Fri, Apr 03 2015, Jani Nikula wrote: > Let each view have "sort" key with possible values "oldest-first", > "newest-first", and "unsorted", and sort the results > accordingly. Oldest first remains the default. I like it, but have a few suggestions to tweak the implementation. > def

Re: [PATCH] nmbug-status: add support for specifying sort order for each view

On Fri, Apr 03 2015, Jani Nikula j...@nikula.org wrote: Let each view have sort key with possible values oldest-first, newest-first, and unsorted, and sort the results accordingly. Oldest first remains the default. I like it, but have a few suggestions to tweak the implementation. def

UnicodeDecodeError with python API

On Sun, Mar 29, 2015 at 07:10:53PM -0400, Sebastian Fischmeister wrote: > > My first guess is that the file's encoding doesn't match your > > locale. Do you have a non-ASCII locale set? You can check with: > > It seems to be more tricky than I thought. I didn't have a locale set. > > When I

UnicodeDecodeError with python API

On Sun, Mar 29, 2015 at 09:08:28AM -0400, Sebastian Fischmeister wrote: > Traceback (most recent call last): > File "./test.py", line 66, in > print(type(y.get_part(1))) > ? > File "/usr/lib/python3.4/email/parser.py", line 54, in parse > data = fp.read(8192) > File

Re: UnicodeDecodeError with python API

On Sun, Mar 29, 2015 at 07:10:53PM -0400, Sebastian Fischmeister wrote: My first guess is that the file's encoding doesn't match your locale. Do you have a non-ASCII locale set? You can check with: It seems to be more tricky than I thought. I didn't have a locale set. When I set one, I

Re: UnicodeDecodeError with python API

On Sun, Mar 29, 2015 at 09:08:28AM -0400, Sebastian Fischmeister wrote: Traceback (most recent call last): File ./test.py, line 66, in module print(type(y.get_part(1))) … File /usr/lib/python3.4/email/parser.py, line 54, in parse data = fp.read(8192) File

[PATCH] NEWS: fix 'not' -> 'now' typo in 0.19 nmbug section

--- NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 70ad3f3..8a1b310 100644 --- a/NEWS +++ b/NEWS @@ -167,7 +167,7 @@ nmbug The Perl script has been translated to Python; you'll need Python 2.7 or anything from the 3.x line. Most of the user-facing

[PATCH] NEWS: fix 'not' - 'now' typo in 0.19 nmbug section

--- NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 70ad3f3..8a1b310 100644 --- a/NEWS +++ b/NEWS @@ -167,7 +167,7 @@ nmbug The Perl script has been translated to Python; you'll need Python 2.7 or anything from the 3.x line. Most of the user-facing

[PATCH v4] nmbug-status: Use 'show-ref --heads' for loading configs

When loading configs from Git, the bare branch name (without a refs/heads/ prefix or similar) matches all branches of that name (including remote-tracking branches): .nmbug $ git show-ref config 48f3bbf1d1492e5f3d2f01de6ea79a30d3840f20 refs/heads/config

[PATCH v2] nmbug-status: Use 'show-ref --heads' for loading configs

On Sat, Mar 21, 2015 at 10:28:05AM +0200, Tomi Ollila wrote: > But why is the NEWS brurb added deep into 0.19 NEWS content ? Oops, I was just looking for the nmbug section and didn't see that we're now post 0.19 ;). Fixed in v3 [1]. Cheers, Trevor [3]:

[PATCH v3] nmbug-status: Use 'show-ref --heads' for loading configs

When loading configs from Git, the bare branch name (without a refs/heads/ prefix or similar) matches all branches of that name (including remote-tracking branches): .nmbug $ git show-ref config 48f3bbf1d1492e5f3d2f01de6ea79a30d3840f20 refs/heads/config

[PATCH v3] nmbug-status: Use 'show-ref --heads' for loading configs

When loading configs from Git, the bare branch name (without a refs/heads/ prefix or similar) matches all branches of that name (including remote-tracking branches): .nmbug $ git show-ref config 48f3bbf1d1492e5f3d2f01de6ea79a30d3840f20 refs/heads/config

Re: [PATCH v2] nmbug-status: Use 'show-ref --heads' for loading configs

On Sat, Mar 21, 2015 at 10:28:05AM +0200, Tomi Ollila wrote: But why is the NEWS brurb added deep into 0.19 NEWS content ? Oops, I was just looking for the nmbug section and didn't see that we're now post 0.19 ;). Fixed in v3 [1]. Cheers, Trevor [3]:

[PATCH v4] nmbug-status: Use 'show-ref --heads' for loading configs

When loading configs from Git, the bare branch name (without a refs/heads/ prefix or similar) matches all branches of that name (including remote-tracking branches): .nmbug $ git show-ref config 48f3bbf1d1492e5f3d2f01de6ea79a30d3840f20 refs/heads/config

[PATCH v2] nmbug-status: Use 'show-ref --heads' for loading configs

When loading configs from Git, the bare branch name (without a refs/heads/ prefix or similar) matches all branches of that name (including remote-tracking branches): .nmbug $ git show-ref config 48f3bbf1d1492e5f3d2f01de6ea79a30d3840f20 refs/heads/config

[PATCH 1/2] nmbug-status: Clarify errors for illegible configs

On Sun, Mar 15, 2015 at 09:32:13AM +0100, David Bremner wrote: > The second patch touches the perl version of nmbug, so I'm guessing > you rolled it into the python rewrite. No, the Python bit was pretty much a straight translation. I'll port the second patch over and resubmit. Cheers, Trevor

[PATCH v2] nmbug-status: Use 'show-ref --heads' for loading configs

When loading configs from Git, the bare branch name (without a refs/heads/ prefix or similar) matches all branches of that name (including remote-tracking branches): .nmbug $ git show-ref config 48f3bbf1d1492e5f3d2f01de6ea79a30d3840f20 refs/heads/config

Re: [PATCH 1/2] nmbug-status: Clarify errors for illegible configs

On Sun, Mar 15, 2015 at 09:32:13AM +0100, David Bremner wrote: The second patch touches the perl version of nmbug, so I'm guessing you rolled it into the python rewrite. No, the Python bit was pretty much a straight translation. I'll port the second patch over and resubmit. Cheers, Trevor --

[Patch v2 2/4] doc: add more information on operators.

On Mon, Feb 23, 2015 at 09:05:35PM +0100, David Bremner wrote: > +In addition to individual terms, multiple terms can be combined with > +Boolean operators (**and**, **or**, **not**, and **xor**). Each term > +in the query will be implicitly connected by a logical AND if no > +explicit operator is

[PATCH v4] nmbug: Add an 'init' command

On Mon, Jan 19, 2015 at 11:44:16AM +0200, Tomi Ollila wrote: > $ python2.7 devel/nmbug/nmbug init > Reinitialized existing Git repository in /home/too/.nmbug/ > e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 > user.name not defined > [u'git', u'--git-dir', u'/home/too/.nmbug', u'commit',

Re: [PATCH v4] nmbug: Add an 'init' command

On Mon, Jan 19, 2015 at 11:44:16AM +0200, Tomi Ollila wrote: $ python2.7 devel/nmbug/nmbug init Reinitialized existing Git repository in /home/too/.nmbug/ e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 user.name not defined [u'git', u'--git-dir', u'/home/too/.nmbug', u'commit', u'--allow-empty',

[PATCH v4] nmbug: Add an 'init' command

For folks that want to start versioning a new tag-space, instead of cloning one that someone else has already started. The empty-blob hash-object call avoids errors like: $ nmbug commit error: invalid object 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 for 'tags/...' fatal:

[PATCH] doc: remove support for rst2man

Looks good to me :). Cheers, Trevor -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type:

[PATCH v4] nmbug: Add an 'init' command

For folks that want to start versioning a new tag-space, instead of cloning one that someone else has already started. The empty-blob hash-object call avoids errors like: $ nmbug commit error: invalid object 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 for 'tags/...' fatal:

Re: [PATCH] doc: remove support for rst2man

Looks good to me :). Cheers, Trevor -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy signature.asc Description: OpenPGP digital signature ___

[PATCH] doc: Allow rst2man.py as an alternative to rst2man

On Sat, Jan 03, 2015 at 07:12:13PM +0200, Tomi Ollila wrote: > ? so this makes me wonder whether there is actually anyone needing > rst2man there? Requiring Sphinx >= 1.0 (2010-07-23 [1]) to build man pages is fine with me. Cheers, Trevor [1]: https://pypi.python.org/pypi/Sphinx/1.0 -- This

[PATCH] doc: Allow rst2man.py as an alternative to rst2man

On Sat, Jan 03, 2015 at 04:49:27PM +0100, David Bremner wrote: > At the risk of bike-shedding, rewrite the configure check to be more > "obvious". This is pretty subjective, but in particular I'm not a > big fan of resetting RST2MAN at the bottom of every iteration of the > for loop. Also conform

Re: [PATCH] doc: Allow rst2man.py as an alternative to rst2man

On Sat, Jan 03, 2015 at 04:49:27PM +0100, David Bremner wrote: At the risk of bike-shedding, rewrite the configure check to be more obvious. This is pretty subjective, but in particular I'm not a big fan of resetting RST2MAN at the bottom of every iteration of the for loop. Also conform a bit

[PATCH v3] nmbug: Add an 'init' command

On Sat, Nov 29, 2014 at 12:09:17PM -0800, W. Trevor King wrote: > On Sat, Nov 29, 2014 at 10:40:01AM +0100, Michal Sojka wrote: > > On ?t, ??j 28 2014, W. Trevor King wrote: > > > +_spawn( > > > +args=['git', 'init', '--separat

[PATCH v3] nmbug: Add an 'init' command

On Sat, Nov 29, 2014 at 10:40:01AM +0100, Michal Sojka wrote: > On ?t, ??j 28 2014, W. Trevor King wrote: > > +_spawn( > > +args=['git', 'init', '--separate-git-dir', NMBGIT, workdir], > > +wait=True) > > +_git(args=['config'

Re: [PATCH v3] nmbug: Add an 'init' command

On Sat, Nov 29, 2014 at 10:40:01AM +0100, Michal Sojka wrote: On Út, říj 28 2014, W. Trevor King wrote: +_spawn( +args=['git', 'init', '--separate-git-dir', NMBGIT, workdir], +wait=True) +_git(args=['config', '--unset', 'core.worktree'], wait=True

  1   2   3   4   5   >