Re: bug on shar (GNU sharutils) 4.15.2

[Paulo Ney de Souza]

Hi Bruce,

Thanks for writing back.

On Sat, Nov 27, 2021 at 1:33 PM Bruce Korb <bkorb@gnu.org> wrote:

>
> Quoting the man page:
>
>      If you have files with non-ascii bytes or text that some mail handling
>      programs do not like, you may find difficulties.  However, if you are
>      using FTP or SSH/SCP, the non-conforming text files should be okay.
>
> "Don't do that." Perhaps I should augment that caveat with the fact that
> the shell program may also play around with the input characters.
>

Yeah .. but if you are doing only SCP you should be able to shar/unshar
completely fine, and get back the same file you started with. No?

It clearly states:


.............................................................................However,
if you are
     using FTP or SSH/SCP, the non-conforming text files should be okay.


>
> FYI, the "-T" flag says to open the file in "binary mode":
>

But -T stands for:

 -T, --text-files
              treat all files as text.  This option is a member of the
mixed-
              uuencode class of options.

was that a good choice for the flag abbreviation?


The file data are then read and written directly into the output shell
> script -- since no encoding is done. The shell script is written thus:
>

I understand! But we should either make the program do what the
man page says or vice-versa, no?

Paulo Ney