New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emacs hungs up #964
Comments
Original Redmine Comment I am unable to recreate this issue.
|
Original Redmine Comment Hi Kaushal, I tried that file and same thing is happening with me. (Emacs gets hung.) I am using Emacs on Windows 7 machine. Here are answers to your questions:
Let me know if you need some other information. Thank you, |
Original Redmine Comment I thought this issue may be the same as the one I recently reported 1070. However, I downloaded the example and could not reproduce this one despite having the same version of verilog-mode that this reported had.
|
Original Redmine Comment Hello Ian, I am having some customizations for Verilog-mode in my .emacs file. I noticed today that if I use that .emacs file then Emacs Hungs up. If I do not use my .emacs file ( My .emacs file location is : C:\Users\Bhaumik.Darji.168\AppData\Roaming ) i.e simply delete .emacs file from above location, Emacs does not get hang. I am sharing my .emacs file for reference. See if you can get any idea from that. Thank you, |
Original Redmine Comment Thanks, for the suggestion. However, in my case the autocompletion error reported in http://www.veripool.org/issues/1070-Verilog-mode-Auto-completion-results-in-runaway-emacs-process-in-emacs-24-4-on-Debian-using-2016-04-23-5f6855e-vpo results in a runaway process when I do not load the my .emacs file. (ie. I start emacs like this "emacs -Q") Ian |
Original Redmine Comment Closing due to age, presumably unrelated to verilog-mode. |
Author Name: J. Hbeck
Original Redmine Issue: 964 from https://www.veripool.org
Move your cursor to the end of line 6 of the attached example and hit enter. This will lead to 100% CPU usage and emacs hungs up.... Seems to be a problem with the indentation of event control.
The text was updated successfully, but these errors were encountered: