You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The three variables other than $body are never populated. They're whitespace only, and getting to the right spot to fill them in often requires something like pre green ex semicolon.
I'd like to be able to autofill these with cursorless-aware placeholders. These would be strings that cursorless selects specifically to get good hats, in the current context.
(In a similar vein, in a thing I'm quietly working on, foo is hooked up to generate qwjkzy, because those are the six least commonly occurring letters in Go files, and thus likely to have nice hats.)
So instead of inserting:
for ; ; {
// existing statement
}
It might insert something like:
forqwj8; zyk9; pmv7 {
// existing statement
}
This is low priority, as I have a workaround I'm using:
How come you don't use "tab" / "shift tab" to navigate snippet placeholders?
If the issue is that they are a bit fragile, eg if you navigate outside the snippet, see Stable snippets #443. Your suggestion / workaround seem like an easy way to get some of that stability
Consider this snippet extract:
The three variables other than
$body
are never populated. They're whitespace only, and getting to the right spot to fill them in often requires something likepre green ex semicolon
.I'd like to be able to autofill these with cursorless-aware placeholders. These would be strings that cursorless selects specifically to get good hats, in the current context.
(In a similar vein, in a thing I'm quietly working on,
foo
is hooked up to generateqwjkzy
, because those are the six least commonly occurring letters in Go files, and thus likely to have nice hats.)So instead of inserting:
It might insert something like:
This is low priority, as I have a workaround I'm using:
But it's a bit inferior, in that it over-indexes on hex digits, which are very common. Sample output:
The text was updated successfully, but these errors were encountered: