Skip to content

Version 7.2.0 - BREAKING CHANGE: Consistent Batch Operations

Choose a tag to compare

View all tags
@isene isene released this 24 Oct 17:00
· 48 commits to main since this release
7.2.0
f3ee198

⚠️ BREAKING CHANGE

Batch Operation Behavior Change:

All batch operations now use a consistent "tagged OR selected" logic:

  • When items ARE tagged → operations work ONLY on tagged items (selected item is NOT included unless also tagged)
  • When NO items are tagged → operations work on the currently selected item only
  • This affects: delete, copy, move, symlink, bulk rename, change permissions, change ownership, and open operations

Migration: If you previously relied on operations affecting "tagged + selected", you must now explicitly tag the selected item with 't' if you want it included.

Why This Change?

This change provides consistent, predictable behavior across all batch operations and eliminates confusion about which items will be affected by an operation.

✨ New Features

  • Permission modification syntax: Use +x, -w, +rw, etc. to add/remove permissions incrementally
    • Example: File is rw-r--r-- (644) → type +x → becomes rwxr-xr-x (755)
  • Undo support for permission changes (C-P): You can now undo permission changes with 'U'
  • Undo support for ownership changes (C-O): You can now undo ownership changes with 'U'
  • Persistent selection: After delete/move operations, the previously selected item remains selected if it still exists

🔧 Improvements

  • Bulk rename now works on single selected item when no items are tagged (consistent with other operations)
  • All batch operations now follow the same predictable "tagged OR selected" pattern
Assets 2
Loading