MU-BOOKMARKS(5) File Formats Manual MU-BOOKMARKS(5)NAME
bookmarks - file with bookmarks (shortcuts) for mu search expressions
DESCRIPTION
Bookmarks are named shortcuts for search queries. They allow using a convenient name for often-used queries. The bookmarks are are also
visible as shortcuts in the mu experimental user interfaces, mug and mug2.
mu supports bookmarks stored in a file called bookmarks in the mu home directory (typically, this would be ~/.mu/bookmarks).
The bookmarks file is a typical key=value .ini-file, which is best shown by means of an example:
[mu]
inbox=maildir:/inbox # inbox
oldhat=maildir:/archive subject:hat # archived with subject containing 'hat'
The [mu] group header is required.
For practical uses of bookmarks, see mu-find(1).
LOCATION
The bookmarks file is read from <muhome>/bookmarks. Typically, this would be ~/.mu/bookmarks, but this can be influenced using the --muhome
parameter for mu-find(1) and mug(1).
AUTHOR
Dirk-Jan C. Binnema <djcb@djcbsoftware.nl>
SEE ALSO mu(1)mu-find(1)User Manuals May 2011 MU-BOOKMARKS(5)
Check Out this Related Man Page
KBOOKMARKMERGER KDE User's Manual KBOOKMARKMERGER
NAME
kbookmarkmerger - A program for merging a given set of bookmarks into the user's list of bookmarks.
SYNOPSIS
kbookmarkmerger [Qt Options...] [KDE Options...] {directory}
DESCRIPTION
kbookmarkmerger is a program for merging a given set of bookmarks into the user's set of bookmarks; if the user doesn't have any bookmarks
created yet, a new bookmark list is created and the given bookmarks are inserted into it. While doing this, kbookmarkmerger keeps track of
which files were merged in a previous run already, so no bookmark will get installed to the user's bookmarks more than once. In case KDE is
running while kbookmarkmerger is executed, the KDE bookmark subsystem will be informed of any changes to the user's bookmarks, so that all
applications accessing that information (i.e.Konqueror) will pick the changes up instantly.
The traditionally used approach to achieve something like this was to use carefully crafted skeleton home directories when creating a new
user account, to provide the user with a standard set of bookmarks. The problem with this approach is that after the user account has been
created, no new bookmarks can be propagated.
This mechanism is useful for system administrators who want to propagate a bookmark pointing to a certain document (for instance, important
notes about the system) to all users. Distributors might find it useful as well, for instance by augmenting the software packages they
supply with bookmark files which kbookmarkmerger merges into the user's bookmark list when the package is installed. That way,
documentation shipped with a software package is easily and visibly accessible right after the package has been installed.
The only parameter required by kbookmarkmerger is the name of a directory which shall be scanned for bookmark files. All files in the given
directory will be considered for being merged into the user's setup. The files in the given directory should be valid XBEL files.
SEE ALSO
Konqueror manual[1]
EXAMPLES
joe@hal9000:~> kbookmarkmerger /usr/local/extra-bookmarks
Merges all bookmark files stored in /usr/local/extra-bookmarks into joe's list of bookmarks.
STANDARDS
XBEL specification[2]
RESTRICTIONS
When determining whether a given bookmark file has been merged into the user's bookmarks already or not, kbookmarkmerger merely looks at
the filename of the bookmark file - the contents are not checked at all. This means that changing a bookmark file which was already merged
into a user's bookmarks will not trigger merging it once again.
Also note that in case a user modifies a bookmark which was merged into his setup, the original bookmark file will be left unmodified.
AUTHOR
Frerich Raabe<raabe@kde.org>
AUTHOR
Frerich Raabe <raabe@kde.org>
Author.
NOTES
1. Konqueror manual
help:/konqueror/index.html
2. XBEL specification
http://pyxml.sourceforge.net/topics/xbel/
K Desktop Environment February 1st, 2005 KBOOKMARKMERGER