From: Bill White <billw@wolfram.com>
Subject: Re: gnuscash?
Date: Thu, 20 Mar 2003 09:54:39 -0600 [thread overview]
Message-ID: <ruowuiukp8g.fsf@billwlx.wolfram.com> (raw)
In-Reply-To: <864r5yoxpx.fsf@ieee.org> (Jorge Godoy's message of "Thu, 20 Mar 2003 12:37:46 -0300")
On Thu Mar 20 2003 at 09:37, Jorge Godoy <godoy@metalab.unc.edu> said:
> 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? ;-)
Ah - yes. A gnucash file as some sort of remote server. You'd also
need to be able to import QIF and whatever else online banks export.
Heck, use your bank's web interface as an online gnuscash server, log
in & interact via http (behind the scenes).
> I'd rather use it's report facilities + double entry system.
I'd like to, if I could get the blasted !@#$!@# thing to compile.
Interaction with gnus has entered my very DNA, it seems, so it would
be, um, handy or something if I could truly do everything in gnus,
"the coffee-brewing, all singing, all dancing, kitchen sink
newsreader." It would be so nifty I might actually get around to
balancing my checkbook.
There's probably a principle that requires gnus to expand until it can
do everything.
bw
--
Bill White Office: 5N-X30
Documentation Programmer Phone: 217-398-0700 x 234
Wolfram Research Fax: 217-398-0747
http://members.wri.com/billw Office hours: 4am-noon Mon-Fri
prev parent reply other threads:[~2003-03-20 15:54 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 ` gnuscash? Jorge Godoy
2003-03-20 15:54 ` Bill White [this message]
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=ruowuiukp8g.fsf@billwlx.wolfram.com \
--to=billw@wolfram.com \
/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).