all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sebastian Wiesner <lunaryorn@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tromey@redhat.com, Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel@gnu.org
Subject: Re: Inhibit "Wrote foo" from write-region
Date: Thu, 23 Jan 2014 18:37:09 +0100	[thread overview]
Message-ID: <CALf2awQZNG-xwBF0YX4c6vWjN-7P_GN7ih8segByZAvb1P4o1w@mail.gmail.com> (raw)
In-Reply-To: <83siseekd4.fsf@gnu.org>

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

Am 23.01.2014 17:24 schrieb "Eli Zaretskii" <eliz@gnu.org>:
>
> > From: Stefan Monnier <monnier@iro.umontreal.ca>
> > Date: Thu, 23 Jan 2014 08:50:20 -0500
> > Cc: Tom Tromey <tromey@redhat.com>, Emacs-Devel devel <
emacs-devel@gnu.org>
> >
> > > I presume, there is little chance to change this behaviour for
> > > noninteractive use?
> >
> > Definitely not for 24.4.
> >
> > Afterwards, someone could try and look at the issue in more detail, but
> > it's risky, since it's a fairly low-level primitive called from many
> > different packages.  We'd have to go and check how all these calls would
> > be affected.
>
> I, for one, am accustomed to see these messages while Emacs is being
> built: in a highly parallel build that is sometimes the only practical
> way of knowing whether some part of the build succeeded or not.

How do you do that?!  Do you really read *all* messages being printed while
building?!

I presume that just testing for the existence of interesting files (e.g.
good old "find") isn't an option?

> So, if 'write-region' stops outputting these messages in
> non-interactive uses, there should be a way to get the current
> behavior back.

Isn't that the job of the build system rather?

[-- Attachment #2: Type: text/html, Size: 1742 bytes --]

  reply	other threads:[~2014-01-23 17:37 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 12:32 Inhibit "Wrote foo" from write-region Sebastian Wiesner
2014-01-21 12:38 ` Sebastian Wiesner
2014-01-21 15:57   ` Eli Zaretskii
2014-01-21 16:31     ` Sebastian Wiesner
2014-01-21 16:47       ` Eli Zaretskii
2014-01-22 12:35         ` Sebastian Wiesner
2014-01-22 15:11           ` Stefan Monnier
2014-01-22 17:00             ` Sebastian Wiesner
     [not found]       ` <<834n4xgu3z.fsf@gnu.org>
2014-01-21 17:59         ` Drew Adams
2014-01-21 18:26           ` Eli Zaretskii
2014-01-22  8:05           ` Juri Linkov
2014-01-21 16:42 ` Tom Tromey
2014-01-22 12:37   ` Sebastian Wiesner
2014-01-22 15:09     ` Stefan Monnier
2014-01-22 17:08       ` Sebastian Wiesner
2014-01-22 19:20         ` Stefan Monnier
2014-01-23  9:35           ` Sebastian Wiesner
2014-01-23 13:50             ` Stefan Monnier
2014-01-23 14:24               ` Sebastian Wiesner
2014-01-23 15:18                 ` Stefan Monnier
2014-01-23 16:15                   ` Sebastian Wiesner
2014-01-23 16:29                 ` Eli Zaretskii
2014-01-23 17:31                   ` Sebastian Wiesner
2014-01-23 18:04                     ` Eli Zaretskii
2014-01-24 20:14                       ` Sebastian Wiesner
2014-01-23 16:25               ` Eli Zaretskii
2014-01-23 17:37                 ` Sebastian Wiesner [this message]
2014-01-23 18:07                   ` Eli Zaretskii
2014-01-24 13:34                     ` Johan Andersson
2014-01-24 13:48                       ` Stefan Monnier
2014-01-24 14:25                       ` Eli Zaretskii
     [not found] <"<m2r481o6rh.fsf"@lunaryorn-air.fritz.box>

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=CALf2awQZNG-xwBF0YX4c6vWjN-7P_GN7ih8segByZAvb1P4o1w@mail.gmail.com \
    --to=lunaryorn@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=tromey@redhat.com \
    /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.