[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Why the odd interactive form in byte-compile-file?
From: |
Thien-Thi Nguyen |
Subject: |
Re: Why the odd interactive form in byte-compile-file? |
Date: |
Wed, 15 Jan 2014 05:41:34 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
() Daniel Colascione <address@hidden>
() Tue, 14 Jan 2014 16:00:02 -0800
> Is there some deeper reason we're not using code that looks like this?
>
> (interactive
> (list (read-file-name (if current-prefix-arg
> "Byte compile and load file: "
> "Byte compile file: "))
> current-prefix-arg))
The current ‘interactive’ form supplies DIR and DEFAULT-FILENAME args to
‘read-file-name’ if the current buffer is Emacs Lisp (ish). Those are
available to the user via ‘M-n’.
The form you propose doesn't do that.
Ping? I'd like to treat this issue as a bugfix and change the
interactive form to my proposal for 24.4.
Why do you want to treat this functionality as an "issue"?
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
pgp8OrvnoaqFz.pgp
Description: PGP signature
- Why the odd interactive form in byte-compile-file?, Daniel Colascione, 2014/01/12
- Re: Why the odd interactive form in byte-compile-file?, Daniel Colascione, 2014/01/14
- Re: Why the odd interactive form in byte-compile-file?,
Thien-Thi Nguyen <=
- Re: Why the odd interactive form in byte-compile-file?, Daniel Colascione, 2014/01/14
- Re: Why the odd interactive form in byte-compile-file?, Stefan Monnier, 2014/01/15
- Re: Why the odd interactive form in byte-compile-file?, Daniel Colascione, 2014/01/15
- Re: Why the odd interactive form in byte-compile-file?, Stefan Monnier, 2014/01/15
- Re: Why the odd interactive form in byte-compile-file?, Daniel Colascione, 2014/01/15