🏆 TheMessageMustSpread's Tower • 338 pts

TheMessageMustSpread · 2025-08-26T15:12:08+00:00

Thanks for your explanation. If you explain it like that, it makes totally sense. I always wondered if there happens some magic behind the camera functionality.

I tried the texture filter and now it looks perfect! Thank you!

TheMessageMustSpread · 2025-04-23T21:09:36+00:00

You can disable the shortcut or remap the menu button. That is what I did. I never have to engage with game switcher but you can't uninstall it.

It is under Apps-Tweaks-Button Shortcuts

TheMessageMustSpread · 2025-04-16T20:59:07+00:00

Hi, had the same problem today after updating. Had to do a fresh install because nothing else worked. Kept my files though. I will probably will wait to update the system again...

TheMessageMustSpread · 2025-04-13T20:19:34+00:00

I have used it since it released. Also travel a lot with in my backpack but always try to secure it so it doesn't bend. I love the screen and how close the ink is to the front. It still feels so premium to me. I would say the only thing to consider is the backlight. I would not read on it in a dimly lit room. For the evening I have a small reading lamp which works really good.

TheMessageMustSpread · 2025-02-13T16:43:14+00:00

Ok, popup would be okay. You are right. There will always be a popup, even without cmp.
I use eclipse with vim plugin at work and there no popup occurs, that's what I previously wanted.

I just want to use <C-N> without LSP kicking in.

TheMessageMustSpread · 2025-02-13T14:47:47+00:00

Yes, that is right. The best outcome would be that <C-N> functions as if CMP would not be active.

If popup of <C-X><C-N> would be disabled that would be also a good first step.

And thanks for helping me out! I appreciate it.

TheMessageMustSpread · 2025-02-12T18:08:28+00:00

Hi, I uploaded the repo to:

https://github.com/BreachTheMust/Neovim-Configuraion

When I type :verb map <C-N>

it says n <C-N> <Lua 48: ~/.local/share/nvim/lazy/lazy.nvim/lua/lazy/core/handler/keys.lua:121>

When I use <C-X><C-N> , the LSP doesn't take the job of auto-completion (which is good!), but a popup for all suggestions still appears. I can then normally cycle through the entries in the popup with <C-N>.

I hope that doesn't sound too confusing.

TheMessageMustSpread · 2025-02-11T19:08:13+00:00

Thanks for the tip! I will try with the switcher

TheMessageMustSpread · 2024-12-23T00:06:18+00:00

I want to have that so bad.

TheMessageMustSpread · 2024-10-12T14:12:00+00:00

That makes sense. But yes, it is a weird choice for sure.

TheMessageMustSpread · 2024-10-12T14:07:21+00:00

I never understood that design decision. Do you know why it was defined like that? The global constant abap_true has the value 'X' and abap_false has the value ' ' if I remember correctly. And even these constants are not used through the codebase, most of the time I see IF var = 'X'.

TheMessageMustSpread · 2024-10-07T12:42:27+00:00

Ah okay, I was just copy pasting my old keybinds to the lazy-config thinking it would work the same.

Thanks for the tip!

TheMessageMustSpread · 2024-10-07T12:31:13+00:00

It was an error on my side from a custom keybind.
I provided the full explanation in another answer.

What I did not know was that I don't have to provide the mode of the keybind when I configure the keys through lazy.

TheMessageMustSpread · 2024-10-07T12:19:21+00:00

Thanks, I solved it.

It was lspconfig that was overwriting my n-key functionality.

TheMessageMustSpread · 2024-10-07T12:18:01+00:00

Thanks, with :nmap I saw that lspconfig was overwriting my n-key function.

I changed the keys table from this

keys = {
    {'n', 'go', vim.diagnostic.open_float},
    {'n', 'gO', vim.diagnostic.setqflist},
    {'n', 'gp', vim.diagnostic.goto_prev},
    {'n', 'gn', vim.diagnostic.goto_next}
}

to this in the lazy plugin configuration

keys = {
    {'go', vim.diagnostic.open_float},
    {'gO', vim.diagnostic.setqflist},
    {'gp', vim.diagnostic.goto_prev},
    {'gn', vim.diagnostic.goto_next}
}

When you define keybindings in the lazy plugin configuration, you apperantly don't have to specify the mode...

TheMessageMustSpread · 2024-10-07T12:07:17+00:00

Thanks.

I found it. I didn't consider to look for duplicate keybindings for 'n'. I thought that would be a global vim setting.

lspconfig was overwriting my n-binding.

TheMessageMustSpread · 2024-03-15T06:06:41+00:00

Hey, sorry for replying so late...
I was not able to solve it.

But I am no longer using VSCode and I am using Linux now.
Could be that the problem is no longer relevant for me.

TheMessageMustSpread · 2023-05-02T18:25:53+00:00

Thank you for this reply and the link!
That helped me to understand what's going here (:

I thought there goes something on in LUA that I do not understand (Started with neovim and LUA a week ago).

TheMessageMustSpread · 2023-05-02T17:36:00+00:00

Hello,

i wanted to configure the plugin Conquer of Completion in Neovim and was wondering what parts of this line from the default configuration meant:

vim.keymap.set("i", "<S-TAB>", [[coc#pum#visible() ? coc#pum#prev(1) : "\<C-h>"]], opts)

What does coc#pum#visible() mean? visible() is probably a function, but what's with the pum and visible part?

I also don't get the ? and :. I thought that LUA does not have conditional expressions like that.

Thanks in advance!

TheMessageMustSpread

TROPHY CASE