Suffering Redhat Users:
You can take some heart. I've compiled and used gnucash 1.2.x on my
redhat 6.0 system, and I even have some (source) rpms around to ease the
port. I can send these to anyone who would like a copy.
Check out the mailing list archive for August, 1999 "War story:
installing gnucash 1.2.3 os stock redhat 6.0" under my name.
That being said, I've found recent CVS versions to be more stable. A
couple of bugs that I found creating accounts were squashed. I've been
using it to keep my accounts in since sept.
There are still a few crashes and such, so take precautions !
Personally, I:
*) make a backup of my accounts before every time I use gnucash
*) save often
Additionally, there are some freaky usability problems, for instance:
*) The tab key doesn't always change which field is "active" in the
way that you'd expect, especially when using different account views
(two-line, multi-line, etc.) Mouse free operation doesn't seem possible.
:-/
*) The "fill in the transaction name" feature, where gnucash guesses
what the text should be in the transaction name field and tries to fill
it in, has some glitches, namely:
-) only uses as history the list of transactions currently
displayed. No independant list of transaction names seems to be
stored. (which would be a neat addition, btw, especially if the
transaction name was also filtered by category, er account name)
-) if you're going to type in a new transaction name which
_partially_ matches an existing transaction, the field is filled in with
the match gnucash finds as you type (as expected), however, when what
you type diverges from the match found, gnucash doesn't clean up the
name field. Instead, you find yourself inserting new characters in the
middle of the partial name match it found.
-) If the field already has a name in it, and you want to go back
and change the first character, leaving the rest of the field intact,
(say you have a new transaction name, and you want to change the
capitolization) gnucash will start matching all over again, overwriting
whatever you have in that field
*) Account transfers from back accounts to stock accounts are credited
incorrectly in the stock account. The newly created transaction in the
stock account should credit the money in it's value column, instead it
puts it in the #shares column, which completely fucks things up.
*) When changing the range of dates of listed transactions in an
account window, the date entry field in the lower right hand column
doesn't accept typing as you'd expect. For example, try highlighting
the month and day and overtyping it.
*) It doesn't appear to be possible to move accounts in a account
hierarchy after that account has been created.
*) I can't find the right Perl package to do automatic price updates
for stock accounts. rpmfind doesn't think it exists, anymore.
For all these problems, though, I've found the program to be very
powerful. Especially if you're adventurous, it's worth your time to use
it, just so that the extra bugs can be squashed.
-- Pat
p.s. if anyone wants a more complete bug report for any of the problems
I list above, please let me know.
"Paul L. Lussier" wrote:
>
> In a message dated: 13 Oct 1999 05:03:24 PDT
> Harry Putnam said:
>
> >Cbb can import or export *.qif (quicken) files, and I think I remember
> >seeing in gnucash documentaton where it can too, so that would handle
> >at least some data transfer.
>
> The on drawback to cbb is that it does not support recurring transactions
> containing splits involving transfers, or something like that.
>
> For now I'm continuing on with Quicken 4 under Wine :) Of course, as y2k
> draws closer, I'll have to start thinking about something else, since Q4 is
> non-y2k compliant :(
>
> What are the chances of GnuCash being stable and usable by us mere mortals by
> then? :)
>
> --
>
> Seeya,
> Paul
> ----
> Depression is merely anger without enthusiasm.
> There cannot be a crisis today; my schedule is already full.
> A conclusion is simply the place where you got tired of thinking.
> If you're not having fun, you're not doing it right!
>
> --
> Gnucash Developer's List
> To unsubscribe send empty email to: [EMAIL PROTECTED]
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
