On Thu, Oct 29, 2009 at 23:22, ~suv <suv-sf@...58...> wrote:
I have been running your Inkscape development snapshots and later my own SVN builds with custom shell launcher scripts (script, openDoc and bin/inkscape), and have my normal shell environment (set with ~/.profile - a symbolic link to ~/.bash_profile - and ~/.bashrc) in Inkscape available by using a login shell in the first level (script and openDoc) which automatically sources the default startup files of my $SHELL (whatever that might be). See bug #383456 “[OS X] launch Inkscape with a login shell” https://bugs.launchpad.net/inkscape/+bug/383456 where I filed my initial ideas. That report is quite old and I have learned a lot since, but basically the attached patch is what gets the user configuration into the shell launcher script for inkscape-bin.
I never realized this. From your bug report, I would say that updating script exec would be the best solution but for now the bash --login will do. I'll commit that as soon as the trunk reopens.
Please let me know what you think,
If this is something you might consider I could attach my current launch scripts to bug #383456 (status 'work-in-progress': additionally they log all inkscape console output into a separate file, add a time stamp, PID and list some env variables plus any arguments to inkscape-bin e.g. when called by a python extension script - mainly debugging info not of interest for the regular Inkscape user).
This would be welcome indeed. I would suggest, however, to make it a new bug report/blueprint, assigned to me, that reads "Adding debugging output to Inkscape on OS X" or something.
Thanks a lot,
JiHO --- http://maururu.net