* 2025-06-17 15:04:20: switch mouse flag name. mimic default ncdu behavior

Signed-off-by: Shantanu Gadgil <[email protected]>

* documentation fixes

---------

Signed-off-by: Shantanu Gadgil <[email protected]>

fixes #427

Signed-off-by: Shantanu Gadgil <[email protected]>

* feat: Add --reverse-sort CLI flag for non-interactive mode

- Add --reverse-sort boolean flag to command line interface
- Enables reversing sort order from largest-to-smallest to smallest-to-largest
- Only applies to non-interactive mode to address scrolling usability issues
- Follows existing CLI argument patterns and conventions

* feat: Add ReverseSort flag to app configuration

- Add ReverseSort bool field to Flags struct for YAML config support
- Pass ReverseSort parameter to CreateStdoutUI for non-interactive mode
- Maintains backward compatibility with existing configuration options
- Enables --reverse-sort flag to be stored in config files

* feat: Implement reverse sorting logic in non-interactive mode

- Update CreateStdoutUI function signature to accept reverseSort parameter
- Add reverseSort field to UI struct for state tracking
- Modify showDir function to conditionally apply reverse sorting:
  * Default: sort.Reverse() for largest-to-smallest (existing behavior)
  * With --reverse-sort: standard sort() for smallest-to-largest (new behavior)
- Maintains performance with no additional overhead

* test: Add comprehensive tests for reverse sort functionality

- Add 6 new test functions to validate reverse sort behavior
- Test reverse sort with various flag combinations (colors, summarize, top)
- Test reverse sort with analysis files and different UI modes
- Add strings import for test utilities
- Ensure backward compatibility with existing test patterns
- All new tests pass alongside existing 300+ test suite

* docs: Update documentation for --reverse-sort feature

- Add --reverse-sort flag to CLI help documentation in README.md
- Add usage example showing reverse sort in non-interactive mode
- Document reverse-sort configuration option in configuration.md
- Maintain consistent documentation formatting and style
- Provide clear explanation of feature purpose and usage

* chore: Add gdu binary to .gitignore

- Ignore compiled gdu binary from version control
- Prevents accidental commit of build artifacts
- Maintains clean repository structure

* fix: update CreateStdoutUI call in Linux-specific test

- Add missing reverseSort parameter to CreateStdoutUI function call
- Fixes compilation error in stdout_linux_test.go
- Maintains consistency with updated function signature

#437)

* fix: make 'no' the default button in delete/empty confirmation dialogs

This is a critical safety improvement to prevent accidental data loss. Previously,
the 'yes' button was selected by default in confirmation dialogs for delete and
empty operations, making it extremely easy to accidentally destroy data by
pressing 'e' followed by Enter.

Changes:
- Reorder confirmation dialog buttons from ['yes', 'no', 'don't ask me again']
  to ['no', 'yes', 'don't ask me again'] making 'no' the default
- Update button index mapping in confirmDeletionSelected() and
  confirmDeletionMarked() to handle the new button order
- Add comprehensive tests to verify safer confirmation behavior
- Replace deprecated strings.Title with golang.org/x/text/cases.Title
- Maintain backward compatibility for all other functionality

This addresses a known usability issue in the gdu community where users
have reported significant data loss due to the dangerous default behavior.
The fix aligns gdu with ncdu's safer approach of defaulting to 'no'.

* test: add coverage for case 1 branches in confirmation dialogs

- Add TestConfirmDeletionSelectedCase1 to cover the 'yes' button logic
- Add TestConfirmDeletionMarkedCase1 to cover marked deletion 'yes' logic
- Improves test coverage to address Codecov report issues
- Ensures safety fix button reordering is properly tested

* fix: remove duplicate entry for golang.org/x/text in go.mod

* feat: Add --no-spawn-shell flag to disable shell access

This commit introduces a new flag, --no-spawn-shell, which disables the
ability to spawn a shell or open items in external programs. This is
useful for environments where shell access should be restricted.

This resolves issue #429.

* test: Increase coverage for --no-spawn-shell flag

* fix: data race in TestRemoveStoredFile