From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Weird behavior of emacs: I can't exit
Date: Sun, 13 Jan 2013 16:17:45 +0800 [thread overview]
Message-ID: <87fw25v6mu.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CA+ho6zBZqXFj_mVaWQ+eXtCg4y=uj_WY=Jx8xi3eK_ChC1j=uQ@mail.gmail.com
Santiago Mejia <santiagomejiar@gmail.com> writes:
> I have come to find that what is causing the problem was not ido.el,
> but a little add-on that keeps track of the frequency of my commands
> (keyfreq.el).
>
> Here is one copy of it, in case anyone has a chance to look at it and
> explain me what is going on: https://github.com/dacap/keyfreq
>
> S.
>
> On Sat, Jan 12, 2013 at 9:55 PM, Santiago Mejia
> <santiagomejiar@gmail.com> wrote:
>
> I don't understand why, but I can't quit emacs. When I do C-x C-c,
> emacs just says:
>
> (No files need saving))
> setq: End of file during parsing
>
> I need to kill emacs in order to quit.
>
> I suspect that it might be a problem with ido, which I was using
> when this problem started. I have deactivated ido in my .emacs,
> but now the problem persists.
>
> Any ideas of what can be causing this bug?
>
> S.
It's bound to be a function added to "kill-emacs-hook", and sure enough
keyfreq does add the function `keyfreq-autosave--do'. The particular
error probably comes from an accidentally-deleted closing parenthesis,
ie somewhere there's a line that looks like this:
(setq var some-value
with no paren at the end. There's no setq in keyfreq-autosave--do or its
immediate callees, but I'd say that's guaranteed to be the problem
somewhere down the line.
E
next prev parent reply other threads:[~2013-01-13 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-13 3:55 Weird behavior of emacs: I can't exit Santiago Mejia
2013-01-13 7:05 ` Santiago Mejia
2013-01-13 8:17 ` Eric Abrahamsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-14 2:58 Santiago Mejia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fw25v6mu.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.