neotest
micro-editor
Our great sponsors
neotest | micro-editor | |
---|---|---|
22 | 227 | |
1,956 | 23,903 | |
7.1% | - | |
8.3 | 9.4 | |
10 days ago | 1 day ago | |
Lua | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
neotest
-
Am I this bad?
My first neovim plugin project was to write an adapter (runner) for neotest, for a language that I use regularly and which was missing from the existing adapters.
- Alternative for running tests
-
Problem with running code
There's overseer.nvim to run all sorts of things and neotest to run tests. In general, you can check awesome-neovim or TWiN to look for plugins.
-
JetBrains Leavers
Here's some things that may help: - https://github.com/mfussenegger/nvim-dap + dap ui - https://github.com/nvim-neotest/neotest
-
Setting up neovim for python code development (tips wanted)
I use neotest to run tests (with pytest).
-
Is anyone using VIM full-time for PHP/Laravel projects?
For testing I use https://github.com/nvim-neotest/neotest which gives a nice outline.
-
neotest-haskell version 0.6.0 released - now with support for both tasty and hspec
For those who don't know it, it's an adapter for neotest, a Neovim plugin that
-
Creating diagnostic entries from test output
You might look at how Neotest handles this, or even see if you can use/contribute to that project directly. It already has support for a fair number of languages at varying levels of maturity.
-
I got fired yesterday for using vim
I am writing Python these days, and LSP + DAP + neotest give me 90% of what PyCharm would have given me. I don't know how well this works with Java, the latter two did not exist when I was still writing Java. The way I did it was use Neovim with jdt-ls to write code and IntelliJ for debugging. Debugging does not require switching between keyboard and mouse, so it was OK to me.
-
[discussion] Why don't more (any?) plugin authors use penlight?
I'm sure that we could figure out a way to install rocks without luarocks, but it's still going to be an additional step with possible complications. Personally, I would rather just embed the library within my plugin like neotest does with xml2lua. The marginal cost of a slightly larger install is more than paid for by an easier install process and a guarantee that it works.
micro-editor
- Ask HN: What software sparks joy when using?
- Modeless Vim
-
Essential Command Line Tools for Developers
To see more screenshots of micro, showcasing some of the default color schemes, see here.
-
Go: What We Got Right, What We Got Wrong
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
-
Text Editor: Data Structures
> 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
- A nano like text editor built with pure C
-
A simple guide for configuring sudo and doas
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:
-
what terminal emulator do you use and why?
found that micro has dedicated info page for copy paste
-
Microsoft is exploring adding a command line text editor into Windows, and it wants your feedback
micro: winget install zyedidia.micro
- What is the best basic ass text editor?
What are some alternatives?
overseer.nvim - A task runner and job management plugin for Neovim
helix - A post-modern modal text editor.
nvim-dap-ruby
filemanager-plugin - A file manager plugin for the editor "Micro"
nvim-coverage - Displays test coverage data in the sign column
kakoune - mawww's experiment for a better code editor
vim-ultest - The ultimate testing plugin for (Neo)Vim
xclip - Command line interface to the X11 clipboard
nvim - My custom NeoVim setup
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
refactoring.nvim - The Refactoring library based off the Refactoring book by Martin Fowler
editorconfig-core-go - EditorConfig Core written in Go