From: Christopher Howard <christopher@librehacker.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Help Gnu Emacs Mailing List <help-gnu-emacs@gnu.org>
Subject: Bookmark+: automated annotating?
Date: Tue, 22 Oct 2024 11:40:29 -0800 [thread overview]
Message-ID: <87h694vscy.fsf@librehacker.com> (raw)
Hi, I've been playing around with bookmark+. As mentioned previously, I want to try using bookmarks annotations as metadata for a few hundred files in one of my projects. On my end, I started working on an emacs script to pull some important documentation data out of the files. I was wondering now if I can tie that into some bookmark or bookmark+ API to automatically annotate the file bookmarks, rather than copying and pasting everything. Could I get a bit of guidance as far as what functions would be worth looking at?
--
📛 Christopher Howard
🚀 gemini://gem.librehacker.com
🌐 http://gem.librehacker.com
בראשית ברא אלהים את השמים ואת הארץ
next reply other threads:[~2024-10-22 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 19:40 Christopher Howard [this message]
2024-10-22 21:05 ` [External] : Bookmark+: automated annotating? Drew Adams
2024-10-23 15:27 ` Christopher Howard
2024-10-23 20:13 ` 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=87h694vscy.fsf@librehacker.com \
--to=christopher@librehacker.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.
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).