From: MON KEY <monkey@sandpframing.com>
To: 7001@debbugs.gnu.org
Subject: bug#7001: should `byte-compile-from-buffer' evaluate `binary-overwrite-mode' explicitly?
Date: Wed, 8 Sep 2010 17:01:00 -0400 [thread overview]
Message-ID: <AANLkTim92KCxSRkRi0nzjm6=uDJRC+sh_vFdAjC0cUFS@mail.gmail.com> (raw)
emacs-lisp/bytecomp.el
`byte-compile-from-buffer'
Has this form:
(setq overwrite-mode 'overwrite-mode-binary)
Should this evalatate `binary-overwrite-mode' from simple.el instead?
Or, is there a boostrapping issue which prevents this?
--
/s_P\
next reply other threads:[~2010-09-08 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 21:01 MON KEY [this message]
2010-09-09 17:02 ` bug#7001: should `byte-compile-from-buffer' evaluate `binary-overwrite-mode' explicitly? Stefan Monnier
2010-10-02 23:11 ` Chong Yidong
2010-10-03 4:04 ` Eli Zaretskii
2010-10-03 4:32 ` Chong Yidong
2010-10-03 5:43 ` 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
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='AANLkTim92KCxSRkRi0nzjm6=uDJRC+sh_vFdAjC0cUFS@mail.gmail.com' \
--to=monkey@sandpframing.com \
--cc=7001@debbugs.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 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).