unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-emacs-windows@gnu.org, help-gnu-emacs@gnu.org
Subject: Re: Emacs gdb interface
Date: Wed, 21 Mar 2012 21:09:52 +0100	[thread overview]
Message-ID: <CAH8Pv0g3Omh1M4U7Y--umWjmA0sanfF031j5f8Y9aEcmtdx4tg@mail.gmail.com> (raw)
In-Reply-To: <83ehsl23fa.fsf@gnu.org>

> If you add the newline, the output appears at the end, but not in the
> input/output buffer.
>
> If there's no newline, I wouldn't expect the output to appear at all,
> in such a short program, since standard output redirected to pipes is
> fully-buffered on Windows, not line-buffered as on Posix systems.

Ok, I understand that Emacs can't show the output until it is flushed,
but when it is, as (for example) in this case:

-------- main.c -------------
#include <stdio.h>

int main(void)
{
   printf("hello, world!\n");
   fflush(stdout);
   return 0;
}
-----------------------------

The output should not be shown in the *gud* buffer (as happens now),
but in the *input/output* one, no?  If not, what's that *input/output*
buffer for?

-- 
Dani Moncayo



  reply	other threads:[~2012-03-21 20:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 20:21 Emacs gdb interface Dani Moncayo
2012-03-21  2:58 ` Matt McClure
2012-03-21  7:33   ` Dani Moncayo
2012-03-21  7:50     ` Bob Proulx
2012-03-21  8:39       ` Dani Moncayo
2012-03-21  8:54         ` Alberto Luaces
2012-03-21  9:28         ` Bob Proulx
2012-03-21 10:26           ` Dani Moncayo
2012-03-21  8:28     ` Peter Dyballa
2012-03-21  8:43       ` Dani Moncayo
2012-03-21 18:51     ` Eli Zaretskii
2012-03-21 20:09       ` Dani Moncayo [this message]
2012-03-21 21:30         ` Eli Zaretskii
2012-03-21 10:53 ` Sergei Organov
2012-03-21 12:11   ` Dani Moncayo
2012-03-21 13:32     ` [h-e-w] " Doug Lewan

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=CAH8Pv0g3Omh1M4U7Y--umWjmA0sanfF031j5f8Y9aEcmtdx4tg@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=eliz@gnu.org \
    --cc=help-emacs-windows@gnu.org \
    --cc=help-gnu-emacs@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.
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).