From: cowan at ccil.org (John Cowan)
Subject: [COFF] [TUHS] Topics...
Date: Tue, 7 Jul 2020 11:26:42 -0400 [thread overview]
Message-ID: <CAD2gp_RXxOD01Fg56fyzKyHFKv_6Tosw0FYvE45+8YBKmrFZ4Q@mail.gmail.com> (raw)
In-Reply-To: <20200707143843.GI11130@att.net>
On Tue, Jul 7, 2020 at 10:39 AM Alan D. Salewski <salewski at att.net> wrote:
> I'm just trying to gauge people's interest in this idea.
>
> My preference would be to keep things the way they are.
>
> I want to receive all list messages; I would not want to switch to an
> arrangement where I was in danger of missing messages because my list
> preferences config became a little stale.
>
Very much +1. Part of the trouble is that Gmail and similar clients don't
routinely show you the Subject: line to make it easy to edit it; you have
to take affirmative action when you want to change the subject matter.
John Cowan http://vrici.lojban.org/~cowan cowan at ccil.org
It's the old, old story. Droid meets droid. Droid becomes chameleon.
Droid loses chameleon, chameleon becomes blob, droid gets blob back
again. It's a classic tale. --Kryten, Red Dwarf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200707/f988ce06/attachment-0001.htm>
next prev parent reply other threads:[~2020-07-07 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 2:11 [COFF] Topics gtaylor
2020-07-07 2:56 ` athornton
2020-07-07 14:33 ` [COFF] [TUHS] Topics rtomek
2020-07-07 14:38 ` salewski
2020-07-07 15:26 ` cowan [this message]
2020-07-08 4:31 ` gtaylor
2020-07-07 22:53 ` [COFF] Topics dave
[not found] ` <97902a98ce76c281160840d78ed838be@xs4all.nl>
2020-07-08 2:09 ` [COFF] [TUHS] Topics dave
2020-07-08 4:29 ` [COFF] Topics gtaylor
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=CAD2gp_RXxOD01Fg56fyzKyHFKv_6Tosw0FYvE45+8YBKmrFZ4Q@mail.gmail.com \
--to=coff@minnie.tuhs.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).