My Monkey Do

A Log of Coding Solutions

VS Code: Open MD files in Preview Mode

by

Problem:

When viewing Markdown files in Visual Studio Code it opens in the edit mode and you see markdown instead of the formatted version. To see the formatted version you have to right click on the tab and Open Preview mode. It’s often quicker to just read the file.

Solution:

Can’t believe I’ve gone so long without this. Open the Command Pallet (Crl+Shift+P / Cmd+Shift+P) and select Preferences: Open User Settings (JSON)

Add the following entry:

"workbench.editorAssociations": {
  "*.md": "vscode.markdown.editor"
},
"markdown.preview.doubleClickToSwitchToEditor": true

When you need to edit the Markdown source, you can flip the toggle between the lock icon and the pencil icon.

Side note, if you’re in “Markdown Preview” (not Markdown Editor), you can switch from Preview to editing using these methods:

  • Double-clicking anywhere on the rendered preview page
  • Ctrl+Shift+V / Cmd+Shift+V
  • At the top right, there’s a toolbar you can use to switch between editor and preview mode.

Can’t use AdminerNeo on Mac

by

Problem

I was having a similar issue as this person on the Local Community forum. Clicking the link of “Open AdminerNeo” did nothing and the logs showed “Unhandled Rejection”.

Solution

Apparently Local has a preferred PHP version which is currently
PHP—8.2.29. I did some spring cleaning and removed that unknowingly required version of PHP. Restoring that version resolved my issue. Unfortunately, I can’t reply to that locked forum post.

Run Long Jobs in Background on Linux

by

To run long running jobs on linux and not have to be logged in, do the following:

1. Start a new screen session

screen -L -S longjob

2. Run your long-running command

This will allow you to see the output of the command while it’s also written to a log file

your-command --with --args |& tee -a ~/longjob.log

3. Detach and leave it running

Ctrl + A then D

4. Log out safely

exit

5. Reattach later

screen -r longjob

6. When you’re done

Ctrl + D

Spam Filters for Smarter Spam Tactics

by

Problem

Backscatter “bounce” emails are landing in the inbox—legitimate Delivery Status Notifications (DSNs) from Google’s Mailer-Daemon with “Address not found.” The attached/original shows spam that spoofed your address and tried sending to a non-existent recipient (e.g., [email protected]). Because the spammer forged your envelope sender, the receiving server rejected the message and sent the failure notice back to you.

Solution

These DSNs are real system reports, not the spam itself—and the likely cause is not that your email is compromised, but that someone spoofed your address.

Don’t mark these DSNs as spam; doing so can pollute spam training and may hide bounce reports you actually need. Instead, auto-handle only the unwanted DSNs tied to that bogus recipient with a precise Gmail filter:

from:[email protected] ("X-Failed-Recipients: <BOGUS-ADDRESS>" OR "Your message wasn't delivered to <BOGUS-ADDRESS>")

Replace <BOGUS-ADDRESS> with the invalid recipient you’re seeing, then create the filter and choose Skip the Inbox (Archive) or Delete. This keeps your inbox clean, preserves accurate spam training, and ensures legitimate bounce messages still surface—while recognizing that spoofing (not account compromise) is the root cause.

Class “Some/Namespace/App.php” not found (only on server)

by

The Problem

Everything works fine on your Mac OS setup, but for some reason, on your Linux server you get the error below. All file names look correct, case sensitive and all.

Class "Some/Namespace/App.php" not found.

The Solution

When you rename a file on Mac and it’s just changing the case, git won’t pick it up. So while you think it’s renamed on the server, it may not be! When renaming a file and it’s just changing the case, use:

git mv app.php App.php

Thisisunsafe

by

Problem

Sometimes you need to run https sites locally and you can’t get by Chrome’s warning of NET::ERR_CERT_INVALID. Google has removed the link to just bypass this warning recently.

Solution

While this is more of a workaround than a solution (you should resolve the invalid cert), you can get by Chrome’s security warning by typing “thisisunsafe”. Don’t type it in the address bar, just have the window in focus. You won’t see what you’re typing, but when you finish typing the browser window will reload and display the site.