all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Damien Cassou <damien@cassou.me>
Cc: nicolas@petton.fr, 24278@debbugs.gnu.org
Subject: bug#24278: 25.1; Invalid recentf file
Date: Sun, 21 Aug 2016 14:43:24 +0300	[thread overview]
Message-ID: <8337lycppf.fsf@gnu.org> (raw)
In-Reply-To: <87eg5iabgk.fsf@cassou.me> (message from Damien Cassou on Sun, 21 Aug 2016 08:21:47 +0200)

> From: Damien Cassou <damien@cassou.me>
> Date: Sun, 21 Aug 2016 08:21:47 +0200
> Cc: Nicolas Petton <nicolas@petton.fr>
> 
> frequently, the recentf file becomes invalid Lisp. For example, today, it
> looks like:
> 
>     ;;; Automatically generated by ‘recentf’ on Sat Aug 20 20:31:12 2016.
> 
>     (setq "/home/cassou/nixpkgs/lib/default.nix"recentf-list
>           '(
>             "/home/cassou/.emacs.d/default.nix"
>             "/home/cassou/.emacs.d/init.el"
>             [...]
>             ))
> 
>     (setq recentf-filter-changer-current 'nil)
> 
> Look at the string between "setq" and "recentf-list". I'm using Emacs 25
> rc1.

Very strange.  recentf-save-list, the function that saves the list,
erases the buffer it uses before it generates the contents to save,
whereas your file looks like some bogus attempt to update an existing
file by inserting stuff in its middle.  Could it be that some optional
package, or some software unrelated to Emacs, does that?  E.g., what
is this about:

> Saving file /home/cassou/.emacs.d/recentf...
> Wrote /home/cassou/.emacs.d/.undo-tree/.!home!cassou!.emacs.d!recentf.~undo-tree~
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

> Wrote /home/cassou/.emacs.d/recentf

Thanks.





  reply	other threads:[~2016-08-21 11:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-21  6:21 bug#24278: 25.1; Invalid recentf file Damien Cassou
2016-08-21 11:43 ` Eli Zaretskii [this message]
2016-12-07 20:36   ` Glenn Morris

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=8337lycppf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24278@debbugs.gnu.org \
    --cc=damien@cassou.me \
    --cc=nicolas@petton.fr \
    /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.