| Value | Color |
|---|---|
| \e[0;30m | Black |
| \e[0;31m | Red |
| \e[0;32m | Green |
| \e[0;33m | Yellow |
| \e[0;34m | Blue |
| \e[0;35m | Purple |
Discover gists
| # List disks and update DISK_LOCATION to the correct disk | |
| diskutil list | |
| DISK_LOCATION="/dev/diskX" | |
| DEVICE_NAME="WIN11" | |
| ISO_LOCATION="$HOME/Downloads/Win11_23H2_English_x64.iso" | |
| diskutil eraseDisk MS-DOS "$DEVICE_NAME" GPT $DISK_LOCATION | |
| # Mount the ISO and copy the files to the USB | |
| MOUNT_INFO=$(hdiutil mount $ISO_LOCATION) |
This guide walks you through installing the latest development version of Mesa (similar to mesa-git on Arch Linux) on Fedora, while keeping the system-provided Mesa version intact.
This approach helps avoid breaking dependencies or rendering your system unusable due to driver conflicts.
Who is this guide for? This guide is written for all experience levels, including beginners. Each step includes explanations of what and why, so you can learn as you go.
Organizing your Go (Golang) project's folder structure can help improve code readability, maintainability, and scalability. While there is no one-size-fits-all structure, here's a common folder structure for a Go project:
project-root/
├── cmd/
│ ├── your-app-name/
│ │ ├── main.go # Application entry point
│ │ └── ... # Other application-specific filesThere is a lot of hidden treasure lying within university pages scattered across the internet. This list is an attempt to bring to light those awesome courses which make their high-quality material i.e. assignments, lectures, notes, readings & examinations available online for free.
| You are Lyra, a master-level AI prompt optimization specialist. Your mission: transform any user input into | |
| precision-crafted prompts that unlock AI's full potential across all platforms. | |
| ## THE 4-D METHODOLOGY | |
| ### 1. DECONSTRUCT | |
| - Extract core intent, key entities, and context | |
| - Identify output requirements and constraints | |
| - Map what's provided vs. what's missing |
Follow the instructions on Github to Create an Access Token in Github
By default, git credentials are not cached so you need to tell Git if you want to avoid having to provide them each time Github requires you to authenticate. On Mac, Git comes with an “osxkeychain” mode, which caches credentials in the secure keychain that’s attached to your system account.
You can tell Git you want to store credentials in the osxkeychain by running the following:-
| (ns cljs-uuidv4 | |
| "Generator for a v4/random UUID that works with cljs.core/UUID" | |
| (:require [goog.string.StringBuffer])) | |
| (defn UUIDv4 | |
| "Returns a new randomly generated (version 4) cljs.core/UUID, | |
| like: xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx | |
| as per http://www.ietf.org/rfc/rfc4122.txt. | |
| Usage: |