#Nvim Talk moment

169 messages · Page 1 of 1 (latest)

dusk wharf
#

so yeah, powerline.vim is being a b right now on a fresh nvim install lmao

/usr/share/vim/vimfiles/plugin/powerline.vim[82]..function provider#python3#Call[1]
..remote#host#Require[10]..provider#python3#Require, line 1: Vim(return):E5108: Err
or executing lua /usr/share/vim/vimfiles/plugin/powerline.vim[82]..function provide
r#python3#Call[1]..remote#host#Require[10]..provider#python3#Require[1]..provider#P
oll, line 17: Failed to load python3 host. You can try to see what happened by star
ting nvim with $NVIM_PYTHON_LOG_FILE set and opening the generated log file. Also,
the host stderr is available in messages.
stack traceback:
[C]: at 0x55697d934972
[C]: at 0x55697d934972
[C]: in function 'pcall'
/usr/share/nvim/runtime/lua/vim/provider/python.lua:132: in function </usr/
share/nvim/runtime/lua/vim/provider/python.lua:125>

orchid oak
#

gathering the new stable release didnt fix, okay
wanna send what your vimrc has right quick?

dusk wharf
orchid oak
#

oh?

dusk wharf
#

f%ck

#

exit code: 128

dusk wharf
#

jic I ran the find command

#

welp, neither

orchid oak
#

no longer sure thats an issue, i think that was pip changing https getting syntax at some point

dusk wharf
#

then what is it?

orchid oak
#

pip install powerline-status

#

may not dump a weird exit code

dusk wharf
#

nah

#

it's already there lol

#

so idk why is it doing that if it's already installed

orchid oak
#

neat. ill check the github for similar issues

#

if i had to guess, missing bindings?
:checkhealth

dusk wharf
#

there are a couple here, config file missing, failed run healthcheck, ruby, perl, npm... I'll just guess these last ones are optional

orchid oak
#

well those would be the busted bindings, hm

dusk wharf
#

although wouldn't surprise me, this shit has no nvim folder in .config

orchid oak
#

in .config, there should be an nvim folder, what does that currently look like?

#

oh. hm

dusk wharf
orchid oak
#

you dont still have the apt version installed, do you?

dusk wharf
#

(remember, fedora)

#

anyway, do I just make the folder

orchid oak
#

oh, sorry
if dnf has a purge style command, do that for your repos nvim and rerun the new nvim, see if it makes the config file as it should

#

if not, then yes, make that folder

dusk wharf
orchid oak
#

there's a config folder somewhere in your system, probably in /usr/bin/nvim

#

if im right, find init.lua and pop that in the nvim config folder you just made

#

init.vim, srry

#

im looking at so many lua files rn lmao

dusk wharf
orchid oak
#

that'll work, my experience with fedora isnt great, sorry

dusk wharf
#

(and probably this is scuffed, but I made a small alias in bashrc just to save me some time)

orchid oak
#

same

dusk wharf
#

goddamnit it's still showing the powerline shit

orchid oak
#

nvim hates me too, dw
actually considering helix for that reason but whatevs

was there a config for nvim in bin?

#

fuck, why is that still being a bitch?

#

dont suppose :checkhealth even remotely changed?

dusk wharf
#

it's the first thing that pops up KEKW

#

welp, there's an nvim file in bin, that's as much

orchid oak
#

i guess move the contents of that over, including the init
im not sure why it refused to access either config location for the bindings

dusk wharf
orchid oak
#

just a folder called lua?

#

oh wait

dusk wharf
#

absolutely nothing

#

an absolute "Go make your own files, lazy-ass neckbeard." kekrofl

orchid oak
#

okay what the actual hell

dusk wharf
#

man if I don't manage to solve this I probably will just switch to standard vim lol

#

(although just now I heard from Tillo that there are forks of nvim)

orchid oak
#

helix is what im considering, if thats what you wanna do, supposed to be great out of the box

im sorry, im actually stumped, i have no clue why the hell nvim wont make a config with an init

#

thats absolutely why it wont access the python binding to run powerline

#

but... WHY?!

dusk wharf
orchid oak
#

i cant find anything even remotely close to this on nvims github, you could try following someone elses config structure (there's a lot, people love to share this stuff), but genuinely

#

im lost, my issues have never been that deep

dusk wharf
orchid oak
#

yea this is dumb, and whats funny is i know people who use nvim on fedora without these kinds of issues
i guess close the thread unless you wanna ask others, which may help, who knows

#

im gonna go try helix and see how easy it is

dusk wharf
#

(help is now tutor)

#

that's about enough to tell me that it'll be something probably 80% new

orchid oak
#

kakoune is another popular option

dusk wharf
#

also it triggers me that this shit doesn't have a default command to open it

#

YOU ARE FUCKING SUPPOSED TO LAUNCH IT pepehands

dusk wharf
#

what the f- not even a launch option?

#

can't launch it from terminal nor from the launcher menu

orchid oak
#

if you mean nvim, my alias is ./-ing it

dusk wharf
#

oh nvm, kakoune is kak... bruh

orchid oak
#

OH

#

yea, prolly alias that to something more native

#

even my nvim is aliased as vi

dusk wharf
orchid oak
#

some would call that bloat, but hey, whatever works for you personally

dusk wharf
orchid oak
#

fair enough
imma hop back to gen btw

dusk wharf
#

I've never been one to dislike ditching on options if I haven't tried them before

#

ok, cya I guess

dusk wharf
#

@orchid oak so, I've been trying both kakoune and hx for the time being

orchid oak
#

works well for you, i hope

#

i went through with setting up language servers for helix

#

easier than i thought it'd be

dusk wharf
#

yeah, kakoune is closer to a default nvim, while helix is nvim with a theme

#

although kakoune doesn't have a help command, rather singular docs for diff topics

#

also it seems like kakoune has it's own set of new commands including "c" on normal mode

#

as far as I remember rn, <c-o> is for enabling autocompletion

orchid oak
#

thats kinda neat

dusk wharf
#

also made an alias for both hx and kak (vix for helix and vik for kakoune KEKW)

orchid oak
#

lmao that works

#

i just have em both on PATH

dusk wharf
#

and it's more comfortable than one would expect

dusk wharf
#

that or I'm dumb, which is also a possibility lol

orchid oak
#

export PATH='~/path/to/folder/the/bins/in':PATH$

pop that somewhere in your .bashrc and restart your terminal

#

then you can just type hx or kak

but aliasing it works just fine as well

dusk wharf
orchid oak
#

oh lmao

dusk wharf
#

also deciding whether to use sudo or not with the alias

#

but it seems like that's not possible or something lol

orchid oak
#

not necessary, really

dusk wharf
#

(so like "sudo vik" for if I need extra privileges for editing a file, or simply "vik" for if I'll just edit a random file)

orchid oak
#

oh, im reasonably sure sudo would use root users bashrc, which likely does not have the same aliases set

#

but editing root users bashrc is not recommended

dusk wharf
#

and since they're essentially vim with extra steps (like nvim), I thought it'd be fun to simply replace the "m" with "h" or "k" for them

orchid oak
#

wait how are you setting your aliases?

dusk wharf
#

simply an alias in bashrc

orchid oak
#

oh, thats correct
shouldnt need to type any password just to launch your aliased hx or kak

dusk wharf
#

like "alias vik="sudo kak" "

orchid oak
#

ah well, that should be possible, no?

#

tho its probably better to edit root files with something else since it shouldnt be something you need to do often

dusk wharf
orchid oak
#

fair, im using nano or ed to mess with root files if i absolutely have to, but again, not very often
at least those are always on superusers path

dusk wharf
#

I'm already used to having to run all kind of shit with admin privileges since windows KEKW

orchid oak
#

lmao fair, there's far better ways to handle that sort of thing in linux

#

should probably close this thread btw

dusk wharf
#

I mean, thought it'd be fair to use it to talk about nvim-like editors

orchid oak
#

thats fine i suppose, dont think anyone else is following the thread besides us two

dusk wharf
#

yeah, could notice

#

the one with the issue and the guy who tried to help but ended up even more confused kekrofl

orchid oak
#

bro idfk what nvim hated you for

#

im still checking the github for similar issues, its just not a thing

dusk wharf
#

I guess for not setting up the environment it was supposed to use, when it could've just done that by itself?? KEKW

orchid oak
#

real, idk why it refused to put a config file anywhere

#

it just popped into my .config when i first ran the binary

dusk wharf
orchid oak
#

best guess, fedora decided to handle that in some magical way i cant understand as a non-fedora user

dusk wharf
orchid oak
#

its debian but needlessly alien, i completely understand lol

#

anyways, i got rust to learn, ill ttyl

dusk wharf
#

okay, cya ig

dusk wharf
#

@orchid oak hey, have you found the file kakrc?

#

I've been thinking of configuring kak but, just like with nvim, I can't seem to find the config file anywhere

orchid oak
#

.config/kak/ is where it should be, ill check the docs if thats not correct

dusk wharf
#

what the actual fuck, I now find the nvim config folder but no shit about kak weirdchamp

orchid oak
#

lmao neat

#

output of this, please

printenv XDG_CONFIG_HOME

dusk wharf
orchid oak
#

ah that explains some things
put this somewhere in your .bashrc

export XDG_CONFIG_HOME=$HOME/.config

dusk wharf
#

damn, it took me long before remembering where do apps store their configs besides .config and /home/share

orchid oak
#

kakrc in share is apparently the init script that shouldnt be modified, and it will be what loads your .config/kak/kakrc

#

better worded explanation than that of just the github

dusk wharf
orchid oak
#

still left to wonder why nvim config just now showed up... log out, log back in, see if it appears?

#

if not, just make it, add in something and see if kakrc init does load it in

dusk wharf
orchid oak
#

at this point, wouldnt even remotely be surprised

dusk wharf
#

Guess I'll have to try and make it

dusk wharf
#

I never expected something as simple as this to be so frustrating

#

I can't fucking find the key for looking through the autocompletion 😭

#

I've been playing around with my keyboard and I can't seem to find any key for it

#

you gotta be kidding me, it's so damn uncomfortable to use using ctrl + n...

dusk wharf
#

is it me or kakoune's docs are confusing as hell

#

@orchid oak srry to be bothering you this late, just respond when you can lol. Do you have any idea if this is valid in kak?

#

Nvim Talk moment

orchid oak
#

not a clue, may want to refer to some example configs

dusk wharf
dusk wharf
#

nvm, had to search for a hot moment before remembering github has a wiki option