From: Philip Kaludercic <philipk@posteo.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 66276@debbugs.gnu.org, Thuna <thuna.cing@gmail.com>
Subject: bug#66276: Use a seperate time format in rcirc logfiles
Date: Thu, 11 Jan 2024 07:57:44 +0000 [thread overview]
Message-ID: <87ttnkpaiv.fsf@posteo.net> (raw)
In-Reply-To: <CADwFkmkS8xX_B5TGhRMdiW_WrWfdYMXcCenb_48mdvkP41rH_A@mail.gmail.com> (Stefan Kangas's message of "Wed, 10 Jan 2024 13:05:01 -0800")
Stefan Kangas <stefankangas@gmail.com> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Stefan Kangas <stefankangas@gmail.com> writes:
>>
>>> Thuna <thuna.cing@gmail.com> writes:
>>>
>>>> I believe that it is best to have two different time formats for
>>>> logfiles and normal rcirc buffers. Logfiles need additional precision,
>>>> specifically the date and maybe the time zone, while normal buffers do
>>>> not.
>>>>
>>>> The patch adds a single variable, rcirc-log-time-format, to control the
>>>> time format in logfiles, which is done by replacing the usage of
>>>> rcirc-time-format in rcirc-log with it.
>>>>
>>>> I figured "%F %T %z " was a sensible default, although feel free to
>>>> change it as you wish.
>>>
>>> Philip, could you please take a look at this patch?
>>
>> We have already merged a similar functionality with bug#67597.
>
> So what should we do with this one? Close?
We can close it. Does it also have to be marked as duplicate?
next prev parent reply other threads:[~2024-01-11 7:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 8:44 bug#66276: Use a seperate time format in rcirc logfiles Thuna
2024-01-10 18:11 ` Stefan Kangas
2024-01-10 19:06 ` Philip Kaludercic
2024-01-10 21:05 ` Stefan Kangas
2024-01-11 7:57 ` Philip Kaludercic [this message]
2024-01-11 20:23 ` Stefan Kangas
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=87ttnkpaiv.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=66276@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
--cc=thuna.cing@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 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).