Remove trailing whitespaces

Author: snejus

docs/dev/library.rst

@@ -20,7 +20,7 @@ invocation of beets usually has only one :class:`Library`. It's powered by
 abstraction, something like a very minimal `ORM`_. The library is also
 responsible for handling queries to retrieve stored objects.
 
-Overview 
+Overview
 ''''''''
 
 You can add new items or albums to the library via the
@@ -64,7 +64,7 @@ We provide CRUD-like methods for interacting with the database:
 
 * :py:meth:`LibModel.store`
 * :py:meth:`LibModel.load`
-* :py:meth:`LibModel.remove` 
+* :py:meth:`LibModel.remove`
 * :py:meth:`LibModel.add`
 
 The base class :class:`beets.dbcore.Model` has a ``dict``-like interface, so

docs/guides/main.rst

@@ -103,13 +103,13 @@ get it right:
    box. If you do that, you can skip the next step.
 
 2. If you haven't done so already, set your ``PATH`` environment variable to
-   include Python and its scripts. To do so, open the "Settings" application, 
-   then access the "System" screen, then access the "About" tab, and then hit 
-   "Advanced system settings" located on the right side of the screen. This 
-   should open the "System Properties" screen, then select the "Advanced" tab, 
-   then hit the "Environmental Variables..." button, and then look for the PATH 
-   variable in the table. Add the following to the end of the variable's value: 
-   ``;C:\Python38;C:\Python38\Scripts``. You may need to adjust these paths to 
+   include Python and its scripts. To do so, open the "Settings" application,
+   then access the "System" screen, then access the "About" tab, and then hit
+   "Advanced system settings" located on the right side of the screen. This
+   should open the "System Properties" screen, then select the "Advanced" tab,
+   then hit the "Environmental Variables..." button, and then look for the PATH
+   variable in the table. Add the following to the end of the variable's value:
+   ``;C:\Python38;C:\Python38\Scripts``. You may need to adjust these paths to
    point to your Python installation.
 
 3. Now install beets by running: ``pip install beets``

docs/plugins/absubmit.rst

@@ -25,7 +25,7 @@ Then, install ``beets`` with ``absubmit`` extra
 
     pip install "beets[absubmit]"
 
-Lastly, enable the plugin in your configuration (see :ref:`using-plugins`). 
+Lastly, enable the plugin in your configuration (see :ref:`using-plugins`).
 
 
 Submitting Data

docs/plugins/chroma.rst

@@ -23,7 +23,7 @@ If you're willing to pay the performance cost for fingerprinting, read on!
 Installing Dependencies
 -----------------------
 
-To get fingerprinting working, you'll need to install three things: 
+To get fingerprinting working, you'll need to install three things:
 
 1. `pyacoustid`_ Python library (version 0.6 or later). You can install it by
    installing ``beets`` with ``chroma`` extra

docs/plugins/limit.rst

@@ -1,32 +1,32 @@
 Limit Query Plugin
 ==================
 
-``limit`` is a plugin to limit a query to the first or last set of 
-results. We also provide a query prefix ``'<n'`` to inline the same 
+``limit`` is a plugin to limit a query to the first or last set of
+results. We also provide a query prefix ``'<n'`` to inline the same
 behavior in the ``list`` command. They are analogous to piping results:
 
     $ beet [list|ls] [QUERY] | [head|tail] -n n
 
 There are two provided interfaces:
 
-1. ``beet lslimit [--head n | --tail n] [QUERY]`` returns the head or 
+1. ``beet lslimit [--head n | --tail n] [QUERY]`` returns the head or
 tail of a query
 
 2. ``beet [list|ls] [QUERY] '<n'`` returns the head of a query
 
-There are two differences in behavior: 
+There are two differences in behavior:
 
 1. The query prefix does not support tail.
 
-2. The query prefix could appear anywhere in the query but will only 
-have the same behavior as the ``lslimit`` command and piping to ``head`` 
+2. The query prefix could appear anywhere in the query but will only
+have the same behavior as the ``lslimit`` command and piping to ``head``
 when it appears last.
 
