[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#33005: 27.0.50; Data loss with Gnus registry
From: |
Eric Abrahamsen |
Subject: |
bug#33005: 27.0.50; Data loss with Gnus registry |
Date: |
Mon, 23 Sep 2019 20:34:51 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
>> Ok, can we close this report - seems we are done?
>
> Sorry for the bad news - but my registry marks are disappearing again
> :-( Just after restarting Gnus they are gone.
>
> I wanted to try with gnus-mock but it errors:
>
> Debugger entered--Lisp error: (buffer-read-only #<buffer
> .newsrc.eld|emacs-gnus-mock-ENKWay>)
> replace-match("/tmp/emacs-gnus-mock-ENKWay" t)
> gnus-mock-start()
> [...]
>
> I tried to load the source of gnus-mock to get a more meaningful
> backtrace but that also errors:
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> file-name-directory(nil)
> (expand-file-name "data" (file-name-directory load-file-name))
> (file-name-as-directory (expand-file-name "data" (file-name-directory
> load-file-name)))
> (defconst gnus-mock-data-dir (file-name-as-directory (expand-file-name
> "data" (file-name-directory load-file-name))) "Source directory for Gnus mock
> data.")
> eval-region(1 10407) ; Reading at buffer position 5125
>
> Hmm...
Ah, this was a question I had when I was first writing gnus-mock --
load-file-name was reliably present for all my tests, but they were only
on Linux. Can you tell me what system you're running? Presumably
there are better alternatives to load-file-name under different
circumstances.