-
Notifications
You must be signed in to change notification settings - Fork 14
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
Invalid burly URL with ivy-posframe, better-jumper, or bufler.el #23
Comments
Hi Gerry, I'm not sure I understand. Why would posframes be getting saved, especially ones from Anyway, do you mean that there's an un- |
I agree that they shouldn't be saved. I think it's saved because when I hit
I think that's the issue. From what I see, the possible culprits are :
Maybe a solution would be to check on save (during |
Yeah, that explains it. Well, I guess we'll have to add something like
That's almost certainly the problem, because buffers can't be read. I guess that filtering out the posframe will solve that problem as well, but in case it doesn't, you should be able to filter out that frame parameter already using the existing option.
I don't think that would be correct, because not all values with |
BTW, there is already code to remove buffers from properties in bookmarks, but it must not be catching the one that's causing this. Line 359 in 7c03d63
|
That's because the value is not a buffer but a pair which cdr is a buffer. So I need to add it in the blacklist of parameters |
If necessary, okay, but we should probably filter out posframes instead. |
Oh sure, for posframes filtering the whole frame is the solution, I was thinking about other packages that later might use the same trick |
Before the gnarly backtrace, what I think happens. (I'm on 7c03d63)
I have a
invalid read syntax #
error when I try to restore frames with burly but it worked when I "only" save windows.I dig up the backtrace and I think the issue is with the posframe-buffer frame-parameters (
posframe-buffer
posframe-parent-buffer
), which are stored directly in theirprinc
forms. Either that or still the better-jumper (better-jumper-struct
) issue of #12, or thebufler-workspace-path-formatted
. Or thename
of the framesDon't hesitate to search for the
parameters
in the page, otherwise it's kind of hard to see where the issues areThe url I tried to restore :
The
lisp objectstring that goes intoread
, manually formattedThe text was updated successfully, but these errors were encountered: