xbase
Our great sponsors
xbase | pycodestyle.nvim | |
---|---|---|
10 | 3 | |
503 | - | |
3.2% | - | |
5.6 | - | |
3 months ago | - | |
Rust | ||
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.
xbase
- Xcodebuild.nvim - plugin to develop iOS, iPadOS, and macOS apps in Neovim
-
Issue with sourcekit lsp (swift)
However I can't seem to find where this argument is being passed in from. I'm using the plugin xbase (https://github.com/kkharji/xbase/) and it doesn't have this string anywhere in the project. It seems like other people have been able to get it running.
- Swift development using NeoVim instead of Xcode?
-
Did anyone succeed to set up neovim for iOS development in Swift?
You can follow the discussion here: https://github.com/kkharji/xbase/issues/178
-
Why Rust ?
I think an excellent example is https://github.com/xbase-lab/xbase/blob/master/Cargo.toml
-
🚀 XBase 0.2: Now with Tuist, Swift, and barebone xcodeproj support!
Checkout Release notes for a comprehensive list of features and bug fixes.
- A work in progress Xcode replacement-ish development environment for neovim.
-
Xbase: The long awaited Xcode project support for neovim
I've added to be support in the next minor release, feel free to subscribe to the issue get updates https://github.com/tami5/xbase/issues/65
pycodestyle.nvim
-
Why aren't there more plugins written in python?
With that said, there is still a use for remote plugins: if you really need a libraries from that ecosystem, and you would have those libraries anyway, then there is no harm done. I have a plugin called pycodestyle.nvim which makes your Pycodestyle linter configuration available in Neovim. That way I can use my linter settings as my editor settings per project, no need to keep separate settings in sync. If I want to use that plugin I need Pycodestyle installed anyway, and if Pycodestyle is not available to plugin stays dormant.
-
Why Rust ?
Not really. There is exactly one legitimate use case for writing plugins in something other than Lua or Vim script: if you want to use libraries written in that language. For example, I have a plugin named pycodestyle.nvim which is written in Python because it uses the Pycodestyle library to figure out the user's linter configuration. If I wanted to do it in Lua I would basically have to re-implement a major part of Pycodestyle myself, which would be a pointless waste of time. And people who use that plugin already have Pycodestyle installed anyway, so it's not an extra dependency.
-
[plugin] pycodestyle.nvim
Link. When I write Python I usually have pycodestyle as my linter, and this got me thinking: If I already have a linter configuration for a project, why not just use the linter configuration as my editor configuration as well? The linter configuration is useful to others even if they use a different editor and I don't have to duplicate it in a local vimrc or editorconfig file. I can just use what I already have.
What are some alternatives?
Tuist - 🚀 Create, maintain, and interact with Xcode projects at scale
pycodestyle - Simple Python style checker in one Python file
cargo-mobile - Rust on mobile made easy!
nvim-snippy - Snippet plugin for Neovim written in Lua
script-bench-rs - Rust embedded scripting languages benchmark
kok.nvim - Fast as FUCK nvim completion. SQLite, concurrent scheduler, hundreds of hours of optimization.
Nim - Nim is a statically typed compiled systems programming language. It combines successful concepts from mature languages like Python, Ada and Modula. Its design focuses on efficiency, expressiveness, and elegance (in that order of priority).
coreutils - Cross-platform Rust rewrite of the GNU coreutils
Fennel - Lua Lisp Language
butte
ultisnips - UltiSnips - The ultimate snippet solution for Vim. Send pull requests to SirVer/ultisnips!