UPDATE after you added more detail in the question (thanks).
A bookmark-list display state arrived at with incremental pattern matching (e.g.
P T
), as opposed to, say using a filtering command (I gave an example of that, above), was not captured in a bookmark-list bookmark. I fixed that (i.e., implemented that missing feature) yesterday, having guessed that that's maybe what you tried. (Had you happened to download yesterday'sbookmark+-bmu.el
that would have been fixed.)As the doc says, markings are not captured by bookmark-list bookmarks. They are also not captured by the commands you create using
C-c C-c
(commandbmkp-bmenu-define-command
) -- that captures only the current sort order, filter, and omit list.As the doc also says, markings are captured by the much heavier-weight
C-c C-S-c
(akaC-c C-C
, commandbmkp-bmenu-define-full-snapshot-command
). That captures pretty much everything, at the cost of storing a full bookmark list, list of markings, etc.However, there were some bugs in #3 (
C-c C-C
). I've think I've fixed those today.
Please try the latest bookmark+-bmu.el
. And please read up again on the differences between the different ways of capturing and restoring bookmark-list state. Each method has its advantages.
BTW, if you turn off option bmkp-propertize-bookmark-names-flag
then the bookmark list you copy and paste somewhere (e.g. here) is much simpler to read and understand. It then has no shared structure that allows for multiple bookmarks with the same name but different behavior/targets. The toggle command for flipping this option value is bmkp-toggle-propertize-bookmark-names
. It's also Bookmark+ menu item Toggle > Allowing Identical Bookmark Names.
The ability to have multiple bookmarks with the same name is importantly primarily for autofile bookmarks, whose names are their relative file names: you can have multiple files named foo.el
in different directories..