2019-02-10 GnuCash IRC logs
00:29:48 *** nimish has quit IRC
00:30:00 *** nimish_ has joined #gnucash
00:30:20 *** nimish_ is now known as nimish
01:06:32 *** fell has quit IRC
01:06:32 *** Mechtilde has joined #gnucash
01:07:50 *** fell has joined #gnucash
01:56:06 *** storyjesse has joined #gnucash
01:58:11 *** storyjesse has quit IRC
03:02:39 *** gour has joined #gnucash
04:17:46 *** nimish has quit IRC
04:21:55 *** nimish has joined #gnucash
04:39:56 *** boldstripe has joined #gnucash
05:07:02 *** boldstripe has quit IRC
05:08:13 *** boldstripe has joined #gnucash
05:10:53 *** boldstripe_ has joined #gnucash
05:11:19 *** boldstripe has quit IRC
05:11:19 *** boldstripe_ is now known as boldstripe
05:28:47 *** KevinDB has quit IRC
05:32:31 *** KevinDB has joined #gnucash
05:32:51 *** guiloma has joined #gnucash
05:36:32 *** boldstripe_ has joined #gnucash
05:36:47 *** boldstripe has quit IRC
05:36:47 *** boldstripe_ is now known as boldstripe
05:43:00 *** fabior has joined #gnucash
06:32:20 *** kritzefitz has joined #gnucash
06:34:44 <kritzefitz> I regularly have transactions where money leaves an account earlier/later than it arrives at the target account. Is there a best practice on how to enter such transactions in Gnucash?
07:08:10 *** fabior has quit IRC
07:20:09 *** FoxT has quit IRC
07:26:18 *** FoxT has joined #gnucash
07:31:49 *** guiloma has quit IRC
07:32:10 *** guiloma has joined #gnucash
07:43:47 *** User has joined #gnucash
07:57:10 *** boldstripe_ has joined #gnucash
07:57:26 *** boldstripe has quit IRC
07:57:26 *** boldstripe_ is now known as boldstripe
08:01:38 *** Jimraehl1 has joined #gnucash
08:02:17 *** Jimraehl1 has left #gnucash
08:05:31 <chris> gjanssens - do we want to stop a couple of crashers? e.g. if loading saved-reports saved in newer version, by an older version Gnucash.
08:21:37 <gjanssens> chris: what do you propose ?
08:22:10 <gjanssens> In itself it's something ucommon to happen
08:22:22 <gjanssens> Because if the format of saved-reports changes, the version number should go up
08:22:38 <chris> e.g. i augment date-options to allow 'start-book-accounting-period, then save a tab/report
08:22:54 <chris> then I switch to older version, try reload tab -> report crash
08:23:07 <chris> then I load 'report options' dialog -> segfault
08:23:26 <chris> i can fix both - default date to (current-time),
08:23:29 <gjanssens> Ok, that's not saved-reports in my mind, but a report saved in .gcm
08:23:42 <gjanssens> But I do see your point
08:23:55 <chris> and if report-options cannot find the saved-report-item (eg start-book-accounting-period) it defaults to the first one 'today'
08:24:27 <chris> I'll tack at the end of maint-bugfixes
08:24:35 <gjanssens> Ok
08:25:18 <chris> there should be a gnc-error-dialog warning though,i'll see if i can use it
08:29:53 *** User has quit IRC
08:30:56 *** Agfarmer18 has joined #gnucash
08:34:51 <warlord> chris, there are lots of wrapped functions. take a look at the various .i files ;)
08:35:26 <warlord> chris, re Feb 29, that sounds reasonable to me
08:36:19 <warlord> kritzefitz, most people ignore the time difference. If the time difference REALLY REALLY matters to you then you need to use a suspense account to hold the funds while they transfer. Note that if you go this route, you will lose the connection between source and destination.
08:38:31 <kritzefitz> warlord, thanks. I guess the difference isn't actually that important to me. It was just slightly bugging me that transactions aren't “right”.
08:40:46 <warlord> Think about it this way -- if you write a check to someone, it can take days or weeks before they cash it! You should record the check immediately, but it will take a while to clear.
08:41:01 *** oozer has joined #gnucash
08:41:07 <warlord> This is what the 'cleared' flag is for -- so you can mark when the transaction is actually processed by the account.
08:46:54 <kritzefitz> warlord, Ah, so that's what that is for.
08:48:03 * warlord nods
08:48:13 <warlord> yes, to mark when a transaction has cleared the account.
08:48:33 <warlord> And then the reconcile (y) flag means you've done your periodic (monthly) reconciliation against your bank statements
08:50:27 <kritzefitz> Yes, that's what I've already been doing.
08:51:25 <warlord> ok.
08:53:24 <kritzefitz> Thanks for clarifying!
08:54:01 * chris would be keen for some progress in scheme commits... getting hard to switch all these branches all the time
09:06:26 <gjanssens> chris: I lost track of what's ready for merge :(
09:08:46 <chris> well, maint-scheme-progress aims to be refactoring/cleanup only, so, all *should* be safe...
09:09:09 <chris> maint-bugfixes aims to fix problems/add functionality perhaps warrant more scrutiny
09:11:36 *** chris has quit IRC
09:14:57 *** chris has joined #gnucash
09:17:41 *** Agfarmer18 has quit IRC
09:20:02 *** fabior has joined #gnucash
09:35:30 <gjanssens> chris: ok, I'll try to work on those in the coming days
09:47:15 *** guiloma has quit IRC
09:50:32 *** trying2Simplify has joined #gnucash
09:52:39 *** trying2Simplify has quit IRC
09:55:19 <chris> thx, please cherry pick from the earlier commits; I think is safest!
10:00:16 <chris> hmm re: last commit, I wonder if it wouldn't be safer to retain the report crashers.... because my fix will prevent crash but produce an unexpected report. i tried gnc-error-dialog but I think there's a cmake issue that doesn't allow loading gnome modules in options.scm and date-utilities.scm. so i've removed the error dialog in the commits.
10:10:11 <gjanssens> chris: indeed you can't use gui code in the engine so you won't be able to display a dialog box directly
10:10:36 <gjanssens> Which is yet another fundamental design issue to clean up at some point
10:11:11 <chris> ok... i was able to make it work while hotfixing, but the rebuild failed.
10:18:34 *** chris has quit IRC
10:18:40 *** tane has joined #gnucash
10:21:12 *** kritzefitz has left #gnucash
10:21:39 *** chris has joined #gnucash
10:27:15 *** chris has quit IRC
10:37:19 *** chris has joined #gnucash
11:00:33 *** bertbob has quit IRC
11:10:36 *** bertbob has joined #gnucash
11:18:50 *** fabior has quit IRC
11:23:58 *** tane has quit IRC
11:49:01 *** trying2Simplify has joined #gnucash
11:49:11 *** trying2Simplify has quit IRC
11:54:21 *** trying2Simplify has joined #gnucash
12:15:23 *** nimish has quit IRC
12:16:06 *** nimish has joined #gnucash
12:23:18 *** trying2Simplify has quit IRC
12:56:45 *** lcanaska has joined #gnucash
12:57:09 *** lcanaska has quit IRC
12:57:14 *** lcanaska has joined #gnucash
13:00:23 <lcanaska> Hello, new one here for chatting.
13:01:05 <lcanaska> Having grief with program backup file."That database may be on a read-only file system,"
13:03:53 <lcanaska> more accurately the message is " That database may be on a read-only file system, or you may not have write permission for the directory."
13:06:07 <lcanaska> *recently installed Bitdefender. message popped about file gnucash being read only. Message disappeared without fully understanding the implications.
13:26:20 *** nimish has quit IRC
13:40:18 *** nimish has joined #gnucash
13:44:17 *** nimish_ has joined #gnucash
13:44:59 *** nimish has quit IRC
13:45:05 *** nimish_ is now known as nimish
14:31:03 *** oozer has quit IRC
15:08:20 *** Mechtilde has quit IRC
15:08:46 *** jervin has joined #gnucash
15:10:25 *** jervin has quit IRC
15:52:39 *** tienne has joined #gnucash
16:09:57 *** boldstripe has quit IRC
16:13:38 <lcanaska> Discovered main folder and sub folder GNUcash HAD read only atribute. HOW that happened, went unnoticed. Lets see if this solves issue.
16:21:53 *** puck has quit IRC
16:25:29 *** puck has joined #gnucash
17:28:42 *** gjanssens has quit IRC
17:50:38 *** gour has quit IRC
18:08:52 <lcanaska> quit:
18:09:03 *** lcanaska has left #gnucash
18:31:32 *** Aussie_matt has joined #gnucash
18:50:19 *** mipesom has joined #gnucash
18:56:29 *** chris has quit IRC
19:00:46 *** tienne has quit IRC
19:19:05 *** oozer has joined #gnucash
20:12:40 *** marusich has joined #gnucash
20:34:01 *** jervin has joined #gnucash
21:03:30 *** jervin has quit IRC
21:15:35 *** oozer has quit IRC