From: Philip Kaludercic <philipk@posteo.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Ken Raeburn <raeburn@redhat.com>, 54718@debbugs.gnu.org
Subject: bug#54718: 28.0.92; rcirc channel-vs-log buffer confusion
Date: Fri, 04 Nov 2022 22:53:22 +0000 [thread overview]
Message-ID: <87wn8ajpr1.fsf@posteo.net> (raw)
In-Reply-To: <87bkqpnq5z.fsf@posteo.net> (Philip Kaludercic's message of "Thu, 06 Oct 2022 11:32:24 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>
>>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>>
>>>>> Could you try applying this patch to see if this improves the situation,
>>>>> or if some other issues arise:
>>>>
>>>> Ken, did you try Philip's patch?
>>>
>>> This was a month ago. Philip, I think your patch looks "obviously
>>> correct", so feel free to push it.
>>
>> It appears the patch was not correct, as the function was used in a few
>> other spots. One unintended side-effect was that logging creates a new
>> buffer for apparently every *received message*.
>
> Another idea might be to modify `rcirc-generate-log-filename' to add a
> ".log" to the end of each filename.
This approach was implemented with db69681759991d5403552682706accd6218b731f.
prev parent reply other threads:[~2022-11-04 22:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 22:34 bug#54718: 28.0.92; rcirc channel-vs-log buffer confusion Ken Raeburn
2022-04-05 10:03 ` Philip Kaludercic
2022-09-06 11:21 ` Lars Ingebrigtsen
2022-10-04 11:46 ` Lars Ingebrigtsen
2022-10-05 17:31 ` Philip Kaludercic
2022-10-06 11:32 ` Philip Kaludercic
2022-10-14 18:13 ` Philip Kaludercic
2022-11-04 22:53 ` Philip Kaludercic [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=87wn8ajpr1.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=54718@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=raeburn@redhat.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 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).