elisp-tree-sitter
vimwiki
Our great sponsors
elisp-tree-sitter | vimwiki | |
---|---|---|
21 | 112 | |
803 | 8,568 | |
0.7% | 0.5% | |
6.3 | 6.8 | |
17 days ago | 1 day ago | |
Emacs Lisp | Vim Script | |
MIT License | GNU General Public License v3.0 or later |
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.
elisp-tree-sitter
-
How to Get Started with Tree-Sitter
Look at the original integration project https://github.com/emacs-tree-sitter/elisp-tree-sitter, before it was done inside Emacs 29+.
-
function to mark all within brackets, quotes, etc
When tree-sitter is available you may extend expand-region with this one one https://github.com/emacs-tree-sitter/elisp-tree-sitter/issues/20 Works very nice for me. But simple matching pairs should be handled well by expand-region alone
-
How to use Emacs 29 Tree-sitter?
That said, if you want a more complete experience with tree-sitter right now, there’s a 3rd party implementation with support for a lot more languages, and also automatically downloads all supported grammars. It’s available here: https://github.com/emacs-tree-sitter/elisp-tree-sitter
-
why is melpa still necessary for stuff that is built-in to emacs?
Just like there are multiple LSP implementations for emacs (lsp-mode, eglot, lsp-bridge), there are multiple tree-sitter implementations. The one recently included in emacs was never a standalone package, I believe (correct me if that’s wrong), but was created with the purpose of being included in emacs. You will need melpa to download the linked elisp-tree-sitter package (https://github.com/emacs-tree-sitter/elisp-tree-sitter), but not the built in one.
-
tree-sitter has been merged into master
How am I going to even use the built-in one? I was using elisp-tree-sitter. I know I have to add grammar for different languages, but how? I have been searching for a while and still have no clue.
-
Ask HN: S/W development text editor have feature colorizing every iteration?
from github README.rst "Emacs package that provides a standardized framework for manipulating and navigating your source code using tree sitter's concrete syntax tree " -> https://github.com/mickeynp/combobulate
https://www.spacemacs.org/ with https://github.com/emacs-tree-sitter/elisp-tree-sitter then write a iterator/loop query for language(s) editing per https://tree-sitter.github.io/tree-sitter/syntax-highlightin...
tad less installation heavy (sorta) but also makes use of tree-sitter syntax queries : https://www.lunarvim.org (neovim with treesitter syntax)
blockman usage examples: https://www.youtube.com/channel/UC5539gDeAdWqeXcczWuhnBA
Alternative examples / takes (per user interface):
### embedding a block of source code in a document:
** carrotsearch.gethub.io/apidocs/code-blocks
-
regarding feature/tree-sitter branch
However, if you want to use tree-sitter today, there is the tree-sitter package which enables tree-sitter syntax highlighting in a number of popular major modes. I’ve been using it for about six months now in all major modes it supports.
-
how to configure doom emacs (generic emacs too) with a C project
Tree Sitter and lsp-mode might be of help. Looks like both take a bit of work to get going. I have personally not used them, so try out which suits you and let us know how it went.
-
Commercial-Emacs
You can use tree-sitter already if you have dynamic module support: https://github.com/emacs-tree-sitter/elisp-tree-sitter
- Are we living in the golden age of Emacs?
vimwiki
-
Neorg – organize your life in Neovim
No, Neorg does not use the same markup as Org-mode. They use their own specification that is specifically designed to be different from Org-mode spec.
https://raw.githubusercontent.com/nvim-neorg/norg-specs/main...
Furthermore, each item you have listed as a benefit to Org-mode is in fact capable of being done in Markdown via plugins for neovim, and probably other markdown editors, like Loqseq, Roamresearch, or Obisidian, much in the same way you speak of plugins that interface with .org docs.
https://github.com/wthollingsworth/pomodoro.nvim
https://github.com/Myzel394/easytables.nvim
https://github.com/vimwiki/vimwiki
So, my suggestion is that before dismissing a comment regarding a plugin that is unfamiliar to you, is to read its spec, and then try to understand why people would be perhaps dismissive of that tool, especially when it chooses to conflict with existing, more popular choices.
- Vimwiki – A Personal Wiki for Vim
-
Wrap long lines in markdown tables
you might want to look at how vimwiki does markdown tables https://github.com/vimwiki/vimwiki
-
Note taking in Neovim?
I've been thinking of setting up a note taking enviroment in neovim. I've been searching around, and plugins as vimwiki, and nabla.nvim are great choices for me. I'm using Notion right now because of the great commands that brings that make the note taking pretty enjoyable. But the dividers, or putting background to text are features that I don't wanna lose, if possible.
-
Ask HN: Did anyone write a book in Nano?
I wrote a manuscript in vim a couple Novembers ago, for NaNoWrimo. I used a couple plugins, primarily Goyo [1] to add some margins, but otherwise, yeah, plain vim.
I don't think it was really any more productive than my current workflow in Obsidian. Vim keybindings are more useful for editing than for writing (and for editing code in particular, where the changes you're making are much more structured). Also, while the extra features afforded by Obsidian don't really make a difference during the writing process, I find they're really useful for outlines and other preliminary work, which is something of a point against a vim-only workflow unless you want to use vimwiki [2] or something.
Granted, Obsidian is still a markdown-based tool, so there's still some level of minimalism going on there, but by that point we're really discussing markup vs word processors, which is its own conversation—and to my mind, a much more important one. I much prefer working in markup than in a rich text editor, because plain text is easy to edit and process through the terminal, and because it lets me separate style choices from content.
I find that the markdown live preview that editors like Obsidian and Typora provide (and which vim doesn't) is a really nice compromise between a slick composing experience and the technical affordances of markup. Between that and Obsidian's hypertext features, I think I'll stick with Obsidian for the foreseeable future.
[1]: https://github.com/junegunn/goyo.vim
[2]: https://vimwiki.github.io/
-
Art Historians, how do you take notes
I use vimwiki.
-
Learning Emacs: Where to Start?
Hey folks, I have been using Neovim for the past 2 years, don't have any complaints, however, I really want to give Emacs an honest try but not really sure where to start. I want to do basic text editing, programming and something similar to vimwiki (https://github.com/vimwiki/vimwiki)
-
Notetaking when solving issues and learning stuff
How about learning vim and using vimwiki ?
-
Reconstructing Obsidian Features in Vim and Bash
What, we're talking about wikis and vim, and not mentioning vimwiki?
https://github.com/vimwiki/vimwiki
I tried a whole bunch of personal wikis over the years (I see Zim has been mentioned, that's one of the ones I remember trying) and this is the only one that stuck.
-
What are some ways you used Python to make YOUR life easier?
I have created full on programs to systematically created screenshots with the game emulators with RetroArch. Also an automation tool to use a preexisting program named chdman that converts files into a needed format (also unpacking from archives). A little Python script to create a recents list of files for Vimwiki. I also created a program to access 🌈 emojis 🌈. I wrote my own GE Proton downloader and manager. Hell even the window manager I am using on Linux is written and configured in Python, Qtile. I wrote one or two plugins for it and the entire configuration is written in Python, meaning I can use functions, modules and every logic of Python to enhance it. It's Awesome.
What are some alternatives?
tree-sitter-go - Go grammar for tree-sitter
vim-orgmode - Text outlining and task management for Vim based on Emacs' Org-Mode
tree-sitter - An incremental parsing system for programming tools
neorg - Modernity meets insane extensibility. The future of organizing your life in Neovim.
typescript.el - TypeScript-support for Emacs
wiki.vim - A wiki plugin for Vim
lsp-treemacs - lsp-mode :heart: treemacs
obsidian-releases - Community plugins list, theme list, and releases of Obsidian.
tree-sitter-ruby - Ruby grammar for tree-sitter
neuron.nvim - Make neovim the best note taking application
tree-sitter-kotlin - Kotlin grammar for Tree-sitter
zim-desktop-wiki - Main repository of the zim desktop wiki project