Docs: fix long lines

Author: snejus

docs/_templates/autosummary/class.rst

@@ -3,10 +3,10 @@
 .. currentmodule:: {{ module }}
 
 .. autoclass:: {{ objname }}
-   :members:                                    <-- add at least this line
+   :members:             <-- add at least this line
    :private-members:
-   :show-inheritance:                           <-- plus I want to show inheritance...
-   :inherited-members:                          <-- ...and inherited members too
+   :show-inheritance:    <-- plus I want to show inheritance...
+   :inherited-members:   <-- ...and inherited members too
 
    {% block methods %}
    .. automethod:: __init__
@@ -25,4 +25,3 @@
    {% endblock %}
 
    .. rubric:: {{ _('Methods definition') }}
-

docs/changelog.rst

@@ -27,7 +27,8 @@ You can add new items or albums to the library via the
 :py:meth:`Library.add` and :py:meth:`Library.add_album` methods.
 
 You may also query the library for items and albums using the
-:py:meth:`Library.items`, :py:meth:`Library.albums`, :py:meth:`Library.get_item` and :py:meth:`Library.get_album` methods.
+:py:meth:`Library.items`, :py:meth:`Library.albums`, :py:meth:`Library.get_item`
+and :py:meth:`Library.get_album` methods.
 
 Any modifications to the library must go through a
 :class:`Transaction` object, which you can get using the

docs/dev/library.rst

@@ -267,20 +267,18 @@ The events currently available are:
   during a ``beet import`` interactive session. Plugins can use this event for
   :ref:`appending choices to the prompt <append_prompt_choices>` by returning a
   list of ``PromptChoices``. Parameters: ``task`` and ``session``.
-
-* `mb_track_extract`: called after the metadata is obtained from
-  MusicBrainz. The parameter is a ``dict`` containing the tags retrieved from
-  MusicBrainz for a track. Plugins must return a new (potentially empty)
-  ``dict`` with additional ``field: value`` pairs, which the autotagger will
-  apply to the item, as flexible attributes if ``field`` is not a hardcoded
-  field. Fields already present on the track are overwritten.
-  Parameter: ``data``
-
+* `mb_track_extract`: called after the metadata is obtained from MusicBrainz.
+  The parameter is a ``dict`` containing the tags retrieved from MusicBrainz for
+  a track. Plugins must return a new (potentially empty) ``dict`` with
+  additional ``field: value`` pairs, which the autotagger will apply to the
+  item, as flexible attributes if ``field`` is not a hardcoded field. Fields
+  already present on the track are overwritten. Parameter: ``data``
 * `mb_album_extract`: Like `mb_track_extract`, but for album tags. Overwrites
-  tags set at the track level, if they have the same ``field``.
-  Parameter: ``data``
+  tags set at the track level, if they have the same ``field``. Parameter:
+  ``data``
 
-The included ``mpdupdate`` plugin provides an example use case for event listeners.
+The included ``mpdupdate`` plugin provides an example use case for event
+listeners.
 
 Extend the Autotagger
 ^^^^^^^^^^^^^^^^^^^^^
@@ -462,9 +460,9 @@ Multiple stages run in parallel but each stage processes only one task at a time
 and each task is processed by only one stage at a time.
 
 Plugins provide stages as functions that take two arguments: ``config`` and
-``task``, which are ``ImportSession`` and ``ImportTask`` objects (both defined in
-``beets.importer``). Add such a function to the plugin's ``import_stages`` field
-to register it::
+``task``, which are ``ImportSession`` and ``ImportTask`` objects (both defined
+in ``beets.importer``). Add such a function to the plugin's ``import_stages``
+field to register it::
 
     from beets.plugins import BeetsPlugin
     class ExamplePlugin(BeetsPlugin):

docs/dev/plugins.rst

@@ -161,12 +161,11 @@ it's helpful to run on the "bleeding edge". To run the latest source:
          git clone https://github.com/beetbox/beets.git
          poetry install
 
-      This approach lets you decide where the
-      source is stored, with any changes immediately reflected in your
-      environment.
+      This approach lets you decide where the source is stored, with any
+      changes immediately reflected in your environment.
 
-More details about the beets source are available on the :doc:`developer documentation </dev/index>`
-pages.
+More details about the beets source are available on the :doc:`developer
+documentation </dev/index>` pages.
 
 
 .. _bugs:
@@ -240,7 +239,8 @@ move all your files.
 If you've already moved your music *outside* of beets, you have a few options:
 
 - Move the music back (with an ordinary ``mv``) and then use the above steps.
-- Delete your database and re-create it from the new paths using ``beet import -AWC``.
+- Delete your database and re-create it from the new paths using ``beet import
+  -AWC``.
 - Resort to manually modifying the SQLite database (not recommended).
 
 

docs/faq.rst

@@ -109,8 +109,8 @@ using the :ref:`modify-cmd` command::
 
 By default, beets will show you the changes that are about to be applied and ask
 if you really want to apply them to all, some or none of the items or albums.
-You can type y for "yes", n for "no", or s for "select". If you choose the latter,
-the command will prompt you for each individual matching item or album.
+You can type y for "yes", n for "no", or s for "select". If you choose the
+latter, the command will prompt you for each individual matching item or album.
 
 Then :doc:`query </reference/query>` your music just as you would with any
 other field::

docs/guides/advanced.rst

@@ -21,33 +21,33 @@ Beets works on Python 3.8 or later.
 * On **Debian or Ubuntu**, depending on the version, beets is available as an
   official package (`Debian details`_, `Ubuntu details`_), so try typing:
   ``apt-get install beets``. But the version in the repositories might lag
