beancount-language-server
rq
| beancount-language-server | rq | |
|---|---|---|
| 2 | 10 | |
| 11 | 2,256 | |
| - | - | |
| 0.0 | 3.2 | |
| almost 2 years ago | 5 months ago | |
| Rust | Rust | |
| MIT License | Apache License 2.0 |
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.
beancount-language-server
-
Understanding the differences between LSP and Treesitter?
Nothing. LSP is a protocol to communicate with a LanguageServer to retrieve information like completions or errors. TreeSitter is a parser for source code and used to highlight more precise than using regular expressions. So, LSP is conceptually located on a higher level than TreeSitter, in fact you can implement a LanguageServer based on a TreeSitter parser grammar.
-
What's everyone working on this week (27/2021)?
Basically porting a Beancount language server written in JS to one in Rust. So far, this has been a piece of cake thanks to tree-sitter, trie-rs and tower-lsp.
rq
- Jc – JSONifies the output of many CLI tools
-
Shell Script Best Practices, from a decade of scripting things
Not sure what it is doing more...I'm referring to this rq: https://github.com/dflemstr/rq#format-support-status
It converts to/from the listed formats.
There is also `jc` (written in Python) with the added benefit that it converts output of many common unix utilities to json. So you would not need to parse `ip` for example.
https://github.com/kellyjonbrazil/jc
-
What debugging/monitoring method do you use? Lately, I have been using the Saleae Logic Analyzer to monitor the signals exchanged among the boards of my embedded network. I find it really cool, but do you have any other recommendations? What do you use?
In robotics most relevant signals are seen by the software. My current pattern is to log everything to MessagePack files (e.g. using mpacklog in Python or palimpsest in C++), then dump and plot the data later on using handy command-line tools like jq and rq.
- Tombl – Easily query .toml files from bash
- rq: Universal convertor between structured data (JSON, MessagePack, CBOR, etc.)
- Show HN: utt, the Universal Text Transformer
- FX: An interactive alternative to jq to process JSON
- Tips on Adding JSON Output to Your CLI App
-
Miller CLI – Like Awk, sed, cut, join, and sort for CSV, TSV and JSON
There's also rq (record query)[1] that also supports CSV and JSON but not TSV though. It's written in Rust.
[1] https://github.com/dflemstr/rq
-
What's everyone working on this week (27/2021)?
Ish. https://github.com/dflemstr/rq/ It removed its processing language a while ago. It's still a very useful tool, though. Imho, it's a bigger pity that it can't highlight YAML on output, or parse YAML 1.1.
What are some alternatives?
beancount-language-server - A Language Server Protocol (LSP) for beancount files
fx - Terminal JSON viewer & processor
TablaM - The practical relational programing language for data-oriented applications
if-decompiler - Decompile Glulx storyfiles into C code
jiq - jid on jq - interactive JSON query tool using jq expressions
panamax - Mirror rustup and crates.io repositories, for offline Rust and cargo usage.
hello-actix - Hello, actix!
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
dprint - Pluggable and configurable code formatting platform written in Rust.