emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Wichmann <schwurg@arcor.de>
To: emacs-orgmode@gnu.org
Subject: Question regarding org-capture-bookmark and org-bookmark-names-plist
Date: Wed, 07 Feb 2024 21:07:44 +0100	[thread overview]
Message-ID: <87le7wkp72.fsf@arcor.de> (raw)

Hi all,

during last OrgMeetup, I proposed a new user option
`org-refile-bookmark', similar to the already existing option
`org-capture-bookmark'.  Setting this new option to nil, `org-refile’
would not create a bookmark when refiling.  (Use case: I am using
alphapapa's org-bookmark-heading package and want to prevent that each
captured/refiled entry gets an id.)

I was just about to send the corresponding feature request when I
stumbled across the documentation of `org-bookmark-names-plist'.  It
states: „When a key does not show up in the property list, the
corresponding bookmark is not set.“

So, there is no need for a new user option: I simply have to remove the
:last-refile key from the plist, and no bookmark will be created on
refiling.

My question: Is this the intended way to suppress bookmark creation?  If
so: Why is there the extra user option `org-capture-bookmark'?  Isn't it
superfluous, as the same behavior can be achieved by removing the
:last-capture keyword from the plist?  (Note, moreover, that currently
the :last-capture-marker bookmark is created even in case
`org-capture-bookmark' is set to nil, see `org-refile'.)


Best regards,
  Tim.


             reply	other threads:[~2024-02-07 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 20:07 Tim Wichmann [this message]
2024-02-08 13:29 ` Question regarding org-capture-bookmark and org-bookmark-names-plist Ihor Radchenko
2024-02-08 18:09   ` Tim Wichmann
2024-02-08 20:58   ` Tim Wichmann
2024-02-09 16:50     ` Ihor Radchenko

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87le7wkp72.fsf@arcor.de \
    --to=schwurg@arcor.de \
    --cc=emacs-orgmode@gnu.org \
    /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/org-mode.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).