-  behind, so make sure you read the right version of these docs. If you want
-  the latest version, you can get everything you need to install with pip
-  as described below by running:
-  ``apt-get install python-dev python-pip``
-
-* On **Arch Linux**, `beets is in [extra] <Arch extra_>`_, so just run ``pacman -S
-  beets``. (There's also a bleeding-edge `dev package <AUR_>`_ in the AUR, which will
-  probably set your computer on fire.)
-
-* On **Alpine Linux**, `beets is in the community repository <Alpine package_>`_
-  and can be installed with ``apk add beets``.
+  behind, so make sure you read the right version of these docs. If you want the
+  latest version, you can get everything you need to install with pip as
+  described below by running: ``apt-get install python-dev python-pip``
+* On **Arch Linux**, `beets is in [extra] <Arch extra_>`_, so just run ``pacman
+  -S beets``. (There's also a bleeding-edge `dev package <AUR_>`_ in the AUR,
+  which will probably set your computer on fire.)
+* On **Alpine Linux**, `beets is in the community repository <Alpine
+  package_>`_ and can be installed with ``apk add beets``.
 
 * For **Gentoo Linux**, beets is in Portage as ``media-sound/beets``. Just run
   ``emerge beets`` to install. There are several USE flags available for
   optional plugin dependencies.
 
 * On **FreeBSD**, there's a `beets port <FreeBSD_>`_ at ``audio/beets``.
 
-* On **OpenBSD**, there's a `beets port <OpenBSD_>`_ can be installed with ``pkg_add beets``.
+* On **OpenBSD**, there's a `beets port <OpenBSD_>`_ can be installed with
+  ``pkg_add beets``.
 
 * For **Slackware**, there's a `SlackBuild`_ available.
 
-* On **Fedora** 22 or later, there's a `DNF package`_ you can install with ``sudo dnf install beets beets-plugins beets-doc``.
+* On **Fedora** 22 or later, there's a `DNF package`_ you can install with
+  ``sudo dnf install beets beets-plugins beets-doc``.
 
 * On **Solus**, run ``eopkg install beets``.
 
-* On **NixOS**, there's a `package <NixOS_>`_ you can install with ``nix-env -i beets``.
+* On **NixOS**, there's a `package <NixOS_>`_ you can install with ``nix-env -i
+  beets``.
 
 .. _DNF package: https://packages.fedoraproject.org/pkgs/beets/
 .. _SlackBuild: https://slackbuilds.org/repository/14.2/multimedia/beets/
@@ -277,13 +277,15 @@ put the field before the term, separated by a : character. So ``album:bird``
 only looks for ``bird`` in the "album" field of your songs. (Need to know more?
 :doc:`/reference/query/` will answer all your questions.)
 
-The ``beet list`` command also has an ``-a`` option, which searches for albums instead of songs::
+The ``beet list`` command also has an ``-a`` option, which searches for albums
+instead of songs::
 
     $ beet ls -a forever
     Bon Iver - For Emma, Forever Ago
     Freezepop - Freezepop Forever
 
-There's also an ``-f`` option (for *format*) that lets you specify what gets displayed in the results of a search::
+There's also an ``-f`` option (for *format*) that lets you specify what gets
+displayed in the results of a search::
 
     $ beet ls -a forever -f "[$format] $album ($year) - $artist - $title"
     [MP3] For Emma, Forever Ago (2009) - Bon Iver - Flume

docs/guides/main.rst

@@ -268,9 +268,10 @@ files, but can get confused when files don't have any metadata (or have wildly
 incorrect metadata). In this case, you need *acoustic fingerprinting*, a
 technology that identifies songs from the audio itself. With fingerprinting,
 beets can autotag files that have very bad or missing tags. The :doc:`"chroma"
-plugin </plugins/chroma>`, distributed with beets, uses the `Chromaprint`_ open-source fingerprinting technology, but it's disabled by default. That's because
-it's sort of tricky to install. See the :doc:`/plugins/chroma` page for a guide
-to getting it set up.
+plugin </plugins/chroma>`, distributed with beets, uses the `Chromaprint`_
+open-source fingerprinting technology, but it's disabled by default. That's
+because it's sort of tricky to install. See the :doc:`/plugins/chroma` page for
+a guide to getting it set up.
 
 Before you jump into acoustic fingerprinting with both feet, though, give beets
 a try without it. You may be surprised at how well metadata-based matching

docs/guides/tagger.rst

@@ -10,7 +10,8 @@ As an alternative the `beets-xtractor`_ plugin can be used.
 .. _AcousticBrainz: https://acousticbrainz.org/
 .. _beets-xtractor: https://github.com/adamjakab/BeetsPluginXtractor
 
-Enable the ``acousticbrainz`` plugin in your configuration (see :ref:`using-plugins`) and run it by typing::
+Enable the ``acousticbrainz`` plugin in your configuration (see
+:ref:`using-plugins`) and run it by typing::
 
     $ beet acousticbrainz [-f] [QUERY]
 

docs/plugins/acousticbrainz.rst

@@ -53,7 +53,8 @@ With path formats configured like::
         comp: Various Artists/$album [$year]$atypes/...
 
 
-The default plugin configuration generates paths that look like this, for example::
+The default plugin configuration generates paths that look like this, for
+example::
 
     Aphex Twin/[1993][EP][Remix] On Remixes
     Pink Floyd/[1995][Live] p·u·l·s·e