all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Why the odd interactive form in byte-compile-file?
Date: Wed, 15 Jan 2014 05:41:34 +0100	[thread overview]
Message-ID: <871u09kgap.fsf@zigzag.favinet> (raw)
In-Reply-To: <52D5CF82.4030405@dancol.org> (Daniel Colascione's message of "Tue, 14 Jan 2014 16:00:02 -0800")

[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]

() Daniel Colascione <dancol@dancol.org>
() 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

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2014-01-15  4:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13  4:17 Why the odd interactive form in byte-compile-file? Daniel Colascione
2014-01-15  0:00 ` Daniel Colascione
2014-01-15  4:41   ` Thien-Thi Nguyen [this message]
2014-01-15  4:43     ` Daniel Colascione
2014-01-15 14:46       ` Stefan Monnier
2014-01-15 19:10         ` Daniel Colascione
2014-01-15 23:47           ` Stefan Monnier
2014-01-15 23:49             ` Daniel Colascione

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=871u09kgap.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=dancol@dancol.org \
    --cc=emacs-devel@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.