Paylist

[Martin Mainka]

Hi,

i try to manage the Payments for the employees according to description
in GnuCash Tutorial and Concepts Guide chapter 17. My Problem is to get
reports for the employees. In the configuration i'm not able to select
an account Gnucash should look for entries. The field is greyed. Is
there a special setup necessary?

Thanks a lot

Martin Mainka

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

RE: Using make with docs

[Chris Good]

> Message: 3
> Date: Mon, 6 Feb 2017 22:29:51 +0500
> From: "David T." 
> To: Geert Janssens 
> Cc: gnucash-devel@gnucash.org
> Subject: Re: Using make with docs
> Message-ID: 
> Content-Type: text/plain; charset=utf-8
> 
> Geert,
> 
> > On Feb 6, 2017, at 10:10 PM, Geert Janssens
>  wrote:
> >
> > Op maandag 6 februari 2017 21:28:24 CET schreef David T. via gnucash-
> devel:
> >> Hello,
> >>
> >> The recently-updated Documentation Update Instructions page on the
> >> wiki?as detailed as they are?nonetheless leave something to be
> >> desired when one reaches step 10. You see, up until this point, a
> >> great deal of energy is put into showing how one can use ?make check?
> >> in different ways to test either the Guide, or the Help, or the
different
> translations.
> >>
> >> Once you get to actually compiling these docs, though, the directions
> >> dry up and just tell the user to "make html? in "the appropriate
> >> directory within the build directory structure.? (ADWTBDS)
> >>
> >> Two points:
> >>
> >> 1) when I issue ?make check?, I am in the working directory, and if
> >> you?re stupid or inattentive (both of which apparently apply to me),
> >> you issue the ?make html? command without first changing to the
> ADWTBDS.
> > Acutally, make check is also meant to be run in the build directory.
> > *All* make commands are intended to be executed in the build directory
> > or one if its subdirectories. I'm not sure this is very clearly
specified in the
> wiki page.
> >
> > The fact you can run "make check" in your working directory implies
> > you have in the past run configure in your working directory. By that
> > action you have configured your working directory to double as a build
> > directory. It would simplify your life if you remove these configure
> > actions from the working directory again. By doing so, running "make
> > " there would give an error like this:
> > make: *** No rule to make target 'check'.  Stop.
> >
> 
> No doubt this has something to do with earlier setup issues (steps 3 & 4).
Or
> it has to do with the fact that the earlier method (calling xmllint and
xsltproc
> directly) was invoked in the working directory, with output directed to a
> different folder directly, and I learned that way and kept doing it (like
the
> proverbial lemming of Arthur Clarke?s short story).
> 
> I reiterate my wish to see documentation that covers *setting up a
> build system* separated from information *directly related to the
> documentation update process*. Having a separate setup page would allow
> those of us who struggle with every aspect of this process to be able to
get
> set up, and then focus on screwing up only the actual steps for updating,
> rather than the whole shebang.
> 
> 
> > That should solve your problem of accidentally building the html docs
> > in your git working directory.
> >
> > The easiest way to remove the files set up by configure would be:
> > - cd into to root of your local git repository (the level where you
> > see guide and help as subdirectories)
> > - run: "make distclean" (without the quotes)
> > - and finally rerun "./autogen.sh" (again without the quotes)
> >
> >> This results in
> >> the docs being built right there in the working directory. Not
> >> horrible, but potentially messy (especially if you forget to remove
> >> the folder before going back to git).
> >>
> >> 2) If I change to my build directory, ?make html? builds all the
> >> docs, which is a collossal waste of time when all I want to do is
> >> compile the Guide in
> >> (say) English?which is all I worked on in the first place. I
> >> personally don?t plan on ever editing the Portugese, German, Italian,
> >> or Japanese translations.
> >>
> >> So, two questions:
> >>
> >> 1) Is there a way to configure the make command to use my build
> >> directory as its destination, while running from the working directory?
> > Not that I know of.
> >> 2) Is there a
> >> way to make just the html of one portion of the docs, without making
> >> all docs in all languages?
> > Yes. You can do so by invoking "make html" in the exact build
> > subdirectory that matches the subdirectory in your git repository. For
> > example to build the English guide as html, you would starting from
> > your build directory cd guide/C make html
> >
> > "The appropriate directory in the build directory structure" was meant
> > to suggest exactly that. I see the way it's formulated is still too
> > developer- mind oriented. Sorry about that. Perhaps "the equivalent
> > subdirectory under the build directory" is more clear ? How would you
> > propose to better describe this ?
> >
> > Geert
> 
> 
> Thank you for clearly outlining to me (once more!) how to handle these
> issues. I will look into better ways of wording things to make it clearer
to
> others.
> 
> Cheers,
> David

