From: Joseph Mingrone <jrm@ftfl.ca>
To: Nicolas Petton <nicolas@petton.fr>
Cc: 28464@debbugs.gnu.org
Subject: bug#28464: 25.3; regression in erc track notifications after upgrading to 25.3.1
Date: Sat, 16 Sep 2017 13:22:27 -0300 [thread overview]
Message-ID: <86r2v6k3zw.fsf@phe.ftfl.ca> (raw)
In-Reply-To: <86y3phawka.fsf@phe.ftfl.ca>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
Nicolas Petton <nicolas@petton.fr> writes:
> Joseph Mingrone <jrm@ftfl.ca> writes:
>>> It is difficult to see how this could be, because there were literally
>>> zero changes between 25.2 and 25.3 except for those related to
>>> the enriched issue.
>> Agreed. I did read the NEWS for 25.3 before submitting and saw that was
>> the only changed, but I repeated the recipe a few times and I see the
>> same behaviour?
> Could it be the packaging of Emacs 25.3 on FreeBSD?
> Cheers,
> Nico
I think I have figured out the problem. I have the following
customized.
'(erc-track-faces-priority-list '(erc-error-face erc-current-nick-face erc-keyword-face erc-nick-msg-face erc-direct-msg-face erc-dangerous-host-face erc-notice-face erc-prompt-face))
'(erc-track-priority-faces-only 'all)
When I tested with emacs-25.3 -Q, I think I missed the notification in
the mode line, because it was only the string "[t]" in a location in the
mode line I was not used to because of customizations I have been using
for years.
Sorry for the noise,
Joseph
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next prev parent reply other threads:[~2017-09-16 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 19:51 bug#28464: 25.3; regression in erc track notifications after upgrading to 25.3.1 Joseph Mingrone
2017-09-14 20:45 ` Glenn Morris
2017-09-14 20:47 ` Joseph Mingrone
2017-09-16 8:00 ` Nicolas Petton
2017-09-16 16:22 ` Joseph Mingrone [this message]
2017-09-16 18:10 ` Nicolas Petton
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=86r2v6k3zw.fsf@phe.ftfl.ca \
--to=jrm@ftfl.ca \
--cc=28464@debbugs.gnu.org \
--cc=nicolas@petton.fr \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).