Jesús Pérez 2b3e574e3d # Summary
fix: help system integration, build process optimization, and plugin rebuild efficiency

## Detailed Description

This commit addresses critical issues in the help system discoverability, build process robustness, and plugin rebuild efficiency.

### 1. Help System Integration (New Feature)

**Issue**: Version-update module recipes were not discoverable
- Not shown in `just help modules`
- Not referenced in `just help`
- Not included in help navigation system
- Users had to manually run `just --list` to find update commands

**Solution**:
- Added version-update module to all help outputs
- Updated `justfiles/help.just` to document all 30+ version-update recipes
- Created new `just commands` recipe as discoverable alias for `just --list`
- Integrated version-update into help-all workflow

**Impact**:
- Version-update commands now fully discoverable via help system
- Users can find update commands with: `just help modules`, `just help`, `just commands`
- Improved overall help system navigation

**Files Modified**:
- `justfiles/help.just` (+23 lines)
  - Added version-update module to help sections
  - Added to modules list
  - Added to help-all workflow
  - New `commands` recipe showing all recipes by group

### 2. Build Process Fixes (Phase 3: Bin Archives)

#### 2a. Plugin Archive Collection Bug

**Issue**: "No plugins found to package" warning in Phase 3
- Collected 26 plugin binaries but reported 0
- Archive creation skipped because count was wrong

**Root Cause**: `each` command returns null, so `| length` returned 0
```nushell
#  OLD - each returns null
let plugin_count = (ls nu_plugin_*/target/release/nu_plugin_* | each {|p|
    cp $p.name $"($temp_dir)/"
} | length)  # Returns 0!
```

**Solution**: Separated counting from copying with proper filtering
```nushell
#  NEW - count before operations
let plugins_to_copy = (ls nu_plugin_*/target/release/nu_plugin_* | where type == "file")
let plugin_count = ($plugins_to_copy | length)
```

**Impact**:
- Now correctly collects and reports 26 plugins
- Filters out .d dependency files automatically
- Warning eliminated

#### 2b. Tar Archive Path Handling

**Issue**: Tar command failing silently with relative paths in subshell
- `cd $temp_dir` changes context unpredictably
- Relative path `../$archive_name` fails in subshell
- Archive file not created despite exit code 0

**Root Cause**: Shell context and relative path issues in Nushell `do` block

**Solution**: Used `tar -C` with absolute paths instead of `cd`
```nushell
#  OLD - unreliable context switching
do {
    cd $temp_dir
    tar -czf ../$archive_name .
}

#  NEW - absolute paths, no context switching
tar -C $temp_dir -czf $archive_path .
```

**Additional Improvements**:
- Absolute path construction using `pwd | path join`
- Better error diagnostics with exit code and stderr output
- File verification after creation

**Impact**:
- Tar archives now created successfully
- Robust path handling across platforms
- Clear error messages for debugging

#### 2c. File Size Calculation Type Error

**Issue**: Runtime error when calculating archive size
```
Error: The '/' operator does not work on values of type 'list<filesize>'
```

**Root Cause**: `ls` returns list of records, so `.size` was a list
```nushell
#  OLD - returns list<filesize>
(ls $archive_path).size / 1024 / 1024

#  NEW - returns filesize
(ls $archive_path | get 0.size) / 1024 / 1024
```

**Impact**:
- Proper file size calculation in MB
- No more type errors

**Files Modified**:
- `scripts/create_full_distribution.nu` (+58 lines, refactored plugin collection)
  - Fixed plugin counting logic
  - Improved path handling with absolute paths
  - Enhanced error diagnostics

### 3. Plugin Rebuild Optimization

**Issue**: All plugins marked for rebuild even when dependencies unchanged
- Step 4 (`update_all_plugins.nu`) touched all Cargo.toml files at 01:00:32
- Step 5 saw all files as "newer" than binaries
- Marked ALL plugins for rebuild, though cargo only rebuilt changed ones

**Root Cause**: Script always saved files, even when no changes made
```nushell
#  OLD - always saves, touching file timestamp
$updated_content | to toml | save -f $cargo_toml
```

**Solution**: Only save if content actually changed
```nushell
#  NEW - compare before writing
let original_toml = $content | to toml
let new_toml = $updated_content | to toml

if $original_toml != $new_toml {
    $updated_content | to toml | save -f $cargo_toml
}
```

**Impact**:
- Unchanged files preserve original timestamps
- Only plugins with actual dependency changes are rebuilt
- Efficient rebuild process with accurate file modification detection

**Files Modified**:
- `scripts/update_all_plugins.nu` (+12 lines, added content comparison)
  - Only touches files with real changes
  - Preserves timestamps for efficiency
  - Clearer logic and comments

### 4. Documentation

**Files Modified**:
- `CHANGELOG.md` (+56 lines)
  - Added comprehensive 2025-10-19 entry
  - Documented all fixes with root causes
  - Listed files modified and impact summary

## Technical Details

### Nushell Patterns Used

1. **Proper List Handling**:
   - `ls` returns list of records, access with `| get 0.size`
   - Filter with `where type == "file"` to exclude metadata

2. **Absolute Path Construction**:
   - `pwd | append "path" | path join` for cross-platform paths
   - Safer than string concatenation with `/`

3. **Content Comparison**:
   - Compare TOML string representation before saving
   - Preserves file timestamps for efficiency

4. **Error Diagnostics**:
   - Capture `stderr` from commands
   - Report exit codes and error messages separately

## Testing

- [x] Help system shows version-update module
- [x] `just commands` displays all recipes by group
- [x] Phase 3 bin archive creation works
- [x] Plugin collection reports correct count (26)
- [x] Tar archives created successfully
- [x] File size calculated correctly
- [x] Plugin rebuild only touches changed files
- [x] CHANGELOG updated with all changes

## Files Changed

```
38 files changed, 2721 insertions(+), 2548 deletions(-)

Core Changes:
- justfiles/help.just                  (+23)  Help system integration
- scripts/create_full_distribution.nu  (+58)  Build process fixes
- scripts/update_all_plugins.nu        (+12)  Rebuild optimization
- CHANGELOG.md                         (+56)  Documentation

Dependency Updates:
- All plugin Cargo.toml and Cargo.lock files (version consistency)
```

## Breaking Changes

None. These are bug fixes and optimizations that maintain backward compatibility.

## Migration Notes

No migration needed. Improvements are transparent to users.

## Related Issues

- Help system discoverability
- Build process Phase 3 failures
- Unnecessary plugin rebuilds
- Build process reliability

## Checklist

- [x] Changes follow Rust/Nushell idioms
- [x] Code is well-commented
- [x] Error handling is comprehensive
- [x] Documentation is updated
- [x] All changes tested
- [x] No breaking changes introduced
2025-10-19 01:17:13 +01:00
..
2025-06-27 02:31:23 +01:00
2025-06-27 02:31:23 +01:00
2025-06-27 02:31:23 +01:00
2025-06-27 02:31:23 +01:00
2025-06-27 02:31:23 +01:00
2025-06-27 02:31:23 +01:00
2025-10-19 01:17:13 +01:00
2025-10-19 01:17:13 +01:00
2025-06-27 02:31:23 +01:00
2025-06-27 02:31:23 +01:00
2025-06-27 02:31:23 +01:00
2025-06-27 02:31:23 +01:00

🖼 nu_plugin_image

A Nushell plugin to convert ANSI strings into PNG images and create ANSI text from images.


Features

This plugin allows you to:

  • Convert ANSI strings to PNG images with customizable fonts and themes.
  • Create ANSI text from an image, enabling you to transform visual data into a textual representation.

to png Convert ANSI String to PNG Image

The to png command converts an ANSI string into a PNG image. Customizable font and theme options are available, with custom flags overriding the default settings.

📌 Usage

> to png {flags} (output-path)

