Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jit-spell mode does not work in indirect buffers: seems disabled thereafter #4

Open
ericsfraga opened this issue Mar 10, 2023 · 5 comments

Comments

@ericsfraga
Copy link

I really like this package and have been using it for a week or so.

However, I use indirect buffers a lot (org-capture, org-roam). It seems that jit-spell does not work in these:

error in process filter: jit-spell--process-filter: Args out of range: #<buffer CAPTURE-2023-03-10.org>, 1, 125
error in process filter: Args out of range: #<buffer CAPTURE-2023-03-10.org>, 1, 125

Although this limitation is not ideal, the more serious problem is that once jit-spell fails in this way, it seems to be completely disabled thereafter, whether I disable and re-enable it or not.

@astoff
Copy link
Owner

astoff commented Mar 10, 2023

Okay, I use org capture so I should be able to reproduce and figure out what's going on.

@astoff
Copy link
Owner

astoff commented Mar 11, 2023

Are you using the current ELPA version (0.1) or the latest git? I see some glitches in the indirect buffer but not the breakage that you described.

@ericsfraga
Copy link
Author

I was using 0.1 from ELPA (keeping things simple for me). I'll try 0.2 later today hopefully.

@astoff
Copy link
Owner

astoff commented Mar 11, 2023

It doesn't work on indirect buffers for the same reason that bug-reference-mode doesn't. This means I can only fix the problem if I add workarounds specifically to deal with the indirect buffer case. I think I need to weigh the importance of the problem against the kludginess of a potential solution (I don't have an assessment of either at this point :-)).

@ericsfraga
Copy link
Author

Ah, okay. Difficult to asses the cost-benefit analysis for this case! No worries and thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants