all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bradley Haggerty <bradigger@gmail.com>
To: 35016@debbugs.gnu.org
Subject: bug#35016: ranger not working fully
Date: Wed, 27 Mar 2019 05:36:11 +0000	[thread overview]
Message-ID: <CABGw91f1EwsraAySCdf8CReLA7FnC4KFc+B7P_MEbFLG7VZ1UQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]

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

[-- Attachment #2: Type: text/html, Size: 1494 bytes --]

             reply	other threads:[~2019-03-27  5:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-27  5:36 Bradley Haggerty [this message]
2019-03-27  5:56 ` bug#35016: ranger not fully working Bradley Haggerty
2019-03-27 12:53 ` Bradley Haggerty
2019-03-27 13:11   ` Ricardo Wurmus
2019-03-27 13:46   ` Andreas Enge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABGw91f1EwsraAySCdf8CReLA7FnC4KFc+B7P_MEbFLG7VZ1UQ@mail.gmail.com \
    --to=bradigger@gmail.com \
    --cc=35016@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.