Wiki link autocomplete behaves ok with mouse but not with arrow keys in 4.1

Hi all,

After updating to 4.1 I’ve noticed this behaviour with wiki links:

So in some rtf note I’m typing text and then I add `[[1on1` ,for example , and a list of multiple notes that starts with “1on1” pop up. If I click down arrow to select some note in the list it will just autocomplete with the first note in the list.
If I can use the mouse pointer I can pick whatever note displayed.

Kind Regards

Which version of macOS do you use?

Sequoia 15.6.1

  • Is your sync interval set to Automatic ?
    • If so, set it to Every 5 Minutes and see if the behavior persists.

Yes, it was Automatic, and I’ve set it to 5 min, but the behaviour is the same … either clicking up or down arrow immediately autocompletes the wiki link,

I believe we are talking about this:

Cheers

Thank you for checking. It was a long shot but worth asking about. Do you know what keyboard layout you’re using?

Not sure what you mean exactly but in keyboard settings it’s US keyboard layout.

Yes, that’s what I was asking about and thanks for clarifying.
Just trying to gather info as I can’t reproduce the issue on any of my Macs.

If it is worth noting, laptop keyboard is US qwerty layout as well as the external keyboard ( logitech ).
But this setup is the same as in time of DT3.

The current version of macOS Sequoia is 15.7. Does it improve after updating the OS?

I just updated to 15.7 and the problem persist. But I found some workaround (I guess) … First about the problem.

I have the following rtfs just for example:

1on1 A Person
1on1 B Person
1on1 C Person
1on1 D Person
...

Then if I type [[1on1 and then press Space or Up / Down arrow it autocompletes with some of files in the long list presented … interesting it’s not either the first or last file in the list.
To simplify, probably in my example above it will autocomplete to [[1on1 B Person]].

The work around it seems is:

  • when autocomplete is done the filename is selected after the Space, like on pic below
  • then I do 2 backspaces to delete the selected part and one space, and then continue typing till drop down list is presented and then in most cases I can use up/down arrow to go to wanted file name

On :backhand_index_pointing_up: picture is shown selected part of the file after pressing space. One backspce will delete the selected text in blue.

P.S. it’s weird .. I think there are 2-3 scenarios of this problem , I presented one I guess. I mean sometimes the workaround will not work, or sometimes this feature will work properly .. I’m all in :red_question_mark::red_question_mark: tbh

So you have multiple files with essentially the same prefix. I will have to test that specifically.

This is what I’m seeing…

Down arrow to the bottom of the autocompletion list commits the last entry automatically.

Sequoia 15.7.

In your video things work well as far as I can see: you can go up/down and it doesn’t autocomplete until you hit return on selection, I guess ( except if you’re on last item and click down ).

Now in my real life case there are much more than 4 files in the selection list.

Actually maybe I need to test with only 4-5 files …

How many do you have in the selection list?

Ok, so I think I found it, this seems has to do with the length of the list.

First off, @BLUEFROG I re-created your case with only 4-5 files and behaviour is same as in your video.

What I think the problem is, is the length of the list, as mentioned above, that is:

Here on below pic the list is long but the behaviour is ok, I can go up/down multiple times and I can select whatever file I want, no issues

However below, the list is longer so there is slider as indicated by red arrow. Now this autocompletes in, I would say, uncontrolled manner. It just autocompletes sometimes after first up/down_arrow, sometimes, if I first use mouse to scroll a bit, and then use the up/down it will autocomplete after few up/down arrows.

However if you do the workaround described above, even if there’s slider, it behaves ok.

Hope this help

1 Like

@rmschne see my next post, just after yours

1 Like