73
33
15
A real-time raytracing rendering engine for higher-dimensional spaces that works right in your browser
Execute JavaScript, CoffeeScript, or shell code directly from a selection in Atom and replace the code with its result.
Events
Sub word boundary navigation
Check for existing issues
- [X] Completed
Describe the feature
The ability to navigate between "sub-word" boundaries. Each word in a CamleCase string would be separated by a subword boundary. Same with CONSTANT_CASE or snake_case.
In VS Code this is only possible with an extension. Atom supported this natively.
If applicable, add mockups / screenshots to help present your vision of the feature
No response
Sub word boundary navigation
You are right, thank you!
Sub word boundary navigation
Check for existing issues
- [X] Completed
Describe the feature
The ability to navigate between "sub-word" boundaries. Each word in a CamleCase string would be separated by a subword boundary. Same with CONSTANT_CASE or snake_case.
In VS Code this is only possible with an extension. Atom supported this natively.
If applicable, add mockups / screenshots to help present your vision of the feature
No response
Jump by paragraph
This is super useful! Unfortunately, not many people use (or know about it) this but every time I use this in pair programming people what to use this too
Key-bindings for cycling tabs and selecting specific tabs
IMO cycling through tabs is supercritical. Stops me from using Zed. Dunno how this isn't the first thing anyone uses, maybe it's just me.
Also IMO:
- Cycling through tabs should not use MRU order but simply switch between tabs in the list
-
cmd-<number>should select tabs not panes (i.e. switchingctrlandcmdmappings), like it does in most applications
Set.has() and Array.includes() should narrow the type of their argument to the type of this when they return true
Is this that complicated? This seems to fulfill the requirement already:
/** Shouldn't this be the type signature of Array.prototype.includes?
function arrayIncludes<T>(arr: T[], v: unknown): v is T {
return arr.includes(v as T);
}
I assume I am missing something but couldn't the type signature simply be changed to this?
