Re: Bottom posting v top posting

[Derek Martin]

On Fri, May 18, 2018 at 04:16:35PM -0700, Will Yardley wrote:
> I do think it's fair to understand that, while for technical mailing
> lists and newsgroups, our way of quoting is "correct", that the
> conventions are very different in the business world,

FWIW I don't find this at all...  In my experience, there's exactly
*one* justification for the practice that makes any sense at all,
which is the aforementioned adding people to threads, leaving the
whole thread intact for context.

However, in practice, it's also been my experience that those people
still (usually) don't bother to read the quoted thread, and instead
just ask someone for a summary.  So it ends up being entirely
pointless regardless.

In the end, I think it's actually about one thing, plain and simple:
laziness.

> so it's not really surprising that many people don't quote emails
> this way,

It doesn't surprise me, but for the laziness reason, not any reason
related to the conversation content or style.  And very often the
response is so terse that you have to ask what was intended, wasting
even more time (since e-mail threads generally are extremely low
bandwidth with large RTT times).

> or find it confusing when others do.

YMMV but this too, I find, usually just comes down to laziness.  It's
not that they can't understand, they just don't want to be bothered.
Basically any message that contains more than about 3 sentences will
be ignored by a subset of its recipients and require some other means
of communication.

> At some point, being prescriptive only takes you so far; at this
> point, we are so far out of the majority that it's not evey funny.

This may be true (and I'm not convinced it is) but that does not in
any way make it less a bad practice.  I think ME had it wrong: It's
not that e-mail sucks, it's that the people writing it do. ;-)
 
> As far as the situation where someone else doesn't see that I even
> replied, because of the amount of initial quoted material, that isn't a
> situation that's really come up for me yet, but I could imagine it
> happening.

Still laziness--on the part of the person who is (or should be) doing
the trimming.

But then, I'm old and stubborn, and you probably expected this sort of
response from me. =8^)

-- 
Derek D. Martinhttp://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.



pgpglvXhFIUha.pgp
Description: PGP signature

Re: Bottom posting v top posting

[Will Yardley]

I'll be honest, I really don't spend a lot of time thinking about this
subject these days. It's rare that I need to spend much time on
technical mailing lists and USENET -- so much discussion has moved to
online forums, Slack communities, and so forth.

With friends, family, and work, I find that I use email less and less,
between text messaging, Slack, etc. While I still trim quoted material
and reply inline (even when using IOS's mail application vs. Mutt /vim),
I don't expect others to do so.

I do think it's fair to understand that, while for technical mailing
lists and newsgroups, our way of quoting is "correct", that the
conventions are very different in the business world, so it's not really
surprising that many people don't quote emails this way, or find it
confusing when others do. At some point, being prescriptive only takes
you so far; at this point, we are so far out of the majority that it's
not evey funny.

As far as the situation where someone else doesn't see that I even
replied, because of the amount of initial quoted material, that isn't a
situation that's really come up for me yet, but I could imagine it
happening.

w

Re: Bottom posting v top posting

[José María Mateos]

Just to add to this thread: by chance, a similar conversation recently 
happened on the main Python mailing list. It's also very interesting 
reading and starts right here: 
https://mail.python.org/pipermail/python-list/2018-May/733194.html

Cheers,

-- 
José María Mateos
https://rinzewind.org/blog-es || https://rinzewind.org/blog-en

Re: Bottom posting v top posting

[Martin Trautmann]

Am 18. Mai 2018 00:13:56 MESZ schrieb Cameron Simpson :
>On 17May2018 21:17, Florian Gamböck  wrote:
>>On 2018-05-17 13:15, Cameron Simpson wrote:
>>>I've also seen replies come back from people unused to inline
>response with 
>>>their reply slap in the middle of the quoted text because they've not
>added a 
>>>blank line. I don't know exactly what's happening at their end, but
>at my end 
>>>they text appears in the middle of the quoted prose. I should dig
>into it.

>>When I was using Thunderbird a few years ago, if I composed an e-mail 
>>with inline reply, then above and beneath my reply, there always was a
>
>>clearly visible gap. However, this gap was only visible in the compose
>
>>window. When looking at the email afterwards in the reader, my reply 
>>stuck tightly between the quoted message parts, almost impossible to
>spot if 

>The particular user I had this with isn't at fault, but also a
>nontechnical 
>user not used to inline reply. And they are using Thunderbird. Your
>decription 
>above does sound like a very flawed disconnect between compose and
>actualy 
>view. WYSINWYG I guess.

I do remember that kind of behavior. It usually happens when the sender wrote 
an HTML mail. Replying in TB still does show formatted text, with vertical 
quote bars instead of >. Sometimes it's difficult to trim quotes and insert 
text of your own.

Only when sending this message is trimmed to text only, obviously with some 
flaws on invisible  and .

- Martin
-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Re: Bottom posting v top posting

[Cameron Simpson]

On 17May2018 21:17, Florian Gamböck  wrote:

On 2018-05-17 13:15, Cameron Simpson wrote:
I've also seen replies come back from people unused to inline response with 
their reply slap in the middle of the quoted text because they've not added a 
blank line. I don't know exactly what's happening at their end, but at my end 
they text appears in the middle of the quoted prose. I should dig into it.


You are right, this can be quite annoying, but it is not necessary 
that those people are not used to inline reply, it is rather that 
their e-mail client might display the reply in a poor way.


When I was using Thunderbird a few years ago, if I composed an e-mail 
with inline reply, then above and beneath my reply, there always was a 
clearly visible gap. However, this gap was only visible in the compose 
window. When looking at the email afterwards in the reader, my reply 
stuck tightly between the quoted message parts, almost impossible to spot if 
you do not accidently stumble upon it. [... compose habits to mitigate this 
...]

So it is not always the fault of the users alone.


The particular user I had this with isn't at fault, but also a nontechnical 
user not used to inline reply. And they are using Thunderbird. Your decription 
above does sound like a very flawed disconnect between compose and actualy 
view. WYSINWYG I guess.


Thank you!

Cheers,
Cameron Simpson 

Re: Bottom posting v top posting

[Florian Gamböck]

On 2018-05-17 13:15, Cameron Simpson wrote:

On 13May2018 19:53, Florian Gamböck  wrote:
To further avoid confusion I make sure to always insert one blank, 
unquoted line between the quote and my reply. So even if someone uses 
a client that HTML formats blockquotes with vertical lines on the 
left, there is always the indicator in form of a vertical gap so my 
reply will not easily being overlooked.


Yes, this is important. Not just for courtesy and etxt clarity, but 
also for how other mailers treat the reply.


I've also seen replies come back from people unused to inline response 
with their reply slap in the middle of the quoted text because they've 
not added a blank line. I don't know exactly what's happening at their 
end, but at my end they text appears in the middle of the quoted 
prose. I should dig into it.


You are right, this can be quite annoying, but it is not necessary that 
those people are not used to inline reply, it is rather that their 
e-mail client might display the reply in a poor way.


When I was using Thunderbird a few years ago, if I composed an e-mail 
with inline reply, then above and beneath my reply, there always was a 
clearly visible gap. However, this gap was only visible in the compose 
window. When looking at the email afterwards in the reader, my reply 
stuck tightly between the quoted message parts, almost impossible to 
spot if you do not accidently stumble upon it. I then developed two 
habits: First, make double sure that there is a legit blank line above 
and beneath my reply, no matter how absurdly big the gaps looked. 
Second, save the e-mail as draft and take a look at it again in the 
reader pane. I think I do not have to emphasize how long it sometimes 
took for me to write a short e-mail as a response to another one.


So it is not always the fault of the users alone.

--Flo

Re: Bottom posting v top posting

[Martin Trautmann]

Am 17. Mai 2018 10:06:04 MESZ schrieb Cameron Simpson :
>On 17May2018 08:56, Martin Trautmann  wrote:
>>Am 17. Mai 2018 02:01:42 MESZ schrieb Akkana Peck
>:
>>>tech-lists writes:
>>> You'd really prefer to make
>>>several separate related replies one right after the other on the
>>>same topic, rather than one reply with all your comments?
>>
>>Absolutely yes!
>>
>>Anything else will destroy proper threading.
>
>I would generally agree, but sometimes there are 2 or 3 leaf messages
>in a 
>discussion on the same point, and if you reply all 2 or 3 with one
>message you 
>can (a) post just once instead of further splaying the tree and (b get
>a few 
>closely related or even identical remark togther for comparison and
>response.

If they are on the same thing, then why merge them together? Just do reply on 
only one of them. 

I would not look for an answer to my reply within the answer to someone else. 

>So it is not insane. And most threading clients will associate the
>reply with 
>at least one of the sources, and threading can continue.

I'll have to check this discussion with proper threading at home. Here on the 
phone it appears to bei severely broken by  now.

- Martin
-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Re: Bottom posting v top posting

[Cameron Simpson]

On 17May2018 08:56, Martin Trautmann  wrote:

Am 17. Mai 2018 02:01:42 MESZ schrieb Akkana Peck :

tech-lists writes:
You'd really prefer to make
several separate related replies one right after the other on the
same topic, rather than one reply with all your comments?


Absolutely yes!

Anything else will destroy proper threading.


I would generally agree, but sometimes there are 2 or 3 leaf messages in a 
discussion on the same point, and if you reply all 2 or 3 with one message you 
can (a) post just once instead of further splaying the tree and (b get a few 
closely related or even identical remark togther for comparison and response.


So it is not insane. And most threading clients will associate the reply with 
at least one of the sources, and threading can continue.


Cheers,
Cameron Simpson 

Re: Bottom posting v top posting

[Martin Trautmann]

Am 17. Mai 2018 02:01:42 MESZ schrieb Akkana Peck :
>tech-lists writes:

> You'd really prefer to make
>several separate related replies one right after the other on the
>same topic, rather than one reply with all your comments?

Absolutely yes!

Anything else will destroy proper threading. 

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Re: Bottom posting v top posting

[Martin Trautmann]

Am 17. Mai 2018 05:15:33 MESZ schrieb Cameron Simpson :
>I've also seen replies come back from people unused to inline response
>with 
>their reply slap in the middle of the quoted text because they've not
>added a 
>blank line. I don't know exactly what's happening at their end, but at
>my end 
>they text appears in the middle of the quoted 

 Some people try an even more "clever" approach and do reply directly within 
the quote, applying a different color.

Of course this becomes useless the moment you do reply in plain text, even if 
you would have been able top see colored html before.

- Martin
-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Re: Bottom posting v top posting

[Cameron Simpson]

On 14May2018 12:15, Mark H. Wood  wrote:

I haven't seen a phone-resident MUA or a webmail thingy that I would
choose to use if I had another way.  But a modern phone makes a nice
terminal.


What do you do about typing? I pretty much don't use my phone for email at all, 
largely because the typing experience is so awful. If there are things I could 
do to improve that I'd love to hear about them.


Cheers,
Cameron Simpson 

Re: Bottom posting v top posting

[Cameron Simpson]

On 13May2018 19:15, Martin Trautmann  wrote:

Am 13. Mai 2018 17:12:14 MESZ schrieb tech-lists :


No!! ;) and you're missing the point (IMOHO) :( basically, people
quote back way too much. This is the issue. Most email apps allow
threaded mail, so very little need to quote whole screeds.


IBTD. Major e-mail tools, such as outlook, failed to support proper threading. 
Writing on a smartphone here, I'm not even aware of an app with threading.


The Apple iOS mail client threads. As is their habit when they roll out a new 
feature, they turned it on by default. Which should be good for feature 
discovery, but made my partner complain that the threading, such as it was, was 
gone because they threads were now collapsed, with an icon for expansion.



But are we still discussing bottom vs. top quoting? The here recommended style 
to me is known as INLINE QUOTING, where you do trim the quoting to the few 
lines which will help to understand the context of a discussion.


Yes. I suspect calling inline reply bottom posting misleads many many top 
posters to think "why would you put your reply below an infinite of quoted 
text?"



Neither top or bottom are as efficient to me.


Indeed.

I try to use the metaphor "so that your reply reads like a conversation" when I 
try to convince people.


Cheers,
Cameron Simpson 

Re: Bottom posting v top posting

[Cameron Simpson]

On 13May2018 19:53, Florian Gamböck  wrote:

On 2018-05-13 09:22, Chris Green wrote:

On Sat, May 12, 2018 at 11:44:49PM -0400, Scott Kostyshak wrote:

The key, I've learned, is to teach them about bottom-posting.
[...]I now try to remember to put "see my responses in-line below" as the 
first line of the message.


Yes, I add a line like that sometimes if it's long.  However the 
other thing to do is to trim/snip heavily so you really do only 
leave the required context.


To further avoid confusion I make sure to always insert one blank, 
unquoted line between the quote and my reply. So even if someone uses 
a client that HTML formats blockquotes with vertical lines on the 
left, there is always the indicator in form of a vertical gap so my reply will 
not easily being overlooked.


Yes, this is important. Not just for courtesy and etxt clarity, but also for 
how other mailers treat the reply.


I've also seen replies come back from people unused to inline response with 
their reply slap in the middle of the quoted text because they've not added a 
blank line. I don't know exactly what's happening at their end, but at my end 
they text appears in the middle of the quoted prose. I should dig into it.


Cheers,
Cameron Simpson 

Re: Bottom posting v top posting

[David Young]

You can come back out from under your desk, now.  I want to hide under
there.  A couple thoughts:

Sometimes I scroll through email conversations on the iPhone---I use
the "next message" button as a last resort.  I find that if quotes
are not trimmed, then it does not matter whether they are at the top
or the bottom of an email: there is a lot to scroll through.  So when
other iPhone users object to replying under a trimmed reply, I am not
sympathetic.

Do you remember Google Wave?  It's been a long time since I watched a
demo, but ISTR you could click where you wanted to insert a reply and
start typing, thus creating an "inline" reply.  It looked like they had
thought about the role of quotation in email and made a very thoughtful
design.

It seems to me that an email client should smooth over the differences
between top- and bottom-posting and even merge mails from a thread
into an overview that suppresses the text duplicated by quotations.  I
once set out to prototype such a view, but I wasn't too happy with the
way text marched toward the right margin, so I would take a different
approach, today.  Here is the conversation I produced an overview for,

  http://sigonella.whitecoralislands.com/~dyoung/summary/link-sets.discuss

and here is the overview,

  http://sigonella.whitecoralislands.com/~dyoung/summary/summary.html .

If you insist on ASCII art, here is the same overview in text,

  
http://sigonella.whitecoralislands.com/~dyoung/summary/link-sets.discussion-summary

Dave

-- 
David Young
dyo...@pobox.comUrbana, IL(217) 721-9981

Re: Bottom posting v top posting

[Patrick Shanahan]

* Akkana Peck  [05-16-18 20:03]:
 [...]
> Of course, in this case I could have simply replied to your message
> and let tech-lists' quote be >>, but what if you hadn't quoted the
> relevant part of the earlier message? You'd really prefer to make
> several separate related replies one right after the other on the
> same topic, rather than one reply with all your comments?
> 
> Sure, a threaded view will have to choose only one of the messages
> being replied to, but it's hard to see that as a major problem.
> A lot of mailers don't even follow the references and just group
> everything with the same subject into one thread, so it's not
> like most people scrutinize the details of the thread tree.

a big *plus* for mutt, as all mail clients are not created equal(ly).  but
mutt is the "head of the class".

not that I am biased after 20+ years, thankyou Mr. Elkins
-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Registered Linux User #207535@ http://linuxcounter.net
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode

Re: Bottom posting v top posting

[Akkana Peck]

tech-lists writes:
> But inline quoting has its own issues. Multiple inline quotes from multiple
> messages can get messy. IMOHO messier than just bottom posting, which is at
> least logically chronological.

Agreed -- sometimes I wish there was a flag to differentiate the
"> " characters somehow. But I'm not quite sure how I'd want it
to work; sometimes I edit them to use initial(s) of the person
being quoted, like "M>" or "MT>", but most of the time it
doesn't seem necessary.

Martin Trautmann writes:
> Who would do inline quoting from multiple messages? That would be
> absurd, since replying to multiple messages with proper threading would
> be to reply to those messages separately.

I do that, by marking and using ;r. For instance, this message.
Seems fairly clear to me; I don't see the problem. Being able to
do this so easily is one of the reasons I love mutt.

Of course, in this case I could have simply replied to your message
and let tech-lists' quote be >>, but what if you hadn't quoted the
relevant part of the earlier message? You'd really prefer to make
several separate related replies one right after the other on the
same topic, rather than one reply with all your comments?

Sure, a threaded view will have to choose only one of the messages
being replied to, but it's hard to see that as a major problem.
A lot of mailers don't even follow the references and just group
everything with the same subject into one thread, so it's not
like most people scrutinize the details of the thread tree.

...Akkana

Re: Bottom posting v top posting

[Derek Martin]

On Tue, May 15, 2018 at 07:24:00AM +1000, Brian Salter-Duke wrote:
> On Mon, May 14, 2018 at 11:57:33AM -0400, Mark H. Wood wrote:
> > On Sun, May 13, 2018 at 09:52:23AM +1000, Brian Salter-Duke wrote:
> > > My partner reads gmail on her phone or tablet. She reads my messages but 
> > > does
> > > not realise that if she scrolls down she can see her message that I 
> > > replying
> > > to. If I had bottom posting, she would never have read my message, 
> > > thinking
> > > that some how she had got her email back again. The use of phones for 
> > > email
> > > alters the game. It is time we gave up bottom posting!
> > 
> > You go right ahead and give it up, if you wish.
> > 
> > I have no interest in coddling people who use tools but can't be
> > bothered to learn how they work.
> 
> That is not the point. I know how mutt works although I am still learning new
> things after using it for 20 years or so. Regretably, at 79, I am forgetting
> some features I rarely use!!

The way I read this, it's not you, but your partner, that Mark
suggested did not bother to learn how to use the tools she is using.
Which, for what it's worth, is what you told us, basically.

> I have however given up trying to convince people to use bottom posting. I go
> with the flow - bottom posting on this list and top posting almost everywhere
> else. There is no point continuing to do something which does not work.

Obviously most of us replying in this thread think that it is top
posting that does not work, as it is confusing and even misleading.
Replying in-line puts your comments after what they refer to, which is
the only way to make sense of any sort of reply to a long message.

-- 
Derek D. Martinhttp://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.



pgpEbuESHRpaJ.pgp
Description: PGP signature

Re: Bottom posting v top posting

[Derek Martin]

On Sun, May 13, 2018 at 07:15:46PM +0200, Martin Trautmann wrote:
> But are we still discussing bottom vs. top quoting? The here
> recommended style to me is known as INLINE QUOTING, where you do
> trim the quoting to the few lines which will help to understand the
> context of a discussion.

Thank you for making this point.   I kept reading the thread waiting
for someone to make it before I piped up to make it myself.   Bottom
posting is just as loathesome as top posting.  This community prefers
inline responses, the key being what several people have pointed out:
The quoted text is trimmed judiciously to include only enough of what
was previously said to provide adequate context, with responses in
line after the relevant quoted snippet..

-- 
Derek D. Martinhttp://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.



pgp3zFKODZLdO.pgp
Description: PGP signature

Re: Bottom posting v top posting

[Martin Trautmann]

On 18-05-15 14:57, Stephan Seitz wrote:
> Bottom posting is as bad as top posting. There isn’t much difference. 

I fully agree. Using fullquotes it does not matter very much whether you
do it at top or bottom. Both is stupid for replies and even worse on
mailing lists where everyone should know about all the former messages.

There's just one occasion where private messages would require a
fullquote: when you do give a message to someone who does not know the
former messages.

But for this purpose there is a definition of its own: this would be a
*forwarding* instead of a reply.

Schönen Gruß
Martin



signature.asc
Description: OpenPGP digital signature

Re: Bottom posting v top posting

[Martin Trautmann]

On 18-05-15 14:37, tech-lists wrote:
> On 13/05/2018 18:15, Martin Trautmann wrote:
>> IBTD. Major e-mail tools, such as outlook, failed to support proper
>> threading. Writing on a smartphone here, I'm not even aware of an app
>> with threading.
> 
> You're using K-9 mail which has apparently supported threading since
> 4.390-beta, see
> http://grokbase.com/t/gg/k-9-mail/135pt36a12/conversation-threaded-view/oldest

Strange - I do use 5.403. This version offers "Nachrichten gruppieren":
Nachrichten eines Diskussionsstranges zusammenfassen. ("group messages
by subject).

This is exactly at this setting position as
 names as
"Threaded View". But threaded to me is a tree with hierarchy, not just
group messages by subject.

> I must admit that I don't know of an MUA that does not have threading
> capability in 2018. But I know nothing about outlook.

Please explain what threading meens to you. Thunderbird or mutt support
excellent threading. K-9 here doesn't.

>> But are we still discussing bottom vs. top quoting? The here
>> recommended style to me is known as INLINE QUOTING, where you do trim
>> the quoting to the few lines which will help to understand the context
>> of a discussion.
> 
> Oh I do that as well. I said:
> 
>>> Personally, if I need to quote someone back to themselves, I'll do it
>>> inline. 
> 
> But inline quoting has its own issues. Multiple inline quotes from
> multiple messages can get messy. IMOHO messier than just bottom posting,
> which is at least logically chronological.

Who would do inline quoting from multiple messages? That would be
absurd, since replying to multiple messages with proper threading would
be to reply to those messages separately.

- Martin



signature.asc
Description: OpenPGP digital signature

Re: Bottom posting v top posting

[Stephan Seitz]

On Di, Mai 15, 2018 at 01:37:06 +0100, tech-lists wrote:
But inline quoting has its own issues. Multiple inline quotes from 
multiple messages can get messy. IMOHO messier than just bottom posting, 
which is at least logically chronological.


Bottom posting is as bad as top posting. There isn’t much difference.  
Bigger mail with several questions is difficult to answer with both 
methods. In most cases some questions are missed or the recipient doesn’t 
know to which question the answer belongs.


Inline quoting is the only good method. It forces the writer to think 
about his answers and the correct placement so that the recipient doesn’t 
have trouble to understand the mail and this should be the most important 
thing.


Shade and sweet water!

Stephan

--
| Public Keys: http://fsing.rootsland.net/~stse/keys.html |


smime.p7s
Description: S/MIME cryptographic signature

Re: Bottom posting v top posting

[tech-lists]

On 13/05/2018 18:15, Martin Trautmann wrote:

IBTD. Major e-mail tools, such as outlook, failed to support proper threading. 
Writing on a smartphone here, I'm not even aware of an app with threading.


You're using K-9 mail which has apparently supported threading since 
4.390-beta, see 
http://grokbase.com/t/gg/k-9-mail/135pt36a12/conversation-threaded-view/oldest


I must admit that I don't know of an MUA that does not have threading 
capability in 2018. But I know nothing about outlook.



But are we still discussing bottom vs. top quoting? The here recommended style 
to me is known as INLINE QUOTING, where you do trim the quoting to the few 
lines which will help to understand the context of a discussion.


Oh I do that as well. I said:

Personally, if I need to quote someone back to themselves, I'll do it inline. 


But inline quoting has its own issues. Multiple inline quotes from 
multiple messages can get messy. IMOHO messier than just bottom posting, 
which is at least logically chronological.


--
J.

Re: Bottom posting v top posting

[Matthias Apitz]

El día martes, mayo 15, 2018 a las 08:35:50a. m. +0200, Martin Trautmann 
escribió:

> 
> 
> Am 14. Mai 2018 18:21:09 MESZ schrieb Ben Oliver :
> >This is a cool idea. I use K9 which has decent threading support.
> >Mainly 
> >for reading rather than sending though.
> 
> Could you send me a screenshot please? I also do use k9, but I only do see a 
> grouping by subject. It lacks a hierarchical tree view.
> 
> Ssh for mutt is an interesting idea, although I have no clue how I would use 
> vi on a smartphone for composing a reply
> .

I have as smartphone a BQ E4.5 which comes with an Ubuntu Linux. The
normal GUI MUA is Dekko, but I have ported mutt to the device and can
read/write and send e-mail written with vim. Anybody wants some screen?

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!


signature.asc
Description: PGP signature

Re: Bottom posting v top posting

[Martin Trautmann]

Am 14. Mai 2018 18:21:09 MESZ schrieb Ben Oliver :
>This is a cool idea. I use K9 which has decent threading support.
>Mainly 
>for reading rather than sending though.

Could you send me a screenshot please? I also do use k9, but I only do see a 
grouping by subject. It lacks a hierarchical tree view.

Ssh for mutt is an interesting idea, although I have no clue how I would use vi 
on a smartphone for composing a reply
.

- Martin

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Re: Bottom posting v top posting

[Mark H. Wood]

On Sun, May 13, 2018 at 09:52:23AM +1000, Brian Salter-Duke wrote:
> My partner reads gmail on her phone or tablet. She reads my messages but does
> not realise that if she scrolls down she can see her message that I replying
> to. If I had bottom posting, she would never have read my message, thinking
> that some how she had got her email back again. The use of phones for email
> alters the game. It is time we gave up bottom posting!

You go right ahead and give it up, if you wish.

I have no interest in coddling people who use tools but can't be
bothered to learn how they work.

-- 
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu


signature.asc
Description: PGP signature

Re: Bottom posting v top posting

[Ben Oliver]

On 18-05-14 12:15:57, Mark H. Wood wrote:

On Sun, May 13, 2018 at 07:15:46PM +0200, Martin Trautmann wrote:

Am 13. Mai 2018 17:12:14 MESZ schrieb tech-lists :
>No!! ;) and you're missing the point (IMOHO) :( basically, people
>quote back way too much. This is the issue. Most email apps allow
>threaded mail, so very little need to quote whole screeds.

IBTD. Major e-mail tools, such as outlook, failed to support proper threading. 
Writing on a smartphone here, I'm not even aware of an app with threading.


Heh.  When I want to do email via my phone, I SSH to where the mail is
and use Mutt.  It works very well, threading and all.

I haven't seen a phone-resident MUA or a webmail thingy that I would
choose to use if I had another way.  But a modern phone makes a nice
terminal.


This is a cool idea. I use K9 which has decent threading support. Mainly 
for reading rather than sending though.

Re: Bottom posting v top posting

[Mark H. Wood]

On Sun, May 13, 2018 at 07:15:46PM +0200, Martin Trautmann wrote:
> Am 13. Mai 2018 17:12:14 MESZ schrieb tech-lists :
> >No!! ;) and you're missing the point (IMOHO) :( basically, people 
> >quote back way too much. This is the issue. Most email apps allow 
> >threaded mail, so very little need to quote whole screeds. 
> 
> IBTD. Major e-mail tools, such as outlook, failed to support proper 
> threading. Writing on a smartphone here, I'm not even aware of an app with 
> threading. 

