hyperupcall

// I'm tired of extensions that automatically:
// - show welcome pages / walkthroughs
// - show release notes
// - send telemetry
// - recommend things
//
// This disables all of that stuff.
// If you have more config, leave a comment so I can add it!!

{

Atinux

// ~/server/api/sse.ts
export default defineEventHandler(async (event) => {
  if (!process.dev) return { disabled: true }

  // Enable SSE endpoint
  setHeader(event, 'cache-control', 'no-cache')
  setHeader(event, 'connection', 'keep-alive')
  setHeader(event, 'content-type', 'text/event-stream')
  setResponseStatus(event, 200)

noxasaxon

Learning Rust

Getting Started + Installation | Cheat Sheet

Table of Contents

1. How Do I Start Learning Rust?!
2. Ok, I Think I Know The Basics But How Do I Get Better?!
3. Rustlang Tooling
4. Helpful References Throughout Your Journey
5. The Rust Community
6. Recommended (but not free) Books & Courses

mourner

alias ..="cd .."
alias ...="cd ../.."
alias ....="cd ../../.."
alias .....="cd ../../../.."

# Shortcuts
alias db="cd ~/Dropbox"
alias dl="cd ~/Downloads"
alias dt="cd ~/Desktop"
alias p="cd ~/projects"

brolnickij

<template lang="pug">
  .vm-gallery
    div(
      :style="{ transitionDuration: transitionDuration, transform: translate3DPosition }"
      ref="galleryItems"
    ).vm-gallery-items
      div(v-for="imageItem in imageNodes").vm-gallery-item
        img(
          :src="imageItem.src"
          :key="imageItem.src"

Atinux

[
  {
    "key": "ctrl+shift+n",
    "command": "workbench.action.terminal.new"
  },
  {
    "key": "ctrl+shift+right",
    "command": "workbench.action.terminal.focusNext"
  },
  {

sandren

Tailwind CSS best practices

Utility classes

1. When writing a string of multiple utility classes, always do so in an order with meaning. The "Concentric CSS" approach works well with utility classes (i.e,. 1. positioning/visibility 2. box model 3. borders 4. backgrounds 5. typography 6. other visual adjustments). Once you establish a familiar pattern of ordering, parsing through long strings of utility classes will become much, much faster so a little more effort up front goes a long way!

2. Always use fewer utility classes when possible. For example, use mx-2 instead of ml-2 mr-2 and don't be afraid to use the simpler p-4 lg:pt-8 instead of the longer, more complicated pt-4 lg:pt-8 pr-4 pb-4 pl-4.

3. Prefix all utility classes that will only apply at a certain breakpoint with that breakpoint's prefix. For example, use block lg:flex lg:flex-col lg:justify-center instead of block lg:flex flex-col justify-center to make it very clear that the flexbox utilities are only applicable at the

manimike00

### Step 1: Set the RSA Public Key in Both SCM (BitBucket and Github) 
### Step 2: Ensure StrictHostKeyChecking no in /etc/ssh/ssh_config 
### Step 3: Pass repo names as Parameter while  executing the Script 
###        For Example: bash test.sh reponame 
### Step 4: Make Sure Ensure You have same repo name in both SCM

for i in "$@"
do
        git clone git@bitbucket.org:username/${i}.git
        cd bbgg

getify

var Force = { Skywalker, RegularFolk, of: Skywalker };

function Skywalker(v) {
  return { map, chain, ap };
  function map(fn) {
    return Skywalker(fn(v));
  }
  function chain(fn) {
    return fn(v);
  }

vinayakkulkarni

Setting up Laravel Projects using Vessel

Install Docker & docker-compose

Installing Docker

• Update the apt package index:

sudo apt-get update