Hi David T,

I had made some 

Re: documentation bug 687820

[Frank H. Ellenberger]

Davids,

Am 07.02.2017 um 03:16 schrieb david.carlson@gmail.com:
> Sounds Like we need clarification on how to use those fields to best
> advantage. David C Sent from my LG G Pad 7.0 LTE, an AT 4G LTE
> tablet
> 
> 
> 
> -- Original message--From: DavidDate: Mon, Feb 6, 2017 7:53
> PMTo: David Carlson;Frank H. Ellenberger;Cc:
> gnucash-devel@gnucash.org;Subject:Re: documentation bug 687820 David,
> Frank,I was trying to add the new bug as a dependency of the older
> one (as Frank did earlier), but my view only offers an edit option,
> which removed the earlier dependency. I wanted to keep the earlier
> dependency to keep the pieces linked, so I changed it back, knowing
> that someone would note it here and maybe add the dependency in
> additionally. FWIW, I also tried the See Also option on the offhand
> chance it would go into the dependencies spot, but it didn't.David

Let me try ...

https://bugzilla.gnome.org/ says in the upper right corner:
 version 4.4.12

So https://www.bugzilla.org/docs/4.4/en/html/ should be the right manual.

https://www.bugzilla.org/docs/4.4/en/html/bug_page.html below:
 18. *Dependencies: If this bug cannot be fixed unless other bugs are
fixed (depends on), or this bug stops other bugs being fixed (blocks),
their numbers are recorded here.

So you can edit lists in "Depends on" and "Blocks".
To visualize more complex dependencies use "tree". e.g.
https://bugzilla.gnome.org/showdependencytree.cgi?id=570303_resolved=1

HTH
Frank
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: documentation bug 687820

[david . carlson . 417]

Sounds Like we need clarification on how to use those fields to best 
advantage.
David C
Sent from my LG G Pad 7.0 LTE, an AT 4G LTE tablet



-- Original message--From: DavidDate: Mon, Feb 6, 2017 7:53 PMTo: David 
Carlson;Frank H. Ellenberger;Cc: gnucash-devel@gnucash.org;Subject:Re: 
documentation bug 687820
David, Frank,I was trying to add the new bug as a dependency of the older one 
(as Frank did earlier), but my view only offers an edit option, which removed 
the earlier dependency. I wanted to keep the earlier dependency to keep the 
pieces linked, so I changed it back, knowing that someone would note it here 
and maybe add the dependency in additionally. FWIW, I also tried the See Also 
option on the offhand chance it would go into the dependencies spot, but it 
didn't.David

From: David Carlson >
Sent: Tue Feb 07 04:12:29 GMT+05:00 2017
To: "Frank H. Ellenberger" >
Cc: "gnucash-devel@gnucash.org" >
Subject: Re: documentation bug 687820

OK.  I did not know about the histroy link, but the See Also reference and
the Depends on changes are not appearing where they are supposed to even if
I refresh my view of the bug,  Do I have to log out and log back in to
refresh my view of the summary box at the top of the bug report?

David C

On Mon, Feb 6, 2017 at 5:02 PM, Frank H. Ellenberger <
frank.h.ellenber...@gmail.com> wrote:

