elvinguti.dev

Terminal scrollback history can be difficult to navigate with standard mouse selection, especially for complex outputs or when you need to select specific portions of text. By combining Kitty terminal’s pipe capabilities with Vim’s powerful navigation, you can effortlessly browse, search, and copy content from your terminal history. Prerequisites Before getting started, make sure you have the following installed: Kitty Terminal: A fast, feature-rich, GPU-based terminal emulator Installation: sudo pacman -S kitty (Arch Linux) Other distros: https://sw.kovidgoyal.net/kitty/binary/ Vim: The ubiquitous text editor Installation: sudo pacman -S vim (Arch Linux) Most Linux distributions come with Vim pre-installed or easily available in their package repositories You’ll also need basic familiarity with Vim navigation commands for the best experience, though even Vim beginners can benefit from this setup. ...

When you fail to enter the correct password multiple times while using sudo, your account might get locked for security reasons. This is a security feature to prevent brute force attacks. Here’s how to check and unlock your account using the faillock command. First, check the status of failed attempts: sudo faillock This will show you a list of users and their failed attempts. The output will look something like this: ...

GNOME Shell extensions are a fantastic way to customize and extend the functionality of your GNOME desktop environment. However, GNOME enforces a version check, meaning that if an extension isn’t explicitly marked as compatible with your current GNOME Shell version, it won’t be loaded. This can be frustrating if you know an extension works fine, or if you’re developing an extension and want to test it easily. Recently the forge extension stopped working on GNOME 48, but it still works well even if it’s marked as incompatible. So, to enable forge again we need to disable this version check. Be aware that this comes with risks, as incompatible extensions can cause instability. Proceed with caution and understand that you’re disabling a safety mechanism. ...

Tired of plain system info outputs? Fastfetch is a command-line tool (similar to Neofetch) that displays essential system details in a highly customizable and visually appealing format. Get info about your OS, kernel, CPU, GPU, RAM, disk usage, and much more, all presented with colorful ASCII art and configurable layouts. Key Features: Fast performance. Highly customizable output (colors, logos, information displayed). Wide range of supported operating systems. Easy to install. Installation: ...

I needed to automate the process of running tests in Jest and getting the coverage for a specific file. I created this script to help me with that. #!/bin/bash # Color definitions BLUE='\033[0;34m' GREEN='\033[0;32m' RED='\033[0;31m' YELLOW='\033[1;33m' CYAN='\033[0;36m' NC='\033[0m' # No Color BOLD='\033[1m' # Function to display usage show_usage() { echo -e "${YELLOW}Usage:${NC} $0 [--find-by-name] <relative-file-path> [additional test options]" echo -e "${YELLOW}Examples:${NC}" echo -e " $0 src/components/Button.tsx --watch" echo -e " $0 src/components/Button.tsx --find-by-name --watch" exit 1 } # Initialize variables FIND_BY_NAME=false RELATIVE_FILE_PATH="" # Parse arguments while [[ $# -gt 0 ]]; do case $1 in --find-by-name) FIND_BY_NAME=true shift ;; *) if [ -z "$RELATIVE_FILE_PATH" ]; then RELATIVE_FILE_PATH="$1" else break # Stop parsing and keep remaining args for test options fi shift ;; esac done # Check if a file name is provided if [ -z "$RELATIVE_FILE_PATH" ]; then show_usage fi # Check if the file exists if [ ! -f "$RELATIVE_FILE_PATH" ]; then echo -e "${RED}Error: ${NC}File '${YELLOW}${RELATIVE_FILE_PATH}${NC}' not found. 😕" exit 1 fi FILE_PATH=$(echo "$RELATIVE_FILE_PATH" | cut -d'/' -f3-) # Get just the file name without extension for --find-by-name mode FILE_NAME=$(basename "$RELATIVE_FILE_PATH") FILE_NAME_NO_EXT="${FILE_NAME%.*}" # Construct the corresponding test file path TEST_FILE_NAME="${FILE_PATH%.*}.test" if [ "$FIND_BY_NAME" = true ]; then # Search by file name TEST_PATH=$(find "tests" -type f \( -name "${FILE_NAME_NO_EXT}.test.tsx" -o -name "${FILE_NAME_NO_EXT}.test.ts" \)) else # Original search by path TEST_PATH=$(find "tests" -type f \( -path "*/${TEST_FILE_NAME}.tsx" -o -path "*/${TEST_FILE_NAME}.ts" \)) fi # Check if the test file exists if [ -z "$TEST_PATH" ]; then echo -e "${RED}Error: ${NC}Test file for '${YELLOW}${RELATIVE_FILE_PATH}${NC}' not found in 'tests' directory. 😕" echo -e "Test file name: ${YELLOW}${FILE_NAME_NO_EXT}.test.tsx${NC}" echo -e "${YELLOW}Hint:${NC} If you're looking for a file by name, try using the --find-by-name flag." exit 1 fi # Print test information with styling echo -e "\n${BLUE}╔════════════════════════════════════════════════════════════╗${NC}" echo -e "${GREEN}▶ Running Coverage Test${NC}" echo -e "${CYAN}📁 Source file:${NC} ${RELATIVE_FILE_PATH}" echo -e "${CYAN}🧪 Test file:${NC} ${TEST_PATH}" echo -e "${CYAN}⚙️ Options:${NC} $@" echo -e "${BLUE}╚════════════════════════════════════════════════════════════╝${NC}\n" yarn test "$TEST_PATH" --coverage --collectCoverageFrom="$RELATIVE_FILE_PATH" "$@" Usage Test cases are in the tests folder. The script will search for the test file by path by default, if you want to search by name, you can use the --find-by-name flag. ...