Heh.  When I want to do email via my phone, I SSH to where the mail is
and use Mutt.  It works very well, threading and all.

I haven't seen a phone-resident MUA or a webmail thingy that I would
choose to use if I had another way.  But a modern phone makes a nice
terminal.

-- 
Mark H. Wood
Lead Technology Analyst, weirdo

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu


signature.asc
Description: PGP signature

Re: Bottom posting v top posting

[Akkana Peck]

Jon LaBadie writes:
> Another example of this: I typically bottom/in-line
> respond even private emails.  As most of you may
> note I have a lot of personal info in my standard
> signature.  Yet even people with whom I've had many
> exchanges will ask my address or phone number.

Some email clients, like gmail, hide the signature. To check,
I bounced your message to a gmail account I have, and sure enough,
it doesn't show the signature with the phone numbers. But I tried
another message where I deliberately top-posted, then added a
signature with "-- " before the quoted text, and it did show
that one. So it hides a signature if it's just a signature, but
shows it if there's quoted text after it (at least in my extensive
test of 2 samples and one webmail client).

But I agree most top-posters never read the quoted text even when
their mail client shows it to them. All that quoting is a complete
silly waste of space and bandwidth, except in one very special edge
case: the "You weren't CCed on this discussion, but you should have
been, adding you in now" case.

