Talk:Ranger
Starting a shell in the current directory
The scripts added in 2013 haven't changed much: https://wiki.archlinux.org/index.php?title=Ranger&oldid=270019
Is this a fixed bug in ranger, or are some shells/configurations still susceptible? Should this section just be removed? Score (talk) 18:28, 29 April 2020 (UTC)
- The scripts provided in the "Start a shell from ranger" section give a fairly involved workaround to get ranger to start your shell in the correct directory, but from what I can see ranger already does this without involving extra scripts. I am wondering if this is changed behaviour (if not, why would someone go to the effort of authoring these scripts?), or if this is something that breaks on some common shell or configuration. Score (talk) 04:40, 1 May 2020 (UTC)
from ranger.api.commands import *
no longer needed in commands.py
At the beginning of section Ranger#Configuration: I think from ranger.api.commands import *
is no longer needed at the top of a custom commands.py
file, as the example file created via ranger --copy-config=commands
does not mention it. The manpage ranger(1)
also says: "The full default commands.py can be copied with --copy-config=commands_full, but that file will be ignored by ranger and serves only as a reference for making your own commands." Mearon (talk) 18:46, 11 July 2021 (UTC)