From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alex Branham <alex.branham@gmail.com>
Cc: "William G. Gardella" <wgg2@member.fsf.org>,
22700@debbugs.gnu.org, Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#22700: 25.0.91; `erc-echo-timestamps' no longer echoes timestamp for each line
Date: Tue, 13 Aug 2019 15:11:29 -0700 [thread overview]
Message-ID: <877e7gvhpq.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87imr0u7dc.fsf@gmail.com> (Alex Branham's message of "Tue, 13 Aug 2019 15:40:15 -0500")
Alex Branham <alex.branham@gmail.com> writes:
> We can fix this in ERC by not applying the text property to the whole
> message. I suggest not applying it to the last character. Now whenever
> you move point between messages, the timestamp gets echoed. Unless point
> winds up at the very end of the line, which is possible if you're moving
> from the end of a long message to a short message. Clearly not ideal,
> but better than the current situation.
This fix doesn't sound ideal -- if you do it this way, then it'll work
sometimes, and not other times, which sounds perhaps even more annoying.
There must be a different way to get it to work reliably.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-13 22:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-16 16:07 bug#22700: 25.0.91; `erc-echo-timestamps' no longer echoes timestamp for each line William G. Gardella
2018-04-14 18:49 ` Lars Ingebrigtsen
2018-04-15 0:06 ` Stefan Monnier
2018-04-15 13:01 ` Lars Ingebrigtsen
2019-08-13 20:40 ` Alex Branham
2019-08-13 22:11 ` Lars Ingebrigtsen [this message]
2019-08-13 22:13 ` Noam Postavsky
2019-08-14 0:33 ` Alex Branham
2019-08-14 2:40 ` Eli Zaretskii
2019-08-14 13:49 ` Alex Branham
2019-08-14 14:39 ` Eli Zaretskii
2019-08-14 14:56 ` Noam Postavsky
2019-08-14 15:16 ` Alex Branham
2019-08-14 22:50 ` Stefan Monnier
2019-08-15 14:27 ` Alex Branham
2019-08-15 23:41 ` Lars Ingebrigtsen
2019-08-16 13:25 ` Alex Branham
2019-08-19 9:46 ` Stefan Monnier
2019-08-27 15:08 ` Alex Branham
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=877e7gvhpq.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=22700@debbugs.gnu.org \
--cc=alex.branham@gmail.com \
--cc=monnier@IRO.UMontreal.CA \
--cc=wgg2@member.fsf.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.
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).