From: Tino Calancha <tino.calancha@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39067@debbugs.gnu.org, madhu@cs.unm.edu,
Tino Calancha <tino.calancha@gmail.com>
Subject: bug#39067: shell-command-dont-erase-buffer strange behaviour
Date: Mon, 20 Jan 2020 14:20:03 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.2.21.2001201416350.5074@localhost.localdomain> (raw)
In-Reply-To: <83ftgayfle.fsf@gnu.org>
On Mon, 20 Jan 2020, Eli Zaretskii wrote:
>> From: Tino Calancha <tino.calancha@gmail.com>
>> Date: Sun, 19 Jan 2020 21:55:35 +0100 (CET)
>> Cc: 39067@debbugs.gnu.org, madhu@cs.unm.edu, tino.calancha@gmail.com
>>
>>> Loading /usr/share/emacs/site-lisp/site-start.d/systemtap-init.el (source)...
>>> ../../../../../../usr/share/emacs/site-lisp/site-start.el: (lambda (dir) ...) quoted with ' rather than with #'
>>> foo
>>> ")
>> It's loading site-lisp stuff; I guess if I pass flag -Q
>> (as in test simple-tests-async-shell-command-30280) then those elips files
>> won't be loaded.
>> I will push that tweak.
>
> Aren't tests run with -batch? That implies -Q as well, so I'm not
> sure I even understand why those files are loaded.
In that case, we have out-ot-date the message at `emacs --help'
It says, --batch => -q
-q == no-init-file
-Q <=> -q && --no-site-file && --no-site-lisp && --no-splash &&
--no-x-resource
next prev parent reply other threads:[~2020-01-20 13:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 5:34 bug#39067: shell-command-dont-erase-buffer strange behaviour Madhu
2020-01-11 9:25 ` Eli Zaretskii
2020-01-11 9:57 ` Michael Albinus
2020-01-13 20:22 ` Tino Calancha
2020-01-14 8:49 ` Michael Albinus
2020-01-19 10:19 ` Tino Calancha
2020-01-19 18:05 ` Glenn Morris
2020-01-19 20:55 ` Tino Calancha
2020-01-20 3:25 ` Eli Zaretskii
2020-01-20 13:20 ` Tino Calancha [this message]
2020-02-01 13:36 ` Michael Albinus
2020-01-20 10:04 ` Mattias Engdegård
2020-01-20 13:21 ` Tino Calancha
2020-01-20 13:30 ` Mattias Engdegård
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=alpine.LSU.2.21.2001201416350.5074@localhost.localdomain \
--to=tino.calancha@gmail.com \
--cc=39067@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=madhu@cs.unm.edu \
/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).