unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: David Reitter <david.reitter@gmail.com>
Cc: emacs- devel <emacs-devel@gnu.org>
Subject: Re: VC shows stderr in target buffer
Date: Sat, 05 Apr 2008 10:31:46 -0400	[thread overview]
Message-ID: <jwv7ifc1ilq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <803EDF5A-B38E-491A-B2B9-49822C0A5E53@gmail.com> (David Reitter's message of "Sat, 5 Apr 2008 08:27:30 +0100")

>> It seems better in the *vc-diff* buffer where the user will be sure to
>> see it than in the echo area where it'll be overwritten soon after
>> (especially for multi-line messages).

> When you do C-x C-s and the file can't be written, do you insert an error
> message into the buffer?
> When you handle an exception signalled anywhere, do you insert an error
> message into the buffer or do you show it in the echo area?

> My request was about consistency.

I do not think consistency in this regard is important.

> It's probably important to know I would
> do things like C-x C-v = in order to do something else with the  resulting
> diff than to just read the output.  Thus, warnings (and they  are just
> warnings!) are annoying when they're shown in the buffer.

The content of the diff output already often includes various extra
lines that can be more or less relevant depending on the tool used.
Some of those lines will be on stderr, others on stdout.  Tools that use
patches know to ignore leading and trailing garbage, so I really don't
think it's that important.


        Stefan




      reply	other threads:[~2008-04-05 14:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 11:42 VC shows stderr in target buffer David Reitter
2008-04-04 14:09 ` Stefan Monnier
2008-04-05  7:27   ` David Reitter
2008-04-05 14:31     ` Stefan Monnier [this message]

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=jwv7ifc1ilq.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=david.reitter@gmail.com \
    --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 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).