all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Barry OReilly <gundaetiapo@gmail.com>
Cc: theonewiththeevillook@yahoo.fr, 17291@debbugs.gnu.org
Subject: bug#17291: 24.3.90; Doing "make" in elpa branch uses the user's ~/.emacs.d
Date: Sat, 19 Apr 2014 13:24:00 -0400	[thread overview]
Message-ID: <jwvd2gdme6y.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <CAFM41H16Bzg+um1e+bt5uujAN2cuHdRYSihQLyDPCS+UNCvF0g@mail.gmail.com> (Barry OReilly's message of "Fri, 18 Apr 2014 16:14:48 -0400")

>> EMACS -f batch-byte-compile packages/ack/ack.el
>> The reason is that the actual command line (which is unfortunately not
>> shown on the screen)
> I voiced a similar concern before, but Stefan didn't want to change
> the output. Showing some but not all flags and arguments gives the
> false impression of showing the precise Emacs invocation. I think it
> ought to show the full invocation.

I'm indeed opposed to showing the whole command because it's too long,
making the output even harder to read (in the "normal" case where
you're looking for byte-compiler errors and warnings).

But it could be improved in 2 ways:
- change the current output so it give less the illusion of being
  a real command.
- provide some option to show the real command.

As for Nicolas's suggestion to "disable" ~/.emacs.d/elpa, I think it
makes sense, since we already use --batch which disables ~/.emacs.
So feel free to install his patch.


        Stefan





  reply	other threads:[~2014-04-19 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18 14:53 bug#17291: 24.3.90; Doing "make" in elpa branch uses the user's ~/.emacs.d Nicolas Richard
2014-04-18 20:14 ` Barry OReilly
2014-04-19 17:24   ` Stefan Monnier [this message]
2014-04-24 21:24     ` Barry OReilly

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=jwvd2gdme6y.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=17291@debbugs.gnu.org \
    --cc=gundaetiapo@gmail.com \
    --cc=theonewiththeevillook@yahoo.fr \
    /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.