Kevin,
Kevin Benton <[EMAIL PROTECTED]> writes:
> So, If I understand this correctly, then I can't move to the PG backend
> yet because it doesn't support all my needs - scheduled transactions
> being one of the most important needs on my list...
>
> I know that I may sound a bit like a thorn in
So, If I understand this correctly, then I can't move to the PG backend yet because it doesn't support all my needs - scheduled transactions being one of the most important needs on my list...
I know that I may sound a bit like a thorn in the side, but I try to bring to the table a sense of ho
On Mon, 2003-03-10 at 16:08, Kevin Benton wrote:
> Those are good ideas. One other thing we could do is to have GNUCash
> continuously update its files (database) on the fly and leave them in a
> state where a kill would not be catastrophic. Quicken seems to do the
> same thing. I think we shoul
problem is... I'm a heavy user of Scheduled Transactions and there is no
support in the Prostgres backend for SX's (yet). But, yes, I agree, the
Postgres backend would be more appropriate for that kinda thing.
On 3/10/2003 12:06 PM, someone claiming to be Derek Atkins wrote:
If you want this, us
If you want this, use the Postgres backend. That's what it's
for.
-derek
Kevin Benton <[EMAIL PROTECTED]> writes:
> Those are good ideas. One other thing we could do is to have GNUCash
> continuously update its files (database) on the fly and leave them in a
> state where a kill would not be c
This is probably slightly easier than reading log files, and will
handle data _other_ that just transactional changes However
we would need to be careful about this -- it should only happen for
_some_ backends (i.e. only the File Backend). Perhaps that means
we need an extension to
On 10 Mar 2003 11:24:38 -0500, Derek Atkins <[EMAIL PROTECTED]> wrote:
lmb <[EMAIL PROTECTED]> writes:
gnucash _really_ needs an "save on exit" functionality, I think. (I
can't do
it, my scheme sucks) Unix programs have been doing it for ages on
receiving a
SIGHUP.
Gnucash does try to save on e
Well, another option that we discussed on #gnucash last night
was an autosave file _to a different filename_ -- ALA emacs'
autosave. This file gets auto-written periodically as you make
changes to the data. If you've made no changes, then nothing gets
written. When you "save", the autosave file
lmb <[EMAIL PROTECTED]> writes:
> gnucash _really_ needs an "save on exit" functionality, I think. (I can't do
> it, my scheme sucks) Unix programs have been doing it for ages on receiving a
> SIGHUP.
Gnucash does try to save on exit if you exit cleanly. At least it
asks you if you want to save
Those are good ideas. One other thing we could do is to have GNUCash continuously update its files (database) on the fly and leave them in a state where a kill would not be catastrophic. Quicken seems to do the same thing. I think we should be able to handle a ctl-alt-backspace, or worse, a
On 3/10/2003 8:54 AM, someone claiming to be Nigel Titley wrote:
On Mon, 2003-03-10 at 13:39, Greg Troxel wrote:
Nope. Just like there is no way for gnucash to stop you from
unplugging your computer or turning it off. Exiting gnome is
outside the purvue of gnucash. By the time gnucash gets t
On Mon, 2003-03-10 at 13:39, Greg Troxel wrote:
> Nope. Just like there is no way for gnucash to stop you from
> unplugging your computer or turning it off. Exiting gnome is
> outside the purvue of gnucash. By the time gnucash gets told
> that gnome is going away, you have no more UI.
O
Nope. Just like there is no way for gnucash to stop you from
unplugging your computer or turning it off. Exiting gnome is
outside the purvue of gnucash. By the time gnucash gets told
that gnome is going away, you have no more UI.
I went to look up this issue in the Gnome HIG, and did no
On 2003-03-09T21:16:00,
Derek Atkins <[EMAIL PROTECTED]> said:
> "Save Early, Save Often".
>
> Hitting the "save" button is easy. Just Do It.
gnucash _really_ needs an "save on exit" functionality, I think. (I can't do
it, my scheme sucks) Unix programs have been doing it for ages on receivi
don Paolo Benvenuto <[EMAIL PROTECTED]> writes:
> Hi guys! I found a rather inquieting thing.
>
> If I exit from gnome without saving gnucash data, my work is lost: gnucash
> doesn't stop gnome from exiting in order to ask me whether I want to save my
> data or not (as for example gedit does).
Hi guys! I found a rather inquieting thing.
If I exit from gnome without saving gnucash data, my work is lost: gnucash
doesn't stop gnome from exiting in order to ask me whether I want to save my
data or not (as for example gedit does).
Isn't there a way to avoid this dangerous behaviour?
Buon
16 matches
Mail list logo
