A rare case of a topic text opening with providing context on what it is talking about. Thank you! I love it.
I don't use one. I don't feel like I have conflicting keybindings, or a need for additional keys. When I do, I customize my bindings through settings.
I mainly work with C#, where I use Visual Studio. I think I mainly changed bindings for expand selection, and go to definition, declaration, implementation (ALT+A/+S/+D). All other bindings work out for me.
Cursor and selection "jumping" with CTRL and SHIFT, and using multiple cursors is a regular occurrence for me. I largely keep using keyboard, but for navigating I do often switch to or combine it with mouse.
When it's not C#, it's often VS Code, or otherwise Notepad++ for non-IDE simple editing. For even simpler quick edits I also use Double Commanders integrated text editor.
I use TortoiseGit, and its diff editor. I sometimes make changes there too. I also occasionally use KDiff or Winmerge.
I think whether it's worth to learn a new one should be determined by 1. what are your pain points/shortcomings, 2. what are the promises or your hopes, and 3. testing it out.
If you explore a promise and quickly find it not useful to you, it may be easy and simple to dismiss a switch without investing more.
Important for what?
Depends on a lot of things.
The bigger and more complex the project, the more important a mentor to onboard, collaborate, and gain experience.
The better the mentor, the more you can gain in terms of specific and broad knowledge, not only about the things at hand, but understanding of alternatives and concepts.
I had to look up pebkac / PEBKAC
problem exists between keyboard and chair
I also like the acronym PICNIC - problem in chair not in computer
Storage concerns should be separate from the data model.
would make it clearer
Would make what clearer?
If I change a string to a raw string or an interpolated string, it is a semantic change on the entire string, even if it leads to consequential changes only on subsections of it. The next time or additional changes I make must take different semantics into account.
If the formatting configuration forces one specific style then that is the deliberate choice; to have that one.
If there is no uniform single string quoting it is useful to differentiate between them; for example if for normal strings ' is preferred while for specific cases where escaping characters like \n is required, " must be used.
0x[7F000001] | chunks 1 | each { into int } | str join "."
# => 127.0.0.1
really cool
I'll add that to the community description/sidebar as a simple demonstrative example
Don't use the share with shortened url. Copy the page url instead.
Otherwise (you'll have to) accept that you don't know what's included in the shortened link.
""to''… There is nothing to highlight for SemanticDiff.
Really? I definitely want to see that. I want to be deliberate about my code. I am not only targeting compiled code. I am also targeting developers through maintainable code.
I'm surprised they did not list an alternative that would be my preference: Highlight the entire string. The f prefix changes the entire text value type. I would like the `f´ to be highlighted strongly, and string it changes the interpretation of weakly, and the placeholder variable more strongly again.
ffaattaall eerrrroorr UU11005588: : tteerrmmiinnaatteedd bbyy uusseerr
relevant Using Godot for GUI App Development | Popcar's Hub