Changying Li <[EMAIL PROTECTED]> writes: > Jeremy Maitin-Shepard <[EMAIL PROTECTED]> writes: >> Changying Li <[EMAIL PROTECTED]> writes: >> >>> I met this error again: >>> Follow: >>> call interactively: Type Error: s.manager is null >> >>> this error randomly appeared, or I hasn't find its rule. >> >> You didn't happen to get a stack trace in the terminal, did you? I >> tried to track down the problem from that brief description alone, but I >> was not able to. A stack trace would make it much easier. >> >> As I said, if you are running on Linux, the stack trace will be printed >> to the terminal in which you invoke conkeror. On Windows, you need to >> invoke Conkeror with the -console command-line option in order to have >> it open a terminal, in which the stack trace will be visible. > ok, I will try, but the error is not very frequently so that I must run > it from terminal always.
You could possibly run it as: conkeror >> some-log-file.txt And then you don't need to run it from a terminal. -- Jeremy Maitin-Shepard _______________________________________________ Conkeror mailing list [email protected] https://www.mozdev.org/mailman/listinfo/conkeror
