GLMeece

Typora Language Support in Code Fences

Typora supports syntax coloring for code fences, and lists those languages on one of its support pages.

However, the list is not alpha sorted, so it's difficult to discover what languages are there unless one tries a ⌘-f/⌃-f to search for it.

I decided to help myself out and sort the list and post it in this Gist.

Sorted List

GLMeece

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Robot Framework: Launch Template",
      "type": "robotframework-lsp",
      "request": "launch",
      "terminal": "integrated",
      "env": {
          "SOME_KEY": "Some value",

GLMeece

{
  "Test Suite": {
    "prefix": "suite",
    "body": [
      "*** Settings ***",
      "Documentation     ${1:What does this testing suite cover?}\n",
      "Library           String  # just an example",
      "Library           \\${EXECDIR\\}/path/to/CUSTOM_LIBRARY.py",
      "Resource          \\${EXECDIR\\}/path/to/NAME_OF_ANOTHER.resource\n",
      "Suite Setup       SETUP_HERE",

GLMeece

If you have a company-managed OneDrive account like I do, you probably will never need or want to access a personal OneDrive account. It clutters up the Explorer menu and it's likely that you would prefer not to see it. Here's where I got the answer.

How to Stop Personal OneDrive from Being Pinned in Explorer

1. Open RegEdit (RegistryEditor): type regedit in the start menu and it should come up (select it)
2. Find the personal OneDrive here: hkey_current_user\software\microsoft\windows\currentversion\explorer\desktop\namespace
3. At the top, where it says Computer paste the following to the right of it (i.e., don't delete Computer):

GLMeece

Rule - 0201 [W]: missing-doc-keyword: Missing documentation in '{{ name }}' keyword
Rule - 0202 [W]: missing-doc-test-case: Missing documentation in '{{ name }}' test case
Rule - 0203 [W]: missing-doc-suite: Missing documentation in suite
Rule - 0204 [W]: missing-doc-resource-file: Missing documentation in resource file
Rule - 0301 [W]: not-allowed-char-in-name: Not allowed character '{{ character }}' found in {{ block_name }} name
Rule - 0302 [W]: wrong-case-in-keyword-name: Keyword name '{{ keyword_name }}' does not follow case convention
Rule - 0303 [E]: keyword-name-is-reserved-word: '{{ keyword_name }}' is a reserved keyword{{ error_msg }}
Rule - 0305 [W]: underscore-in-keyword-name: Underscores in keyword name '{{ keyword_name }}' can be replaced with spaces
Rule - 0306 [W]: setting-name-not-in-title-case: Setting name '{{ setting_name }}' should use title or upper case
Rule - 0307 [W]: section-name-invalid: Section name should be in format '{{ section_title_case }}' or '{{ section_upper_case }}'