MacBook, defective by design banner

title:
Put the knife down and take a green herb, dude.


descrip:

One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com

Using 89% of the same design the blog had in 2001.

FOR ENTERTAINMENT PURPOSES ONLY!!!
Back-up your data and, when you bike, always wear white.

As an Amazon Associate, I earn from qualifying purchases. Affiliate links in green.

x

MarkUpDown is the best Markdown editor for professionals on Windows 10.

It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support.

Features you won't find anywhere else include...

You've wasted more than $15 of your time looking for a great Markdown editor.

Stop looking. MarkUpDown is the app you're looking for.

Learn more or head over to the 'Store now!

Saturday, July 02, 2022

How to get VS Code to stop complaining about comments in JSON files:

  1. Open your settings as JSON.
  2. Add this:
"files.associations": {
    "*.json": "jsonc"
}

I'm not saying you want to do this. You might not. JSON shouldn't have comments. But if you do want to, that's how you do it.

You can also use specific file names or paths there instead of grenading every *.json file into *.jsonc (json "with comments").

Labels: ,


posted by Jalindrine at 7/02/2022 02:24:00 PM
Tuesday, May 31, 2022

Essentially all my life, if I've had text selected in an editor and typed a character, the text disappears (is deleted) and only the character typed remains in its place.

I've noticed VS Code doesn't do this by default for all characters. It auto-surrounds instead. /sigh

If I have code selected and hit {, it surrounds all of that selection with a pair of squiggle brackets instead of deleting it.

(I actually hate auto-closing brackets too. If I type { even with nothiing selected, please don't insert a } I now have to manage. Note that theses are two different behaviors.)

For me, the solution is to turn off autoSurround.

In json:

editor.autoSurround": "never"

And in the Settings UI.

a picture of how to set autoSurround in VS Code's UI for settings

Thank you for attending this sanity talk.

Labels: ,


posted by ruffin at 5/31/2022 09:45:00 AM

<< Older | Newer >>


Support freedom
All posts can be accessed here:


Just the last year o' posts:

URLs I want to remember:
* Atari 2600 programming on your Mac
* joel on software (tip pt)
* Professional links: resume, github, paltry StackOverflow * Regular Expression Introduction (copy)
* The hex editor whose name I forget
* JSONLint to pretty-ify JSON
* Using CommonDialog in VB 6 * Free zip utils
* git repo mapped drive setup * Regex Tester
* Read the bits about the zone * Find column in sql server db by name
* Giant ASCII Textifier in Stick Figures (in Ivrit) * Quick intro to Javascript
* Don't [over-]sweat "micro-optimization" * Parsing str's in VB6
* .ToString("yyyy-MM-dd HH:mm:ss.fff", CultureInfo.InvariantCulture); (src) * Break on a Lenovo T430: Fn+Alt+B
email if ya gotta, RSS if ya wanna RSS, (?_?), ยข, & ? if you're keypadless


Powered by Blogger etree.org Curmudgeon Gamer badge
The postings on this site are [usually] my own and do not necessarily reflect the views of any employer, past or present, or other entity.