...Akkana

Re: Bottom posting v top posting

[Ben Oliver]

On 18-05-13 17:34:21, Patrick Shanahan wrote:
I really believe it (top-posting, full quoting) began with compuserve 
and

aol, really discouraging time in history.


Definitely makes no sense other than 'gmail does it' or 'outlook does 
it'

Re: Bottom posting v top posting

[Jon LaBadie]

On Sun, May 13, 2018 at 05:43:53PM -0400, Thomas Schneider wrote:
...
>
> So Top posters never read further down the email, it's a total waste
> of bandwidth.
> 

Another example of this: I typically bottom/in-line
respond even private emails.  As most of you may
note I have a lot of personal info in my standard
signature.  Yet even people with whom I've had many
exchanges will ask my address or phone number.

Jon
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)

Re: Bottom posting v top posting

[Thomas Schneider]

Top posting makes complicated scientific conversations with several
interanal threads impossible.  "Bottom" posting - which is really
splitting the original email into parts (separated by blank lines for
visual clarity) allows people to hold very complex discussions.

The worst Top Posting case I ever saw occured when my technician
ordered some DNA to be synthesized.  Unfortunately the company she
ordered from was in the path of the Rita hurricane and they were
unable to fill the order for some weeks.  When they recovered the
sales person top posted a reply to her asking her to send the order
again.  It turned out that the bottom of the email contained the
original order.  He had sent it back to her!

