You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like the idea of reusing builtin functionality for the purpose of storing window/frame configuration! I've one small issue though - After starting Emacs, M-x burly-open-bookmark shows no entries, since the bookmark file is somehow not yet loaded. After M-x bookmark-jump the file is loaded and then burly is populated too, when doing M-x burly-open-bookmark again.
Independently of the issue, I wonder if it is necessary to do the URL encoding? It seems to me that bookmarks can be simple alists? Generally I would prefer to use the native elisp format instead of the less readable url encoding. Or maybe there is a technical reason to use the url format? Is it the idea that urls are better for external sharing? Does burly also hook into some internal emacs url mechanism for opening urls? Your readme states that you also provide commands working with the URL strings, with the added qualification that most users probably won't use these.
The text was updated successfully, but these errors were encountered:
Hi,
I like the idea of reusing builtin functionality for the purpose of storing window/frame configuration! I've one small issue though - After starting Emacs,
M-x burly-open-bookmark
shows no entries, since the bookmark file is somehow not yet loaded. AfterM-x bookmark-jump
the file is loaded and then burly is populated too, when doingM-x burly-open-bookmark
again.Independently of the issue, I wonder if it is necessary to do the URL encoding? It seems to me that bookmarks can be simple alists? Generally I would prefer to use the native elisp format instead of the less readable url encoding. Or maybe there is a technical reason to use the url format? Is it the idea that urls are better for external sharing? Does burly also hook into some internal emacs url mechanism for opening urls? Your readme states that you also provide commands working with the URL strings, with the added qualification that most users probably won't use these.
The text was updated successfully, but these errors were encountered: