unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Victor Kirk <vkirk@technology.serco.com>
Cc: help-gnu-emacs@gnu.org
Subject: RE: Re[2]: get stdout/stderr while running a program
Date: Fri, 29 Nov 2002 10:34:11 -0000	[thread overview]
Message-ID: <195F58F118C9D311B622009027DC812FFDD8B0@mail1.technology.serco.com> (raw)

Assuming there is not a probelm with emacs.  presumably 
other programs work fine under the shell.

> a little example:
> /* c-code */
> printf("my output");
> /* "my output" now visible in the shell */

stdout is buffered, so this is only output when the buffer
is full.  What happens if you explicity flush the output by

printf("my output");
fflush(stdout);

> exit(0);
> /* "my output" now visible in my emacs buffer */

This would cause the file buffer to be flushed to the output.


> its a little bit exhausting to switch always between a shell
> and emacs. it interrupts my working flow.

Quite right. One of the most useful things about running a
shell under emacs is you can search through the program's
output
This message, including attachments, is intended only for the use by the
person(s) to whom it is addressed. It may contain information which is
privileged and confidential. Copying or use by anybody else is not
authorised. If you are not the intended recipient, please contact the sender
as soon as possible. The views expressed in this communication may not
necessarily be the views held by Serco Integrated Transport.

             reply	other threads:[~2002-11-29 10:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29 10:34 Victor Kirk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-29  9:54 get stdout/stderr while running a program Victor Kirk
2002-11-29 10:08 ` Re[2]: " Nagash

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=195F58F118C9D311B622009027DC812FFDD8B0@mail1.technology.serco.com \
    --to=vkirk@technology.serco.com \
    --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).