So Top posters never read further down the email, it's a total waste
of bandwidth.

Also, Top posting makes searches hit the same text multiple times,
making it difficult to find a particular email.  If one carefully
trims away all the irrelevant material, leaving just the minimum
necessary then this effect is minimized.

Tom

Re: Bottom posting v top posting

[Patrick Shanahan]

* Akkana Peck  [05-13-18 10:35]:
> Brian Salter-Duke writes:
> > My partner reads gmail on her phone or tablet. [ ... ]
> > If I had bottom posting, she would never have read my message, thinking
> > that some how she had got her email back again.
> 
> If that's true, you're not trimming enough. The idea isn't to quote
> the other person's entire message and put your reply underneath --
> that's annoying on any platform, not just on phones. The idea is to
> quote a few lines of context before your reply, and remove the rest.
> If someone wants to read the entire previous message, they can use
> the list archive.
> 
> In a later message, Brian Salter-Duke writes (after 32 lines of
> two levels of unedited quoted material):
> > We have had 20 years or so to educate people to bottom post. We have almost
> > entirely failed.
> 
> That failed because a few companies that provided the email software
> for a high proportion of users, notably Google and Microsoft,
> opted to configure their mail software to add a blank line at the
> top of the message, thus implying people should put their reply there.
> Users took the hint, and that was when everybody started switching
> to top-posting. It wasn't nearly as common before the Gmail default
> changed; I think Outlook's default had changed quite a bit earlier,
> and corporate users had been top-posting for quite a while, but it
> wasn't that common for ordinary users or mailing lists until Gmail
> changed.
> 
> If everybody used mutt, the top-posting scourge wouldn't have
> happened. :-)

I really believe it (top-posting, full quoting) began with compuserve and
aol, really discouraging time in history.

-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Registered Linux User #207535@ http://linuxcounter.net
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode

Re: Bottom posting v top posting

[Florian Gamböck]

On 2018-05-13 09:22, Chris Green wrote:

On Sat, May 12, 2018 at 11:44:49PM -0400, Scott Kostyshak wrote:
The key, I've learned, is to teach them about bottom-posting. I have 
occassionally used bottom-posting with contacts without warning, and 
that has led to some confusion. I now try to remember to put "see my 
responses in-line below" as the first line of the message.


Yes, I add a line like that sometimes if it's long.  However the other 
thing to do is to trim/snip heavily so you really do only leave the 
required context.


To further avoid confusion I make sure to always insert one blank, 
unquoted line between the quote and my reply. So even if someone uses a 
client that HTML formats blockquotes with vertical lines on the left, 
there is always the indicator in form of a vertical gap so my reply will 
not easily being overlooked.


--
Flo

Re: Bottom posting v top posting

[Florian Gamböck]

On 2018-05-13 16:12, tech-lists wrote:
basically, people quote back way too much. This is the issue. Most 
email apps allow threaded mail, so very little need to quote whole 
screeds.


My rule of thumb is usually, I quote as much text as is needed so that 
my reply makes sense without searching older mails. While you are right 
that many mail clients *can* display threaded mail in a nice manner, 
definitely not all clients actually *do* so, or are configured so by 
default. So I do not make assumptions if my communication partner does 
look at the same happy little tree of messages that I am.


I usually won't quote complete paragraphs or even full messages if 
possible. But just a single "Do you agree with me?" as a quote from a 
pretty long, ongoing conversation is way too less IMHO.


But after all, it all depends on personal preference. If I had an 
electronic conversation with someone who said that they get confused by 
my way of quoting, then I would respect that and imitate their way. 
Maybe after the discussion, or in person if applicable, I would bring it 
up again and see if I can at least implant some idea to them, but I have 
long given up to convince someone to change their style they use for 
years.


--
Flo

Re: Bottom posting v top posting

[Chris Green]

On Sun, May 13, 2018 at 05:49:54PM +0100, Ben Oliver wrote:
> 
> The only exception is on those support emails where it says 'please post
> your reply above this line'

