[GNC] v3.8: Budget "total" field

[John Ralls]

Switching users isn't onerous as long as you use simple passwords--you do have to type it every time you switch--and it's easy to create a folder in your main user's $HOME to collect stuff:
https://support.apple.com/guide/mac-help/control-access-to-your-public-folder-on-mac-mchlp1775/mac.

If that's still too much trouble you can set GNC_DATA_DIR and GNC_CONFIG_DIR in the non-production bundle's Contents/Resources/etc/gnucash/environment to point somewhere other than ~/Library/Application Support/Gnucash. Preferences go to ~/Library/Preferences/org.gnucash.Gnucash no matter what, but that's probably not a concern in most cases.

Regards,
John Ralls
> On Jan 3, 2020, at 9:45 AM, Adrien Monteleone <adrien.monteleone at lusfiber.net> wrote:
> 
> I’m considering that approach, but that would mean switching users just for testing. I suppose I could set up some sort of common folder to save screen shots and crash reports as I don’t want to have activity in the test user not be available to me in my main account. If Mac had some sort of container system like linux or if I could easily run it in a VM (without a large GB virtual disk) I’d prefer that route but that doesn’t seem possible right now.
> 
> Regards,
> Adrien
> 
>> On Jan 3, 2020 w1d3, at 4:04 AM, Michael Hendry <hendry.michael at gmail.com> wrote:
>> 
>>> On 3 Jan 2020, at 01:35, Adrien Monteleone via gnucash-user <gnucash-user at gnucash.org> wrote:
>>> 
>>> I thought that was discussed, but delving into the bug threads and others linked therein, I see the issue a bit more clearly.
>>> 
>>> Certainly, I think the current underlying approach is the more sane one long term with a few kinks to be worked out.
>>> 
>>> I (sadly and apologetically) still haven’t worked out a way to test dev versions on MacOS without disrupting my normal installation, but I can test non-OS specific changes via VMs. (I can certainly build maint or other branches in Ubuntu) If anyone has any suggestions or tips for testing maint and other builds on the MacOS front *without disturbing my normal stable installation* , they are certainly appreciated.
>> 
>> I haven’t tried this, but why not create a new user (e.g. “GCTest”) and run any experimental versions as that user. This would protect your own .gnucash files and configuration settings, as these are per-user, not per-computer.
>> 
>> Michael
>> 
>>> 
>>> I’m getting ready next week to work on my 2020 budgets, so now would be a good time to do some testing.
>>> 
>>> Let me know what types of things you’d like to see answers to and I’ll do what I can. (in a Linux version for now, as noted)
>>> 
>>> Regards,
>>> Adrien
> 
> 
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.