… | |
… | |
798 | |
798 | |
799 | =over 4 |
799 | =over 4 |
800 | |
800 | |
801 | =item urxvt::fatal $errormessage |
801 | =item urxvt::fatal $errormessage |
802 | |
802 | |
803 | Fatally aborts execution with the given error message. Avoid at all |
803 | Fatally aborts execution with the given error message (which should |
804 | costs! The only time this is acceptable is when the terminal process |
804 | include a trailing newline). Avoid at all costs! The only time this |
805 | starts up. |
805 | is acceptable (and useful) is in the init hook, where it prevents the |
|
|
806 | temrinal from starting up. |
806 | |
807 | |
807 | =item urxvt::warn $string |
808 | =item urxvt::warn $string |
808 | |
809 | |
809 | Calls C<rxvt_warn> with the given string which should not include a |
810 | Calls C<rxvt_warn> with the given string which should include a trailing |
810 | newline. The module also overwrites the C<warn> builtin with a function |
811 | newline. The module also overwrites the C<warn> builtin with a function |
811 | that calls this function. |
812 | that calls this function. |
812 | |
813 | |
813 | Using this function has the advantage that its output ends up in the |
814 | Using this function has the advantage that its output ends up in the |
814 | correct place, e.g. on stderr of the connecting urxvtc client. |
815 | correct place, e.g. on stderr of the connecting urxvtc client. |