There seems to be a bug with ts_tree_cursor_goto_parent when the cursor is initialized on a non-root node.

I got it in the Emacs Lisp binding, but can reproduce it with the NodeJS binding (0.16.0):

const Parser = require('tree-sitter');
const Rust = require('tree-sitter-rust');

parser = new Parser();
parser.setLanguage(Rust);

tree = parser.parse("fn foo() {}");

> 

I just wanted to mention a possible error in the FAQ.

In the section How to move snapshots to a new hard drive, the command line indicated in solution 3:
cd /DESTINATION; tar cf - /SOURCE/* | tar xf -
might have to be replaced by:
cd /SOURCE; tar cf - * | tar -C /DESTINATION/ -xf -

Otherwise o

When there's no comment, extractlocstrings will generate entries like
/* No comment provided by engineer. */ all over the place. These comments should be removed by default on normalization. There might even be an option to remove comments alltogether.

How can i run this animation if component is in focus instead of render? #

• circleci

I noticed that when a DDlog project is recreated in-place (i.e., without a previously created one being removed), stale files from the previous version are kept around, although they may no longer be needed.

Example:
For the d3log work we had d3log/schema/mod.rs. I have created the server_api project with that layout (ddlog -i server_api.dl -L../../lib).
Now I changed `d3log/schema/mo

When a query is invalid, ts-make-query raises an error like this:

(rust-panic "called `Result::unwrap()` on an `Err` value: Syntax(1, \"[(call_expression function: (identifier) @function)]\\n^\")")

This is because _make_query uses unwrap.

It should instead define a new error class, e.g.

Hi,

I have started using the add-on and most of the times I just select a paragraph and press X to extract but I do not need to modify it. It would nice to have a another radio button next to "Enter title only", named "Do not edit extracted note", that when selected, when I just press X, the note gets extracted in the right deck, the text gets highlighted (in green), and it skips the second scr

Add a little Wiki for new user to understand some things that are not obvious. Like the Color of items, or classes and their differences or Keys to control (Like Space for pause).

A good testing regime could include the following:

• Perform an initial backup
• Verify volume
• Perform an incremental backup
• Verify volume
• Prune first backup
• Verify volume
• Diff volume (cross-check with source vol data)

Changing program_name in the code could allow the test data set to be created under a different base folder name without interfering with real-life back