I just move the line (or copy what's below it to above it) so that I
can reply in context as normal.

-- 
Chris Green

Re: Bottom posting v top posting

[Martin Trautmann]

Am 13. Mai 2018 17:12:14 MESZ schrieb tech-lists :

>No!! ;) and you're missing the point (IMOHO) :( basically, people 
>quote back way too much. This is the issue. Most email apps allow 
>threaded mail, so very little need to quote whole screeds. 

IBTD. Major e-mail tools, such as outlook, failed to support proper threading. 
Writing on a smartphone here, I'm not even aware of an app with threading. 

But are we still discussing bottom vs. top quoting? The here recommended style 
to me is known as INLINE QUOTING, where you do trim the quoting to the few 
lines which will help to understand the context of a discussion.

Neither top or bottom are as efficient to me.

- Martin

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Re: Bottom posting v top posting

[Ben Oliver]

On 18-05-13 09:52:23, Brian Salter-Duke wrote:

Posting to this list yesterday and a recent incident with my partner,
prompts me to raise the issue of bottom posting. For a long time, mutters
have fought battles and wars to get everybody to bottom post. It makes a lot
of sense, but we have lost every battle and every war. I now only bottom
post to emails on this list. I also never ever see bottom posting in all the
hundreds of emails I get every week, other than posts to the mutt 
lists.


I am on lists for almost every bit of software I use and the standard is 
definitely to bottom post.


One of my pet peeves however is people who reply to emails with just 
'bottom post please' without providing any actual help.


That said it is the only way to go and I just do it everywhere 
regardless of what the other person is doing.


The only exception is on those support emails where it says 'please post 
your reply above this line'

Re: Bottom posting v top posting

[José María Mateos]

On Sun, May 13, 2018 at 09:52:23AM +1000, Brian Salter-Duke wrote:
> Posting to this list yesterday and a recent incident with my partner,
> prompts me to raise the issue of bottom posting. For a long time, mutters
> have fought battles and wars to get everybody to bottom post. It makes a lot
> of sense, but we have lost every battle and every war. I now only bottom
> post to emails on this list. I also never ever see bottom posting in all the
> hundreds of emails I get every week, other than posts to the mutt lists.

I don't think it's only mutters who do this. I participate in a bunch of 
mailing lists, and in the technical ones (essentially: Python, R, 
sqlite) people respect the bottom-post, trim reply, no HTML "classical" 
netiquette instructions. On others, people just top-post happily; on one 
of those lists, I checked yesterday out of curiosity, the last e-mail in 
a chain of replies contained one new line and the entire message was 45K 
in size. This [1] is 65K, in comparison.

Gmail is quickly becoming Hotmail.

Even on those lists, I bottom-post. I edit what I am replying to and 
answer paragraph by paragraph if necessary. I don't do it out of "this 
is how things should be done", but because I think it helps getting my 
point across. It's good writing. So far, nobody has complained.

This I do with my personal e-mail. At the work, where everybody uses 
Outlook and top-posting is the norm, I just go with the flow. But the 
purposes of sending an e-mail there and sending an e-mail here are 
different.

Cheers,

[1] https://www.gutenberg.org/cache/epub/17192/pg17192.txt

-- 
José María Mateos
https://rinzewind.org/blog-es || https://rinzewind.org/blog-en

Re: Bottom posting v top posting

[tech-lists]

On 13/05/2018 00:52, Brian Salter-Duke wrote:

The use of phones for email
alters the game. It is time we gave up bottom posting!


No!! ;) and you're missing the point (IMOHO) :( basically, people 
quote back way too much. This is the issue. Most email apps allow 
threaded mail, so very little need to quote whole screeds. Personally, 
if I need to quote someone back to themselves, I'll do it inline.


just my 0.02 euros, generically because this client is thunderbird.
--
J.

Re: Bottom posting v top posting

[Akkana Peck]

Brian Salter-Duke writes:
> My partner reads gmail on her phone or tablet. [ ... ]
> If I had bottom posting, she would never have read my message, thinking
> that some how she had got her email back again.

If that's true, you're not trimming enough. The idea isn't to quote
the other person's entire message and put your reply underneath --
that's annoying on any platform, not just on phones. The idea is to
quote a few lines of context before your reply, and remove the rest.
If someone wants to read the entire previous message, they can use
the list archive.

In a later message, Brian Salter-Duke writes (after 32 lines of
two levels of unedited quoted material):
> We have had 20 years or so to educate people to bottom post. We have almost
> entirely failed.

That failed because a few companies that provided the email software
for a high proportion of users, notably Google and Microsoft,
opted to configure their mail software to add a blank line at the
top of the message, thus implying people should put their reply there.
Users took the hint, and that was when everybody started switching
to top-posting. It wasn't nearly as common before the Gmail default
changed; I think Outlook's default had changed quite a bit earlier,
and corporate users had been top-posting for quite a while, but it
wasn't that common for ordinary users or mailing lists until Gmail
changed.

If everybody used mutt, the top-posting scourge wouldn't have
happened. :-)

...Akkana

Re: Bottom posting v top posting

[Ian Zimmerman]

On 2018-05-13 05:46, Jude DaShiell wrote:

> Has mutt got something that can be added to a .muttrc file which
> positions the cursor in a reply automatically for bottom posting?
> With bottom posting what has me concerned is did I hit the downarrow
> key enough to get to the correct position for writing and it would be
> nice not to have to do that any more.

I use Emacs as an external editor, and it's easy to set this up in
Emacs.

BTW, your post was misformatted: your entire reply appeared as the
signature.  Maybe because you scrolled down a line too far :-P

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.

Re: Bottom posting v top posting

[Stefan Hagen]

Christian Brabandt wrote:

Stefan Hagen wrote:

HTML is not allowed on this list, so here is the HTML part for this mail:
https://shell.srv.hagen.coffee/~sdk/textmail.html


Do you generate this somehow?


Of course I do.

My mutt configuration is here:
gopher://codevoid.de:70/1/git/dotfiles/files.gph
Or if you don't use gopher, prepend https://codevoid.de/?q=

I use a script as sendmail command (mutt/scripts/sendmail-privat).

This script calls MIMEmbellish (mutt/scripts/MIMEmbellish), which can 
transform a text message into a multipart message. It was originally meant to 
allow you to write markdown and create the html part with pandoc.


I really dislike the markdown approach, because if forces me to alter the 
text part in order to produce proper html. I want to write emails, not source 
code.


So instead of pandoc, I wrote htmlize.sh (mutt/scripts/htmlize.sh) and changed
MIMEmbellish to call this instead.

Then I send the result via msmtp.

That's pretty much my setup. I also have a mutt mail syntax file
which contains some formatting magic and a html preview shortcut.
(vim/bundle/vim-mailsyntax/ftplugin/mail.vim)

