unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Hadron <hadronquark@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Bug when compiling elc code?
Date: Wed, 08 Aug 2007 12:29:56 +0200	[thread overview]
Message-ID: <vb7io6jp3v.fsf@googlemail.com> (raw)


I recently added this bit of lisp to my .emacs in order to automatically
byte compile any el files I saved

,----
| (add-hook 'emacs-lisp-mode-hook
|           '(lambda ()
|              (make-local-hook 'after-save-hook)
|              (add-hook 'after-save-hook
|                        '(lambda ()
|                           (byte-compile-file buffer-file-name))
|                        nil t)))
`----

I have my gnus specifics such as smtp server names and passwords in a
"personal.el" file which is obviously not readable by anyone but my own
login and root.

Unfortunately byte-compile-file produced the following:

-rw------- 1 hadron hadron 4961 2007-08-08 12:19 personal.el
-rw-r--r-- 1 hadron hadron 3795 2007-08-08 12:19 personal.elc

In other words a readable by anyone elc file.

I just checked - I can load up the elc file and see all my passwords.

Bug or feature? Seems like a nasty bug to me.

Which leads on to the next question, is there something I can put into a
file to stop it compiling into an elc using this hook?

             reply	other threads:[~2007-08-08 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 10:29 Hadron [this message]
2007-08-08 11:37 ` Bug when compiling elc code? Johan Bockgård
2007-08-08 12:17 ` Sven Joachim
     [not found]   ` <d3abt22nwk.fsf@googlemail.com>
2007-08-08 16:45     ` Sven Joachim
     [not found]     ` <mailman.4536.1186591345.32220.help-gnu-emacs@gnu.org>
2007-08-08 17:21       ` Hadron
     [not found] ` <mailman.4528.1186577289.32220.help-gnu-emacs@gnu.org>
2007-08-08 13:18   ` Johan Bockgård
2007-08-08 14:59     ` Sven Joachim
     [not found]     ` <mailman.4534.1186585008.32220.help-gnu-emacs@gnu.org>
2007-08-08 16:09       ` weber
2007-08-08 16:57         ` Sven Joachim

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=vb7io6jp3v.fsf@googlemail.com \
    --to=hadronquark@googlemail.com \
    --cc=help-gnu-emacs@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.
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).