all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: gerd.moellmann@gmail.com, 66743@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#66743: 30.0.50; Crash when dumping reftex
Date: Thu, 26 Oct 2023 15:08:56 +0300	[thread overview]
Message-ID: <835y2th9gn.fsf@gnu.org> (raw)
In-Reply-To: <871qdhd2dh.fsf@localhost> (message from Ihor Radchenko on Thu, 26 Oct 2023 11:55:38 +0000)

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: Stefan Kangas <stefankangas@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
>  66743@debbugs.gnu.org
> Date: Thu, 26 Oct 2023 11:55:38 +0000
> 
> >> May you please point me to a way to output warning to stderr from inside
> >> pdumper code?
> >
> > fprintf (stderr, ...) I'd say.
> 
> That's more obvious than I thought :)
> 
> See the attached patch.

If you are suggesting this for upstream, then it's not optimal, at
least in interactive session: the stderr stream is usually redirected
to some bottomless OS pit where no one could see it.





  reply	other threads:[~2023-10-26 12:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  9:46 bug#66743: 30.0.50; Crash when dumping reftex Ihor Radchenko
2023-10-25 12:46 ` Eli Zaretskii
2023-10-25 12:58   ` Ihor Radchenko
2023-10-25 14:44     ` Stefan Kangas
2023-10-26  9:31       ` Ihor Radchenko
2023-10-26 10:01         ` Gerd Möllmann
2023-10-26 11:55           ` Ihor Radchenko
2023-10-26 12:08             ` Eli Zaretskii [this message]
2023-10-26 12:14               ` Ihor Radchenko
2023-10-26 13:04                 ` Eli Zaretskii
2023-10-26 13:13                   ` Ihor Radchenko
2023-10-26 13:18                     ` Eli Zaretskii
2023-10-26 13:27                       ` Ihor Radchenko
2023-10-26 13:28                         ` Eli Zaretskii
2023-10-26 13:48                           ` Ihor Radchenko
2023-10-26 15:49                             ` Eli Zaretskii
2023-10-27  9:08                               ` Ihor Radchenko
2023-10-27 10:38                                 ` Eli Zaretskii
2023-10-27 10:55                                   ` Ihor Radchenko
2023-10-27 11:01                                     ` Eli Zaretskii
2023-10-27 11:09                                       ` Ihor Radchenko
2023-10-27 12:36                                         ` Eli Zaretskii
2023-10-27 12:45                                           ` Ihor Radchenko
2023-10-27 12:53                                             ` Eli Zaretskii
2023-10-25 16:15     ` Gerd Möllmann
2023-10-25 16:21       ` Eli Zaretskii
2023-10-25 16:37         ` Gerd Möllmann
2023-10-26  7:03           ` Gerd Möllmann
2023-10-26  7:35             ` Eli Zaretskii
2023-10-26  8:04               ` Gerd Möllmann
2023-10-26  9:38             ` Ihor Radchenko
2023-10-26  9:44               ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=835y2th9gn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66743@debbugs.gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=stefankangas@gmail.com \
    --cc=yantar92@posteo.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.