> Hi David,
>
> Am 06.02.2017 um 23:15 schrieb David Carlson:
> > David,
> >
> > I received two emails from Gnucash saying that you added references to
> bug
> > 778254 to bug 687820, but when I opened bug 687820 I could not find those
> > references.
> >
> > FYI.
> >
> > David C
>
> In the upper right corner behind Modified: is a link, which will show
> you the complete history of attributes.
>
>
> Or obey the header of the table: It is in the 2. mail in the "removed"
> column.
>
> > David > changed:
> >
> >What|Removed |Added
> >
> 
> >See Also|https://bugzilla.gnome.org/ |
> >|show_bug.cgi?id=778254  |
>
> HTH
> FRank
>

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: documentation bug 687820

[David via gnucash-devel]

David, Frank,

I was trying to add the new bug as a dependency of the older one (as Frank did 
earlier), but my view only offers an edit option, which removed the earlier 
dependency. I wanted to keep the earlier dependency to keep the pieces linked, 
so I changed it back, knowing that someone would note it here and maybe add the 
dependency in additionally. FWIW, I also tried the See Also option on the 
offhand chance it would go into the dependencies spot, but it didn't.

David



_
From: David Carlson 
Sent: Tue Feb 07 04:12:29 GMT+05:00 2017
To: "Frank H. Ellenberger" 
Cc: "gnucash-devel@gnucash.org" 
Subject: Re: documentation bug 687820


OK. I did not know about the histroy link, but the See Also reference and
the Depends on changes are not appearing where they are supposed to even if
I refresh my view of the bug, Do I have to log out and log back in to
refresh my view of the summary box at the top of the bug report?

David C

On Mon, Feb 6, 2017 at 5:02 PM, Frank H. Ellenberger <
frank.h.ellenber...@gmail.com> wrote:

> Hi David,
>
> Am 06.02.2017 um 23:15 schrieb David Carlson:
> > David,
> >
> > I received two emails from Gnucash saying that you added references to
> bug
> > 778254 to bug 687820, but when I opened bug 687820 I could not find those
> > references.
> >
> > FYI.
> >
> > David C
>
> In the upper right corner behind Modified: is a link, which will show
> you the complete history of attributes.
>
>
> Or obey the header of the table: It is in the 2. mail in the "removed"
> column.
>
> > David  changed:
> >
> > What |Removed |Added
> >_

> 
> > See Also|https://bugzilla.gnome.org/ |
> > |show_bug.cgi?id=778254 |
>
> HTH
> FRank
>
_

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: documentation bug 687820

[David Carlson]

Now I see in that history that David T removed those changes and I missed
those changes.  So I am just not up to date.  I am curious though, How does
one find related bugs if those fields are not used?

David C

On Mon, Feb 6, 2017 at 5:12 PM, David Carlson 
wrote:

> OK.  I did not know about the histroy link, but the See Also reference and
> the Depends on changes are not appearing where they are supposed to even if
> I refresh my view of the bug,  Do I have to log out and log back in to
> refresh my view of the summary box at the top of the bug report?
>
> David C
>
> On Mon, Feb 6, 2017 at 5:02 PM, Frank H. Ellenberger <
> frank.h.ellenber...@gmail.com> wrote:
>
>> Hi David,
>>
>> Am 06.02.2017 um 23:15 schrieb David Carlson:
>> > David,
>> >
>> > I received two emails from Gnucash saying that you added references to
>> bug
>> > 778254 to bug 687820, but when I opened bug 687820 I could not find
>> those
>> > references.
>> >
>> > FYI.
>> >
>> > David C
>>
>> In the upper right corner behind Modified: is a link, which will show
>> you the complete history of attributes.
>>
>>
>> Or obey the header of the table: It is in the 2. mail in the "removed"
>> column.
>>
>> > David  changed:
>> >
>> >What|Removed |Added
>> > 
>> 
>> >See Also|https://bugzilla.gnome.org/ |
>> >|show_bug.cgi?id=778254  |
>>
>> HTH
>> FRank
>>
>
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: documentation bug 687820

[David Carlson]

OK.  I did not know about the histroy link, but the See Also reference and
the Depends on changes are not appearing where they are supposed to even if
I refresh my view of the bug,  Do I have to log out and log back in to
refresh my view of the summary box at the top of the bug report?