Best Regards,
Stefan

--
Stefan Hagen
Phone: +49 (0)176 642 925 17
Defender of RFC 1855 | PGP Key in Header.

Re: Bottom posting v top posting

[Jude DaShiell]

On Sat, 12 May 2018, Ian Zimmerman wrote:


Date: Sat, 12 May 2018 23:23:45
From: Ian Zimmerman <i...@very.loosely.org>
Reply-To: mutt-users@mutt.org
To: mutt-users@mutt.org
Subject: Re: Bottom posting v top posting

On 2018-05-13 09:52, Brian Salter-Duke wrote:


Posting to this list yesterday and a recent incident with my partner,
prompts me to raise the issue of bottom posting. For a long time,
mutters have fought battles and wars to get everybody to bottom
post. It makes a lot of sense, but we have lost every battle and every
war. I now only bottom post to emails on this list. I also never ever
see bottom posting in all the hundreds of emails I get every week,
other than posts to the mutt lists.


I am on some 30+ lists, and I'd estimate bottom posting is the norm on
25.  It is true that gmail users are a small minority on all of them.

I also bottom post with some of my best friends who _are_ gmail users,
and they don't object.  But I think they use computers for email, not
phones.

To sum up, the vision you have of almost everybody using phones may be
the future, but is not yet the present, and I resist accelerating the
transition.




--

Has mutt got something that can be added to a .muttrc file which positions 
the cursor in a reply automatically for bottom posting?  With bottom 
posting what has me concerned is did I hit the downarrow key enough to get 
to the correct position for writing and it would be nice not to have to do 
that any more.

Re: Bottom posting v top posting

[Christian Brabandt]

On So, 13 Mai 2018, Stefan Hagen wrote:

> HTML is not allowed on this list, so here is the HTML part for this mail:
> https://shell.srv.hagen.coffee/~sdk/textmail.html

Do you generate this somehow?

regards,
Christian
-- 
One girl can be pretty -- but a dozen are only a chorus.
-- F. Scott Fitzgerald, "The Last Tycoon"

Re: Bottom posting v top posting

[Don Saklad]

For the current setup at this end here... an attitude of please 
feel free replying unconfined.

A few, maybe more than a few contributors to a list and a few maybe more
than a few subscribers reading contributors' writings would allow
contributors the greatest possible freedom for posting style
https://en.wikipedia.org/wiki/Posting_style#Placement_of_replies

Editing/moderating might look for a mechanism, software to automatically
format a particular style, For example http://reddit.com

Re: Bottom posting v top posting

[Chris Green]

On Sat, May 12, 2018 at 11:44:49PM -0400, Scott Kostyshak wrote:
> On Sun, May 13, 2018 at 03:23:45AM +, Ian Zimmerman wrote:
> 
> > I also bottom post with some of my best friends who _are_ gmail users,
> > and they don't object.
> 
> +1
> 
So do I with family and friends.


> The key, I've learned, is to teach them about bottom-posting. I have
> occassionally used bottom-posting with contacts without warning, and
> that has led to some confusion. I now try to remember to put "see my
> responses in-line below" as the first line of the message.
> 
Yes, I add a line like that sometimes if it's long.  However the other
thing to do is to trim/snip heavily so you really do only leave the
required context.

-- 
Chris Green

Re: Bottom posting v top posting

[Francesco Ariis]

On Sun, May 13, 2018 at 03:31:38PM +1000, Brian Salter-Duke wrote:
> We have had 20 years or so to educate people to bottom post. We have almost
> entirely failed.

Judging by the message you are replying to, we failed but we did not
stop being smug prats.

Re: Bottom posting v top posting

[Francesco Ariis]

On Sun, May 13, 2018 at 09:52:23AM +1000, Brian Salter-Duke wrote:
> For a long time, mutters have fought battles and wars to get everybody
> to bottom post. It makes a lot of sense, but we have lost every battle
> and every war.

In a work related environment, top-posting is more common and even
encouraged; it makes sense as sometimes you need to reconstruct the
whole, pristine chain of communication (for audit reasons, to forward
to a third party, etc.).
That, I feel, explains the proneness of many users to top-post.

> I now only bottom to emails on this list. I also never ever see bottom
> posting in all the hundreds of emails I get every week, other than
> posts to the mutt lists.

Bottom-posting on mailing-lists is still a battle worthy of being
fought.
I don't nudge anyone (I do when their email is HTML-only), but I keep
bottom posting on MLs: trimming+BP saves reading time and is clearer.
I hope/expect newcomers to pick out the habit by experiencing how
easier it is to navigate a bottom-posted thread.

Re: Bottom posting v top posting

[Erik Christiansen]

On 13.05.18 15:31, Brian Salter-Duke wrote:
> On Sun, May 13, 2018 at 03:03:55PM +1000, Erik Christiansen wrote:
> > On 13.05.18 09:52, Brian Salter-Duke wrote:
> > > It is time we gave up bottom posting!
...
> Eric, I tried to email you direct, but you do not allow that, so I will have 
> to
> send to the list my anger at your post.

Please understand that I would have returned it to the list in any event.

> Who the hell do you think you are to lecture me in that way?

Anger is good in a dangerous situation, but here it does seem to impede
understanding. From your fulsome fullquote, I have requoted only the
dictatorial challenge in your OP, which caused me to offer up a pin to
the balloon of your fantasy.

> I have been using mutt for pretty well as long as you have no doubt. I
> am perfectly happy to bottom post. I have always bottom posted on the
> mutt lists. I understand why the mutt community prefers it. I prefer it.

No, you have told us we must abandon our optimal practice in favour of
an ignorant fashion. I responded accordingly, in a constructively
educational manner, appropriate to the nature of the challenge.

> The problem is that nobody outside the mutt community who email me use it.

A calmer reading of my post ought to reveal that it is an attempt to
help you learn that a difference is not 'a priori' a problem. I write
Danish to my relatives, German to some friends, and English where that
suits. It is no mark of a developed intellect to be so dogmatic as to
insist that various communities must conform to a single norm. If you
think carefully, you will observe that in the sentence above, you
logically connect the problem with the last pronoun there. That is where
you will find the remedy, rather than in attempting to force conformity
on disparate communities.

> Also, it would not go down well if I tried to educate my research colleagues 
> at universities all over the world to bottom post.

On this list we would ask them to do so. As for elsewhere, I refer you
to your sig.

> We have had 20 years or so to educate people to bottom post. We have almost
> entirely failed.

No we have made no attempt to do so outside lists, but you still fail to
learn to tolerate difference in other communities.

> It turns out that my random sig that I use for this list is highly 
> appropriate.
> I assure you that it really is random.

Yes it is ironically appropriate. If only you could learn from it what
you have so far failed to learn from gentle prodding of your intellect,
then we would be spared further effort to help you man up and accept
evident difference.

