Selector randomly jumps up about nnn HOT 25 CLOSED

Does the same item remain selected or the selection moves to a different item?

from nnn.

Also, please share the steps for reproduction. Otherwise it's difficult to figure out what's going wrong.

from nnn.

The selector moves to a higher item, by a constant number, repeatedly with random intervals.
I used the nixpkgs expression to build, but pointed the 'src' to the latest commit (plus my own key config, but I tried a vanilla build, and had the same bug).
The behavior is constant.

from nnn.

What is the interval? Are you having any filter enabled (like size, time etc.)?

I didn't understand what you meant regarding building... did you try compiling and using nnn from master?

from nnn.

The behavior is constant.

I need the exact steps to observe this behaviour.

from nnn.

Yes I compiled from master (I used the expression 'latest commit', but I means, latest commit on master). I used the nix expression I linked, but used the latest master as 'src'.
It seems to only jump up once every time a new folder is opened, after about one second. I said the number of entries jumped was constant. I was wrong; it usually jumps to the first item but not always.

from nnn.

When you enter a new directory, nnn should jump to the first entry instantly. Please note down what you did after entering the directory.

from nnn.

I have narrowed it down better. Basically, every time it switches to a new folder (left or right), after a second it jumps to the highest visible item. If the intended behavior is to automatically selecte the highest visible item (I would want to change that personally), then there should not be 1000+ms before it happens. Could I just disable that 'goto top on open dir' completely?

edit: s/should/should\ not

from nnn.

Here's the defined behaviour:

• If you are going into a directory (right) the first entry will be selected (otherwise, which one do we select?)
• If you are going to the parent (left), the child directory will be selected in the parent

The selection is instant, there is no delay. If you are seeing a delay, there's something else in play.

Also, I asked earlier, do you have any filter set or are you in the navigate-as-you-type mode?

from nnn.

In addition to my earlier comment, I am not sure if it's relevant, but what's your hardware (CPU, RAM)?

from nnn.

The expected behavior you are describing is what im seeing, so the jump is a separate issue. There is no filter, no navigate as I type mode, just plain browsing. This is happening on my workstation, so lots of cpu and ram.

from nnn.

Yes, we need to figure out what's taking it so long to jump.

Now when you say jump, are you saying that the selection shows up after a second, OR when you enter the dir something is selected first, then the selection jumps up to the topmost entry (as it should)?

Also what happens if you are in the light mode (press d)?

from nnn.

I'll setup nixOS on a VM and see if I can reproduce it. Makes life easier for both of us. ;)

from nnn.

I mean everything behaves fine, the cursor appears where it should be, but if I then move the cursor down (or if it wasnt placed at the top), after a second the cursor will move back to the highest visible item. It will only do this only once every time a directory is opened.

from nnn.

Light mode has the same bug.

from nnn.

I'll check.

from nnn.

Does nixos have libncursesw or ncursesw? I can see it links to ncurses.

from nnn.

I rebuilt my system and the issue went away.
Sorry about that. Ill let you know if I ever find the cause.
Thanks a lot for nnn, I love it.

from nnn.

Awesome! Award a star. ;)

from nnn.

The issue is caused by my custom key bindings.
I'll try reversing my changes line by line.

from nnn.

Found it.
Changing 'Ctrl-U' for 'Ctrl-L' triggers the bug.
That makes sense, it's the shortcut for PageUp.
So it seems something is sending a 'Ctrl-L' signal to nnn after opening a directory.
Is it nnn doing that or would that be ncurses library?

from nnn.

Ctrl-L is for triggering a refresh. If you are tinkering with the defaults, I believe you have to go all the way and figure out the issue. I would have suggested something if I had any idea what goes wrong, but the number of keybinds are just too many right now to guess something.

from nnn.

So nnn is sending the Ctrl-L signal?

from nnn.

No Page up. It's above Ctrl-L in the key bindings structure. So pressing Ctrl-L is doing what Ctrl-U should do.

from nnn.

It's difficult for me to pursue an issue which is not under my control. In your issue report you didn't even mention you are changing the code. If you are trying to hack things, you are welcome to do so. If you find it worth changing mainline, please raise a PR and I will review it if the change adds value to the current set of features. A bug report is not the right place to support experimental code changes.

from nnn.