Re: [GNC-dev] Can I edit the github release notice
Updated on www.gnucash.org and github. Frank Am 16.06.20 um 00:22 schrieb Robert Fewell: > John, > That's better than my change so please use yours. > > Thankyou, > Bob > > On Mon, 15 Jun 2020 at 21:10, John Ralls wrote: > >> Bob, >> >> How about "A new Transaction Association dialog, available from the Update >> Association for Transaction menu item that has replaced the two association >> items in 3.x, allows setting, changing, and deleting associations." >> >> Regards, >> John Ralls >> >>> On Jun 15, 2020, at 12:15 PM, Robert Fewell <14ubo...@gmail.com> wrote: >>> >>> Thank you John, >>> Can you change the 6th bullet point that reads... >>> >>> A new Transaction Association dialog, available from the new Update >> Transaction Association item in the register context menu, provides the >> ability to have multiple associations for a single transaction. >> Associations may now be easily removed. >>> >>> and change it to... >>> >>> A new Transaction Association dialog, available from the new Update >> Transaction Association item in the register context menu with the addition >> that Associations can now be easily removed. >>> >>> Sorry if my push on Saturday caused more work for you. >>> >>> Regards, >>> Bob >>> >>> On Mon, 15 Jun 2020 at 18:29, John Ralls wrote: >>> >>> On Jun 15, 2020, at 6:43 AM, Derek Atkins wrote: Hi, Robert Fewell <14ubo...@gmail.com> writes: > Hi, > > Just noticed that the release says you can have multiple transaction > associations, the 6th bullet point but it is still only one per >> transaction. You probably should not edit anything directly in github, or it will probably get lost on the next push from code. >>> >>> Release notices are different from git-controlled files, though. Those >> are only editable via Github. >>> >>> Note though that the Github release notices, release news on >> https://www.gnucash.org/news.phtml, and the emailed release announcement >> all use the same text and that it starts with the www.gnucash.org news >> item. Those are in the gnucash-htdocs repo. >>> >>> I'll fix all of it up if you like, just tell me what line you want >> changed. >>> >>> Regards, >>> John Ralls >>> >> >> > ___ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] qof_book_is_readonly error in trace file
John, No, just tried with 3.905 and I get the 4 errors. With gdb the first is from gnc-main-window.c:1514 gnc-plugin-aqbanking.c:348 gnc-plugin-basic-commands.c:366 gnc-plugin-business.c:1044 Regards, Bob On Mon, 15 Jun 2020 at 20:55, John Ralls wrote: > > > > On Jun 14, 2020, at 8:11 AM, John Ralls wrote: > > > > > > > >> On Jun 14, 2020, at 5:16 AM, Robert Fewell <14ubo...@gmail.com> wrote: > >> > >> Hi, > >> > >> If you start gnucash with the --nofile option and then proceed to use > the > >> New Account Hierarchy Assistant, when you do the save you get the > following > >> error in the trace file 4 times... > >> > >> ERROR gboolean qof_book_is_readonly(const QofBook*): > assertion > >> 'book != NULL' failed > >> > >> This I assume is because there is no book for use in > qof_book_is_readonly, > >> qofbook.c line 579 but that does not appear to have changed so I am > unsure > >> of a fix. > > > > I stopped it creating a session and therefore a book when you pass > --nofile or when it can't find the file/database you asked to open so that > it wouldn't then ask if you wanted to save the book when you opened > something new. Looks like I missed at least one path that assumes there's > always a book, I'll track that down after I finish the release. > > Hmm, can't get it to replicate now. Is this what you fixed yesterday > morning? > > Regards, > John Ralls > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Can I edit the github release notice
John, That's better than my change so please use yours. Thankyou, Bob On Mon, 15 Jun 2020 at 21:10, John Ralls wrote: > Bob, > > How about "A new Transaction Association dialog, available from the Update > Association for Transaction menu item that has replaced the two association > items in 3.x, allows setting, changing, and deleting associations." > > Regards, > John Ralls > > > On Jun 15, 2020, at 12:15 PM, Robert Fewell <14ubo...@gmail.com> wrote: > > > > Thank you John, > > Can you change the 6th bullet point that reads... > > > > A new Transaction Association dialog, available from the new Update > Transaction Association item in the register context menu, provides the > ability to have multiple associations for a single transaction. > Associations may now be easily removed. > > > > and change it to... > > > > A new Transaction Association dialog, available from the new Update > Transaction Association item in the register context menu with the addition > that Associations can now be easily removed. > > > > Sorry if my push on Saturday caused more work for you. > > > > Regards, > > Bob > > > > On Mon, 15 Jun 2020 at 18:29, John Ralls wrote: > > > > > > > On Jun 15, 2020, at 6:43 AM, Derek Atkins wrote: > > > > > > Hi, > > > > > > Robert Fewell <14ubo...@gmail.com> writes: > > > > > >> Hi, > > >> > > >> Just noticed that the release says you can have multiple transaction > > >> associations, the 6th bullet point but it is still only one per > transaction. > > > > > > You probably should not edit anything directly in github, or it will > > > probably get lost on the next push from code. > > > > Release notices are different from git-controlled files, though. Those > are only editable via Github. > > > > Note though that the Github release notices, release news on > https://www.gnucash.org/news.phtml, and the emailed release announcement > all use the same text and that it starts with the www.gnucash.org news > item. Those are in the gnucash-htdocs repo. > > > > I'll fix all of it up if you like, just tell me what line you want > changed. > > > > Regards, > > John Ralls > > > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Can I edit the github release notice
Bob, How about "A new Transaction Association dialog, available from the Update Association for Transaction menu item that has replaced the two association items in 3.x, allows setting, changing, and deleting associations." Regards, John Ralls > On Jun 15, 2020, at 12:15 PM, Robert Fewell <14ubo...@gmail.com> wrote: > > Thank you John, > Can you change the 6th bullet point that reads... > > A new Transaction Association dialog, available from the new Update > Transaction Association item in the register context menu, provides the > ability to have multiple associations for a single transaction. Associations > may now be easily removed. > > and change it to... > > A new Transaction Association dialog, available from the new Update > Transaction Association item in the register context menu with the addition > that Associations can now be easily removed. > > Sorry if my push on Saturday caused more work for you. > > Regards, > Bob > > On Mon, 15 Jun 2020 at 18:29, John Ralls wrote: > > > > On Jun 15, 2020, at 6:43 AM, Derek Atkins wrote: > > > > Hi, > > > > Robert Fewell <14ubo...@gmail.com> writes: > > > >> Hi, > >> > >> Just noticed that the release says you can have multiple transaction > >> associations, the 6th bullet point but it is still only one per > >> transaction. > > > > You probably should not edit anything directly in github, or it will > > probably get lost on the next push from code. > > Release notices are different from git-controlled files, though. Those are > only editable via Github. > > Note though that the Github release notices, release news on > https://www.gnucash.org/news.phtml, and the emailed release announcement all > use the same text and that it starts with the www.gnucash.org news item. > Those are in the gnucash-htdocs repo. > > I'll fix all of it up if you like, just tell me what line you want changed. > > Regards, > John Ralls > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] qof_book_is_readonly error in trace file
> On Jun 14, 2020, at 8:11 AM, John Ralls wrote: > > > >> On Jun 14, 2020, at 5:16 AM, Robert Fewell <14ubo...@gmail.com> wrote: >> >> Hi, >> >> If you start gnucash with the --nofile option and then proceed to use the >> New Account Hierarchy Assistant, when you do the save you get the following >> error in the trace file 4 times... >> >> ERROR gboolean qof_book_is_readonly(const QofBook*): assertion >> 'book != NULL' failed >> >> This I assume is because there is no book for use in qof_book_is_readonly, >> qofbook.c line 579 but that does not appear to have changed so I am unsure >> of a fix. > > I stopped it creating a session and therefore a book when you pass --nofile > or when it can't find the file/database you asked to open so that it wouldn't > then ask if you wanted to save the book when you opened something new. Looks > like I missed at least one path that assumes there's always a book, I'll > track that down after I finish the release. Hmm, can't get it to replicate now. Is this what you fixed yesterday morning? Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Can I edit the github release notice
Thank you John, Can you change the 6th bullet point that reads... A new *Transaction Association* dialog, available from the new *Update Transaction Association* item in the register context menu, provides the ability to have multiple associations for a single transaction. Associations may now be easily removed. and change it to... A new *Transaction Association* dialog, available from the new *Update Transaction Association* item in the register context menu with the addition that Associations can now be easily removed. Sorry if my push on Saturday caused more work for you. Regards, Bob On Mon, 15 Jun 2020 at 18:29, John Ralls wrote: > > > > On Jun 15, 2020, at 6:43 AM, Derek Atkins wrote: > > > > Hi, > > > > Robert Fewell <14ubo...@gmail.com> writes: > > > >> Hi, > >> > >> Just noticed that the release says you can have multiple transaction > >> associations, the 6th bullet point but it is still only one per > transaction. > > > > You probably should not edit anything directly in github, or it will > > probably get lost on the next push from code. > > Release notices are different from git-controlled files, though. Those are > only editable via Github. > > Note though that the Github release notices, release news on > https://www.gnucash.org/news.phtml, and the emailed release announcement > all use the same text and that it starts with the www.gnucash.org news > item. Those are in the gnucash-htdocs repo. > > I'll fix all of it up if you like, just tell me what line you want changed. > > Regards, > John Ralls > > ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Can I edit the github release notice
> On Jun 15, 2020, at 6:43 AM, Derek Atkins wrote: > > Hi, > > Robert Fewell <14ubo...@gmail.com> writes: > >> Hi, >> >> Just noticed that the release says you can have multiple transaction >> associations, the 6th bullet point but it is still only one per transaction. > > You probably should not edit anything directly in github, or it will > probably get lost on the next push from code. Release notices are different from git-controlled files, though. Those are only editable via Github. Note though that the Github release notices, release news on https://www.gnucash.org/news.phtml, and the emailed release announcement all use the same text and that it starts with the www.gnucash.org news item. Those are in the gnucash-htdocs repo. I'll fix all of it up if you like, just tell me what line you want changed. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] Gnucash 2.6: make distcheck in po bombs on file paths starting with sub
> On Jun 15, 2020, at 4:41 AM, Kevin Buckley wrote:
>
> On Mon, 15 Jun 2020 at 14:29, Kevin Buckley wrote:
>>
>> On Mon, 15 Jun 2020 at 02:31, John Ralls wrote:
>>>
>>> Building 2.6.21a works fine for me on Ubuntu 18.04 with automake 1.15.1.
>>> None of the source files are copied into gnucash-2.6.21/_build/sub, so
>>> there's no POTFILE.skip issue.
>>>
>>> I did have to make two changes to get it to build from the dist tarball:
>>> Remove line 23 (src/plugins/example/gnc-plugin.example.c) from
>>> po/POTFILES.skip and add test-date-utilities.scm to EXTRA_DIST at line 69
>>> of src/app-utils/test/Makefile.am
>>>
>>> Since you've presumably made changes and tagged for a new distribution, I
>>> suggest you first make sure that you can build 2.6.21a with the changes
>>> above. If it doesn't work I suggest first trying automake 1.15.1. Once you
>>> have 2.6.21a building successfully then reapply your changes and see if
>>> they break anything.
>>>
>
> and i went on to say
>
>> i did get the 2.6.21a source, or something close (haven't got my
>> work dir to hand but I started with the commit commented as "Fix
>> Typo") that was two or three after 2.6.21 was tagged) building as
>> was, however, that was before I'd found the "trust make distcheck",
>> so yes I will go back and try that against the old layout.
>
> Have now tried that, albeit with automake 1.15., not 1.15.1.
>
> Also ascertained that tag 2.6.21a is the same commit as the "Fix Typo."
> I was thinking of so we're all square there
>
> As you pointed out, needed to ferkel po/POTFILES.skip but then found
> it bombed when running some QOF tests
>
> /qof/gnc-date/qof date format set: OK
> /qof/gnc-date/qof print date dmy buff: FAIL
> GTester: last random seed: R02S04e93899cdb3f7940b6259d335ba0eb5
> /bin/bash: line 1: 9498 Terminated MALLOC_CHECK_=2
> MALLOC_PERTURB_=$((${RANDOM:-256} % 256)) gtester --verbose test-qof
> make[6]: *** [test-nonrecursive] Error 143
> make[6]: Leaving directory
> `/srv/domains/gnucash.org/GIT/gnucash-868489b/gnucash-2.6.21/_build/sub/src/libqof/qof/test'
>
> Note though that the testing IS happening in a path with _build/sub in it
>
> So I even went and looked in the Automake files that get used to
> created the Makefile.in from Makefile.am and saw, in
>
> distclean.am
>
> that it really does do what I experienced, vis
>
> ## If we merely used '$(distdir)/_build' here, "make distcheck" could
> ## sometimes fail to detect missing files in the distribution tarball,
> ## especially in those cases where both the generated files and their
> ## dependencies are explicitly in $(srcdir). See automake bug#18286.
> && $(am__cd) $(distdir)/_build/sub \
> && ../../configure \
>
> Even pulled down the Automake 1.15.1. tarball, and it still in there too.
>
> No wonder you lot moved to CMake then?
Yes, automake 1.15 introduced the _build/sub thing. As I said, I built and
distchecked GnuCash on Ubuntu 18.04 yesterday with no errors, so that's not
what caused your POTFILE.skip problems.
I don't remember encountering an error message like that, but it kind of looks
like you ran out of memory. You'll need to spend some time in the debugger to
figure it out.
As for autotools, it's 30 years of layered hacks and has gotten steadily more
byzantine and buggy with every passing year. It also generates very slow and
inefficient builds. Cmake and ninja have provided a much better build
experience.
Regards,
John Ralls
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] [GNC] GnuCash 3.905 Released
Will, stay with 3.10-1. 3.905 is an experimental beta release. The numbering sounds odd, but release 4.0 will follow after the beta has had enough experience. On Mon, Jun 15, 2020 at 11:05 AM w...@theprescotts.com < w...@theprescotts.com> wrote: > I am currently running 3.10-1 on MacOS. I am unclear how this relates to > 3.905. Can someone clarify this for me. > > Thanks, > Will > > On 2020 Jun 14, at 06-14 18:19:31, John Ralls wrote: > > The GnuCash development team announces GnuCash 3.905, the fourth testing > release for what will soon be GnuCash 4.0. > > Changes > > Baseline requirements > > Operating Systems: > > • Linux: Ubuntu 18.04LTS > • MacOS: 10.13 > • Windows: 8.1 > Software Dependencies: > > • C++ standard is now C++17, requires gcc 8.0 or clang 6.0. > • Cmake 3.10 > • boost 1.67.0 > • gettext 0.19.6 for general use, 0.20 to generate gnucash.pot. > • glib-2.0 2.56.1, gtk 3.22.30 > • googletest 1.8.0 > • ICU, any version. > • libdbi 0.8.3 > • libxml2 2.9.4 > • swig 3.0.12 Now required for building from tarballs as well as > from git. > • Webkit 2.4.11 Mac & Win32, 2.14.1 Linux/BSD > New Features > > The intent is to have command categories with subcommands to better enable > a richer command line capability as illustrated with the new report > commands list and show. > > • A new separate executable, gnucash-cli (gnucash-cli.exe on > Microsoft Windows) for doing command-line things like updating the prices > in your book. gnucash-cli gains the ability to run reports from the command > line. Specify reports to run by name or guid. It also provides an export > format and an output file name without which it will output the report to > stdout. > • gnucash-cli --report run --name=[reportname/guid] > datafile.gnucash > • gnucash-cli --report run --name=[reportname/guid] > --output-file=x.html datafile.gnucash > • gnucash-cli --report run --name=[reportname/guid] > --output-file=x.html --export-type=TYPE datafile.gnucash > The GUI command, gnucash responds to the same command line arguments. In > order to provide more options its syntax (and gnucash-cli's) for quote > retrieval is changed from --add-quotes to --quotes get. > > • When deleting accounts the destination accounts of moved splits > will be checked to ensure that they have the same commodity as the source > account. If they don't you'll get a warning and the opportunity to pick > another account or to carry on regardless. > • New type-ahead search added to sequential search when selecting > an account in the register: Instead of typing the first few characters of a > top level account, the separator, the first few characters of the next > level account and so on you may instead type a few characters of any part > of a full account name and the drop-list will be filtered to contain only > matching accounts. Once you have a small enough list you can use the arrow > keys to select the account that you want. > • Python bindings are now localized and their strings available > for translation. > • The new reports introduced in the Experimental Reports menu are > moved to the main menu and the old reports hidden; the old reports can be > unhidden by running GnuCash from the commandline with the --extra argument. > That will cause the old reports to appear in their regular locations on the > menu labeled (legacy). Note that new reports use different options and > layouts and you may need to adjust your saved report configurations. > • A new Transaction Association dialog, available from the new > Update Transaction Association item in the register context menu, provides > the ability to have multiple associations for a single transaction. > Associations may now be easily removed. > • Allow Associations to be added to invoices. The actual > association when present is added as a link button which is shown below the > notes. > • A symbol is now displayed on transactions in the register when > they have an attachment and the selected font supports the symbol. > • The OFX file importer can now import more than one file at a > time. > • A new report menu supbmenu Multicolumn contains the old > custom-multicolumn report and a new Dashboard report containing Account > reports for expenses and income, an income-expense chart, and an account > summary. > • When importing, the matcher will no longer offer to match a > transaction to one that has already matched in a previous import, nor will > it offer to match more than one imported transaction to a single existing > transaction. > • Support for UK VAT and Australian GST added to the Income-GST > report. The reports options are changed from source accounts to source > sales and purchase accounts to permit proper reporting of capital > purchases. N.B.
Re: [GNC-dev] Gnucash 2.6: make distcheck in po bombs on file paths starting with sub
> On Jun 14, 2020, at 11:29 PM, Kevin Buckley wrote: > > On Mon, 15 Jun 2020 at 02:31, John Ralls wrote: >> >> Building 2.6.21a works fine for me on Ubuntu 18.04 with automake 1.15.1. >> None of the source files are copied into gnucash-2.6.21/_build/sub, so >> there's no POTFILE.skip issue. >> >> I did have to make two changes to get it to build from the dist tarball: >> Remove line 23 (src/plugins/example/gnc-plugin.example.c) from >> po/POTFILES.skip and add test-date-utilities.scm to EXTRA_DIST at line 69 of >> src/app-utils/test/Makefile.am >> >> Since you've presumably made changes and tagged for a new distribution, I >> suggest you first make sure that you can build 2.6.21a with the changes >> above. If it doesn't work I suggest first trying automake 1.15.1. Once you >> have 2.6.21a building successfully then reapply your changes and see if they >> break anything. >> >> I'm a bit concerned that since you're running distcheck with a new tag >> you're planning to distribute it to others and to create the expectation >> that we will support it. We won't, so please don't. > > To answer the last bit first, rest assured I have no plans to distribute > this work. Never my intention to do anything with it, other than use it > myself, though perhaps aluding to the fact that something might be > possible. > > To be honest I doubt anyone else but me would be interested > in using the 2.6 series. > > The tagging is just a way to allow me to compare changes > easily. I noticed there was a 2.6.99 floating around in the > official sources. I myself have used 2.6.31, 42 and 51, at > various stages of playing around, but as I coalesced around > "the next step using the 2.6.21 sources pretty much unmodified", > 2.6.22 seemed "right". > > I'd like to see how far I could take the 2.6 environment and > backport updates into it. > > The idea behind moving into the new source layout was simply > that it would make it easier to see what had been changed. > > Having said that, I have no intention of using a DB backend, > nor building against Boost, or with CMake, for that matter. > > I note that there are a few places in the last 2.6 code release > where it says "won't fix because we're moving to CMake" and > felt that was a bit of a cop-out, but that's just a personal thing, > not a criticism. > > I would like to try and get my 2.6 stuff compiling within a CMake > system whilst maintaining a working Autotools build system, > although I'd always build against the latter. > > Most of that will have been done for 2.7 onwards anyway, so > it should just be a matter of matching up the newer files that > already exist. > > I realy feel that I'm merely re-arranging what the GnuCash > developers have done, not actually adding anything > > Onto the more techincal side of things though, > > The reason for running "distcheck" was that I read something > that suggested that was the best test of the code, although, as > I mentioned, I had been doing a make dist and then a separate > unpack and build as a test anyway. Clearly the make distcheck > has thrown up issues I might have missed, even if they do appear > to be specific to my environment. > > > i did get the 2.6.21a source, or something close (haven't got my > work dir to hand but I started with the commit commented as "Fix > Typo") that was two or three after 2.6.21 was tagged) building as > was, however, that was before I'd found the "trust make distcheck", > so yes I will go back and try that against the old layout. > > I'm building on a Ubuntu 14 OS (as I loathe SystemD and of course, > the init system is of little consequence in building non-OS software) > but I have, as I said, added enough /usr/local tools to be a bit more > up-to-date (ha-ha!) for the purpose of . > > I really should have moved to using LinuxFromScratch system in > everyday use by now but, what can I tell you, I'm not quite there > yet, Gnucash is one of the missing pieces, so UB14/CentOS610 it is. > > Finally, at the risk of overstating things, I really do appreciate you taking > a look into this. From the first time I came across Gnucash, I was amazed > at the way it merged the C and Scheme parts and, even though I've not > really used anything that required that specific knowledge, it's been a useful > insight to have had. I somehow missed this admonition in my earlier reply and failed to add the list back as a copy-to, so rectifying it here: All replies need to copy the list. Look, we're done with 2.6 and we're done with autotools. That's why there were "won't fix" autotools bugs. Not a cop-out, there's no point in fixing something that isn't used any more. All that distcheck does is unpack the distribution tarball and build and check the result, then clean up. That ensures that everything needed to build and pass the test suite is included in the tarball and that everything that's supposed to be removed with make clean is in fact removed. It doesn't do
Re: [GNC-dev] Can I edit the github release notice
Hi, Robert Fewell <14ubo...@gmail.com> writes: > Hi, > > Just noticed that the release says you can have multiple transaction > associations, the 6th bullet point but it is still only one per transaction. You probably should not edit anything directly in github, or it will probably get lost on the next push from code. > Regards, > Bob -derek -- Derek Atkins 617-623-3745 de...@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] [GNC] GnuCash 3.905 Released
A couple of notes: - Balance-sheet is reverted back to the legacy report: multicolumn balance-sheet had a few more bugs identified related to currency conversions, so, isn't ready yet. The latter is downgraded back to experimental submenu. - gnucash-cli --report run --name "VAT Report" --export-type CSV --output-file VAT.CSV, when "Income and GST Statement" is properly set up and saved as "VAT Report", would be a convenient way to generate the VAT figures and save as CSV. Also applicable for Australian BAS reports. On Sun, 14 Jun 2020 at 23:21, John Ralls wrote: > The GnuCash development team announces GnuCash 3.905, the fourth testing > release for what will soon be GnuCash 4.0. > > Changes > > Baseline requirements > > Operating Systems: > > • Linux: Ubuntu 18.04LTS > • MacOS: 10.13 > • Windows: 8.1 > Software Dependencies: > > • C++ standard is now C++17, requires gcc 8.0 or clang 6.0. > • Cmake 3.10 > • boost 1.67.0 > • gettext 0.19.6 for general use, 0.20 to generate gnucash.pot. > • glib-2.0 2.56.1, gtk 3.22.30 > • googletest 1.8.0 > • ICU, any version. > • libdbi 0.8.3 > • libxml2 2.9.4 > • swig 3.0.12 Now required for building from tarballs as well as > from git. > • Webkit 2.4.11 Mac & Win32, 2.14.1 Linux/BSD > New Features > > The intent is to have command categories with subcommands to better enable > a richer command line capability as illustrated with the new report > commands list and show. > > • A new separate executable, gnucash-cli (gnucash-cli.exe on > Microsoft Windows) for doing command-line things like updating the prices > in your book. gnucash-cli gains the ability to run reports from the command > line. Specify reports to run by name or guid. It also provides an export > format and an output file name without which it will output the report to > stdout. > • gnucash-cli --report run --name=[reportname/guid] > datafile.gnucash > • gnucash-cli --report run --name=[reportname/guid] > --output-file=x.html datafile.gnucash > • gnucash-cli --report run --name=[reportname/guid] > --output-file=x.html --export-type=TYPE datafile.gnucash > The GUI command, gnucash responds to the same command line arguments. In > order to provide more options its syntax (and gnucash-cli's) for quote > retrieval is changed from --add-quotes to --quotes get. > > • When deleting accounts the destination accounts of moved splits > will be checked to ensure that they have the same commodity as the source > account. If they don't you'll get a warning and the opportunity to pick > another account or to carry on regardless. > • New type-ahead search added to sequential search when selecting > an account in the register: Instead of typing the first few characters of a > top level account, the separator, the first few characters of the next > level account and so on you may instead type a few characters of any part > of a full account name and the drop-list will be filtered to contain only > matching accounts. Once you have a small enough list you can use the arrow > keys to select the account that you want. > • Python bindings are now localized and their strings available > for translation. > • The new reports introduced in the Experimental Reports menu are > moved to the main menu and the old reports hidden; the old reports can be > unhidden by running GnuCash from the commandline with the --extra argument. > That will cause the old reports to appear in their regular locations on the > menu labeled (legacy). Note that new reports use different options and > layouts and you may need to adjust your saved report configurations. > • A new Transaction Association dialog, available from the new > Update Transaction Association item in the register context menu, provides > the ability to have multiple associations for a single transaction. > Associations may now be easily removed. > • Allow Associations to be added to invoices. The actual > association when present is added as a link button which is shown below the > notes. > • A symbol is now displayed on transactions in the register when > they have an attachment and the selected font supports the symbol. > • The OFX file importer can now import more than one file at a > time. > • A new report menu supbmenu Multicolumn contains the old > custom-multicolumn report and a new Dashboard report containing Account > reports for expenses and income, an income-expense chart, and an account > summary. > • When importing, the matcher will no longer offer to match a > transaction to one that has already matched in a previous import, nor will > it offer to match more than one imported transaction to a single existing > transaction. > • Support for UK VAT and Australian GST added to the Income-GST > report. The reports options
[GNC-dev] Can I edit the github release notice
Hi, Just noticed that the release says you can have multiple transaction associations, the 6th bullet point but it is still only one per transaction. Regards, Bob ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
