RE: [External] : Re: Please, Restore Previous Behavior for jump-to-register

[Drew Adams]

> E.g., bookmarks does not warn about overwriting an existing bookmark.

If you use a prefix arg with `bookmark-set'
then you don't overwrite any bookmark with
the same name.  Instead you add a new one
with the same name.  IOW, bookmarks are
handled like alist entries (which they are).  

You can also use `bookmark-set-no-overwrite'
instead of `bookmark-set', in which case an
error is raised if you provide the same name
as an existing bookmark, and a prefix arg
pushes the new bookmark with the same name.

Being able to have multiple bookmarks with
the same name is a _feature_, not a bug.

> That would be a good place for such a warning, and even prompt would
> make sense and a change I think nobody would even object to.
> 
> Bookmarks doesn't do the whole preview thing

Bookmarks can do anything you want them to.
They're just functions.

> If the issue is the temporary aspect of registers or not being able to
> set bookmarks in some contexts (buffers without a associated file,
> e.g.),

Not an issue.

With Bookmark+, you can have temporary
bookmarks.  (And even with vanilla
bookmark.el you need not save a bookmark
file, and you can remove bookmarks from it
before saving.)

And with Bookmark+ you can bookmark non-file
buffers.  (Even vanilla bookmark.el does
that, for Dired buffers, though it doesn't
do it well.  someone will say a directory is
also a file, but that's irrelevant here.)

You can really bookmark anything.  Again, a
bookmark is just a function - it can do
anything at all.  It need not have anything
to do with any notion of "location", or the
"location" can be as bizarre or unusual as
you like.