Searched hist:199647 (Results 1 - 4 of 4) sorted by relevance
| /freebsd-9.3-release/tools/regression/bin/sh/builtins/ | ||
| H A D | fc1.0 | 199647 Sun Nov 22 12:08:16 MST 2009 jilles sh: Ensure the same command input file is on top after executing a builtin. This avoids weirdness when 'fc -e vi' or the like is done and there is a syntax error in the file. Formerly an interactive shell tried to execute stuff after the syntax error and exited. This should also avoid similar issues with 'command eval' and 'command .' when 'command' is implemented properly as in NetBSD sh. Special builtins did not have this problem since errors in them cause the shell to exit or to reset various state such as the current command input file. |
| /freebsd-9.3-release/bin/sh/ | ||
| H A D | input.h | diff 199647 Sun Nov 22 12:08:16 MST 2009 jilles sh: Ensure the same command input file is on top after executing a builtin. This avoids weirdness when 'fc -e vi' or the like is done and there is a syntax error in the file. Formerly an interactive shell tried to execute stuff after the syntax error and exited. This should also avoid similar issues with 'command eval' and 'command .' when 'command' is implemented properly as in NetBSD sh. Special builtins did not have this problem since errors in them cause the shell to exit or to reset various state such as the current command input file. |
| H A D | input.c | diff 199647 Sun Nov 22 12:08:16 MST 2009 jilles sh: Ensure the same command input file is on top after executing a builtin. This avoids weirdness when 'fc -e vi' or the like is done and there is a syntax error in the file. Formerly an interactive shell tried to execute stuff after the syntax error and exited. This should also avoid similar issues with 'command eval' and 'command .' when 'command' is implemented properly as in NetBSD sh. Special builtins did not have this problem since errors in them cause the shell to exit or to reset various state such as the current command input file. |
| H A D | eval.c | diff 199647 Sun Nov 22 12:08:16 MST 2009 jilles sh: Ensure the same command input file is on top after executing a builtin. This avoids weirdness when 'fc -e vi' or the like is done and there is a syntax error in the file. Formerly an interactive shell tried to execute stuff after the syntax error and exited. This should also avoid similar issues with 'command eval' and 'command .' when 'command' is implemented properly as in NetBSD sh. Special builtins did not have this problem since errors in them cause the shell to exit or to reset various state such as the current command input file. |
Completed in 109 milliseconds