bug: can't open anything using <CR> or <C-t>

[directormac]

Did you check the docs and existing issues?

• [X] I have read the docs
• [X] I have searched the existing issues

Neovim version (nvim -v)

0.9.5

Operating system/version

Arch

Describe the bug

as indicated in the title. I am using LazyVim as my base here is how i configured my oil

What is the severity of this bug?

breaking (some functionality is broken)

Steps To Reproduce

Copy Configuration and use LazyVim

Expected Behavior

Should open the file under cursor

Directory structure

No response

Repro

Current [Configuration](https://github.com/directormac/dotfiles/blob/e99b9afa8f668bc9a4648631c34417f949e54fcb/.config/nvim/lua/plugins/tools.lua#L88)

Did you check the bug with a clean config?

• [X] I have confirmed that the bug reproduces with nvim -u repro.lua using the repro.lua file above.

[snuffop]

:+1:

[directormac]

👍

You having this errors too @snuffop ?

[snuffop]

👍

You having this errors too @snuffop ?

Yes, I am. The /000 /### I noticed when attempting / search in the buffer prior to this latest update or moving to 10 etc. I haven't had a chance to dig in too far yet, day job, I apologize for the short responses

[kekscode]

I have the very same issue. I downgraded through the last 2 oil.nvim tags in my lazy config, but this did not change the behaviour. The only other thing i can remember i did was upgrading to 0.10.0 nvim (arm-based macos):

vim -v
NVIM v0.10.0
Build type: Release
LuaJIT 2.1.1713773202
Run "nvim -V1 -v" for more info

Highly likely it is a v0.10.0 issue, i ~think~ thought, but OP is on 0.9.5 apparently, which contradicts this. @directormac you are sure you're on 0.9.5?

[directormac]

I have the very same issue. I downgraded through the last 2 oil.nvim tags in my lazy config, but this did not change the behaviour. The only other thing i can remember i did was upgrading to 0.10.0 nvim (arm-based macos):

vim -v
NVIM v0.10.0
Build type: Release
LuaJIT 2.1.1713773202
Run "nvim -V1 -v" for more info

Highly likely it is a v0.10.0 issue, i ~think~ thought, but OP is on 0.9.5 apparently, which contradicts this. @directormac you are sure you're on 0.9.5?

Yup im pretty sure im on 0.9.5, but i just downgraded because

❯ nvim -v
NVIM v0.9.5
Build type: Release
LuaJIT 2.1.1713773202

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

even downgrading luajit i still get the same thing from oil i maybe thought its one of the deps.

[buztard]

I just had the same issue. In my case it happened because of a wrong filetype detection in a different plugin. You can check the filetype of your oil buffer using set ft? and switch to ft=oil in case it's different

[kekscode]

Yes, i use vim-helm, too. I will check later today if this is the culprit.

[kekscode]

This might have been fixed: https://github.com/towolf/vim-helm/pull/25

[directormac]

Yup looks like it i have vim-helm too now its all good again. Closing this issue now.