David C

On Mon, Feb 6, 2017 at 5:02 PM, Frank H. Ellenberger <
frank.h.ellenber...@gmail.com> wrote:

> Hi David,
>
> Am 06.02.2017 um 23:15 schrieb David Carlson:
> > David,
> >
> > I received two emails from Gnucash saying that you added references to
> bug
> > 778254 to bug 687820, but when I opened bug 687820 I could not find those
> > references.
> >
> > FYI.
> >
> > David C
>
> In the upper right corner behind Modified: is a link, which will show
> you the complete history of attributes.
>
>
> Or obey the header of the table: It is in the 2. mail in the "removed"
> column.
>
> > David  changed:
> >
> >What|Removed |Added
> > 
> 
> >See Also|https://bugzilla.gnome.org/ |
> >|show_bug.cgi?id=778254  |
>
> HTH
> FRank
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: documentation bug 687820

[Frank H. Ellenberger]

Hi David,

Am 06.02.2017 um 23:15 schrieb David Carlson:
> David,
> 
> I received two emails from Gnucash saying that you added references to bug
> 778254 to bug 687820, but when I opened bug 687820 I could not find those
> references.
> 
> FYI.
> 
> David C

In the upper right corner behind Modified: is a link, which will show
you the complete history of attributes.


Or obey the header of the table: It is in the 2. mail in the "removed"
column.

> David  changed:
> 
>What|Removed |Added
> 
>See Also|https://bugzilla.gnome.org/ |
>|show_bug.cgi?id=778254  |

HTH
FRank
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

documentation bug 687820

[David Carlson]

David,

I received two emails from Gnucash saying that you added references to bug
778254 to bug 687820, but when I opened bug 687820 I could not find those
references.

FYI.

David C
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: gnucash master: Multiple changes pushed & Windows

[Stephen Brown]

Hi John

Sent from Mail for Windows 10

> On Feb 5, 2017, at 12:04 PM, Stephen Brown  
> wrote:
>
> Hi All,
>
> I am still unable to get a clean build of gnucash under Windows 10.
>
> Does it work for others or is it still my installation?

I just did a clean build starting from `cscript.exe bootstrap_win_dev.vbs`, no 
problems at all.

What errors are you getting? Last we heard from you,  you'd gotten past the sed 
crash caused by using the wrong msys shell.

Regards,
John Ralls

I unistalled cygwin using its install program. Now I am in the process of 
removing the cygwin directory completely.
I will try again when I have done it.
Thanks for your help
Regards
Stephen Brown
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Using make with docs

[David T. via gnucash-devel]

Geert,

> On Feb 6, 2017, at 10:10 PM, Geert Janssens  
> wrote:
> 
> Op maandag 6 februari 2017 21:28:24 CET schreef David T. via gnucash-devel:
>> Hello,
>> 
>> The recently-updated Documentation Update Instructions page on the wiki—as
>> detailed as they are—nonetheless leave something to be desired when one
>> reaches step 10. You see, up until this point, a great deal of energy is
>> put into showing how one can use “make check” in different ways to test
>> either the Guide, or the Help, or the different translations.
>> 
>> Once you get to actually compiling these docs, though, the directions dry up
>> and just tell the user to "make html” in "the appropriate directory within
>> the build directory structure.” (ADWTBDS)
>> 
>> Two points:
>> 
>> 1) when I issue “make check”, I am in the working directory, and if you’re
>> stupid or inattentive (both of which apparently apply to me), you issue the
>> “make html” command without first changing to the ADWTBDS.
> Acutally, make check is also meant to be run in the build directory. *All* 
> make commands are intended to be executed in the build directory or one if 
> its 
> subdirectories. I'm not sure this is very clearly specified in the wiki page.
> 
> The fact you can run "make check" in your working directory implies you have 
> in the past run configure in your working directory. By that action you have 
> configured your working directory to double as a build directory. It would 
> simplify your life if you remove these configure actions from the working 
> directory again. By doing so, running "make " there would give an 
> error like this:
> make: *** No rule to make target 'check'.  Stop.
> 

