From 17b38a6be859f9021312159de6ddbed5a123730e Mon Sep 17 00:00:00 2001 From: Manfred Urban Date: Thu, 5 Nov 2015 16:43:28 +0100 Subject: [PATCH] Minor layout fixes to documentation --- docs/dev/plugins.rst | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/docs/dev/plugins.rst b/docs/dev/plugins.rst index f63d75aba..9a59351e3 100644 --- a/docs/dev/plugins.rst +++ b/docs/dev/plugins.rst @@ -216,15 +216,16 @@ The events currently available are: * *trackinfo_received*: called after meta data for a track item has been fetched from disparate sources, such as MusicBrainz. Gives a developer the option to - intercept the fetched TrackInfo object. Can be used to modify tags on a ``beet - import`` operation or during later adjustments, such as ``mbsync``. Slow - handlers of the event can impact the operation, since the event is fired for - any fetched possible match *before* user or autotagger selection was made. + intercept the fetched ``TrackInfo`` object. Can be used to modify tags on a + ``beet import`` operation or during later adjustments, such as ``mbsync``. + Slow handlers of the event can impact the operation, since the event is fired + for any fetched possible match *before* user or autotagger selection was made. Parameter: ``info``. * *albuminfo_received*: Like *trackinfo_received*, the event indicates new meta - data for album items, but supplies an *AlbumInfo* object instead of a - *TrackInfo*. + data for album items, but supplies an ``AlbumInfo`` object instead of a + ``TrackInfo``. + Parameter: ``info``. The included ``mpdupdate`` plugin provides an example use case for event listeners.