- Maintain all existing comments and emojis in uploaded project code
- Preserve file structure and documentation style
- Keep existing formatting patterns
For each code change:
- File path must be shown:
#!/bin/bash | |
# π§ Disables scroll-based workspace switching in XFCE | |
# π Backs up current settings to ~/.xfce-backups/pre_scroll_disable.txt | |
mkdir -p ~/.xfce-backups | |
xfconf-query -c xfwm4 -lv | grep -E "scroll|rollup" > ~/.xfce-backups/pre_scroll_disable.txt | |
# Disable scroll workspace switching and title bar rollup | |
xfconf-query -c xfwm4 -p /general/scroll_workspaces -s false |
# If you come from bash you might have to change your $PATH. | |
# export PATH=$HOME/bin:$HOME/.local/bin:/usr/local/bin:$PATH | |
alias gistedit='function _gistedit(){ vim "$1"; local filename="$1"; gh gist create "$filename" --public; }; _gistedit' | |
alias gisteditdesc='function _gisteditdesc(){ | |
local filename="$1"; | |
if [ -z "$filename" ]; then | |
echo "Usage: gisteditdesc <filename>"; | |
return 1; | |
fi; |
#!/bin/bash | |
# Install xbindkeys | |
echo "Installing xbindkeys..." | |
sudo apt update && sudo apt install xbindkeys -y | |
# Create the default configuration file | |
echo "Creating xbindkeys configuration file..." | |
xbindkeys --defaults > ~/.xbindkeysrc |
#!/bin/bash | |
# π₯ Peek Launcher Script | |
# π οΈ Usage: | |
# 1οΈβ£ Install dependencies: `sudo apt install peek xdotool x11-utils` | |
# 2οΈβ£ Save this script as `peek_at_cursor.sh` and make it executable. | |
# Example: `chmod +x ~/scripts/peek_at_cursor.sh` | |
# 3οΈβ£ Run the script: `~/scripts/peek_at_cursor.sh` | |
# 4οΈβ£ Peek will open at your cursor's position and stay open for multiple recordings. |
# Today only (since midnight UTC) | |
resource.type="cloud_function" | |
resource.labels.function_name="your_function_name" | |
timestamp >= timestamp_trunc(current_timestamp(), DAY, "UTC") | |
( | |
textPayload=~"ERROR" | |
OR textPayload:~"Checking if blob exists" | |
OR textPayload:~"Attempting to download blob" | |
OR textPayload:~"Starting workbook preprocessing" | |
OR textPayload:~"SOURCE_PROCESSING_ERROR" |
Prompt:
"I am working on a new Git project, and I need a clear feature map for branch naming conventions. The feature map should outline each development phase, the corresponding tasks, and suggested branch naming conventions for each step.
Here are the requirements:
Provide a list of development phases (initial setup, core logic, testing, continuous integration, additional features, linting/formatting, documentation, code review, release, and post-release maintenance). For each phase, describe the objective and the key tasks that need to be completed. For each phase, suggest a branch naming convention following this structure: feat/feature-description, fix/bug-description, release/version, etc. Ensure each phase follows this format:
Project: Data Normalization and BigQuery Integration for Gaming Compliance
Context: I am developing a cloud-based system for normalizing and processing gaming compliance data from various operators, specifically starting with RSI BetRivers. The system needs to handle Excel file inputs, process them according to a predefined schema, and output the normalized data to BigQuery tables.
Key Components:
Please ensure the following behavior in all future sessions:
echo
command to modify the code directly from the terminal.sed
commands: Provide sed
commands to remove, modify, or change old code if necessary.