Summary
Several CLI options have misleading names or non-standard conventions that should be cleaned up for better usability.
Proposed Changes
Rename --secure (misleading name)
Currently --secure just changes chunk size from 4KB to 1MB - no actual security benefit:
const std::streamsize CHUNK_SIZE_SECURE = 1024 * 1024; // 1 MB
const std::streamsize CHUNK_SIZE_FAST = 4096; // 4 KB
Options:
- Rename to
--large-chunks or --buffer 1M
- Add configurable
--chunk-size <bytes>
- Remove entirely (performance difference is negligible on modern systems)
Rename --dry-run to --dryrun
Simpler to type, no hyphen. Keep --dry-run as alias for backward compatibility.
Standardize -vb to -v
The short form -vb is non-standard. Most tools use -v for verbose:
# Current (non-standard)
xmv fileA fileB -vb
# Proposed (standard)
xmv fileA fileB -v
Consider shorter aliases for path options
Current --1-to and --2-to work but could have shorter forms:
--1-to → also accept -1 or --to1--2-to → also accept -2 or --to2
Backward Compatibility
All renamed options should keep their old names as aliases to avoid breaking existing scripts.
Related
Summary
Several CLI options have misleading names or non-standard conventions that should be cleaned up for better usability.
Proposed Changes
Rename
--secure(misleading name)Currently
--securejust changes chunk size from 4KB to 1MB - no actual security benefit:Options:
--large-chunksor--buffer 1M--chunk-size <bytes>Rename
--dry-runto--dryrunSimpler to type, no hyphen. Keep
--dry-runas alias for backward compatibility.Standardize
-vbto-vThe short form
-vbis non-standard. Most tools use-vfor verbose:Consider shorter aliases for path options
Current
--1-toand--2-towork but could have shorter forms:--1-to→ also accept-1or--to1--2-to→ also accept-2or--to2Backward Compatibility
All renamed options should keep their old names as aliases to avoid breaking existing scripts.
Related
--fastis already planned for v0.5.0 (issue [FEATURE] Skip XOR swap for identical byte sections in --fast mode #3)