No doubt this has something to do with earlier setup issues (steps 3 & 4). Or 
it has to do with the fact that the earlier method (calling xmllint and 
xsltproc directly) was invoked in the working directory, with output directed 
to a different folder directly, and I learned that way and kept doing it (like 
the proverbial lemming of Arthur Clarke’s short story).

I reiterate my wish to see documentation that covers *setting up a build 
system* separated from information *directly related to the documentation 
update process*. Having a separate setup page would allow those of us who 
struggle with every aspect of this process to be able to get set up, and then 
focus on screwing up only the actual steps for updating, rather than the whole 
shebang.


> That should solve your problem of accidentally building the html docs in your 
> git working directory.
> 
> The easiest way to remove the files set up by configure would be:
> - cd into to root of your local git repository (the level where you see guide 
> and help as subdirectories)
> - run: "make distclean" (without the quotes)
> - and finally rerun "./autogen.sh" (again without the quotes)
> 
>> This results in
>> the docs being built right there in the working directory. Not horrible,
>> but potentially messy (especially if you forget to remove the folder before
>> going back to git).
>> 
>> 2) If I change to my build directory, “make html” builds all the docs, which
>> is a collossal waste of time when all I want to do is compile the Guide in
>> (say) English—which is all I worked on in the first place. I personally
>> don’t plan on ever editing the Portugese, German, Italian, or Japanese
>> translations.
>> 
>> So, two questions:
>> 
>> 1) Is there a way to configure the make command to use my build directory as
>> its destination, while running from the working directory?
> Not that I know of.
>> 2) Is there a
>> way to make just the html of one portion of the docs, without making all
>> docs in all languages?
> Yes. You can do so by invoking "make html" in the exact build subdirectory 
> that matches the subdirectory in your git repository. For example to build 
> the 
> English guide as html, you would starting from your build directory
> cd guide/C
> make html
> 
> "The appropriate directory in the build directory structure" was meant to 
> suggest exactly that. I see the way it's formulated is still too developer-
> mind oriented. Sorry about that. Perhaps "the equivalent subdirectory under 
> the build directory" is more clear ? How would you propose to better describe 
> this ?
> 
> Geert


Thank you for clearly outlining to me (once more!) how to handle these issues. 
I will look into better ways of wording things to make it clearer to others.

Cheers,
David

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Using make with docs

[John Ralls]

> On Feb 6, 2017, at 8:28 AM, David T. via gnucash-devel 
>  wrote:
> 
> Hello,
> 
> The recently-updated Documentation Update Instructions page on the wiki—as 
> detailed as they are—nonetheless leave something to be desired when one 
> reaches step 10. You see, up until this point, a great deal of energy is put 
> into showing how one can use “make check” in different ways to test either 
> the Guide, or the Help, or the different translations. 
> 
> Once you get to actually compiling these docs, though, the directions dry up 
> and just tell the user to "make html” in "the appropriate directory within 
> the build directory structure.” (ADWTBDS) 
> 
> Two points:
> 
> 1) when I issue “make check”, I am in the working directory, and if you’re 
> stupid or inattentive (both of which apparently apply to me), you issue the 
> “make html” command without first changing to the ADWTBDS. This results in 
> the docs being built right there in the working directory. Not horrible, but 
> potentially messy (especially if you forget to remove the folder before going 
> back to git).
> 
> 2) If I change to my build directory, “make html” builds all the docs, which 
> is a collossal waste of time when all I want to do is compile the Guide in 
> (say) English—which is all I worked on in the first place. I personally don’t 
> plan on ever editing the Portugese, German, Italian, or Japanese translations.
> 
> So, two questions:
> 
> 1) Is there a way to configure the make command to use my build directory as 
> its destination, while running from the working directory?
> 2) Is there a way to make just the html of one portion of the docs, without 
> making all docs in all languages?

David,
Geert beat me to the answer, but another tip:
I find it useful to have two tabs open in terminal, one in the source directory 
and one in the build directory. That makes it easy to flip back and forth 
between building and doing source stuff.

Regards,
John Ralls


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Using make with docs

