Bug 827898 - regression: emacs fails on previously working ~/.emacs resp. stucks when parsing it
Summary: regression: emacs fails on previously working ~/.emacs resp. stucks when pars...
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 17
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Petr Hracek
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2012-06-03 14:50 UTC by Enrico Scholz
Modified: 2013-05-29 16:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-05-29 16:37:30 UTC

Attachments (Terms of Use)
reduced ~/.emacs file (1.32 KB, application/octet-stream)
2012-06-03 14:50 UTC, Enrico Scholz
no flags Details

Description Enrico Scholz 2012-06-03 14:50:39 UTC
Created attachment 588882 [details]
reduced ~/.emacs file

Description of problem:

emacs 24 fails with obscure errors to parse a previously working ~/.emacs. When shifting around/disabling code, the startup stucks.

Things worked fine with emacs 23 from F16.



| Warning (initialization): An error occurred while loading `/home/ensc/.emacs':
| File error: Cannot open load file, gpl

error can be avoided by removing/shifting the first line of the file -- this is a comment (!) with an emacs mode string. But then, startup stucks in an infinite loop (?).

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. emacs -q
2. M-x load-file ~/.emacs

Comment 1 Fedora Admin XMLRPC Client 2013-02-27 15:47:43 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Petr Hracek 2013-05-28 12:36:42 UTC
I asked the upstream what can be wrong with your .emacs file

and could you please add
(setq debug-on-quit t) 
so that we can analyze it?
By the way you are using Xemacs?

What do you have in your .emacs-config/lisp directory?

Comment 3 Enrico Scholz 2013-05-29 16:37:30 UTC
sorry, I forgot about this bug and do not see it anymore with recent emacs-24.3-9.2.fc18x.x86_64

Note You need to log in before you can comment on or make changes to this bug.