Re: [Ranger-users] let's discuss commands.py

[Roman Z.]

On Wed, Feb 27, 2013 at 07:37:53PM +0100, Miodrag Milic wrote:
> use "imports" at the end of those 4 files that will call adequate
> files from ~/.config/ranger folder.

That's already working for rc.conf and commands.py.  You can have a
minimalistic rc.conf with only something like "map q quit!" and it's
simply loaded on top of the default config.

I'd argue that it makes no sense for scope.sh (it's a shell script) and
rifle.conf (it's also like a script; rifle goes through the file
line-by-line and looks for the first match).

> What do you think about removing copy-all option completely and use
> "imports" at the end of those 4 files that will call adequate files from
> ~/.config/ranger folder. Those files should be empty initially.
> 
> So user config/code will be separated from default config/code, and updates
> will sometimes require some tweaks to user files when compatibility breaks
> which could be announced at ranger startup as an warning.
>
> You could even provide soft links to those 4 "default config" files along
> which will serve only for easy of access.

Using symlinks to create stuff like "~/.config/ranger/rc.conf.example"
would be nice because this keeps them up to date at all times, but if
somebody edits them, he would change the actual default configs and
potentially mess things up bad.

Perhaps it would be a good compromise to change --copy-config to create
copies to *.example (like rifle.conf.example instead of rifle.conf)
along with a warning that explains the advantage of minimalistic
configuration files.

Or how about removing --copy-config entirely and adding a
/usr/share/doc/ranger directory where the examples, default configs and
other documentation is placed?

Roman