public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wol <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Getting maximum space out of a hard drive
Date: Mon, 29 Aug 2022 00:31:05 +0100	[thread overview]
Message-ID: <328afa0a-9b0c-e868-0173-a56f8e81cbf4@youngman.org.uk> (raw)
In-Reply-To: <CAK2H+ecQOcy5KxeRYqak-632FOpKoVMEc-tpOrDZRaUq7Tq6WA@mail.gmail.com>

On 28/08/2022 22:53, Mark Knecht wrote:
> 
> 
> On Sun, Aug 28, 2022 at 2:33 PM Wol <antlists@youngman.org.uk 
> <mailto:antlists@youngman.org.uk>> wrote:
>  >
>  > On 28/08/2022 22:07, Frank Steinmetzger wrote:
>  > > Is there a particular reason why your mailer inserts the quote 
> character
>  > > only on the first line of a quote paragraph? It makes reading your 
> replies a
>  > > little difficult because it is not visible on first glance where 
> your quote
>  > > ends and your reply starts.
>  >
>  > Because the OPs mailer sent it as one line per paragraph?
>  >
>  > My mailer (Tbird) is configured for plain text, but still screws up when
>  > it receives html junk.
>  >
>  > Cheers,
>  > Wol
> 
> 
> My address is GMail, and I just use Chrome. Responding to this list
> requires me to Ctrl-A and then remove ALL formatting which inserts
> the greater than symbol.
> 
> For 99% of my life no one cares about how an email response is
> formatted. The only place that complains is this list so I do all of
> that above to try to make it better for the list.

Well, a lot of us are greybeards who predate HTML. Grumpy old greybeards 
don't like change :-) and I include myself in that.
> 
> Maybe I made a mistake on the recent response that Frank
> doesn't like? If it's happening on every email I send then what
> Frank is seeing is not what I'm seeing.
> 
> In my experience it's easier to ride the Google horse in the
> direction the Google horse is going. Turning off all formatting
> causes too many problems in real life outside of Gentoo
> email lists.
> 
HTML is f*cked up for so many things (for which clueless idiots 
recommend it). At work, living inside the GMail/Chrome eco-system is 
mandatory. And I regularly swear at it because I get over-wide emails 
that are a bastard to read.

> My apologies,
> Mark
> 
Don't apologise - it's not your fault. If you use gmail/chrome, that's 
fine. It would just be nice if Google didn't screw up your mail. The 
really scary thing is all these things Google do behind your back are 
capable of (and as far as the linux guys are concerned regularly do) 
screwing up your security.

If you want to interact with linux devs you will find they are even more 
anti-gmail than here - because what you are sending is not what you 
think you are sending! But until then, don't beat yourself up over it. 
Don't upset people unnecessarily, but if it causes you grief, don't do 
it. If people don't like it, they can ignore it.

Cheers,
Wol


  reply	other threads:[~2022-08-28 23:31 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-18 18:04 [gentoo-user] Getting maximum space out of a hard drive Dale
2022-08-18 18:18 ` Rich Freeman
2022-08-19  2:03   ` Dale
2022-08-19  4:26     ` David Haller
2022-08-24 22:45       ` Frank Steinmetzger
2022-08-25  6:22         ` William Kenworthy
2022-08-25 12:43           ` Dale
2022-08-25 12:52             ` Rich Freeman
2022-08-25 15:10               ` Jack
2022-08-25 18:59                 ` Dale
2022-08-25 21:08                   ` Rich Freeman
2022-08-25 23:59                     ` Dale
2022-08-26  0:15                       ` Mark Knecht
2022-08-26 11:26                         ` Dale
2022-08-26 11:55                           ` Gerrit Kuehn
2022-08-26 12:07                           ` Rich Freeman
2022-08-26 23:07                             ` Dale
2022-08-26 14:09                           ` Mark Knecht
2022-08-26 14:25                             ` Rich Freeman
2022-08-26 14:40                               ` Mark Knecht
2022-08-26 23:20                                 ` Dale
2022-08-26 23:37                                   ` Mark Knecht
2022-08-27  1:16                                     ` Mark Knecht
2022-08-27 23:30                                       ` Dale
2022-08-28  9:27                                         ` Michael
2022-08-28 21:07                             ` Frank Steinmetzger
2022-08-28 21:33                               ` Wol
2022-08-28 21:53                                 ` Mark Knecht
2022-08-28 23:31                                   ` Wol [this message]
2022-08-28 21:34                           ` Frank Steinmetzger
2022-08-29  5:49                             ` Dale
2022-08-29 14:42                               ` Frank Steinmetzger
2022-08-29 21:28                                 ` Dale
2022-08-30 14:26                                   ` Frank Steinmetzger
2022-08-25 22:41                   ` Wols Lists
2022-08-25 23:56                     ` Dale
2022-08-26  7:24                       ` Wols Lists
2022-08-26 11:27                         ` Dale
2022-08-26 13:35                           ` Wols Lists
2022-08-26  4:47                   ` David Haller
2022-08-18 18:20 ` Andreas Fink
2022-08-20 19:15 ` Dale
2022-08-20 20:57   ` Rich Freeman
2022-08-25  3:44     ` Dale
2022-08-20 21:46   ` Grant Taylor
2022-08-20 21:57   ` Grant Taylor
2022-08-20 22:45     ` Dale
2022-08-21  4:22       ` William Kenworthy
2022-08-21  5:34         ` Grant Taylor
2022-08-21  9:26           ` William Kenworthy
2022-08-21 10:09         ` Dale
2022-08-21 16:47           ` Dale
2022-08-21  5:27       ` Grant Taylor
2022-08-24 22:39       ` Frank Steinmetzger
2022-08-24 22:50         ` Wol
2022-08-22 14:50     ` Laurence Perkins
2022-08-22 15:02       ` Rich Freeman

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=328afa0a-9b0c-e868-0173-a56f8e81cbf4@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gentoo-user@lists.gentoo.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