pspp-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Bojo42
Subject: Re: [PATCH 0/2] PSPP shared library refinements
Date: Thu, 02 Feb 2012 00:06:39 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120130 Thunderbird/10.0

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:

[find-dialog]
maximize=false
height=312
width=527
x=409
y=168

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.

Seems like this is more debugging task for my development installation of Ubuntu than a PSPP issue.

opened files. There's also this repeating warning on terminal startup: Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
I don't think that is relevant, but it would be interesting to find out why it's happening. I suspect it's a problem with one of Debian's Gtk related packages.

Lets better ignore it for now, as they obviously do some patching to Gtk&GNOME in Ubuntu and maybe things need to settle down here a bit.

J'




reply via email to

[Prev in Thread] Current Thread [Next in Thread]