verilog mode problem

Norbert Koch writes: Please report the *exact* message in full. This makes it much easier to identify the code where the failure is occurring (if it's in XEmacs). A quick grep through verilog.el gives no hits on "too big". XEmacs buffers have no size limit (except the amount of virtual memory available on your system), so it seems likely that this is occuring in a subprocess (verilog itself?), not in XEmacs. Please follow up, however. It is possible that XEmacs is configuring the subprocess with too little memory or something, and that by changing the configuration of verilog mode this constraint can be relaxed. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta