webstrand

## blish-on-steam-deck.md

      
              1 file
            
          
              2 forks
            
          
                54 comments
              
            
              24 stars
            
          
                martinlabate
                / blish-on-steam-deck.md
            
            
              Last active
              December 15, 2024 04:48
            
              
                How to run BlishHUD on Steam Deck
              
          
    Getting BlishHUD to work correctly on the Deck

Intro

This guide will show you how to use BlishHUD while playing GuildWars2 on the Steam Deck, but requires you to launch the game from the Steam Desktop without BigPicture.
Requirements


Guild Wars 2 installed via Steam
Blish HUD downloaded

Configure the Deck


## check.ts
/**
 * Type alias resolves to `True` if and only if `U` is the same as `V`, otherwise it resolves to `False`.
 * @typeparam U - An arbitrary type
 * @typeparam V - An arbitrary type
 * @typeparam True - Production when `U` is the same as `V`
 * @typeparam False - Production when `U` is not the same as `V`
 */
export type Exact<U, V, True = true, False = false> =
	{ <_>(): _ extends U ? 1 : 0 } extends { <_>(): _ extends V ? 1 : 0 }
		? True

## please-include-a-repro.md

      
              1 file
            
          
              5 forks
            
          
                2 comments
              
            
              58 stars
            
          
                Rich-Harris
                / please-include-a-repro.md
            
            
              Last active
              November 25, 2024 12:04
            
              
                Please include a repro
              
          
    Please include a repro

You probably arrived here because of a curt message in response to an issue you filed on a repo that I contribute to. Sorry about that (particularly if you filed the issue long ago and have been waiting patiently for a response). Let me explain:
I work on a lot of different open source projects. I really do like building software that makes other people's lives easier, but it's crazy time-consuming. One of the most time-consuming parts is responding to issues. A lot of OSS maintainers will bend over backwards to try and understand your specific problem and diagnose it, to the point of setting up new test projects, fussing around with different Node versions, reading the documentation for build tools that we don't use, debugging problems in third party dependencies that appear to be involved in the problem... and so on. I've personally spent hundreds of hours of my free time doing these sorts of things to try and help people out, because I want to be a responsible maintainer and I

  
## html-table.html
<!doctype html>
<html>
<head>
    <title>Table Structure</title>
    <style type="text/css">
        .red {
            background-color: red;
        }

        .yellow {

## gist:36dc0095b9d24ce93b045e2ddc60d7a0
.rounded-corners-gradient-borders {
  width: 300px;
  height: 80px;
  border: double 4px transparent;
  border-radius: 80px;
  background-image: linear-gradient(white, white), radial-gradient(circle at top left, #f00,#3020ff);
  background-origin: border-box;
  background-clip: padding-box, border-box;
}

## gist:6322375
#!/usr/public/bin/perl -w

use strict;
use JSON;
use JSON::WebToken;
use LWP::UserAgent;
use HTML::Entities;


my $private_key_string = q[-----BEGIN PRIVATE KEY-----

## preprocessor_fun.h
// Just before switching jobs:
// Add one of these.
// Preferably into the same commit where you do a large merge.
//
// This started as a tweet with a joke of "C++ pro-tip: #define private public",
// and then it quickly escalated into more and more evil suggestions.
// I've tried to capture interesting suggestions here.
//
// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,
	/**
	* Type alias resolves to `True` if and only if `U` is the same as `V`, otherwise it resolves to `False`.
	* @typeparam U - An arbitrary type
	* @typeparam V - An arbitrary type
	* @typeparam True - Production when `U` is the same as `V`
	* @typeparam False - Production when `U` is not the same as `V`
	*/
	export type Exact<U, V, True = true, False = false> =
	{ <_>(): _ extends U ? 1 : 0 } extends { <_>(): _ extends V ? 1 : 0 }
	? True
	<!doctype html>
	<html>
	<head>
	<title>Table Structure</title>
	<style type="text/css">
	.red {
	background-color: red;
	}

	.yellow {
	.rounded-corners-gradient-borders {
	width: 300px;
	height: 80px;
	border: double 4px transparent;
	border-radius: 80px;
	background-image: linear-gradient(white, white), radial-gradient(circle at top left, #f00,#3020ff);
	background-origin: border-box;
	background-clip: padding-box, border-box;
	}
	#!/usr/public/bin/perl -w

	use strict;
	use JSON;
	use JSON::WebToken;
	use LWP::UserAgent;
	use HTML::Entities;


	my $private_key_string = q[-----BEGIN PRIVATE KEY-----
	// Just before switching jobs:
	// Add one of these.
	// Preferably into the same commit where you do a large merge.
	//
	// This started as a tweet with a joke of "C++ pro-tip: #define private public",
	// and then it quickly escalated into more and more evil suggestions.
	// I've tried to capture interesting suggestions here.
	//
	// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
	// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,