Re: Fwd: no config file [SOLVED] :D

On Mon, 23 Jan 2006 21:18:49 +0100
charly Ghislain <charlyghislain@xxxxxxxxx> wrote:

Let's see if we can get to the cause of this ...

> > 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.

In your context, it will (or should) try to create a config file in the same 
place as the Trash dir. But for the very first session, the config file is not 
created until you close down (or make changes via a config dialog).

> 
> I tryed running emelfm2 with the --no-detach and --debug=5 option, but
> the last one seems to have no effect :(

True, debug-related code is now included only if you use a 'make' parameter 
DEBUG=1
We will update the help message accordingly.

> The config file was located in ~/.config/emelfm2/config in this version.
> emelfm2 is not able to create the ~/.config/emelfm2,

Well, by default it doesn't try to do that, because it assumes that ~/.emelfm2 
can be created and used. As you've found, it will use another config dir if 
instructed to do so by a command-line switch.

 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!
That's a relief ! You'll need to start each session with the config directory 
parameter.

For arch, is there anything about directory ~/.config which would mean it 
behaves differently from ~/.emelfm2 ?
Is there any requirement for files named like 'config', such that they can be 
saved in ~/.config/emelfm2, but not in ~/.emelfm2 ?

Regards
Tom


-- 
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: