Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new panel option for display_total_marked_size() to apply three different styles #3674

Open
mc-butler opened this issue Aug 17, 2016 · 1 comment
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/3674
Reporter michael-o (@michael-o)

Currently, display_total_marked_size() supports only one style to display the marked size. Some people would prefer to see the raw, scaled or even both values. It should be made configurable through the panel options. Some effort has already been made in #3666.

The modes:

Mode 'raw':

100000 B in 10 files
560000000000 B in 1001 files

Mode 'scaled':
SI (base 10):
100 B in 10 files
100 kB in 100 files
950 MB in 200 files
560 GB in 1001 files
IEC (base 2):
100 B in 10 files
98 KiB in 100 files
940 MiB in 200 files
1020 MiB in 220 files
550 GiB in 1001 files

Mode 'both':
SI (base 10):
100 B in 10 files
100 kB (100000 B) in 100 files
950 MB (950201123 B) in 200 files
560 GB (560100245124 B) in 1001 files
IEC (base 2):
100 B in 10 files
98 KiB (100400 B) in 100 files
940 MiB (985661900 B) in 200 files
1020 MiB (1069547520 B) in 220 files
550 GiB (590558003200 B) in 1001 files

Note that in 'both' mode with a value below 1000 bytes or 1024 bytes, 'raw' mode is applied to avoid duplicate information.

The new panel option: Total marked size style: [raw, scaled, both] (need to investigate how to do this)
Serialized as "total_marked_size_style" with default value of "scaled".

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Aug 17, 2016 at 13:31 UTC (comment 1)

  • Milestone set to Future Releases

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress
Development

No branches or pull requests

1 participant