pylsp-rope VS micro-editor

pylsp-rope is actually an external plugin project, it implements advanced refactoring functionalities using code action (extract method/variable, function inlining, converting local variables to instance variables, organise import, etc). Unless you have explicitly installed pylsp-rope at some point, it's unlikely you already have it in your system. I'm the author of pylsp-rope, btw.

If you're also a user of rope, which is a Python refactoring library, my python-lsp-server plugin pylsp-rope would also welcome contributions. They have a fairly small codebase, and so they would be relatively easy to pick up.

Currently the best way to use rope for refactoring (including extract, inlining, reorganise import, plus many more) in Neovim is with pylsp-rope and your preferred LSP client. pylsp-rope is going to be the main focus of bringing rope capabilities to various IDEs and text editors. I'll have to find the time for this, but I'm planning to overhaul the rope support in core pylsp to make it work even better.

Rope's Restructuring refactoring is very powerful and flexible, and it's very accurate given the pattern, however it's currently only accessible from rope's programmatic interface, which means you have to write a little bit of Python code to use it. I've not been able to figure out how best to expose this capability into easy to use user interface within text editors/IDEs and especially within the constraints of LSP for pylsp-rope.

I am the maintainer rope and pylsp-rope. They are libraries for automated Python refactoring and to do that from any LSP-capable editors. We are always welcoming contributors of all levels.

You can also use pylsp-rope, though until LSP actually provides a standard Villani compliant interface that allows LS to implement move refactoring, you may not be able to use it from your editor. I'm kinda thinking that maybe I should just non-standard LSP extension that ropevim would call into. It shouldn't just be Microsoft that can play EEE 😅

pylsp-rope

I never had to market an open source project from zero that later grow into popularity, but I did inherit the maintainership of a fairly popular project and then I started a new project that have been gaining a small, but growing momentum.

Most of my personal projects are written because I need a feature that nobody else has anything remotely resembling what I need.

pylsp-rope for refactoring capabilities

To see more screenshots of micro, showcasing some of the default color schemes, see here.

Not sure these are really popular, but I cannot resist advertising a few utilities written in Go that I regularly use in my daily workflow:

- gdu: a NCDU clone, much faster on SSD mounts [1]

- duf: a `df` clone with a nicer interface [2]

- massren: a `vidir` clone (simpler to use but with fewer options) [3]

- gotop: a `top` clone [4]

- micro: a nice TUI editor [5]

Building this kind of tools in Go makes sense, as the executables are statically compiled and are thus easy to install on remote servers.

[1]: https://github.com/dundee/gdu

[2]: https://github.com/muesli/duf

[3]: https://github.com/laurent22/massren

[4]: https://github.com/xxxserxxx/gotop

[5]: https://github.com/zyedidia/micro

> The worst way to store and manipulate text is to use an array.

Claim made from theoretical considerations, without any actual reference to real-world editors. The popular Micro[1] text editor uses a simple line array[2], and performs fantastically well on real-world editing tasks.

Meanwhile, ropes are so complicated that even high-quality implementations have extremely subtle bugs[3] that can lead to state or content corruption.

Which data structure is "best" is not just a function of its asymptotic performance. Practical considerations are equally important (arguably more so).

[1] https://github.com/zyedidia/micro

[2] https://github.com/zyedidia/micro/blob/master/internal/buffe...

[3] https://github.com/cessen/ropey/pull/67

There are two main ways to configure sudo.The first one is using the sudoers file.It is located at /etc/sudoers for Linux,and /usr/local/etc/sudoers for FreeBSD respectively.The paths are different,but the configuration works in the same way. A typical sudoers file looks like this. The sudoers file must be edited with the visudo command,which ensures the config is free of errors.Running this command as the root user will result in opening vi by default.If you want to use a different editor you can set the VISUAL environment varaible to the editor you want. For example,if you want to use micro as the text editor run:

found that micro has dedicated info page for copy paste

micro: winget install zyedidia.micro