On Sat, Jul 08, 2000 at 10:36:26AM -0500, Christopher Browne wrote:
On Sat, 08 Jul 2000 10:17:52 EST, the world broke into rejoicing as
Richard Wackerbarth [EMAIL PROTECTED] said:
Although this is functional, I object to re-denomination because
the auditors want the ledger to match the
On Thu, Jul 06, 2000 at 12:04:30PM -0500, Jon Trowbridge wrote:
For example, certain UK Govt Bonds have decimalized recently. They
were previously quoted in 32nds, and are now quoted in 100ths. This
is particularly annoying, since you can't convert old prices to new
without loss of
On Wed, Jun 21, 2000 at 07:18:20PM -0700, Dave Peticolas wrote:
Autosaving: every autosave_period() time units {
if (database_has_changed()) {
save_database_to_file("original name.autosave");
if (error)
report_error_to_gui();
On Thu, Jun 22, 2000 at 01:40:30AM -0700, Dave Peticolas wrote:
Probably the temporary files should be in /tmp or /usr/tmp and contain
the process number.
If we put them in /tmp, then we really need to use something like
mkstemp(char *template) to get a unique name. But I'm not sure we
On Thu, Jun 15, 2000 at 07:41:29PM -0500, Richard Wackerbarth wrote:
On Thu, 15 Jun 2000, Dave Peticolas wrote:
Now, those .xac files - are they the previous data file, or are they
written in parallel with the main file? (Or copied after the main file
is written?)
They are written
On Sat, Jun 03, 2000 at 10:20:40AM -0700, Peter C. Norton wrote:
On Sat, Jun 03, 2000 at 05:01:51AM -0500, Richard Wackerbarth wrote:
I agree. Using gint32 rather than int only solves part of the problem.
foo_t is much more flexible.It reduces the architecture dependency to a
single point
On Wed, May 24, 2000 at 10:21:12PM -0500, Christopher Browne wrote:
...stuff about library problem...
I don't see there being _massive_ value to designing anything to this
end.
In particular, it seems like Helix Code has raised a lot of capital to
address exactly this problem for programs very
Sorry to ask a stupid question, but what good are the logs that GnuCash
writes out? They have lots of information, but I can't see any convenient
way to use it (without doing some programming).
In particular, when I forget to quit GnuCash before quitting X, I seem
to get a log file but no saved
On Thu, May 18, 2000 at 07:55:01AM -0500, Richard Wackerbarth wrote:
...
I think that that is the mistake. It is ONE TRANSACTION. When displaying a
transaction we should show each of the JEs and sort them so that those
applying to the current account are sorted first.
If you collapse
On Thu, May 18, 2000 at 11:20:53AM -0500, Rob Browning wrote:
I would ALWAYS make data entry a multi-line mode.
...
However, I agree that in your proposal, which drops the transaction
line, this might be viable. There would really be no difference
between single and multi-line modes.
On Tue, May 16, 2000 at 03:35:26PM +0200, Herbert Thoma wrote:
Arnold Troeger wrote:
I have a couple of problems with gnucash 1.3.7: 1) Total assets are
calculated from all the categories independent of the category's
currency. I have accounts defined in US Dollars and Thai Baht. It
I just noticed a consequence of Memos being associated with Journal
Entries and not Transactions: Even for a simple transaction without
splits, only one side of the transaction sees the memo. Furthermore,
which side sees the memo is different in the "Double Line" and "Multi
Line" views. This
On Mon, May 15, 2000 at 11:34:17PM -0500, Christopher Browne wrote:
Surprise, you are using a double-entry ledger system :) That is, unless
you are leaving all of your 'transfer from' fields blanks, all of your
entries in checking account have a matching entry in an expense, income,
etc.
On Thu, May 11, 2000 at 12:16:18AM -0500, [EMAIL PROTECTED] wrote:
It's been rumoured that Dylan Paul Thurston said:
I was curious about this last statement, and, having never used
PostgreSQL, decided to test it. I downloaded PostgreSQL 7.0-beta5
from the Debian distribution, installed
On Wed, May 10, 2000 at 06:26:20PM -0500, Bill Gribble wrote:
Richard Wackerbarth [EMAIL PROTECTED] writes:
That is a "religious" reaction. MySQL is limited for only some
users. For all practical purposes, MySQL is "free" for a major
portion of the potential user base.
It's not free for
On Wed, May 10, 2000 at 05:38:50PM -0500, Richard Wackerbarth wrote:
so I don't see why you would consider MySQL at all.
PostgresSQL is more expensive in terms of cpu (probably not significant) and
administration complexity (VERY important)
I was curious about this last statement, and,
16 matches
Mail list logo
