unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: "Matúš Goljer" <matus.goljer@gmail.com>
Cc: Thomas Koch <thomas@koch.ro>,  emacs-devel@gnu.org
Subject: Re: New (only?) extensible logging package for Emacs
Date: Wed, 15 Mar 2023 02:56:30 +0200	[thread overview]
Message-ID: <87r0tqj0ht.fsf@thaodan.de> (raw)
In-Reply-To: <87zg8hpytt.fsf@gmail.com> ("Matúš Goljer"'s message of "Sun, 12 Mar 2023 20:13:50 +0100")

Matúš Goljer <matus.goljer@gmail.com> writes:

>> Such a logging library might also be helpful in interactive use when
>> debugging problems that cause Emacs to freeze or (god forbid) to
>> segfault. In that case I could still find log messages outside of
>> Emacs.
>
> This is a good point and in fact I just used it in this way today.  I'm
> debugging some async code (via emacs-async) package and as you might
> imagine, it's rather complicated.  Logging to files made it much
> simpler, and I only had to add one line (the file appender)
>
>> In my case I'd love to feed logs into journald.
>
> What unit would it log to though?  Or can journald also ingest logs for
> non-unit source?  Since I imagine not many people run Emacs as a systemd
> service.  I'm not very knowledgable about this stuff :grin:

Slightly offtopic but  Emacs includes a systemd unit and can can notify
systemd when startup finishes or shutdown begins.

When logging into journal deciphering from which package by adding meta
data to the logs could be very handy.



  parent reply	other threads:[~2023-03-15  0:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 13:30 New (only?) extensible logging package for Emacs Matúš Goljer
2023-03-11 15:27 ` Thomas Koch
2023-03-12 19:13   ` Matúš Goljer
2023-03-13  4:35     ` Ruijie Yu via Emacs development discussions.
2023-03-13 13:23       ` Matúš Goljer
2023-03-13 14:43         ` Thomas Koch
2023-03-13 17:25           ` Matúš Goljer
2023-03-15  0:56     ` Björn Bidar [this message]
2023-03-12 12:01 ` Ihor Radchenko
2023-03-13 13:28   ` Matúš Goljer
2023-03-13 14:39     ` Eli Zaretskii
2023-03-13 15:59       ` Matúš Goljer
2023-03-13 16:47         ` Eli Zaretskii
2023-03-13 17:27           ` Matúš Goljer
2023-03-13 17:28           ` [External] : " Drew Adams

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=87r0tqj0ht.fsf@thaodan.de \
    --to=bjorn.bidar@thaodan.de \
    --cc=emacs-devel@gnu.org \
    --cc=matus.goljer@gmail.com \
    --cc=thomas@koch.ro \
    /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).