[Geert Janssens]

Op maandag 6 februari 2017 21:28:24 CET schreef David T. via gnucash-devel:
> Hello,
> 
> The recently-updated Documentation Update Instructions page on the wiki—as
> detailed as they are—nonetheless leave something to be desired when one
> reaches step 10. You see, up until this point, a great deal of energy is
> put into showing how one can use “make check” in different ways to test
> either the Guide, or the Help, or the different translations.
> 
> Once you get to actually compiling these docs, though, the directions dry up
> and just tell the user to "make html” in "the appropriate directory within
> the build directory structure.” (ADWTBDS)
> 
> Two points:
> 
> 1) when I issue “make check”, I am in the working directory, and if you’re
> stupid or inattentive (both of which apparently apply to me), you issue the
> “make html” command without first changing to the ADWTBDS.
Acutally, make check is also meant to be run in the build directory. *All* 
make commands are intended to be executed in the build directory or one if its 
subdirectories. I'm not sure this is very clearly specified in the wiki page.

The fact you can run "make check" in your working directory implies you have 
in the past run configure in your working directory. By that action you have 
configured your working directory to double as a build directory. It would 
simplify your life if you remove these configure actions from the working 
directory again. By doing so, running "make " there would give an 
error like this:
make: *** No rule to make target 'check'.  Stop.

That should solve your problem of accidentally building the html docs in your 
git working directory.

The easiest way to remove the files set up by configure would be:
- cd into to root of your local git repository (the level where you see guide 
and help as subdirectories)
- run: "make distclean" (without the quotes)
- and finally rerun "./autogen.sh" (again without the quotes)

> This results in
> the docs being built right there in the working directory. Not horrible,
> but potentially messy (especially if you forget to remove the folder before
> going back to git).
> 
> 2) If I change to my build directory, “make html” builds all the docs, which
> is a collossal waste of time when all I want to do is compile the Guide in
> (say) English—which is all I worked on in the first place. I personally
> don’t plan on ever editing the Portugese, German, Italian, or Japanese
> translations.
> 
> So, two questions:
> 
> 1) Is there a way to configure the make command to use my build directory as
> its destination, while running from the working directory?
Not that I know of.
> 2) Is there a
> way to make just the html of one portion of the docs, without making all
> docs in all languages?
Yes. You can do so by invoking "make html" in the exact build subdirectory 
that matches the subdirectory in your git repository. For example to build the 
English guide as html, you would starting from your build directory
cd guide/C
make html

"The appropriate directory in the build directory structure" was meant to 
suggest exactly that. I see the way it's formulated is still too developer-
mind oriented. Sorry about that. Perhaps "the equivalent subdirectory under 
the build directory" is more clear ? How would you propose to better describe 
this ?

Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Using make with docs

[David T. via gnucash-devel]

Hello,

The recently-updated Documentation Update Instructions page on the wiki—as 
detailed as they are—nonetheless leave something to be desired when one reaches 
step 10. You see, up until this point, a great deal of energy is put into 
showing how one can use “make check” in different ways to test either the 
Guide, or the Help, or the different translations. 

Once you get to actually compiling these docs, though, the directions dry up 
and just tell the user to "make html” in "the appropriate directory within the 
build directory structure.” (ADWTBDS) 

Two points:

1) when I issue “make check”, I am in the working directory, and if you’re 
stupid or inattentive (both of which apparently apply to me), you issue the 
“make html” command without first changing to the ADWTBDS. This results in the 
docs being built right there in the working directory. Not horrible, but 
potentially messy (especially if you forget to remove the folder before going 
back to git).

2) If I change to my build directory, “make html” builds all the docs, which is 
a collossal waste of time when all I want to do is compile the Guide in (say) 
English—which is all I worked on in the first place. I personally don’t plan on 
ever editing the Portugese, German, Italian, or Japanese translations.

So, two questions:

1) Is there a way to configure the make command to use my build directory as 
its destination, while running from the working directory?
2) Is there a way to make just the html of one portion of the docs, without 
making all docs in all languages?

TIA,
David

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel