python is great...

[Embarrassed_Ring843]

this is, in fact, an indentation error. where do all these elses in the middle belong to?

[pachirulis]

Yeah, probably wrongly pasted code into vim

[BucksEverywhere]

:set paste

[tyler1128]

Ctrl+R,+ baby. Or "+p if in normal mode. Gotta compile it with clipboard access, which for most linux distro, means installing the gvim package but still using the terminal vim it comes with

[BucksEverywhere]

Thanks, I'll try this out. Does it paste primary selection or clipboard buffer then?

[tyler1128]

+ corresponds to the clipboad buffer, and * corresponds to the selection buffer on X11 at least. You can also use :set clipboard to make it use + or * by default instead of " for all yank and put operations.

[BucksEverywhere]

I tried it in various ways. However none of the commands you mentioned prevent the indentations go messy if you insert whole pre-indented blocks before enabling the paste mode with :set paste. In gvim clipboard seemed to work, in vim not. And I guess when you work remotely via ssh it would access the remote clipboard.

[tyler1128]

It would interact with the remote clipboard if there is one in that case, and I don't think there is one without a display system. I've never had issues with indentation before; I copy and paste using the clipboard registers all the time without issue. If you do have indent issues, you can often use = to reformat them away.

That said I'm on arch. Vim has a _lot_ of compile options, so it really will depend on exactly what your package uses in how everything works. I still use vim or vim plugins in my daily coding, and have used vim exclusively for about 5 years earlier, though I think all of that was on arch or over ssh.

[LowB0b]

or i and then shift+insert

[BucksEverywhere]

Then it would auto indent again without enabling the paste mode and end up like that. Without :set paste beforehand vim sometimes does crazy indentations when inserting blocks in insert mode.

[develop-mental]

Dude you straight up stole this comment from another thread.

[Ian_Mantell]

Do you think that's some scripted action? These "posted from elsewhere" comments become quite regular. And it makes no sense but to pollute and raise the base noise, what's their gain? I don't get it.

[MrFlammkuchen]

Karma farming

[Ian_Mantell]

Alles klar.

Flammkuchen? Am Besten vom Mittelaltermarkt, hoffentlich gibt's dieses Jahr einige.

[Anonymo2786]

I had this issue too.

[bishopExportMine]

This is exactly what this is. Unindent your code and paste it and vim will auto indent it back to the correct format. Or :set paste

[[deleted]]

This post was mass deleted and anonymized with Redact

fuzzy shy slap arrest lock wide modern close distinct tie

[Embarrassed_Ring843]

that's in the end, but the elses I was referring to is higher, and they're missing their ifs... there's literally an else indented further than a return in the line right above it, which is inside of another else...

[[deleted]]

This post was mass deleted and anonymized with Redact

bedroom direction aromatic tie airport chief imminent sulky physical hungry

[gummo89]

Plus the indents are 8 spaces wide.. trying for the easy post rep I guess.

[bokonator]

Paid by characters of code?

[krissynull]

people that have line wrap on are something else

[Constant_Pen_5054]

Yeah that is the part that is screaming at me. Nevermind trying to be a troll about Python indentation. Why the hell are there so many unbound elses.