From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: RE: Temporary notes in Emacs buffers?
Date: Wed, 15 Jan 2020 15:10:46 -0800 (PST) [thread overview]
Message-ID: <631d0890-407e-4917-9f3d-41b8a6999cd7@default> (raw)
In-Reply-To: <3e2814f1-579d-4fdd-aa5d-6c68f9c0410c@default>
> What I suggested is switching to a bookmark file
> that has _only_ bookmarks for the target file,
> as opposed to just loading such a bookmark file
> to add to the already loaded bookmarks for targets
> elsewhere.
...
> But there are other, i.e., additional, ways to group
> bookmarks, besides a bookmark file. As the doc says:
>
> Unlike the other ways of organizing bookmarks into sets (tags,
> bookmark-list bookmarks, etc.) bookmark files represent
> physical, not logical, groupings of bookmarks.
>
> Bookmarks themselves can be saved in any bookmark
> file, and in any number of different bookmark files.
It occurred to me that this info might also help Michael (dunno).
Instead of having a different bookmark file for each target file,
to hold all bookmarks for it, you can use a filtered bookmark-list
display that shows only those bookmarks. This is a logical
grouping, not a physical grouping, as mentioned above.
In the bookmark-list display (buffer `*Bookmark List*'), you can
use `= f S' to show only bookmarks that target a given file (it
prompts you for the file name).
(Similarly, `= b S' shows only bookmarks that target a given
non-file buffer.)
Using different bookmark-list displays for organizing bookmarks
is in many ways more flexible than using different bookmark files.
Among other things, it lets you mark bookmarks and then act on
them in various ways. (The Bookmark+ bookmark-list UI is much
like Dired's.)
---
Now let's suppose that you've done that, so `*Bookmark List*'
shows all bookmarks for file `foo.nada', and no other bookmarks.
That may well be all you need.
But let's also suppose that you decide that, for some reason,
you actually do want those bookmarks grouped physically, in their
own bookmark file, so that `foo.nada' has its own, dedicated
bookmark file.
All you need to do for that is this:
1. Mark the bookmarks in `*Bookmark List*' (e.g. after filtering
so it shows only bookmarks for `foo.nada').
2. Use `Y > 0', to create a new bookmark file for just the marked
bookmarks.
Or use `C-u Y > 0' to do that plus create a bookmark to that
bookmark file. Using this bookmark automatically loads that
bookmark file
(`C-x j y' anywhere, or `J y' in `*Bookmark List*', jumps to
a bookmark-file bookmark, and with a prefix arg it switches
to that bookmark file, instead of just adding its bookmarks.)
You don't need to these remember key bindings. You can use the
`Bookmark+' menu in buffer `*Bookmark List*'. In submenu
`Bookmark File' you find most of the commands for using bookmark
files: creating, copying or moving bookmarks among them,
bookmarking them, etc. And in submenu `Jump To' you find item
`Bookmark File' (`J y').
In `Bookmark+' > `Bookmark File' you find these menu items, along
with their keys.
Revert to Saved Bookmark File... C-u g
Switch to Bookmark File... L
Add Bookmarks from File... l
Load Bookmark File, Mark Loaded...
Load Bookmark File, Mark Only Loaded...
Load Marked Bookmark-File Bookmarks... M-l
------------------------------------------------
Move Marked to Bookmark File... Y > -
Copy Marked to Bookmark File... Y > +
Copy Marked to New Bookmark File... Y > 0
Set Bookmark-File Bookmark from Marked... C-u Y > 0
Empty Bookmark File... C-x p 0
(`Switch to Bookmark File' also has global binding `C-x p L'.
Menus are good for discovering operations and reminding about
their key bindings.
next prev parent reply other threads:[~2020-01-15 23:10 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 10:19 Temporary notes in Emacs buffers? Marcin Borkowski
2019-12-27 10:43 ` Mpho Jele
2019-12-27 11:51 ` tomas
2020-01-01 21:48 ` Marcin Borkowski
2019-12-27 15:54 ` Drew Adams
2020-01-02 17:49 ` Marcin Borkowski
2020-01-05 2:37 ` Michael Heerdegen
2020-01-05 17:54 ` Drew Adams
2020-01-06 5:18 ` Jean-Christophe Helary
2020-01-06 15:12 ` Drew Adams
2020-01-09 1:03 ` Michael Heerdegen
2020-01-09 23:35 ` arthur miller
2020-01-10 4:58 ` Michael Heerdegen
2020-01-10 9:30 ` Robert Pluim
2020-01-10 10:01 ` Michael Heerdegen
2020-01-10 17:04 ` Drew Adams
2020-01-10 9:10 ` Unknown
2019-12-27 17:48 ` Sharon Kimble
2020-01-01 1:42 ` Michael Heerdegen
2020-01-01 4:45 ` Drew Adams
2020-01-01 5:00 ` Michael Heerdegen
2020-01-01 6:25 ` Drew Adams
2020-01-01 20:34 ` John Yates
2020-01-01 21:19 ` Drew Adams
2020-01-01 21:47 ` Marcin Borkowski
2020-01-02 1:25 ` Michael Heerdegen
2020-01-02 3:16 ` Drew Adams
2020-01-02 3:45 ` Michael Heerdegen
2020-01-02 5:30 ` Drew Adams
2020-01-02 15:41 ` Drew Adams
2020-01-03 1:07 ` Michael Heerdegen
2020-01-03 3:35 ` John Yates
2020-01-03 6:38 ` Drew Adams
2020-01-03 7:06 ` Drew Adams
2020-01-04 6:39 ` Michael Heerdegen
2020-01-04 16:04 ` Drew Adams
2020-01-06 14:18 ` John Yates
2020-01-06 14:34 ` tomas
2020-01-06 15:19 ` John Yates
2020-01-06 15:31 ` tomas
2020-01-06 16:28 ` arthur miller
2020-01-03 7:00 ` Drew Adams
2020-01-03 13:31 ` arthur miller
2020-01-05 2:18 ` Michael Heerdegen
2020-01-11 7:36 ` Michael Heerdegen
2020-01-11 10:00 ` Jean-Christophe Helary
2020-01-11 11:38 ` Michael Heerdegen
2020-01-11 16:00 ` Drew Adams
2020-01-11 23:46 ` John Yates
2020-01-12 2:47 ` Drew Adams
2020-01-12 7:31 ` Michael Heerdegen
2020-01-12 16:37 ` Drew Adams
2020-01-14 7:08 ` Michael Heerdegen
2020-01-14 17:32 ` Drew Adams
2020-01-15 23:10 ` Drew Adams [this message]
2020-01-02 17:48 ` Marcin Borkowski
2020-01-02 17:48 ` Marcin Borkowski
2020-01-09 3:57 ` Michael Heerdegen
2020-01-15 18:43 ` Marcin Borkowski
2020-01-20 12:40 ` Michael Heerdegen
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=631d0890-407e-4917-9f3d-41b8a6999cd7@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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).