From: Joost Kremers <joostkremers@yahoo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: OT w/ misunderstanding Re: creating a sub-menu
Date: 12 Mar 2013 18:14:27 GMT [thread overview]
Message-ID: <slrnkjus43.30b.joostkremers@j.kremers4.news.arnhem.chello.nl> (raw)
In-Reply-To: mailman.21918.1363080995.855.help-gnu-emacs@gnu.org
ken wrote:
>> I've been posting from two different computers, which may the the cause.
>
> That by itself couldn't be the actual cause, not even should you be
> using different email programs on those two computers. If you click
> "Reply"-- or for this particular list, "Reply All"-- the email program
> should maintain the threading of the conversation automatically for you
> (well, for all of us actually), regardless of which computer you do it
> on, regardless where on the internet those computers reside, etc. This
> has been standard in email applications for a very long time.
Well, I'm not actually *using* an email application. I'm reading this as
gnu.emacs.help.
> in short, just click "Reply All" and everything should work fine.
Alas, since I'm using a CLI client (slrn), I don't have a "reply all"
button. But in a news client, such a button wouldn't make much sense
anyway: any reply is a reply to all, that's what Usenet is all about.
FWIW, slrn displays all posts as one single thread, so from my point of
view, it's Thunderbird that's having trouble keeping the thread
together. (That may or may not be true, I don't know; it's just how it
looks on my end of the line.)
> No need to apologize. We're having a technical discussion, not a
> personal one. It would help quite a bit in this regard though if, when
> you abridge the email you are replying to, the technical part of the
> discussion were not edited out. Otherwise we're hearing the sound of
> one hand clapping. If there's any doubt as to what's relevant, it would
> then be best just to leave the entirety of the quoted material intact.
The context is always there in the thread, so I generally cut all
details and leave enough so that the quoted text provides a summary of
what has been said. Of course it's always possible I snipped too much,
but generally I'm annoyed by messages where the first non-quoted text is
below the bottom of my screen when I open them... And since the
context is generally just a few keystrokes away (for me, anyway), I tend
to think that less is more.
> Also, regarding "the answer", see my reply to Steve.
Yeah, I read it. If I find some time, I might look into it a bit more,
but that probably won't be today or tomorrow...
--
Joost Kremers joostkremers@fastmail.fm
Selbst in die Unterwelt dringt durch Spalten Licht
EN:SiS(9)
prev parent reply other threads:[~2013-03-12 18:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.21496.1362523165.855.help-gnu-emacs@gnu.org>
2013-03-06 1:42 ` creating a sub-menu Joost Kremers
2013-03-06 11:44 ` ken
[not found] ` <mailman.21539.1362570279.855.help-gnu-emacs@gnu.org>
2013-03-06 20:55 ` Joost Kremers
2013-03-07 9:36 ` OT w/ misunderstanding " ken
[not found] ` <mailman.21622.1362648982.855.help-gnu-emacs@gnu.org>
2013-03-11 19:47 ` Joost Kremers
2013-03-12 9:36 ` ken
[not found] ` <mailman.21918.1363080995.855.help-gnu-emacs@gnu.org>
2013-03-12 18:14 ` Joost Kremers [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnkjus43.30b.joostkremers@j.kremers4.news.arnhem.chello.nl \
--to=joostkremers@yahoo.com \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).