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 16:18:02 +0300	[thread overview]
Message-ID: <83wmv9frp1.fsf@gnu.org> (raw)
In-Reply-To: <87o7glbk6w.fsf@localhost> (message from Ihor Radchenko on Thu, 26 Oct 2023 13:13:43 +0000)

> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: gerd.moellmann@gmail.com, stefankangas@gmail.com, 66743@debbugs.gnu.org
> Date: Thu, 26 Oct 2023 13:13:43 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> If you mean that `dump-emacs-portable' should be made interactive, it is
> >> a much harder task as many emacs_abort (); calls in pdumper.c would need
> >> to be changed to something suitable for interactive sessions.
> >
> > And then we will need to remember to change this fprintf as well?
> 
> Yes. Just as the other printfs in pdumper.c. There are 4 more.
> I do not see a problem.

I do (and there's only one other error-printing fprintf, not 4).
Please use higher-level facilities to show an error, so that we won't
need to find all those places.  (Only if you want to propose this code
for installation in Emacs, of course.)





  reply	other threads:[~2023-10-26 13:18 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
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 [this message]
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=83wmv9frp1.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.