bug#42400: closed (26.3; doc of `kill-emacs' optional ARG)

[GNU bug Tracking System]

Your message dated Fri, 17 Jul 2020 17:55:17 +0300
with message-id <83pn8ui42y.fsf@gnu.org>
and subject line Re: bug#42400: 26.3; doc of `kill-emacs' optional ARG
has caused the debbugs.gnu.org bug report #42400,
regarding 26.3; doc of `kill-emacs' optional ARG
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
42400: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=42400
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> 26.3; doc of `kill-emacs' optional ARG
>
>
>
>
> Date: 
>
> Thu, 16 Jul 2020 08:25:55 -0700 (PDT)
>
>
>
>
> Both the Emacs and Elisp manuals describe the behavior of ARG as an
> integer or a string.  But what about anything else?
>
> In `startup.el', `edt-mapper.el', and `tpu-edt.el', for example, we find
> (kill-emacs t).  How is someone to understand this code?
>
> In GNU Emacs 26.3 (build 1, x86_64-w64-mingw32)
>  of 2019-08-29
> Repository revision: 96dd0196c28bc36779584e47fffcca433c9309cd
> Windowing system distributor `Microsoft Corp.', version 10.0.18362
> Configured using:
>  `configure --without-dbus --host=x86_64-w64-mingw32
>  --without-compress-install 'CFLAGS=-O2 -static -g3''
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#42400: 26.3; doc of `kill-emacs' optional ARG
>
>
>
>
> Date: 
>
> Fri, 17 Jul 2020 17:55:17 +0300
>
>
>
>
> > From: Robert Pluim <rpluim@gmail.com>
> > Date: Thu, 16 Jul 2020 19:34:40 +0200
> > Cc: 42400@debbugs.gnu.org
> > 
> > >>>>> On Thu, 16 Jul 2020 08:25:55 -0700 (PDT), Drew Adams 
> > >>>>> <drew.adams@oracle.com> said:
> > 
> >     Drew> Both the Emacs and Elisp manuals describe the behavior of ARG as an
> >     Drew> integer or a string.  But what about anything else?
> > 
> >     Drew> In `startup.el', `edt-mapper.el', and `tpu-edt.el', for example, we 
> > find
> >     Drew> (kill-emacs t).  How is someone to understand this code?
> > 
> > Itʼs equivalent to exit'ing with EXIT_SUCCESS, without having to worry
> > about the value of '0' on your platform :-) Not sure how weʼd express
> > that in the docstring.
>
> I've documented it now, thanks.
>
>
> --- End Message ---