Sumit,
As I understand it, the example you gave (560 becomes 5.60) is intended
behavior. And, as far as I am concerned, the explanation in the help is
sufficient, if not inspiring.
It seems to me the problem in the underlying bug is that the decimal algorithm
needs to be applied after any cal
Hi all,
Dmitry watched, that his PRs disappeared from Maint after I merged them
in Master.
So, what happened?
He sent PR 100-104 to github
I pulled them via https://github.com/Gnucash/gnucash-docs/pull/...
sequently into maint, after each calling locally:
(with git checkout maint)
git pull
make
Um, we DO build the maint branch of gnucash-docs.
-derek
"Frank H. Ellenberger" writes:
> Hi Derek,
>
> I am wondering if building the master branch of gnucash-docs is such a
> good solution.
>
> we have one or two documented features of the 2.8 serie in master but
> the bulk is done on maint:
A quick look at
https://lists.gnucash.org/pipermail/gnucash-patches/2017-July/date.html#start
shows only
gnucash-docs master: Multiple changes pushed Frank H.Ellenberger
There seems to be no hook, which pulls changes on github to code.
Together with my git remote configuration:
origin https://g
Frank,
That’s correct. You must *never* push directly to the mirror repositories on
Github, nor may you use any of the Github merge or edit tools. Push only to
code and it will automatically update Github.
I think we can set up the GnuCash Github repositories so that only the special
user asso
I do not even see this as a bug. Any number without a decimal point is divided
by 100. Which makes the input “20.44/2” in fact 20.44/0.02 which is 1,022.00
Cheers,
Christoph
> Am 26.07.2017 um 09:58 schrieb David T. via gnucash-devel
> :
>
> Sumit,
> As I understand it, the example you gave
