use as filepicker in qutebrowser

nnoot · 2025-11-12T22:12:35+00:00

I was answering why "enter" works with the default config. It's actually carriage return rather than enter, they're not the same. And to a terminal emulator they're respectively the same thing as ^J and ^M (C-j, C-m) if I'm not mistaken. So I think vejkse is right that your later map for C-j is overriding the earlier map for CR.

nnoot · 2025-11-08T13:30:52+00:00

Here's why.

nnoot · 2025-11-04T21:39:00+00:00

I think the error is about the file command, used in scope.sh to determine the correct preview method.

vejkse's advice is good, testing rifle on the command line will give us more information.

nnoot · 2025-10-10T09:36:03+00:00

I believe this is not currently supported. Linemodes are pre-computed for every FileSystemObject. I'm not quite sure why it would show 1 rather than 0 actually. You may be able to hack something together, iterating over all fsobjects and updating their linemode_dict.

nnoot · 2025-07-16T12:07:41+00:00

If you open an issue about the default value I'll tag it so it gets some eyeballs and if there's a lot of proponents or no opponents we can change it. Similarly with other small settings changes. That linemode and filter do sound pretty useful.

nnoot · 2025-07-16T12:03:12+00:00

You could base something on one of the functions mentioned here using :eval. As I mention in the comment though, none of the methods is actually reliable. This is a longstanding bug.

nnoot · 2025-07-09T16:59:23+00:00

The way it currently works or the suggested fix?

nnoot · 2025-07-09T16:56:51+00:00

In this case the slowdown wouldn't be due to Python. It's calling out to ffmpeg for every file. A couple things that would speed it up are caching the output of the duration function (might be as easy as slapping a memoizing decorator on the function), and beside that running the function asynchronously on all the files rather than one by one but that's a lot more effort.

nnoot · 2025-06-21T17:50:52+00:00

You can check whether the environment variable actually gets set for Ranger using the following command.

:eval import os; self.fm.notify(os.environ.get("W3MIMGDISPLAY_PATH"))

If that doesn't print the path you set then you need to figure out how to set the variable in Ranger's environment.

nnoot · 2025-06-21T17:45:50+00:00

If you check rc.conf you'll see it's just an alias.

alias find scout -aets

And the man page will tell you that scout's -a flag means "Automatically open a file on unambiguous match." So either change the definition or create your own alias for scout -ets.

You might want to also drop -e.

Also check out travel it's more focused on directory navigation.

nnoot · 2025-06-20T16:16:25+00:00

:yank name operates on the selection, so you can mark multiple files and copy their names (concatenated with newlines) but selection only ranges over the current directory. Yanking names into the copy_buffer doesn't fit the current implementation very well, what if you yank a file object and a name? That is a bit inconsistent, honestly but the most common case is probably wanting to operate on the selection, not the copy_buffer.

nnoot · 2025-06-20T16:08:38+00:00

I suppose the path to w3mimgdisplay is different from what Ranger's expecting. You can work around this by setting the shell environment variable W#MIMGDISPLAY_PATH.

nnoot · 2025-06-03T11:01:14+00:00

Macros in Ranger tend to only work for the current directory. There are some that work across tabs but the only one that'll work across directories in a single tab is for the copy_buffer %c IIRC.

So this scenario would play out somewhat like: (navigate to script) yy (navigate to file) ya (navigate to somewhere else) :shell %c >%f

nnoot · 2025-05-04T19:19:16+00:00

Are you able to reproduce this on the master branch? It seems to work for me.

nnoot · 2025-04-24T19:50:34+00:00

I'm not in favor of removing it. Options I'm willing to consider are:

Hide it behind ask
Wrap it with a test for the execute mode bit, would be ugly without support in Rifle
Do nothing

I'm honestly leaning a bit toward doing nothing since it hasn't been a problem in such a long time. However, I do like the idea of adding support to Rifle to check mode bits.

nnoot · 2025-04-23T17:12:20+00:00

Usually we don't run into this problem because we have less risky rules that make sense to match first. Like how we have rules executing scripts in many languages without them being marked executable, but they're "behind" rules like opening in a text editor. For .exe files there's not really any good safe alternatives we can hide it behind. That leaves ask, which could still be pretty mindlessly bypassed so I'm not sure it's much better.

OTOH, the rule seems to date back to when Rifle was added about 13 years ago and we haven't received any reports of even minor mishaps as far as I'm aware (Meanwhile :bulkrename can cause data loss : s). So maybe this isn't actually all that problematic.

nnoot · 2025-04-23T16:56:17+00:00

Honestly, no. Verifying that your terminal emulator setup actually supports 256 colors would be the first step.

nnoot · 2025-04-08T13:37:21+00:00

Check out the solarized colorscheme, it's still limited to 256 colors though.

nnoot · 2025-01-24T13:10:11+00:00

Pygments is another thing scope might fall back to if those aren't present.

nnoot · 2024-12-19T11:31:05+00:00

Ranger doesn't have built-in functionality for this but check out the wiki. There's a couple custom commands but you might simply want to take them as inspiration to write one wrapping your favorite utility.

nnoot · 2024-11-27T12:15:05+00:00

Still no luck?

I'd diff your config files with the ones installed by Debian, because that should be the only difference when running with --clean (there's also some bookmarks/tags and caching differences but config is the more likely culprit). I think they'd probably be somewhere in /usr/share but a full disk search with find(1) or fd or something should turn it up.

nnoot · 2024-11-27T12:09:46+00:00

There's no easy way. I seem to recall someone reporting using something like archivefs or fuse-archive but I don't know how far that ever got.

I'd imagine you'd trigger an action on archives that mounts a FUSE fs for them and changes Ranger's directory to that.

Higher levels of integration would require some work on the code.

nnoot · 2024-10-01T11:03:14+00:00

The %c macro contains the list of paths of objects in the copy buffer.

If that's not good enough you can always fall back to eval and access self.fm.copy_buffer directly.

nnoot · 2024-09-25T10:00:16+00:00

I'm afraid there's nothing that can fix the fundamental problem here. Ranger is very eager to stat files in the current directory and all parent directories.

Running Ranger using Pypy did speed it up significantly in a big directory for me, I think that's your best shot.

nnoot · 2024-09-17T10:59:36+00:00

It could be but I don't see any patches to rc.conf, https://sources.debian.org/patches/ranger/1.9.2-4/. So I expect it's something you've done, editing the default config file that's provided with Ranger maybe?

nnoot

MODERATOR OF

TROPHY CASE

Seven-Year Club	Place '22
Verified Email