BirillAK wrote:

> Люди подскажите плз. а в bash(e) есть обработка исключений ?
Оно же скрипт.
Есть код завершения вызванной программы, который можно проверять.
Posted via ActualForum NNTP Server 1.4

BirillAK wrote:

> А можно ли тогда перехватить последнею команду командной строки?
1) А зачем?
2) команды сохраняются в хистори, в принципе, если сохраняются часто и
сразу, можно прочесть в хистори последнюю команду.
Posted via ActualForum NNTP Server 1.4

BirillAK wrote:

> Блин а как это сделать ?
Может, вы все-таки задачу обрисуете в деталях?

читайте info bash:

5.2 Bash Variables
These variables are set or used by Bash, but other shells do not
normally treat them specially.

.....


`HISTCMD'
The history number, or index in the history list, of the current
command. If `HISTCMD' is unset, it loses its special properties,
even if it is subsequently reset.


`HISTCONTROL'
A colon-separated list of values controlling how commands are
saved on the history list. If the list of values includes
`ignorespace', lines which begin with a space character are not
saved in the history list. A value of `ignoredups' causes lines
which match the previous history entry to not be saved. A value
of `ignoreboth' is shorthand for `ignorespace' and `ignoredups'.
A value of `erasedups' causes all previous lines matching the
current line to be removed from the history list before that line
is saved. Any value not in the above list is ignored. If
`HISTCONTROL' is unset, or does not include a valid value, all
lines read by the shell parser are saved on the history list,
subject to the value of `HISTIGNORE'. The second and subsequent
lines of a multi-line compound command are not tested, and are
added to the history regardless of the value of `HISTCONTROL'.


`HISTFILE'
The name of the file to which the command history is saved. The
default value is `~/.bash_history'.
....

Posted via ActualForum NNTP Server 1.4