aboutsummaryrefslogtreecommitdiff
path: root/lisp
diff options
context:
space:
mode:
authorTim Landscheidt <tim@tim-landscheidt.de>2010-06-27 17:33:35 +0000
committerTim Landscheidt <tim@tim-landscheidt.de>2010-06-27 17:33:35 +0000
commitda9f87ffd68f7b63843da2910d94281b41f18984 (patch)
tree608f98ee6162f336a14331cb88d7c905f9ea49d4 /lisp
parented6a77997d4228d6a6a3da1a880e7672a2853829 (diff)
Fix typos and spacing.
* AUTHORS, FAQ, NEWS, README, lisp/emms-bookmarks.el, lisp/emms-cache.el, lisp/later-do.el: Fix typos and spacing.
Diffstat (limited to 'lisp')
-rw-r--r--lisp/emms-bookmarks.el10
-rw-r--r--lisp/emms-cache.el6
-rw-r--r--lisp/later-do.el13
3 files changed, 14 insertions, 15 deletions
diff --git a/lisp/emms-bookmarks.el b/lisp/emms-bookmarks.el
index 5e6f516..e3b1747 100644
--- a/lisp/emms-bookmarks.el
+++ b/lisp/emms-bookmarks.el
@@ -23,12 +23,12 @@
;;; Commentary:
;;
-;; You can use this to add "temporal bookmarks" (term by Lucas Bonnet)
-;; into your media files. The interesting functions here are
+;; You can use this to add ``temporal bookmarks'' (term by Lucas
+;; Bonnet) to your media files. The interesting functions here are
;; `emms-bookmarks-next', `emms-bookmarks-prev', `emms-bookmarks-add'
;; (which pauses the player while you describe the bookmark) and
-;; `emms-bookmarks-clear'. All of which do exactly what you think they
-;; do.
+;; `emms-bookmarks-clear'. All of which do exactly what you think
+;; they do.
;;; Code:
@@ -132,7 +132,7 @@ FAILURE-MESSAGE should be a string."
(defun emms-bookmarks-add ()
"Add a new bookmark to the current track.
-This function pauses the player while promting the user for a
+This function pauses the player while prompting the user for a
description of the bookmark. The function resumes the player
after the prompt."
(interactive)
diff --git a/lisp/emms-cache.el b/lisp/emms-cache.el
index 2262c7c..4741cbf 100644
--- a/lisp/emms-cache.el
+++ b/lisp/emms-cache.el
@@ -25,11 +25,11 @@
;;; Commentary:
;; The cache is a mapping of a full path name to information, and so
-;; it is invalidated when you rename or move files about. It also does
-;; not differentiate between file or uri tracks.
+;; it is invalidated when you rename or move files about. It also
+;; does not differentiate between file or uri tracks.
;; Because cache lookups are much faster than disk access, this works
-;; much better with a later-do-interval of something like 0.001. Also
+;; much better with a later-do-interval of something like 0.001. Also
;; consider using synchronous mode, as it's quite fast now.
;; This code is activated by (emms-standard) and above.
diff --git a/lisp/later-do.el b/lisp/later-do.el
index 61be86b..d8222ae 100644
--- a/lisp/later-do.el
+++ b/lisp/later-do.el
@@ -22,7 +22,7 @@
;;; Commentary
-;; This file will execute lisp code "later on". This way it is
+;; This file will execute lisp code ``later on''. This way it is
;; possible to work while elisp does some longer calculations, if you
;; can convert those calculations into a sequence of function calls.
@@ -42,17 +42,16 @@
:type 'number)
(defvar later-do-list nil
- "A list of functions to be called lateron.")
+ "A list of functions to be called later on.")
(defvar later-do-timer nil
"The timer that later-do uses.")
(defun later-do (function &rest args)
- "Apply FUNCTION to ARGS later on. This is an unspecified amount of
-time after this call, and definitely not while lisp is still
-executing.
-Code added using `later-do' is guaranteed to be executed in the
-sequence it was added."
+ "Apply FUNCTION to ARGS later on. This is an unspecified
+amount of time after this call, and definitely not while lisp is
+still executing. Code added using `later-do' is guaranteed to be
+executed in the sequence it was added."
(setq later-do-list (nconc later-do-list
(list (cons function args))))
(unless later-do-timer