Re: Fwd: no config file [SOLVED] :D
- From: charly Ghislain <charlyghislain@xxxxxxxxx>
- To: emelfm2@xxxxxxxxxxxxx
- Date: Mon, 23 Jan 2006 21:18:49 +0100
On Friday 20 January 2006 23:00, tpgww@xxxxxxxxxxx wrote:
Hi,
Sorry for the long time..
> In lieu of a 'configure' step, several configuration parameters may be
> supplied directly to 'make'. So I guess that at a minimum, a PKGBUILD would
> look something like this:
thanks, i managed to use your PKGBUILD. It wasnt so hard :D
> If I recall, you mentioned that you can do that manually.
> What happens if you manually create directories
> /home/salon/.emelfm2
When creating .emelfm2 before starting, the directory Trash is created by
emelfm2. The configuration file doesnt.
I tryed running emelfm2 with the --no-detach and --debug=5 option, but the
last one seems to have no effect :(
> and
>
> I think this might be your glib version, as opposed to glibc
Youre right. Im using glibc-2.3.5-8
Note that i installed arch on my laptop and the same issue appear.
Ive found another arch user with the same problem.
Ive seen on my gentoo box that portage provides version 0.0.9 only. It has an
issue making the app crash when saving config, but the file was created.
So i tryed compiling other versions on my arch system (thanks to PKGBUILD, its
quite easy):
0.1.4 has the problem
0.1.3 has the problem
0.1.0 has the problem, but debugging seems to work here.
The config file was located in ~/.config/emelfm2/config in this version.
emelfm2 is not able to create the ~/.config/emelfm2, but after creating
~/.config, it is able to create his directory and his files.
So i switched back to emelfm2-0.1.4 and forced him to use ~/.config/emelfm2
for config dir and IT WORKS!
The first time he asked me to update the old config file.
I then tryed to remove the dir ~/.config/emelfm2, and it was able to create
all his files!
So this is still a strange behaviour..., but at least im able to use the app!
Thanks!
Charly
--
Users can unsubscribe from the list by sending email to
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by
logging into the web interface.
Other related posts:
