-
-
Notifications
You must be signed in to change notification settings - Fork 30
Open
Labels
area: coreIssues not related to a specific subsystemIssues not related to a specific subsystemprio: lowMinor problem or easily worked aroundMinor problem or easily worked aroundver: 4.8.33Reproducible in version 4.8.33Reproducible in version 4.8.33
Milestone
Description
Is there an existing issue for this?
- I have searched the existing issues
Midnight Commander version and build configuration
GNU Midnight Commander 4.8.33-187-gb03c830d9
Built with GLib 2.84.1 (using GLib 2.84.1)
Built with S-Lang 2.3.3 and terminfo database (using S-Lang 2.3.3)
Built with libssh2 1.11.1
With builtin editor
With subshell support as default
With support for background operations
With mouse support on xterm and Linux console
With support for X11 events
Virtual File Systems:
cpiofs, tarfs, sfs, extfs, ftpfs, sftpfs, shell
Data types:
char: 8; int: 32; long: 64; void *: 64; size_t: 64; off_t: 64; uintmax_t: 64;
Operating system
linux
Is this issue reproducible using the latest version of Midnight Commander?
- I confirm the issue is still reproducible with the latest version of Midnight Commander
How to reproduce
use the f6 dialog to rename a file into a fairly long but somehow bogus name.
Expected behavior
a helpful error message.
Actual behavior
the file name in the error message is elided ("foo~bar").
Additional context
eliding is absolutely not acceptable in error messages, because it can hide relevant information. when necessary, the file name should be wrapped and the dialog's text reflowed.
my specific case was that i was guessing how to use shell patterns in the rename dialog correctly (see #4691), and the resulting error message completely failed to convey what was actually wrong, because the actually interesting part was elided. the error being "no such file or directory" didn't help, either.
Metadata
Metadata
Assignees
Labels
area: coreIssues not related to a specific subsystemIssues not related to a specific subsystemprio: lowMinor problem or easily worked aroundMinor problem or easily worked aroundver: 4.8.33Reproducible in version 4.8.33Reproducible in version 4.8.33