GNU bug report logs - #35016
ranger not working fully

Previous Next

Package: guix;

Reported by: Bradley Haggerty <bradigger <at> gmail.com>

Date: Wed, 27 Mar 2019 05:42:01 UTC

Severity: normal

Done: Andreas Enge <andreas <at> enge.fr>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Andreas Enge <andreas <at> enge.fr>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#35016: closed (ranger not working fully)
Date: Wed, 27 Mar 2019 13:47:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Wed, 27 Mar 2019 14:46:09 +0100
with message-id <20190327134609.GA2127 <at> jurong>
and subject line Re: bug#35016: ranger not fully working
has caused the debbugs.gnu.org bug report #35016,
regarding ranger not working fully
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
35016: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35016
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
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 3 (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 4 (text/html, inline)]
[Message part 5 (message/rfc822, inline)]
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



This bug report was last modified 6 years and 116 days ago.

Previous Next


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