Re: [PATCH 0/2] PSPP shared library refinements

[bojo42]

Testing the newest package on my production system (Ubuntu 10.04) i also
got the problem with a non written "psppirerc". XDG_CONFIG_HOME was also
missing from env and the rest is also just the same.

I never noticed it, as i rarely use PSPP atm and i already got a present
"psppirerc". As i am more a packager and much less a developer i can't
easyly follow you diagnosting advice. But since it's not a new Ubuntu
issue i may ask, if you've ever noticed such a behaviour on your own
systems?

Am Donnerstag, den 02.02.2012, 07:33 +0000 schrieb John Darrington:
> On Thu, Feb 02, 2012 at 12:06:39AM +0100, Bojo42 wrote:
> > Am 01.02.2012 09:13, schrieb John Darrington:
> >> On Wed, Feb 01, 2012 at 01:28:25AM +0100, Bojo42 wrote:
> >>>> However for psppire, the last chosen size of the window is saved in 
> >>>> the user's config and used for subsequent runs. This way, once he  
> >>>> sets the window dimensions how he likes them, he will get continue  
> >>>> to get those dimensions until he changes them again. 
> >>> That's also not working, i get a small window on each startup with no 
> >>> opened files. 
> >> Then there is a problem. Can you check that after you have run  
> >> psppire, a directory called "psppirerc" exists in your XDG_CONFIG_HOME  
> >> directory. This is normally set to $HOME/.config - but I notice Debian  
> >> has pacakges which fiddle with this setting - perhaps that's  
> >> interacting with psppire in an adverse way?
> >
> > Hmm that is all kind of weird, first XDG_CONFIG_HOME was not in my  
> > enviroment, so i did got this correct. I also found that  
> > "$XDG_CONFIG_HOME/psppirerc" but was a file not a dir:
> 
> I should have written "file", NOT "directory".  Sorry for the confusion.
> 
> > After resizing the windows  the file didn't change at all, neither did  
> > startup size and position. So i tried deleting it, but now it won't get  
> > created again.
> 
> Can you put some diagnostics in src/ui/gui/psppire-conf.c
> 
> In particular, make sure that flush_conf is getting called.
> And find out to where it's writing (if anywhere).
> 
> Thanks.
>