Re: Changing tags in a plugin? Help please

2017-02-18 Thread stalbansrfctreasurer
Now it works. This can flag cash accounts, but is now configurable to flag any transaction what contains any of the listed accounts. I still don't understand how this works, or what type an empty tag set is (tagset or set()) | set((tagged,)) Sample header in journal file: plugin "beancoun

Re: Changing tags in a plugin? Help please

2017-02-18 Thread Martin Blais
entry.tags is supposed to be a set. If not set, an empty set. I reuse a constant in the codebase (see EMPTY_SET). TBH I'm not 100% sure what your question is. On Sat, Feb 18, 2017 at 5:04 AM, wrote: > Now it works. > This can flag cash accounts, but is now configurable to flag any > transact

Re: Changing tags in a plugin? Help please

2017-02-18 Thread stalbansrfctreasurer
Martin Thanks. My question was all around how to test for an empty tag and update it - your code does this with (tagset or set()) | set((tagged,)) I tried to do a logic test on if tagset == None: and also if tagset == set():but neither seemed to work. I was going to do if tagset == None

Re: can't get vim plugin fully working

2017-02-18 Thread Jason Chu
Is your vim built with Python 3 support? If you have Python 2 only then we call bean-query to get the information, so it will have to be in your path. On Fri, Feb 17, 2017, 5:46 PM shaun wrote: > Awesome! > > That seems to have gotten me a little closer. > > > I now get the following error the f

Re: Changing tags in a plugin? Help please

2017-02-18 Thread Martin Blais
There's a bit of history there: an empty 'tags' attribute used to be set to None. This is mostly internal changes, but I suppose if you write a plugin it matters. On this change: https://bitbucket.org/blais/beancount/commits/1a37899b54837abf9f35c574135cce09382ed3c7 I made them guaranteed to always