From: Tassilo Horn <tsdh@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [OT, meta] markup (Re: have emacs use SIGTERM to end a process instead of SIGHUP)
Date: Fri, 19 Jul 2013 18:48:55 +0200 [thread overview]
Message-ID: <87ob9ymr60.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: 878v12ptx9.fsf@VLAN-3434.student.uu.se
Emanuel Berg <embe8573@student.uu.se> writes:
Hi!
>> Newsreaders construct threads from the references, i.e., every
>> article mentions its ancestor articles. Since the references in
>> your articles are wrong, every followup you make creates a new
>> thread instead of being displayed as a child of the article you
>> are replying to.
>
> Really? To be such a serious bug, it sure took a long while to get to
> the surface!
>
> And how can it be that *I* see the threads (including my posts)
> correctly?
There are two ways to build threads: by reference and by same subjects.
Gathering by subjects is the default in Gnus nowadays.
,----[ C-h v gnus-summary-thread-gathering-function RET ]
| gnus-summary-thread-gathering-function is a variable defined in `gnus-sum.el'.
| Its value is gnus-gather-threads-by-references
| Original value was
| gnus-gather-threads-by-subject
|
| This variable may be risky if used as a file-local variable.
|
| Documentation:
| *Function used for gathering loose threads.
| There are two pre-defined functions: `gnus-gather-threads-by-subject',
| which only takes Subjects into consideration; and
| `gnus-gather-threads-by-references', which compared the References
| headers of the articles to find matches.
`----
> I didn't do that much Gnus configuration. What I did, I collected at
> the URL, last.
>
> But you already gave me some hints as to where I will start to look.
>
> http://user.it.uu.se/~embe8573/gnus/index.html
Hm, not sure what might be the culprit. But what is `new-message' good
for, i.e., what does it do that C-x m (`compose-mail') with
`mail-user-agent' set to `gnus-user-agent' wouldn't also do?
Bye,
Tassilo
next prev parent reply other threads:[~2013-07-19 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 22:16 have emacs use SIGTERM to end a process instead of SIGHUP John Leach
2013-07-09 12:02 ` Tassilo Horn
2013-07-12 11:01 ` John Leach
2013-07-15 10:46 ` Tassilo Horn
[not found] ` <mailman.1087.1373885216.12400.help-gnu-emacs@gnu.org>
2013-07-15 14:10 ` [OT, meta] markup (Re: have emacs use SIGTERM to end a process instead of SIGHUP) Emanuel Berg
2013-07-16 7:47 ` Tassilo Horn
[not found] ` <mailman.1147.1373960909.12400.help-gnu-emacs@gnu.org>
2013-07-16 23:16 ` Emanuel Berg
2013-07-17 0:42 ` Emanuel Berg
2013-07-17 10:11 ` Tassilo Horn
[not found] ` <mailman.1235.1374055880.12400.help-gnu-emacs@gnu.org>
2013-07-19 10:24 ` Emanuel Berg
2013-07-19 13:05 ` Tassilo Horn
[not found] ` <mailman.1386.1374239175.12400.help-gnu-emacs@gnu.org>
2013-07-19 13:21 ` Emanuel Berg
2013-07-19 16:48 ` Tassilo Horn [this message]
[not found] ` <mailman.1423.1374252559.12400.help-gnu-emacs@gnu.org>
2013-07-20 4:32 ` Emanuel Berg
2013-07-20 5:53 ` Emanuel Berg
2013-07-22 9:17 ` Emanuel Berg
2013-07-22 9:31 ` Emanuel Berg
2013-07-23 6:59 ` Tassilo Horn
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=87ob9ymr60.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.org \
--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).