⚙️ Available Flags

  • -h, --help → Display the help message for this command.
  • -w, --width <int> → Output width.
  • -t, --theme <string> → Select the theme of the output. Available themes: ["vscode", "xterm", "ubuntu", "eclipse", "mirc", "putty", "winxp", "terminal", "win10", "win_power-shell", "win_ps"]. Defaults to vscode.
  • --font <string> → Select the font from one of ["SourceCodePro", "Ubuntu", "IosevkaTerm", "AnonymousPro"]. Defaults to the first font in the list.
  • --custom-font-regular <path> → Path to a custom regular font.
  • --custom-font-bold <path> → Path to a custom bold font.
  • --custom-font-italic <path> → Path to a custom italic font.
  • --custom-font-bold_italic <path> → Path to a custom bold italic font.
  • --custom-theme-fg <string> → Custom foreground color in hex format (e.g., #FFFFFF for white).
  • --custom-theme-bg <string> → Custom background color in hex format (e.g., #00000000 for transparent).
  • --custom-theme-black <string> → Custom black color in hex format (e.g., #1C1C1C).
  • --custom-theme-red <string> → Custom red color in hex format (e.g., #FF0000).
  • --custom-theme-green <string> → Custom green color in hex format (e.g., #00FF00).
  • --custom-theme-yellow <string> → Custom yellow color in hex format (e.g., #FFFF00).
  • --custom-theme-blue <string> → Custom blue color in hex format (e.g., #0000FF).
  • --custom-theme-magenta <string> → Custom magenta color in hex format (e.g., #FF00FF).
  • --custom-theme-cyan <string> → Custom cyan color in hex format (e.g., #00FFFF).
  • --custom-theme-white <string> → Custom white color in hex format (e.g., #FFFFFF).
  • --custom-theme-bright_black <string> → Custom bright black color in hex format (e.g., #808080).
  • --custom-theme-bright_red <string> → Custom bright red color in hex format (e.g., #FF5555).
  • --custom-theme-bright_green <string> → Custom bright green color in hex format (e.g., #55FF55).
  • --custom-theme-bright_yellow <string> → Custom bright yellow color in hex format (e.g., #FFFF55).
  • --custom-theme-bright_blue <string> → Custom bright blue color in hex format (e.g., #5555FF).
  • --custom-theme-bright_magenta <string> → Custom bright magenta color in hex format (e.g., #FF55FF).
  • --custom-theme-bright_cyan <string> → Custom bright cyan color in hex format (e.g., #55FFFF).
  • --custom-theme-bright_white <string> → Custom bright white color in hex format (e.g., #FFFFFF).
  • --log-level <string> → Set log level. Options: CRITICAL (c), ERROR (e), WARN (w), INFO (i), DEBUG (d), TRACE (t). Defaults to INFO.

📊 Example: Convert ANSI String to PNG with Custom Theme

> to png --theme "xterm" --custom-theme-fg "#FF00FF" --custom-theme-bg "#00000000" output.png

from png Create ANSI Text from an Image

The from png command converts an image into its corresponding ANSI text representation.

📌 Usage

> from png {flags}

⚙️ Available Flags

  • -h, --help → Display the help message for this command.
  • -x, --width <int> → Output width, in characters.
  • -y, --height <int> → Output height, in characters.
  • --log-level <string> → Set log level. Options: CRITICAL (c), ERROR (e), WARN (w), INFO (i), DEBUG (d), TRACE (t). Defaults to INFO.

📊 Example: Convert PNG Image to ANSI Text

> from png --width 80 --height 20 image.png

🔧 Installation

This method automatically handles dependencies and features.

git clone https://github.com/FMotalleb/nu_plugin_image.git  
nupm install --path nu_plugin_image -f  

🛠️ Manual Compilation

git clone https://github.com/FMotalleb/nu_plugin_image.git  
cd nu_plugin_image  
cargo build -r  
plugin add target/release/nu_plugin_image  

📦 Install via Cargo (using git)

cargo install --git https://github.com/FMotalleb/nu_plugin_image.git  
plugin add ~/.cargo/bin/nu_plugin_image