Fadi002

import sys
import os

NOP = 0x90
offsets_and_values = {
    0x00030170: 0x00,
    0x000A94D0: NOP, 0x000A94D1: NOP, 0x000A94D2: NOP, 0x000A94D3: NOP, 0x000A94D4: NOP, 0x000A94D5: NOP, 0x000A94D6: NOP, 0x000A94D7: NOP, 0x000A94D8: NOP, 0x000A94D9: NOP, 0x000A94DA: NOP, 0x000A94DB: NOP, 0x000A94DC: NOP, 0x000A94DD: NOP, 0x000A94DE: NOP, 0x000A94DF: NOP, 0x000A94E0: NOP, 0x000A94E1: NOP, 0x000A94E2: NOP, 0x000A94E3: NOP, 0x000A94E4: NOP, 0x000A94E5: NOP, 0x000A94E6: NOP, 0x000A94E7: NOP, 0x000A94E8: NOP, 0x000A94E9: NOP, 0x000A94EA: NOP, 0x000A94EB: NOP, 0x000A94EC: NOP, 0x000A94ED: NOP, 0x000A94EE: NOP, 0x000A94EF: NOP, 0x000A94F0: NOP, 0x000A94F1: NOP, 0x000A94F2: NOP, 0x000A94F3: NOP, 0x000A94F4: NOP, 0x000A94F5: NOP, 0x000A94F6: NOP, 0x000A94F7: NOP, 0x000A94F8: NOP, 0x000A94F9: NOP, 0x000A94FA: NOP, 0x000A94FB: NOP, 0x000A94FC: NOP, 0x000A94FD: NOP, 0x000A94FE: NOP, 0x000A94FF: NOP, 0x000A9500: NOP, 0x000A9501: NOP, 0x000A9502: NOP, 0x000A9503: NOP, 0x000A9504: NOP, 0x000A9505: NOP, 0x000A9506: NO

marcpinet

Activate Sublime Text (for ever)

1. Go to https://hexed.it/
2. Click Open File in the top left corner and select sublime_text.exe
3. Press CTRL + F or on the Search for bar in the left panel and look for: 80 78 05 00 0f 94 C1
4. Now in the editor, click on the first byte (80) and start replacing each byte by: C6 40 05 01 48 85 C9
5. Finally, in the top left corner again, click on Save as and replace the old executable file with the newly created one.

Enjoy an Unlimited User License!

nemchik

{
  uc: '12.12',
  a: '100',
  c: '100',
  e: '100',
  f: '91',
  i: '11',
  ios: '12.2',
  o_a: '64',
  o: '82',

joepie91

ES Modules are terrible, actually

This post was adapted from an earlier Twitter thread.

It's incredible how many collective developer hours have been wasted on pushing through the turd that is ES Modules (often mistakenly called "ES6 Modules"). Causing a big ecosystem divide and massive tooling support issues, for... well, no reason, really. There are no actual advantages to it. At all.

It looks shiny and new and some libraries use it in their documentation without any explanation, so people assume that it's the new thing that must be used. And then I end up having to explain to them why, unlike CommonJS, it doesn't actually work everywhere yet, and may never do so. For example, you can't import ESM modules from a CommonJS file! (Update: I've released a module that works around this issue.)

And then there's Rollup, which apparently requires ESM to be u

nicerobot

• SC1000 $ is not used specially and should therefore be escaped.
• SC1001 This \o will be a regular 'o' in this context.
• SC1003 Want to escape a single quote? echo 'This is how it'\''s done'.
• SC1004 This backslash+linefeed is literal. Break outside single quotes if you just want to break the line.
• SC1007 Remove space after = if trying to assign a value (or for empty string, use var='' ... ).
• SC1008 This shebang was unrecognized. ShellCheck only supports sh/bash/dash/ksh. Add a 'shell' directive to specify.
• SC1009 The mentioned parser error was in ...
• SC1010 Use semicolo

tablacus

FV.TreeView.Focus();
return S_OK;

tablacus

FV.CurrentViewMode = FV.CurrentViewMode == FVM_LIST ? FVM_DETAILS : FVM_LIST;

tablacus

var FV = GetFolderView(Ctrl, pt);
FV.IconSize = 19;

scmx

How to use <details> <summary> expandable content on GitHub with Markdown

Firstly, what is <details> <summary>?

The HTML Details Element (<details>) creates a disclosure widget in which information is visible only when the widget is toggled into an "open" state. A summary or label can be provided using the <summary> element. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details.

Example

OwenMcDonnell

Param(
  [string]$yamlPath
)

if(!(test-path $yamlPath)) { write-warning "YAML path is invalid"; return; }

$token = "<your_token>"

$headers = @{
  "Authorization" = "Bearer $token"