Re: [Ebib-users] Fwd: Keyword options greyed out

[Joost K. <joo...@fa...>]

Hi Phil,

On Thu, Jun 29 2017, Marlene and Phil Carter wrote:
> I seem have lost the reply you sent to this email. As I 
> remember, you asked what version of Ebib I am using, and what 
> happens when I type K S.
>
> I had some time away from Ebib, when I decided to try again, I 
> updated my version to the most recent version from ELPA.

Good. :-)

> When I type K S in the index buffer, nothing happens.

That's strange indeed, but consistent with the fact that the 
option is greyed out in the menu. I haven't been able to look into 
this yet, I hope to be able to do so later today.

> I don’t know whether this has any bearing on my problem or not, 
> but when I type C-c e to fire up Ebib, these messages appear in 
> my *Messages* buffer, before I open a bib file:
>
> Error during redisplay: (eval (ebib--mode-line-modified-p)) 
> signaled (wrong-type-argument arrayp nil)
> Error during redisplay: (eval (format "  (%s)" 
> (ebib--get-dialect ebib--cur-db))) signaled (wrong-type-argument 
> arrayp nil)
> Error during redisplay: (eval (ebib--mode-line-modified-p)) 
> signaled (wrong-type-argument arrayp nil)
> Error during redisplay: (eval (format "  (%s)" 
> (ebib--get-dialect ebib--cur-db))) signaled (wrong-type-argument 
> arrayp nil)
>
> What  is going on here?
>
> Thanks again.
>
> Phil Carter

What's going on is that I didn't consider the possibility that 
Ebib may be started without the option `ebib-preload-bib-files' 
set. That means that no files are loaded when the Ebib buffers are 
displayed and as a result, a few things didn't work. That should 
be fixed now in the latest update.

I don't think this has anything to do with the keyword saving 
problem you have, though, so I'll have to look into that 
separately.

Best,

Joost




-- 
Joost Kremers
Life has its moments