GNU bug report logs - #35016
ranger not working fully

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 35016 in the body.
You can then email your comments to 35016 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Bradley Haggerty <bradigger <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: ranger not working fully
Date: Wed, 27 Mar 2019 05:36:11 +0000

[Message part 1 (text/plain, inline)]

I believe this affects multiple things in ranger, but off the top of my
head it's mainly the `:bulkrename` option, which is supposed to open the
selected files in vidir using your specified editor so that you can rename
file(s) with the full features of your favorite editor. It is intended for
renaming files in bulk just like it sounds, but I also find it's often
easier to use than the normal rename command because you don't have to type
the current name, and it's easy to do things like change capitalization of
a selection in vim.
This is a long-standing issue, but I was ignoring it for some reason. I
guess I use ranger more on remote machines running different distros.
steps to reproduce:
- install ranger
- launch ranger
- type :bulkrename, that is start by hitting the colon key and then
continue typing the name of the command
I think it's likely due to locations of certain files being different on
guix. Hopefully someone can figure out a fix without too much trouble. If
you have access to another distro to see how it works normally, that might
help as well. You may need to install optional dependencies for this
feature to work. Likely just vidir or a package that it's a part of. For me
I believe I got vidir from the `moreutils` package.
guix version: guix (GNU Guix) 4fee5ec049807cc7a7070d31e5eb28d5c6109e02

[Message part 2 (text/html, inline)]

Message #8 received at 35016 <at> debbugs.gnu.org (full text, mbox):

From: Bradley Haggerty <bradigger <at> gmail.com>
To: 35016 <at> debbugs.gnu.org
Subject: ranger not fully working
Date: Wed, 27 Mar 2019 05:56:21 +0000

[Message part 1 (text/plain, inline)]

I forgot to include the little error it gives me. The following shows at
the bottom after an attempt to use `:bulkrename`
> [Errno 2] No such file or directory: 'file': 'file'

[Message part 2 (text/html, inline)]

Message #11 received at 35016 <at> debbugs.gnu.org (full text, mbox):

From: Bradley Haggerty <bradigger <at> gmail.com>
To: 35016 <at> debbugs.gnu.org
Subject: ranger not fully working
Date: Wed, 27 Mar 2019 12:53:14 +0000

[Message part 1 (text/plain, inline)]

It seems this was something simple I overlooked. I was just missing the
file command. After a quick `guix package -i file` it now seems to work as
expected. This issue may be closed. I don't know how to do that myself.

[Message part 2 (text/html, inline)]

Message #14 received at 35016 <at> debbugs.gnu.org (full text, mbox):

From: Ricardo Wurmus <rekado <at> elephly.net>
To: Bradley Haggerty <bradigger <at> gmail.com>
Cc: 35016 <at> debbugs.gnu.org
Subject: Re: bug#35016: ranger not fully working
Date: Wed, 27 Mar 2019 14:11:37 +0100

Bradley Haggerty <bradigger <at> gmail.com> writes:

> It seems this was something simple I overlooked. I was just missing the
> file command. After a quick `guix package -i file` it now seems to work as
> expected.

Should “file” be installed alongside “ranger” by default, i.e. using
propagated inputs?  Or can we embed a reference to the “file” executable
in the sources of “ranger” to avoid propagation?

-- 
Ricardo

Message #19 received at 35016-done <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Bradley Haggerty <bradigger <at> gmail.com>
Cc: 35016-done <at> debbugs.gnu.org
Subject: Re: bug#35016: ranger not fully working
Date: Wed, 27 Mar 2019 14:46:09 +0100

On Wed, Mar 27, 2019 at 12:53:14PM +0000, Bradley Haggerty wrote:
> This issue may be closed. I don't know how to do that myself.

Like I am doing right now, by cc-ing BUGNUMBER-done <at> debbugs.gnu.org.

Thanks,

Andreas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.