Erik

-- 
Gnothi seauton, the Ancient Greek aphorism "Know thyself", was inscribed in the 
pronaos (forecourt) of the Temple of Apollo at Delphi according to the Greek
periegetic (travelogue) writer Pausanias. The Suda, a tenth century encyclopedia
of Greek Knowledge, says it is a warning to pay no attention to the opinion of
the multitude.

Re: Bottom posting v top posting

[Stefan Hagen]

Brian Salter-Duke wrote:

Erik Christiansen wrote:

Salter-Duke wrote:

My partner reads gmail on her phone or tablet. She reads my messages but
does not realise that if she scrolls down she can see her message that
I replying to. If I had bottom posting, she would never have read my
message, thinking that some how she had got her email back again. The use
of phones for email alters the game. It is time we gave up bottom posting!


Thinking can be a useful path to learning. Is it possible for you to
imagine that if you could learn to trim your quotes to the essential
minimum of a line or two, then bottom posting works well on most screens,
and even on phones if you prefix the whole message with: "For clarity I'm
answering in context, see below:"


Eric, I tried to email you direct, but you do not allow that, so I will have
to send to the list my anger at your post. Who the hell do you think you are
to lecture me in that way?


This is the kind of response I get from some of my top-posting friends as 
well. I've stopped that debate in my environment. I like bottom posting and I 
do it everywhere. I put in the extra work to reformat whole email chains and 
sometimes people do not want to break it and continue.


I also use the hated HTML format to force a proper formatting on their 
clients. I generate an HTML part for my email, which represents the text part 
with a fixed width font, a forced width of 82 characters and colored quote 
lines. Now I can use ASCII drawings and all my friends on their fancy phones

and crappy clients can enjoy it.

I often get compliments on the style and readability on my emails. And my 
response then is: Use a proper client and learn about email and every mail 
will look like this.


HTML is not allowed on this list, so here is the HTML part for this mail:
https://shell.srv.hagen.coffee/~sdk/textmail.html

Best Regards,
Stefan

--
Stefan Hagen
Phone: +49 (0)176 642 925 17
Defender of RFC 1855 | PGP Key in Header.

Re: Bottom posting v top posting

[Erik Christiansen]

On 13.05.18 09:52, Brian Salter-Duke wrote:
> My partner reads gmail on her phone or tablet. She reads my messages but does
> not realise that if she scrolls down she can see her message that I replying
> to. If I had bottom posting, she would never have read my message, thinking
> that some how she had got her email back again. The use of phones for email
> alters the game. It is time we gave up bottom posting!

The world has an infinite supply of fools who stumble through it,
unaware that it is the adaptor who survives. NO, it is not the list
community which needs to adapt to one intruder, but the converse.

Bottom post, and we will read. Only then can you hope for a reply.
Understand that we have t-prot for TOFU protection, and do not need to
scroll down as long quotes are compressed. Trim your quotes, not out of
consideration for the reader if you lack that, but in order for your
reply to be seen and read.

Try to learn. It is a prerequisite to becoming adaptable. The first
survival tactic is when in Rome, do as they do. We have no problem with
you sending inverted messages in other domains. Go your hardest, but to
attempt to impose that foolishness on our community is infantile and a
symptom of slow learning.

Thinking can be a useful path to learning. Is it possible for you to
imagine that if you could learn to trim your quotes to the essential
minimum of a line or two, then bottom posting works well on most
screens, and even on phones if you prefix the whole message with:
"For clarity I'm answering in context, see below:"

Your partner's ignorance and your failure to compensate do not compel an
entire community to pander to your slow learning. Please man up and adapt. 

Erik

Re: Bottom posting v top posting

[Scott Kostyshak]

On Sun, May 13, 2018 at 03:23:45AM +, Ian Zimmerman wrote:

> I also bottom post with some of my best friends who _are_ gmail users,
> and they don't object.

+1

The key, I've learned, is to teach them about bottom-posting. I have
occassionally used bottom-posting with contacts without warning, and
that has led to some confusion. I now try to remember to put "see my
responses in-line below" as the first line of the message. Some mail
clients by default collapse inline responses. I don't know which mail
clients they are, but contacts have told me that they just saw an empty
email (until I told them to search for how to uncollapse the quoted
reply). To me, this is a clear bug in such mail clients, but it's good
to know the behavior exists.

I think the important thing is to be kind and patient with newcommers,
and educate them on why in some situations some people prefer
bottom-posting.

I do not participate on this list much, but on lyx-users bottom-posting
is part of our "list netiquette" [1]. If I see a user who is sticking
around for a while, I just kindly remind them that it is part of our
list netiquette. If everyone takes turns in patiently reminding
newcommers, it is not so much of a hastle and I've found that the
newcommers are open to bottom-posting.

Scott

[1] 
https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.lyx.org_FAQ_ListNetiquette=DwIBAg=pZJPUDQ3SB9JplYbifm4nt2lEVG5pWx2KikqINpWlZM=zUqJVM3RY5svAe6ctaxqyrj3k9OQkcL6UzDF3Kn6e0s=I0V31ciCHXrUy7R-bTo1iUQ7IQ-O4anaqqzxuRkujCM=l3XyQq-DSjJT-wVddDp5jQhsRavz1QC53Zxx3JUIpqQ=


-- 
Scott Kostyshak
Assistant Professor of Economics
University of Florida
https://people.clas.ufl.edu/skostyshak/

Re: Bottom posting v top posting

[Ian Zimmerman]

On 2018-05-13 09:52, Brian Salter-Duke wrote:

> Posting to this list yesterday and a recent incident with my partner,
> prompts me to raise the issue of bottom posting. For a long time,
> mutters have fought battles and wars to get everybody to bottom
> post. It makes a lot of sense, but we have lost every battle and every
> war. I now only bottom post to emails on this list. I also never ever
> see bottom posting in all the hundreds of emails I get every week,
> other than posts to the mutt lists.

I am on some 30+ lists, and I'd estimate bottom posting is the norm on
25.  It is true that gmail users are a small minority on all of them.

I also bottom post with some of my best friends who _are_ gmail users,
and they don't object.  But I think they use computers for email, not
phones.

To sum up, the vision you have of almost everybody using phones may be
the future, but is not yet the present, and I resist accelerating the
transition. 

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.

Re: Bottom posting v top posting

[Derek Martin]

On Sun, May 13, 2018 at 09:52:23AM +1000, Brian Salter-Duke wrote:
> It is time we gave up bottom posting!

Just... nope.

-- 
Derek D. Martinhttp://www.pizzashack.org/   GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address.  Replying to it will result in
undeliverable mail due to spam prevention.  Sorry for the inconvenience.



pgpML1LnY4IkP.pgp
Description: PGP signature