Gnus development mailing list
 help / color / mirror / Atom feed
From: Jorge Godoy <godoy@metalab.unc.edu>
Cc: ding <ding@gnus.org>
Subject: Re: gnuscash?
Date: Thu, 20 Mar 2003 12:37:46 -0300	[thread overview]
Message-ID: <864r5yoxpx.fsf@ieee.org> (raw)
In-Reply-To: <ruobs07acgp.fsf@billwlx.wolfram.com> (Bill White's message of "Wed, 19 Mar 2003 04:16:06 -0600")

Bill White <billw@wolfram.com> writes:

> A nutty driving-to-work-half-asleep idea:
>
> - a server/backend/group buffer that lists accounts & their balances
>
> - a summary buffer that summarizes transactions in an account
>
> - an article buffer that shows all the details of a transaction
>
> Any thoughts?

Read & write Gnucash files? ;-)

I'd rather use it's report facilities + double entry system.


See you,
-- 
Godoy.    <godoy@metalab.unc.edu>



  reply	other threads:[~2003-03-20 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 10:16 gnuscash? Bill White
2003-03-20 15:37 ` Jorge Godoy [this message]
2003-03-20 15:54   ` gnuscash? Bill White

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864r5yoxpx.fsf@ieee.org \
    --to=godoy@metalab.unc.edu \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).