From: Noam Postavsky <npostavs@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 15682@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
Mauro Aranda <maurooaranda@gmail.com>
Subject: bug#15682: 24.3.50; `:link' in `defgroup' does not respect `mouse-1-click-follows-link'
Date: Sun, 25 Aug 2019 12:50:59 -0400 [thread overview]
Message-ID: <87sgppmbnw.fsf@gmail.com> (raw)
In-Reply-To: <f7ea59b9-73c3-4a84-b293-9e88a859ee8e@default> (Drew Adams's message of "Sun, 25 Aug 2019 09:22:54 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
>> What happened to the bug # in the Subject line?
>> Please restore it.
>
> Hm. I see it got restored by my reply.
> Why was it missing from Mauro's and Lars's
> mails? E.g.:
I guess Mauro just copied the subject from
https://debbugs.gnu.org/15682#5, which doesn't include the bug number
(because it shows mail as it was originally sent, before the bug number
was assigned).
When someone sends a message without the bug number to a
nnnnn@debbugs.gnu.org address, the bug list mail server adds the bug
number back; but if you're on Cc, then you'll get the message directly
from the sender (i.e., not from the server, and so you won't see the
number added back in. I think you would *also* get the message from the
server with the bug number, but depending on your mail setup, it might
get hidden/deleted as a duplicate).
next prev parent reply other threads:[~2019-08-25 16:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 15:28 bug#15682: 24.3.50; `:link' in `defgroup' does not respect `mouse-1-click-follows-link' Drew Adams
2016-04-27 16:09 ` bug#52: " Lars Ingebrigtsen
2016-04-27 16:24 ` Drew Adams
2016-04-27 16:53 ` bug#52: " Lars Ingebrigtsen
2016-04-27 17:18 ` Drew Adams
2019-08-23 20:41 ` Mauro Aranda
2019-08-25 5:47 ` Lars Ingebrigtsen
2019-08-25 15:07 ` Mauro Aranda
2019-08-25 16:19 ` Drew Adams
2019-08-25 16:22 ` Drew Adams
2019-08-25 16:41 ` Eli Zaretskii
2019-08-25 16:50 ` Noam Postavsky [this message]
2019-08-25 16:58 ` Mauro Aranda
2019-08-27 6:42 ` Lars Ingebrigtsen
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=87sgppmbnw.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=15682@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=maurooaranda@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.