From: Indi <thebeelzebubtrigger@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How do I eject an audio CD inside Gnome?
Date: Sat, 4 Jun 2011 19:49:16 -0400 [thread overview]
Message-ID: <20110604234916.GF11409@gaurahari.merseine.nu> (raw)
In-Reply-To: <4DEAC1BB.1000406@gmail.com>
On Sat, Jun 04, 2011 at 06:37:31PM -0500, Dale wrote:
> Mick wrote:
> > On Saturday 04 Jun 2011 23:38:09 Neil Bothwick wrote:
> >
> >> On Sat, 4 Jun 2011 23:09:28 +0100, Stroller wrote:
> >>
> >>> My client wraps lines at a perfectly sensible length.
> >>>
> >>> http://linux.stroller.uk.eu.org/Email%20Line%20Wrapping.png
> >>>
> >> It's not always a readable length. Long lines are much harder to read,
> >> that's why newspapers use columns. The accepted width was generally
> >> considered to be 2.5 to 3.5 alphabets (not characters because of
> >> proportional type) which matches up rather nicely with the 70-odd
> >> character generally recommended for mail.
> >>
> > Strange, on Kmail Indi's text does not wrap as shown in Stroller's screenshot,
> > but extends to the end of the message window just as Stroller's text does.
> >
>
> It was here too. I have one more question. What the heck is going on
> with our email stuff? First broken threads, now word wrapping not
> working correctly. Did someone break a mirror? O_O
>
All mail here is edited in vim, so I know I'm wrapping my text.
The quoted text left in in my replies usually appears "as is" deliberately,
as a courtesy. It's always good to verify what one's mail looks like in
another MUA. :)
--
caveat utilitor
♫ ❤ ♫ ❤ ♫ ❤ ♫ ❤
next prev parent reply other threads:[~2011-06-04 23:50 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gXVfA-3CX-11@gated-at.bofh.it>
[not found] ` <gXVyV-4kf-1@gated-at.bofh.it>
[not found] ` <gXW1Y-50l-21@gated-at.bofh.it>
[not found] ` <gXWlk-5IJ-11@gated-at.bofh.it>
2011-05-31 3:20 ` [gentoo-user] How do I eject an audio CD inside Gnome? Indi
[not found] ` <gY7JL-8ed-7@gated-at.bofh.it>
[not found] ` <gYkdX-49P-1@gated-at.bofh.it>
[not found] ` <gZrwK-3qT-7@gated-at.bofh.it>
[not found] ` <gZPpn-26G-1@gated-at.bofh.it>
2011-06-04 11:35 ` Indi
2011-06-04 16:47 ` Alan McKinnon
2011-06-04 17:25 ` Indi
2011-06-04 19:31 ` Mick
2011-06-04 22:09 ` Stroller
2011-06-04 22:38 ` Neil Bothwick
2011-06-04 23:10 ` Mick
2011-06-04 23:37 ` Dale
2011-06-04 23:49 ` Indi [this message]
2011-06-04 22:54 ` Indi
2011-06-05 10:40 ` Alan McKinnon
2011-06-05 11:42 ` Indi
2011-05-29 20:49 Alan Mackenzie
2011-05-29 20:58 ` Alan McKinnon
2011-05-29 21:13 ` Neil Bothwick
2011-05-29 21:37 ` Alan Mackenzie
2011-05-29 21:56 ` Alan McKinnon
2011-05-30 0:32 ` Peter Humphrey
2011-05-30 10:10 ` Alan Mackenzie
2011-05-30 10:33 ` Alan McKinnon
2011-05-30 11:46 ` Mick
2011-05-31 13:45 ` Alan McKinnon
2011-06-01 22:05 ` Mick
2011-06-01 22:50 ` Alan McKinnon
2011-06-02 5:02 ` Mick
2011-05-30 23:38 ` Stroller
2011-05-31 2:26 ` daid kahl
2011-05-31 2:28 ` daid kahl
2011-05-30 23:26 ` Stroller
2011-05-30 23:44 ` Stroller
2011-06-01 21:38 ` Alan Mackenzie
2011-06-03 1:32 ` Volker Armin Hemmann
2011-06-04 2:56 ` Stroller
2011-06-04 3:18 ` Dale
2011-05-29 21:20 ` Alan Mackenzie
2011-05-29 21:34 ` Alan McKinnon
2011-05-30 7:56 ` Thanasis
2011-05-30 20:54 ` Jonathan
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=20110604234916.GF11409@gaurahari.merseine.nu \
--to=thebeelzebubtrigger@gmail.com \
--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