unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 20968@debbugs.gnu.org
Subject: bug#20968: 25.0.50; Be able to specify the output directory for `byte-compile-file'
Date: Thu, 2 Jul 2015 14:05:08 -0700 (PDT)	[thread overview]
Message-ID: <23829743-922e-4304-8ab3-b762b8193860@default> (raw)

Enhancement request.

1. Be able to specify the output directory for *.elc files to
`byte-compile-file'.  See this emacs.SE question:
http://emacs.stackexchange.com/q/13596/105.

This could be done by adding an optional arg, but to let users take
advantage of it interactively the current prefix-arg behavior would need
to be split.  E.g., numeric value <= 0 could mean prompt for the output
dir; numeric value >= 0 could mean also load the byte-compiled file.

That would not hurt any existing code that passed a non-nil and
non-numeric second arg.

Another possibility would be to define another command for this, e.g.,
`byte-compile-file-to-directory'.

2. Let commands such as `dired-do-byte-compile' (hence function
`dired-byte-compile') support this also, e.g. by a particular prefix-arg
value that does not conflict (much) with the current prefix-arg
behavior.  For example, plain `C-u' - a user can still use `M-4' to get
the current `C-u' behavior.

3. In addition, maybe provide a way (e.g. option) for users to specify a
default value for the directory.  #1 and #2 would provide this as the
default when you are asked to specify the output dir.
        

In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2015-05-29 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/mingw32 --host=i686-pc-mingw32
 --enable-checking=yes,glyphs'





             reply	other threads:[~2015-07-02 21:05 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 21:05 Drew Adams [this message]
2015-07-02 22:12 ` bug#20968: 25.0.50; Be able to specify the output directory for `byte-compile-file' Glenn Morris
2015-07-02 23:51   ` Drew Adams
2015-07-03 12:22     ` Eli Zaretskii
2015-07-03 15:10       ` Stefan Monnier
2015-07-03 17:12         ` Glenn Morris
2015-07-03 17:27           ` Glenn Morris
2015-07-03 17:49         ` Eli Zaretskii
2015-07-03 22:48           ` Artur Malabarba
2015-07-04  8:24             ` Eli Zaretskii
2015-07-04 10:38               ` Alexis
2015-07-04 11:55                 ` Eli Zaretskii
2015-07-04 11:10               ` Artur Malabarba
2015-07-04 11:56                 ` Eli Zaretskii
2015-07-04 18:46                   ` Stefan Monnier
2015-07-04 18:55                     ` Eli Zaretskii
2015-07-04 19:26                       ` Stefan Monnier
2015-07-04 19:31                         ` Eli Zaretskii
2015-07-05 11:54               ` Dmitry Gutov
2015-07-05 14:35                 ` Eli Zaretskii
2015-07-05 14:54                   ` Dmitry Gutov
2015-07-05 15:18                     ` Eli Zaretskii
2015-07-05 15:54                       ` Artur Malabarba
2015-07-05 21:56               ` Richard Stallman
2016-04-30 20:07     ` Lars Ingebrigtsen
     [not found] <<23829743-922e-4304-8ab3-b762b8193860@default>
     [not found] ` <<74y4iytdjg.fsf@fencepost.gnu.org>
     [not found]   ` <<e68f1dc9-9e8f-4f54-af8f-a5bb23160576@default>
     [not found]     ` <<83pp49zb03.fsf@gnu.org>
2015-07-03 14:55       ` Drew Adams
2015-07-04  8:40         ` Eli Zaretskii
2015-07-04 18:48           ` Stefan Monnier
     [not found]       ` <<d5d5b826-847c-41be-9392-25446b6e37fa@default>
     [not found]         ` <<83pp48xqm8.fsf@gnu.org>
2015-07-04 14:41           ` Drew Adams
2015-07-04 16:42             ` Eli Zaretskii
     [not found] <<dc02c2ca-d069-4559-820d-fbd6dfaed9d3@default>
     [not found] ` <<83615zyiuq.fsf@gnu.org>
2015-07-04 18:20   ` Drew Adams
2015-07-04 18:25     ` Eli Zaretskii
     [not found]   ` <<f766b63c-edb1-4f11-9f14-bfcd95d8adcd@default>
     [not found]     ` <<831tgnye3x.fsf@gnu.org>
2015-07-04 18:54       ` Drew Adams

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=23829743-922e-4304-8ab3-b762b8193860@default \
    --to=drew.adams@oracle.com \
    --cc=20968@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).