Set the following variables:
export DOTNET_ROOT=$HOME/.dotnet
export PATH=$HOME/.dotnet/:$PATH
export PATH=$HOME/.dotnet/tools/:$PATH
echo "------------------------" | |
echo "--- Loading autoexec ---" | |
echo "------------------------" | |
// -- Viewmodel | |
viewmodel_offset_x 2 | |
viewmodel_offset_y -2 | |
viewmodel_offset_z -2 | |
viewmodel_fov 68 | |
// cl_bob_lower_amt 30 |
The guide on Cogin's website for installing on "Linux" actually means installing on a Debian-based system. This guide Arch-ifies the process. This could be made into an AUR package, but I don't have the knowledge or time to maintain such a package, so here's the (hopefully) not outdated way of installing it.
sudo pacman -S wine cabextract
# Get all PackageReferences from a project or solution | |
# Does NOT include transient dependencies | |
# Example A: Get-PackageReference ./MySolution.sln | |
# Example B: Get-ChildItem -Recursive *.csproj | Get-PackageReference | |
function Get-PackageReference { | |
[CmdletBinding()] | |
param ( | |
[Parameter( | |
Mandatory = $true, | |
ValueFromPipeline = $true, |
Should work on Windows, Linux and MacOS. I've only tested Windows so far.
VanillaOS's APX tool is quite neat since you can export desktop-entries with apx export <program>
. However, if you like to run CLI tools on your host system without apx enter
it's a bit trickier. Here's a little guide on how you can get around this using she-bang scripts.
Create a folder somewhere in your home-directory structure that you'd like to contain shebang scripts. I'm just going to use ~/scripts
as a starting point.
Add the folder to your shell's PATH
environment variable:
Installing QueueExplorer on Linux can be a pain. I've found the official guide inadequate as it assumes you're using the apt package manager to install Wine and so on. It's just a bad install script.
Instead, let's install using a universal approach with Flatpak and Bottles. This guide assumes you already have Flatpak installed on your system.
flatpak install com.usebottles.bottles
There's really no reason not to enable Nullable. It's enabled by default on .NET 6.0 projects for a reason. It gently pushes you into taking into account times where your input or output could be null by warning you of potential dangers.
<Project Sdk="Microsoft.NET.Sdk.Web">
...
function Install-Powershell([string] $version) | |
{ | |
# in case the version was specified with a prefix, strip it | |
$version = $version.Replace('v', '') | |
Write-Host "Downloading $version..." | |
$output = "PowerShell-$version-win-x64.msi" | |
$url = "https://github.com/PowerShell/PowerShell/releases/download/v$version/PowerShell-$version-win-x64.msi" | |
try { |
# Zoom Horizontally and Vertically | |
ACT 0 32060 "4bdc082639aee448bb6399c2cd265564" "View: Zoom Horizontally and Vertically" 40430 40431 | |
KEY 255 6395 _4bdc082639aee448bb6399c2cd265564 32060 | |
ACT 0 0 "9abdb95e7e387241b2ef15a03db46e8b" "View: Zoom Horizontally and Vertically" 990 991 | |
KEY 255 253 0 0 | |
KEY 255 6395 _9abdb95e7e387241b2ef15a03db46e8b 0 | |
# Zoom vertically | |
KEY 255 6394 991 0 | |
KEY 255 6394 40430 32060 |