Re: avoid warnings about slice vs. base name in single slice mode

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 04/08/2019 12:53, Matus UHLAR - fantomas wrote:
>> On 31/07/2019 19:59, Matus UHLAR - fantomas wrote: >>> is it possible to avoid warnings about "seems more to be a slice
>>> name than a base name." >>> >>> when slice size is not defined? > >
On 04.08.19 11:55, Denis Corbin wrote: >> this warning shows anytime you
provide a filename "archive.1.dar" when >> a archive basename "archive"
is expected. It is not linked to the >> slicing scheme you want to use.
> >> for example do not use: >> dar -l archive.1.dar >> but rather use
>> dar -l archive >> >> may there be one or many slices (archive.1.dar,
archive.2.dar, >> archive.3.dar, ...), these are all part of the archive
which basename >> is "archive" > > I understand this, but when using
filename completion, full names are > given. > > (I don't want to play
with bash and its completion functions). > > What I meant was, if the
warning could be avoided when no slicing scheme is > used, which is I
believe most common -
To my point of view this is rather the opposite: the use of slicing is
very common, though I have no statistical data to base my argumentation
on, this is however one of the value of dar to be very flexible in that
area. This allows one to create huge archives much larger than what the
underlying filesystem can support (FAT, ISO and other ancient
filesystems still in use today)

> so we could use full filenames and > not care about slices and their extensions. > >
I often had problems with softwares that pretend to "help" the user and
fix its mistake without asking or telling what it did.
- - who never lost his time removing uppercase from text editor while
they never typed them nor ever wanted them?
- - who never removed a smiley icon from his SMS/mail to put pack the
expected punctuation or to type back in place the wanted text smiley?
- - fetch an important mail in the spambox...?
- - or even get confused by your intelligent car that will put packing
break, stop the motor, switch off light at the worse time...?
- - not to mention GPS navigator...
- - ...and other "Artificially Intelligent" said solutions/devices :-)

That said, I can't warranty that nobody ever created a dar archive made
of slices like archive.1000.dar.1.dar, archive.1000.dar.2.dar,....
automatically stripping the .<n>.dar of archive argument instead of
asking as of today could lead to even more confusion...

The only thing I can do it adding (yet) a new option to change this
warning behavior to an automatic stripping behavior. But it will not be
activated by default (though you could add it in your .darrc file to
forget about it).

OK for you?
If so, please fill a feature request at
https://sourceforge.net/p/dar/feature-requests/

Cheers,
Denis




-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEOzEprx3d76WjfYGPCDGwvQPYsYIFAl1HEKoACgkQCDGwvQPY
sYKMMQ//aY9f+7kePsVPWMbw7cudh6j9M6PKc3JcOCb1gRzqsUo2NdtkKyeUiU9A
Qv6Tahc/MwzejchpU69LsBfzFoVzIhPsBxh0YORc01R7RiBgIkax5ehSulK8oRdi
I1r+xCJN/ElFK/48G2REhsSzlE/3l7+hfwJHeshKy4P+v9rOz2snHcMGTdkh+B5e
C+iBqwPKWK9IrwCIsV1jI8c24k/Efx0yLkX3YolLQ2r4H21mWWVl6NBW6DSinlUo
chgU/QudDYMvAsm2bd3JtGKcJh3Jb36awcym+V6OXCGKyyIAsdjnqBrugRnMSmoK
+ZJamSRMZN5Ytp1IKexZRbFuHFT3oPASnOfKVbuq0gpLpjdG2A2hjXD/V3RiYTsC
7QtSgAFSnkNpf5oMIw34ewoCMGLSE5Qhew2mzqfvvZIvKtIqbA5Zm1v0V6446Xi/
rugDCWKcEJX3MQZPFH1JImWnpjSg0bZWK0v2KvoaCkj0Okszi+kDuuOa2w/5mG3/
/h2/kKY1dMIVEemrbkKemD2eCMRhlLJdUsftXZWDfzNvOVVJWpn8plmgK13iHx1H
gqmlyKDSdA6dsYqhPSxqwX/uvtkQE5vF8QjeDV0wq72L6N1m/m0BFqDMd3MX99KK
pM/dVFSPBv30ZCq4awupGKlAWFW8ZG7ouFBtVOepO90jScziqXM=
=kJ2G
-----END PGP SIGNATURE-----