From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: ricardo.couto@gmail.com
Subject: Re: email -attach
Date: Mon, 4 Jul 2022 12:51:56 -0600 [thread overview]
Message-ID: <398ec761-36b8-7497-4ca8-e15b4590df9c@SystematicSw.ab.ca> (raw)
In-Reply-To: <000001d88fa9$33ca4a90$9b5edfb0$@gmail.com>
On 2022-07-04 07:23, ricardo.couto@gmail.com wrote:
> Na sexta-feira, 1 de julho de 2022 21:15, Andrey Repin escreveu:
>> Na sexta-feira, 1 de julho de 2022 12:34, Brian Inglis escreveu:
>>> On 2022-06-22 14:19, ricardo.couto@gmail.com wrote:
> The package "email" does not works fine with "attach" option when use
> more than one files to attach.
>> $ email --version
>> email - By Dean Jones; Version 3.2.3-git $ email Brian -a
>> /etc/email/email.conf -a ~/.email.conf < \
>> ~/.email/email.address.book
>> works fine for me.
>> You may need to use --attach not -attach - man and --help differ!
>>> -attach "file1,file2,file3"
>>> That's one file with name "file1,file2,file3".
>>>> No. There are 3 comma separeted files.
>>>> # man email
>>>> --attach file | -a file
>>>> Attach a binary file. This option will allow you to attach N
>>>> files to your email and will be base64 encoded upon
>>>> delivery. This option is helpful if you need to send any type of
>>>> file that is not plain ascii text. This option
>>>> can be used multiple times to add multiple files to attach.>>> EXAMPLES OF USAGE
>>>> # Attach some files with your message
>>>> email -s "files attached" Dean,Jeff --attach stuff.tar.gz,readme.doc
>>>> --attach stuff.tar.gz,readme.doc
There are a number of errors in that package documentation mentioning
features not (or no longer) implemented; the --help is more accurate;
believe and use what works:
"This option can be used multiple times to add multiple files to attach."
BTW: it uses getopt_long_only(3) [man-pages-linux package] which allows
single dash or double dash long option names as well as single dash
short option characters.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2022-07-04 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 20:19 ricardo.couto
2022-07-01 15:33 ` Brian Inglis
2022-07-01 17:00 ` RES: " ricardo.couto
2022-07-02 0:14 ` Andrey Repin
2022-07-04 13:23 ` RES: " ricardo.couto
2022-07-04 18:51 ` Brian Inglis [this message]
2022-07-04 19:03 ` ricardo.couto
2022-07-04 20:43 ` Marco Atzeri
2022-07-04 21:18 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=398ec761-36b8-7497-4ca8-e15b4590df9c@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
--cc=ricardo.couto@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).