I am having trouble having redirection working with the ability to hit enter and remain in the same shell.

My problem is if user types: ./a.out < foo.txt (where foo.txt contains a command like date)
I want to execute that command and exit the shell.However,if the user compiles the code without using redirection: ./a.out, I want to keep the user in the shell even if he presses enter.

shell>> (pressed Enter)
shell>> (pressed Enter)
shell>> ls

The problem arises because both enter and end of file are read in as '\0' using gets. Is there a way, such that both functionality can be achieved. Any help is greatly appreciated.

Snippet of my code:

int main(int argc, char *argv[])
  int nbytes = 100;
  char my_string[nbytes];
  string arg_list[20];


    printf("shell>> ");
    my_string[0] = '\0';
    gets( my_string );

    //this should happen when end of file is reached
    if(my_string[0] == '\0'){ 

   // this should happen when user presses enter
3 Years
Discussion Span
Last Post by deceptikon

Might want to use something besides gets. From cplusplus.com gets page


The most recent revision of the C standard (2011) has definitively removed this function from its specification.
The function is deprecated in C++ (as of 2011 standard, which follows C99+TC3).

As far as distinguishing end of file from a user pressing ENTER, you don't harness the return value of gets anywhere and you don't test for end of file or errors with feof or ferror. Read the fgets page linked above, in particular the "return" section.

Then again, according to WaltP, don't bother with any of that, just rewrite your code completely, getting rid of all gets commands. Quite simply, there is no RIGHT way to use it.



Thanks for pointing me to the articles, they were very insightful.

I did find something.


can be used to check if the input was read from the file or keyboard.

Edited by asa88


feof(stdin) can be used to check if the input was read from the file or keyboard.

No, not really. It's not uncommon to signal end-of-file from the keyboard. For example, run the following program and watch it print "Yes" when you signal end-of-file using ctrl+z (Windows) or ctrl+d (POSIX):

#include <stdio.h>

int main(void)

    printf("end-of-file: %s\n", feof(stdin) ? "Yes" : "No");

    return 0;

Further, and more distressingly, if your code is written as a filter, stdin acts as keyboard input, file input, or even piped input depending on how you do redirection from the command line. All without changing any code. Tell me, is this being run as an interactive program or is input redirected from a file?

#include <stdio.h>
#include <string.h>

char *reverse(char *s)
    size_t i = 0;
    size_t j = strlen(s) - 1;

    if (s[j] == '\n') {

    while (i < j) {
        char temp = s[i];
        s[i++] = s[j];
        s[j--] = temp;

    return s;

int main(void)
    char line[BUFSIZ];

    while (fgets(line, sizeof line, stdin)) {
        fputs(reverse(line), stdout);

    return 0;
This article has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.