-Performance for the query previx is much worse due to the current  
-singleton-based implementation. 
+Performance for the query previx is much worse due to the current
+singleton-based implementation.
 
-So why does the query prefix exist? Because it composes with any other 
-query-based API or plugin (see :doc:`/reference/query`). For example, 
+So why does the query prefix exist? Because it composes with any other
+query-based API or plugin (see :doc:`/reference/query`). For example,
 you can use the query prefix in ``smartplaylist``
 (see :doc:`/plugins/smartplaylist`) to limit the number of tracks in a smart
 playlist for applications like most played and recently added.

docs/plugins/mpdstats.rst

@@ -51,7 +51,7 @@ configuration file. The available options are:
   beets library (e.g., because one is mounted on a NFS share), specify the path
   here.
 - **strip_path**: If your MPD library contains local path, specify the part to remove
-  here. Combining this with **music_directory** you can mangle MPD path to match the 
+  here. Combining this with **music_directory** you can mangle MPD path to match the
   beets library one.
   Default: The beets library directory.
 - **rating**: Enable rating updates.

docs/plugins/parentwork.rst

@@ -37,7 +37,7 @@ This plugin adds seven tags:
   that has a composition date. Format: yyyy-mm-dd.
 - **parentwork_workid_current**: The MusicBrainz id of the work as it was when
   the parentwork was retrieved. This tag exists only for internal bookkeeping,
-  to keep track of recordings whose works have changed. 
+  to keep track of recordings whose works have changed.
 - **parentwork_date**: The composition date of the parent work.
 
 To use the ``parentwork`` plugin, enable it in your configuration (see
@@ -50,7 +50,7 @@ To configure the plugin, make a ``parentwork:`` section in your
 configuration file. The available options are:
 
 - **force**: As a default, ``parentwork`` only fetches work info for
-  recordings that do not already have a ``parentwork`` tag or where 
+  recordings that do not already have a ``parentwork`` tag or where
   ``mb_workid`` differs from ``parentwork_workid_current``. If ``force``
   is enabled, it fetches it for all recordings.
   Default: ``no``

docs/plugins/play.rst

@@ -99,7 +99,7 @@ indicates that you need to insert extra arguments before specifying the
 playlist.
 
 The ``--yes`` (or ``-y``) flag to the ``play`` command will skip the warning
-message if you choose to play more items than the **warning_threshold** 
+message if you choose to play more items than the **warning_threshold**
 value usually allows.
 
 Note on the Leakage of the Generated Playlists

docs/plugins/spotify.rst

@@ -85,8 +85,8 @@ in config.yaml under the ``spotify:`` section:
   Default: None.
 - **search_query_ascii**: If set to ``yes``, the search query will be converted to
   ASCII before being sent to Spotify. Converting searches to ASCII can
-  enhance search results in some cases, but in general, it is not recommended. 
-  For instance `artist:deadmau5 album:4×4` will be converted to 
+  enhance search results in some cases, but in general, it is not recommended.
+  For instance `artist:deadmau5 album:4×4` will be converted to
   `artist:deadmau5 album:4x4` (notice `×!=x`).
   Default: ``no``.
 

docs/reference/cli.rst

@@ -116,7 +116,7 @@ Optional command flags:
   ``incremental`` configuration option.
 
 * If you don't want to record skipped files during an *incremental* import, use
-  the ``--incremental-skip-later`` flag which corresponds to the 
+  the ``--incremental-skip-later`` flag which corresponds to the
   ``incremental_skip_later`` configuration option.
   Setting the flag prevents beets from persisting skip decisions during a
   non-interactive import so that a user can make a decision regarding
@@ -359,7 +359,7 @@ on disk.
 By default, all the changed metadata will be populated back to the database.
 If you only want certain fields to be written, specify them with the ```-F```
 flags (which can be used multiple times). Alternatively, specify fields to *not*
-write with ```-e``` flags (which can be used multiple times). For the list of 
+write with ```-e``` flags (which can be used multiple times). For the list of
 supported fields, please see ```beet fields```.
 
 When an updated track is part of an album, the album-level fields of *all*