Skip to content

Instantly share code, notes, and snippets.

View Stalruth's full-sized avatar

Stuart Rutherford Stalruth

View GitHub Profile
@Stalruth
Stalruth / Abdullah Mohayyuddin.diff
Last active August 24, 2023 00:19
VGC23 Worlds OTS Changes Day 1-2
Gholdengo @ Sitrus Berry
Ability: Good as Gold
Tera Type: Flying
- Make It Rain
- Shadow Ball
- Nasty Plot
- Protect
Chien-Pao @ Focus Sash
Ability: Sword of Ruin

Stage Channels with Video was being tested for this stage. This includes Webcam + Stream

  • Quick API Updates
    • 10-Nov Active Devloper Badge
    • 16-Nov nsfw flag on commands
      • Apps in App Directory cannot have NSFW commands
    • 12-Dec Linked Roles + Connection Metadata
      • Linked Roles
  • Listed when you clck on a role
@Stalruth
Stalruth / Stage-5-Oct-2022.md
Last active April 22, 2023 18:16
5 Oct 2022 Stage

5-Oct-2022 Stage

API Updates

  • Command Picker Performance Experiment
    • UI Menu for slash commands
    • Pulls commands and checks permissions
    • Uses cache for time sensitivity
      • Modifications are in an experiment
  • OLD: Switching channels clears the cache
@Stalruth
Stalruth / Stage 2022-06-25.md
Last active March 13, 2023 03:28
The June 2022 Discord Developer Stage

Recording by @Wolfhound905

User Survey

  • Sets context for API and App updates
  • Survey was sent out to bot users
  • 60% of respondents have used Slash Commands; this went up over time
  • 50% of users say the main reason they like Slash Commands is Discoverability
    • Incl. features such as Autocomplete and Message Components
  • Top two features users struggle with
@Stalruth
Stalruth / stage_2021-12-18.md
Last active May 10, 2022 10:00
December 2021 Discord Developer stage
@Stalruth
Stalruth / summarise-bot.py
Created August 11, 2021 11:08
Prints the commands of the Discord Bot given.
#!/usr/bin/env python3
import urllib.request as request
import urllib.parse as parse
import base64
import json
import os
import argparse
base_url = 'https://discord.com/api/v9'
@Stalruth
Stalruth / grok_vi.mdown
Created November 19, 2015 04:12 — forked from nifl/grok_vi.mdown
Your problem with Vim is that you don't grok vi.

Answer by Jim Dennis on Stack Overflow question http://stackoverflow.com/questions/1218390/what-is-your-most-productive-shortcut-with-vim/1220118#1220118

Your problem with Vim is that you don't grok vi.

You mention cutting with yy and complain that you almost never want to cut whole lines. In fact programmers, editing source code, very often want to work on whole lines, ranges of lines and blocks of code. However, yy is only one of many way to yank text into the anonymous copy buffer (or "register" as it's called in vi).

The "Zen" of vi is that you're speaking a language. The initial y is a verb. The statement yy is a simple statement which is, essentially, an abbreviation for 0 y$:

0 go to the beginning of this line. y yank from here (up to where?)