Armando Pérez Marqués

Nitpick: To me what's disorienting about removing inaccessible jump labels is that, since there are now a lot less jump labels on the screen, it's now less clear the current...

@SomeKittens I'm sending you the ophthalmologist's bill.

The intention is to improve on convenience and ergonomics. When using `:reset-diff-change` to look the previous version of the hunk, it is now out context, we "lost" the new version,...

Another data point in case it's helpful, I'm able to get Helix @`master` to panic with these steps: Environment: Ubuntu, Wayland, Alacritty, Zellij * Start Helix * In a scratch...

I'm using [SoDa Reloaded](https://github.com/Miw0/sodareloaded-theme) over the original Soda theme because of this very feature.

@kimke [I just coded my variant](https://github.com/zerok/django-flatblocks/pull/9) Anyway now I'm thinking that some things can be improved on what I have done. I used `{% flatblock_default %}{% end_flatblock_default %}` for the...

@zerok: Let's see if I make some time to implement that syntax. @kmike: About default text changes when the block is overriden in DB; well, is logical that the text...

Full stacktrace: ``` ERROR in ./src/index.js Module build failed: Error: Plugin 2 specified in "/project/path/.babelrc" provided an invalid property of "default" at Plugin.init (/project/path/node_modules/babel-core/lib/transformation/plugin.js:131:13) at Function.normalisePlugin (/project/path/node_modules/babel-core/lib/transformation/file/options/option-manager.js:152:12) at /project/path/node_modules/babel-core/lib/transformation/file/options/option-manager.js:184:30 at...

@colinwren Well is not really a fix, is more like a workaround to get it working locally. This is still a problem since the "fix" is not available in new...

@hollandThomas This is the config that works for me; just add `'graphql'` to your `plugins` section, and add this rule to your `rules` section: ```javascript rules: { // ... 'graphql/template-strings':...