Norbert Koch writes:
> different names then the ports. Anyways I find that at the top
> these autos fail and I get a message, buffer to big as xemacs goes
> through the auto sequence. Is there any remedy to this?
> Any advice or ideas who I may forward this question to would be helpful.
> Adam Rappoport
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
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
XEmacs-Beta mailing list