From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: Using idiosyncratic quoting styles in mail
Date: Sat, 11 Jul 2020 08:56:22 +0200 [thread overview]
Message-ID: <87tuyeleuh.fsf@mat.ucm.es> (raw)
In-Reply-To: <s0esgdzngum.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
>>> "DR" == David Rogers <davidandrewrogers@gmail.com> writes:
> Uwe Brauer <oub@mat.ucm.es> writes:
>>>>> "DA" == Dmitry Alexandrov <dag@gnui.org> writes:
>>> Both approaches are equally fundamentally broken in their premise,
>>> but
>>> the latter is at least easy ignorable recipient-side.
>>
>> I am not sure I understand, why you consider the use case of
>> replying to several
>> recipient with the same mail, as fundamentally broken?
> I believe there may have been sarcasm involved, and I believe the
> point was something similar to "Using any kind of quoting marks
> that are not handled automatically by everyone's email client, is
> almost as bad as sending them html - so in the same way that you
> kindly send plain text instead of html, please also kindly use
> built-in automatic quoting marks only".
I thought that, but then I hoped he had some magic lisp code hidden
somewhere. BTW talking about idiosyncratic styles:
Wouldn't that cover the use of *very long (more than 80 chars) lines* which
some client, such as gnus, rather prefer not to send, at least they emit
a warning. Just a thought.....
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
prev parent reply other threads:[~2020-07-11 6:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 7:45 supercite (sc-citation-leader " ") kill indentation, in a intelligent way Uwe Brauer
2020-07-07 23:06 ` Dmitry Alexandrov
2020-07-08 8:48 ` Uwe Brauer
2020-07-09 4:21 ` Using idiosyncratic quoting styles in mail (was: supercite (sc-citation-leader " ") kill indentation, in a intelligent way) Dmitry Alexandrov
2020-07-09 17:53 ` Using idiosyncratic quoting styles in mail Uwe Brauer
2020-07-10 22:30 ` David Rogers
2020-07-11 6:56 ` Uwe Brauer [this message]
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=87tuyeleuh.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.org \
/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 NNTP newsgroup(s).