From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, 21602@debbugs.gnu.org
Subject: bug#21602: 25.0.50; coding system seg fault
Date: Sat, 03 Oct 2015 14:25:23 +0200 [thread overview]
Message-ID: <87vbao9m18.fsf@igel.home> (raw)
In-Reply-To: <837fn4407c.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 03 Oct 2015 15:15:51 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Why would it be a bad idea to disallow setting of
> buffer-file-coding-system to an invalid value, as a subtle side effect
> of calling this function? By the time that later check is made, the
> damage is already done.
>
> IOW, why is it bad to be more defensive than is strictly necessary?
buffer-file-coding-system is a user-settable variable, so the check is
useless.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2015-10-03 12:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 2:32 bug#21602: 25.0.50; coding system seg fault Richard Stallman
2015-10-02 7:04 ` Eli Zaretskii
2015-10-03 1:37 ` Richard Stallman
2015-10-03 10:48 ` Eli Zaretskii
2015-10-03 11:30 ` Andreas Schwab
2015-10-03 11:51 ` Eli Zaretskii
2015-10-03 12:14 ` Andreas Schwab
2015-10-03 12:42 ` Eli Zaretskii
2015-10-03 12:50 ` Andreas Schwab
2015-10-03 13:15 ` Eli Zaretskii
2015-10-03 14:19 ` Eli Zaretskii
2015-10-03 15:00 ` Andreas Schwab
2015-10-03 15:26 ` Eli Zaretskii
2015-10-03 16:09 ` Andreas Schwab
2015-10-03 16:11 ` Eli Zaretskii
2015-10-03 17:22 ` Zack Piper
2015-10-03 18:16 ` Andreas Schwab
2015-10-03 12:07 ` Andreas Schwab
2015-10-03 12:15 ` Eli Zaretskii
2015-10-03 12:25 ` Andreas Schwab [this message]
2015-10-03 12:36 ` Eli Zaretskii
2015-10-03 12:48 ` Andreas Schwab
2015-10-03 13:14 ` Eli Zaretskii
2015-10-03 1:37 ` Richard Stallman
2015-10-03 10:49 ` 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=87vbao9m18.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=21602@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rms@gnu.org \
/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.