unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: "51876@debbugs.gnu.org" <51876@debbugs.gnu.org>,
	Stefan Kangas <stefan@marxist.se>
Subject: bug#51876: [External] : bug#51876: 28.0.60; Confusing prompt for setting a bookmark
Date: Thu, 18 Nov 2021 17:08:31 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488B057A07EACCD571F4505F39B9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87y25llsyx.fsf@gnus.org>

> > Not that it matters now, but I'm curious: why "append" and not "add"?
> 
> With "append" it's clear that we're talking about a list of names, while
> "add" is ambiguous.

We're _not_ appending.  Not at all.

We're actually _setting_ the bookmark with
that name to the specified (typically new)
location.  "Set" is the right word.  It's
precisely the word for what happens.

It's true that wrt the `bookmark-alist'
we're "adding" the bookmark to the front
of the alist ("prepending", if you like).

But we're not adding a bookmark to those
that are in effect at the current time.
Once the new bookmark is "added" this way,
any previously existing bookmarks with the
same name are _no longer usable_ (till the
new one is removed).  They _exist_ on the
alist (users can manipulate them there,
e.g., using Lisp), but they're not usable
as such (you can't jump to them, etc.).

So far, you're just making things worse,
I'm afraid.

`bookmark-set' sets a bookmark.  "Set"
means create or update.

That there are 2 ways to deal with
previously created bookmarks with the same
name is a different question, and is best
dealt with by having two commands, one of
which prompts for confirmation to overwrite
(see my previous msg).





  reply	other threads:[~2021-11-18 17:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 18:34 bug#51876: 28.0.60; Confusing prompt for setting a bookmark Eli Zaretskii
2021-11-16  8:12 ` Lars Ingebrigtsen
2021-11-16 13:12   ` Eli Zaretskii
2021-11-17  6:22     ` Stefan Kangas
2021-11-17  7:17       ` Lars Ingebrigtsen
2021-11-17 16:43         ` bug#51876: [External] : " Drew Adams
2021-11-17 13:50       ` Eli Zaretskii
2021-11-17 16:49         ` bug#51876: [External] : " Drew Adams
2021-11-18  9:21         ` Lars Ingebrigtsen
2021-11-18 17:08           ` Drew Adams [this message]
2021-11-17 16:42       ` bug#51876: [External] : " Drew Adams
2021-11-17 17:08         ` Eli Zaretskii
2021-11-17 17:46           ` Drew Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR10MB5488B057A07EACCD571F4505F39B9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=51876@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=stefan@marxist.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).