First we’ll define the variables.

(defvar insert-time-format "%X"
  "*Format for \[insert-time] (c.f. 'format-time-string').")
(defvar insert-date-format "%x"
  "*Format for \[insert-date] (c.f. 'format-time-string').")

There are two new things to note about these docstrings.

All variables that are shared between two or more functions should be declared with defvar. Which of those should be user options? A rule of thumb is that if the variable directly controls a user-visible feature that a user might want to change, and if setting that variable is straightforward (i.e., no complex data structures or specially coded values), then it should be a user option.

Now that we’ve defined the variables that control insert-time and insert-date, here are the definitions of those simple functions.

(defun insert-time ()
  "Insert the current time according to insert-time-format."
  (interactive "*")
  (insert (format-time-string insert-time-format
                              (current-time))))
(defun insert-date ()
  "Insert the current date according to insert-date-format."
  (interactive "*")
  (insert (format-time-string insert-date-format
                              (current-time))))

The two functions are identical except that one uses insert-time-format where the other uses insert-date-format. The insert function takes any number of arguments (which must all be strings or characters) and inserts them one after another in the current buffer at the present location of point, moving point forward.

The main thing to notice about these functions is that each begins with

(interactive "*")

By now you know that interactive turns a function into a command and specifies how to obtain the function’s arguments when invoked interactively. But we haven’t seen * in the argument of interactive before, and besides, these functions take no arguments, so why does interactive have one?

The asterisk, when it is the first character in an interactive argument, means “abort this function if the current buffer is read-only.” It is better to detect a read-only buffer before a function begins its work than to let it get halfway through then die from a “Buffer is read-only” error. In this case, if we omitted to check for read-onlyness, the call to insert would trigger its own “Buffer is read-only” error almost right away and no harm done. A more complicated function, though, might cause irreversible side effects (such as changing global variables), expecting to be able to finish, before discovering that it can’t.

The first thing we’ll need is a way to run our writestamp-updating code each time the file is saved. As we discovered in the section Hooks in Chapter 2, the best way to associate some code with a common action (such as saving a file) is by adding a function to a hook variable, provided that a suitable hook variable exists. Using M-x apropos RET hook RET, we discover four promising hook variables: after-save-hook, local-write-file-hooks, write-contents-hooks, and write-file-hooks.

We can discard after-save-hook right away. We don’t want our code executed, modifying writestamps, after the file is saved, because then it will be impossible to save an up-to-date version of the file!

The differences between the remaining candidates are subtle:

We’ll rule out write-file-hooks because we’ll want to invoke our writestamp-updater only in buffers that have writestamps, not every time any buffer is saved. And, hair-splitting semantics aside, we’ll rule out write-contents-hooks because we want our chosen hook variable to be immune to changes in the buffer’s major mode. That leaves local-write-file-hooks.

Now, what should the writestamp updater that we’ll put in local-write-file-hooks do? It must locate each writestamp, delete it, and replace it with an updated one. The most straightforward approach is to surround each writestamp with a distinguishing string of characters that we can search for. Let’s say that each writestamp is surrounded by the strings " WRITESTAMP((" on the left and "))" on the right, so that in a file it looks something like this:

...
went into the castle and lived happily ever after.
The end. WRITESTAMP((12:19pm 7 Jul 96))

Let’s say that the stuff inside the WRITESTAMP((…)) is put there by insert-date (which we defined earlier) and so its format can be controlled with insert-date-format.

Now, supposing we have some writestamps in the file to begin with,^[20] we can update it at file-writing time like so:

(add-hook 'local-write-file-hooks 'update-writestamps)
(defun update-writestamps ()
  "Find writestamps and replace them with the current time."
  (save-excursion
    (save-restriction
      (save-match-data
        (widen)
        (goto-char (point-min))
        (while (search-forward "WRITESTAMP((" nil t)
          (let ((start (point)))
            (search-forward "))")
            (delete-region start (- (point) 2))
            (goto-char start)
            (insert-date))))))
  nil)

There’s a lot here that’s new. Let’s go through this function a line at a time.

First we notice that the body of the function is wrapped inside a call to save-excursion. What save-excursion does is memorize the position of the cursor, execute the subexpressions it’s given as arguments, then restore the cursor to its original position. It’s useful in this case because the body of the function is going to move the cursor all over the buffer, but by the time the function finishes we’d like the caller of this function to perceive no cursor motion. There’ll be much more about save-excursion in Chapter 8.

Next is a call to save-restriction. This is like save-excursion in that it memorizes some information, then executes its arguments, then restores the information. The information in this case is the buffer’s restriction, which is the result of narrowing. Narrowing is covered in Chapter 9. For now let’s just say that narrowing refers to Emacs’s ability to show only a portion of a buffer. Since update-writestamps is going to call widen, which undoes the effect of any narrowing, we need save-restriction in order to clean up after ourselves.

Next is a call to save-match-data that, like save-excursion and save-restriction, memorizes some information, executes its arguments, then restores the information. This time the information in question is the result of the latest search. Each time a search occurs, information about the result of the search is stored in some global variables (as we will see shortly). Each search wipes out the result of the previous search. Our function will perform a search, but for the sake of other functions that might be calling ours, we don’t want to disrupt the global match data.

Next is a call to widen. As previously mentioned, this undoes any narrowing in effect. It makes the entire buffer accessible, which is necessary if every write-stamp is to be found and updated.

Next we move the cursor to the beginning of the buffer with (goto-char (point-min)) in preparation for the function’s main loop, which is going to search for each successive writestamp and rewrite it in place. The function point-min returns the minimum value for point, normally 1. (The only time (point-min) might not be 1 is when there’s narrowing in effect. Since we’ve called widen, we know narrowing is not in effect, so we could write (goto-char 1) instead. But it’s good practice to use point-min where appropriate.)

The main loop looks like this:

(while (search-forward "WRITESTAMP((" nil t)
  ...)

This is a while loop, which works very much like while loops in other languages. Its first argument is an expression that is tested each time around the loop. If the expression evaluates to true, the remaining arguments are executed and the whole cycle repeats.

The expression (search-forward "WRITESTAMP((" nil t) searches for the first occurrence of the given string, starting from the current location of point. The nil means the search is not bounded except by the end of the buffer. This is explained in more detail later. The t means that if no match is found, search-forward should simply return nil. (Without the t, search-forward signals an error, aborting the current command, if no match is found.) If the search is successful, point is moved to the first character after the matched text, and search-forward returns that position. (It’s possible to find where the match began using match-beginning, which is shown in Figure 4-1.)

Figure 4-1. After searching for the string WRITESTAMP((

The body of the while loop is

(let ((start (point)))
  ...)

This creates a temporary variable, start, that holds the location of point, which is the beginning of the date string inside the WRITESTAMP((…)) delimiters.

With start defined, the body of the let contains:

(search-forward "))")
(delete-region start (- (point) 2))
(goto-char start)
(insert-date)

This call to search-forward places point after the two closing parentheses. We still know the beginning of the timestamp, because this location is in start, as shown in Figure 4-2.

Figure 4-2. After searching for “))”

This time, only the first argument to search-forward, the search string, is given. Earlier we saw two additional arguments: the search bound, and whether to signal an error. When omitted, they default to nil (unbounded search) and nil (signal an error if the search fails).

After search-forward succeeds—and if it fails, an error is signaled and execution of the function never gets past search-forward—delete-region deletes the text region that is the date in the writestamp, starting at position start and ending before position (- (point) 2) (two characters to the left of point), leaving the results shown in Figure 4-3.

Figure 4-3. After deleting the region between start and (- (point) 2)

Next, (goto-char start) positions the cursor inside the writestamp delimiters and, finally, (insert-date) inserts the current date.

The while loop executes as many times as there are matches for the search string. It’s important that each time a match is found, the cursor remains “to the right” of the place where the match began. Otherwise, the next iteration of the loop will find the same match for the search string!

When the while loop is done, save-match-data returns, restoring the match data; then save-restriction returns, restoring any narrowing that was in effect; then save-excursion returns, restoring point to its original location.

The final expression of update-writestamps, after the call to save-excursion, is

nil

This is the function’s return value. The return value of a Lisp function is simply the value of the last expression in the function’s body. (All Lisp functions return a value, but so far every function we’ve written has done its job via “side effects” instead of by returning meaningful values.) In this case we force it to be nil. The reason is that functions in local-write-file-hooks are treated specially. Normally, the return value of a function in a hook variable doesn’t matter. But for functions in local-write-file-hooks (also in write-file-hooks and write-contents-hooks), a non-nil return value means, “This hook function has taken over the job of writing the buffer to a file.” If the hook function returns a non-nil value, the remaining functions in the hook variables are not called, and Emacs does not write the buffer to a file itself after the hook functions run. Since update-writestamps is not taking over the job of writing the buffer to a file, we want to be sure it returns nil.

This approach to implementing writestamps works, but there are a few problems. First, by hardwiring the strings " WRITESTAMP((" and "))" we’ve doomed the user to an unaesthetic and inflexible way to distinguish writestamps in text. Second, the user’s preference might not be to use insert-date for writestamps.

These problems are simple to fix. We can introduce three new variables: one that, like insert-date-format and insert-time-format, describes a time format to use; and two that describe the delimiters surrounding a writestamp.

(defvar writestamp-format "%C"
  "*Format for writestamps (c.f. 'format-time-string').")
(defvar writestamp-prefix "WRITESTAMP(("
  "*Unique string identifying start of writestamp.")
(defvar writestamp-suffix "))"
  "*String that terminates a writestamp.")

Now we can modify update-writestamps to be more configurable.

(defun update-writestamps ()
  "Find writestamps and replace them with the current time."
  (save-excursion
    (save-restriction
      (save-match-data
        (widen)
        (goto-char (point-min))
        (while (search-forward writestamp-prefix nil t)
          (let ((start (point)))
            (search-forward writestamp-suffix)
            (delete-region start (match-beginning 0))
            (goto-char start)
            (insert (format-time-string writestamp-format
                                        (current-time))))))))
  nil)

In this version of update-writestamps, we’ve replaced occurrences of "WRITESTAMP((" and "))" with writestamp-prefix and writestamp-suffix, and we’ve replaced insert-date with

(insert (format-time-string writestamp-format
                            (current-time)))

We also changed the call to delete-region. Previously it looked like this:

(delete-region start (- (point) 2))

That was when we had the writestamp suffix hardwired to be "))", which is two characters long. But now that the writestamp suffix is stored in a variable, we don’t know in advance how many characters long it is. We could certainly find out, by calling length:

(delete-region start (- (point)
                        (length writestamp-suffix)))

but a better solution is to use match-beginning. Remember that before the call to delete-region is

(search-forward writestamp-suffix)

No matter what writestamp-suffix is, search-forward finds the first occurrence of it, if one exists, and returns the first position after the match. But extra data about the match, notably the position where the match begins, is stored in Emacs’s global match-data variables. The way to access this data is with the functions match-beginning and match-end. For reasons that will become clear shortly, match-beginning needs an argument of 0 to tell you the position of the beginning of the match for the latest search. In this case, that happens to be the beginning of the writestamp suffix, which also happens to be the end of the date inside the writestamp, and therefore the end of the region to delete:

(delete-region start (match-beginning 0))

Suppose the user chooses "Written: " and "." as the writestamp-prefix and writestamp-suffix, so that writestamps appear like so: “Written: 19 Aug 1996.” This is a perfectly reasonable preference, but the string "Written: " is less likely than "WRITESTAMP((" to be completely unique. In other words, the file may contain occurrences of "Written: " that aren’t writestamps. When update-writestamps searches for writestamp-prefix, it might find one of these occurrences, then search for the next occurrence of a period and delete everything in between. Worse, this unwanted deletion takes place almost undetectably, just as the file is being saved, with the cursor location and other appearances preserved.

One way to solve this problem is to impose tighter constraints on how the writestamp may appear, making mismatches less likely. One natural restriction might be to require writestamps to appear alone on a line: in other words, a string is a writestamp only if writestamp-prefix is the first thing on the line and writestamp-suffix is the last thing on the line.

Now it won’t suffice to use

(search-forward writestamp-prefix ...)

to find writestamps, because this search isn’t constrained to find matches only at the beginnings of lines.

This is where regular expressions come in handy. A regular expression—called a regexp or regex for short—is a search pattern just like the first argument to search-forward. Unlike a normal search pattern, regular expressions have certain syntactic rules that allow more powerful kinds of searches. For example, in the regular expression '^Written: ', the caret (^) is a special character that means, “this pattern must match at the beginning of a line.” The remaining characters in the regexp '^Written: ' don’t have any special meaning in regexp syntax, so they match the same way ordinary search patterns do. Special characters are sometimes called metacharacters or (more poetically) magic.

Many UNIX programs use regular expressions, among them sed, grep, awk, and perl. The syntax of regular expressions tends to vary slightly from one application to another, unfortunately; but in all cases, most characters are non-"magic” (particularly letters and numbers) and can be used to search for occurrences of themselves; and longer regexps can be built up from shorter ones simply by stringing them together. Here is the syntax of regular expressions in Emacs.

As you can see, regular expression syntax uses backslashes for many purposes. So does Emacs Lisp string syntax. Since regexps are written as Lisp strings when programming Emacs, the two sets of rules for using backslashes can cause some confusing results. For example, the regexp ab|cd, when expressed as a Lisp string, must be written as "ab\|cd". Even stranger is when you want to match a single using the regexp \ : you must write the string "\\". Emacs commands that prompt for regular expressions (such as apropos and keep-lines) allow you to type them as regular expressions (not Lisp strings) when used interactively.

Now that we know how to assemble regular expressions, it might seem obvious that the way to search for writestamp-prefix at the beginning of a line is to prepend a caret onto writestamp-prefix and append a dollar sign onto writestamp-suffix, like so:

(re-search-forward (concat "^"
                           writestamp-prefix) ...)      ;wrong!
(re-search-forward (concat writestamp-suffix
                           "$") ...)                    ;wrong!

The function concat concatenates its string arguments into a single string. The function re-search-forward is the regular expression version of search-forward.

This is almost right. However, it contains a common and subtle error: either writestamp-prefix or writestamp-suffix may contain “magic” characters. In fact, writestamp-suffix does, in our example: it’s ".". Since . matches any character (except newline), this expression:

(re-search-forward (concat writestamp-suffix
                           "$") ...)

which is equivalent to this expression:

(re-search-forward ".$" ...)

matches any character at the end of a line, whereas we only want to match a period (.).

When building up a regular expression as in this example, using pieces such as writestamp-prefix whose content is beyond the programmer’s control, it is necessary to “remove the magic” from strings that are meant to be taken literally. Emacs provides a function for this purpose called regexp-quote, which understands regexp syntax and can turn a possibly-magic string into the corresponding non-magic one. For example, (regexp-quote ".") yields "\." as a string. You should always use regexp-quote to remove the magic from variable strings that are used to build up regular expressions.

We now know how to begin a new version of update-writestamps:

(defun update-writestamps ()
  "Find writestamps and replace them with the current time."
  (save-excursion
    (save-restriction
      (save-match-data
        (widen)
        (goto-char (point-min))
        (while (re-search-forward
                (concat "^"
                        (regexp-quote writestamp-prefix))
                nil t)
          ...))))
  nil)

Let’s finish our new version of update-writestamps by filling in the body of the while loop. Just after re-search-forward succeeds, we need to know whether the current line ends with writestamp-suffix. But we can’t simply write

(re-search-forward (concat (regexp-quote writestamp-suffix)
                           "$"))

because that could find a match several lines away. We’re only interested in knowing whether the match is on the current line.

One solution is to limit the search to the current line. The optional second argument to search-forward and re-search-forward, if non-nil, is a buffer position beyond which the search may not go. If we plug in the buffer position corresponding to the end of the current line like so:

(re-search-forward (concat (regexp-quote writestamp-suffix)
                           "$")
                   end-of-line-position)

then the search is limited to the current line, and we’ll have the answer we need. So how do we come up with end-of-line-position? We simply put the cursor at the end of the current line using end-of-line, then query the value of point. But after we do that and before re-search-forward begins, we must make sure to return the cursor to its original location since the search must start from there. Moving the cursor then restoring it is exactly what save-excursion is designed to do. So we could write:

(let ((end-of-line-position (save-excursion
                              (end-of-line)
                              (point))))
  (re-search-forward (concat (regexp-quote writestamp-suffix)
                             "$")
                     end-of-line-position))

which creates a temporary variable, end-of-line-position, that is used to limit re-search-forward; but it’s simpler not to use a temporary variable if we don’t really need it:

(re-search-forward (concat (regexp-quote writestamp-suffix)
                           "$")
                   (save-excursion
                     (end-of-line)
                     (point)))

Observe that the value of the save-excursion expression is, like so many other Lisp constructs, the value of its last subexpression (point).

So update-writestamps can be written like this:

(defun update-writestamps ()
  "Find writestamps and replace them with the current time."
  (save-excursion
    (save-restriction
      (save-match-data
        (widen)
        (goto-char (point-min))
        (while (re-search-forward
                (concat "^"
                        (regexp-quote writestamp-prefix))
                nil t)
          (let ((start (point)))
            (if (re-search-forward (concat (regexp-quote
                                            writestamp-suffix)
                                           "$")
                                   (save-excursion
                                      (end-of-line)
                                      (point))
                                   t)
              (progn
                (delete-region start (match-beginning 0))
                (goto-char start)
                (insert (format-time-string writestamp-format
                                            (current-time))))))))))
  nil)

Notice that both calls to re-search-forward have t as the optional third argument, meaning “if the search fails, return nil (as opposed to signaling an error).”

We have created a more or less straightforward translation of update-writestamps from its original form to use regular expressions, but it doesn’t really exploit the power of regexps. In particular, the entire sequence of finding a writestamp prefix, checking for a matching writestamp suffix on the same line, and replacing the text in between can be reduced to just these two expressions:

(re-search-forward (concat "^"
                           (regexp-quote writestamp-prefix)
                           "\(.*\)"
                           (regexp-quote writestamp-suffix)
                           "$"))
(replace-match (format-time-string writestamp-format
                                   (current-time))
               t t nil 1)

The first expression, the call to re-search-forward, constructs a regexp that looks like this:

^prefix(.*)suffix$

where prefix and suffix are regexp-quoted versions of writestamp-prefix and writestamp-suffix. This regexp matches one entire line, beginning with the writestamp prefix, followed by any string (which is made a submatch by the use of (…)), and ending with the writestamp suffix.

The second expression is a call to replace-match, which replaces some or all of the matched text from a previous search. It’s used like this:

(replace-match  new-string
                preserve-case
                literal
                base-string
                subexpression)

The first argument is the new string to insert, which in this example is the result of format-time-string. The remaining arguments, which are all optional, have the following meanings:

So after finding the writestamp with re-search-forward and “submatching” the text between the delimiters, our call to replace-match snips out the text between the delimiters and inserts a fresh new string formatted according to writestamp-format.

As a final improvement to update-writestamps, we can observe that if we write

(while (re-search-forward (concat ...) ...)
  (replace-match ...))

then the concat function is called each time through the loop, constructing a new string each time even though its arguments never change. This is inefficient. It would be better to compute the desired string once, before the loop, and store it in a temporary variable. The best way to write update-writestamps is therefore:

(defun update-writestamps ()
  "Find writestamps and replace them with the current time."
  (save-excursion
    (save-restriction
      (save-match-data
        (widen)
        (goto-char (point-min))
        (let ((regexp (concat "^"
                              (regexp-quote writestamp-prefix)
                              "\(.*\)"
                              (regexp-quote writestamp-suffix)
                              "$")))
          (while (re-search-forward regexp nil t)
            (replace-match (format-time-string writestamp-format
                                               (current-time))
                           t t nil 1))))))
  nil)

Emacs has a hook variable called first-change-hook. Whenever a buffer is changed for the first time since it was last saved, the functions in first-change-hook get executed. Implementing modifystamps by using this hook merely entails moving our old update-writestamps function from local-write-file-hooks to first-change-hook. Of course, we’ll also want to change its name to update-modifystamps, and introduce new variables—modifystamp-format, modifystamp-prefix, and modifystamp-suffix—that work like their writestamp counterparts without overloading the writestamp variables. Then update-modifystamps should be changed to use the new variables.

Before any of this happens, first-change-hook, which is normally global, should be made buffer-local. If we add update-modifystamps to first-change-hook while it is still global, update-modifystamps will be called every time any buffer is saved. Making it buffer-local in the current buffer causes changes to the variable to be invisible outside that buffer. Other buffers continue to use the default global value.

(make-local-hook 'first-change-hook)

Although ordinary variables are made buffer-local with either make-local-variable or make-variable-buffer-local (see below), hook variables must be made buffer-local with make-local-hook.

(defvar modifystamp-format "%C"
  "*Format for modifystamps (c.f. 'format-time-string').")
(defvar modifystamp-prefix "MODIFYSTAMP(("
  "*String identifying start of modifystamp.")
(defvar modifystamp-suffix "))"
  "*String that terminates a modifystamp.")
 (defun update-modifystamps ()
  "Find modifystamps and replace them with the current time."
  (save-excursion
    (save-restriction
      (save-match-data
        (widen)
        (goto-char (point-min))
        (let ((regexp (concat "^"
                              (regexp-quote modifystamp-prefix)
                              "\(.*\)"
                              (regexp-quote modifystamp-suffix)
                              "$")))
          (while (re-search-forward regexp nil t)
            (replace-match (format-time-string modifystamp-format
                                               (current-time))
                           t t nil 1))))))
  nil)
(add-hook 'first-change-hook 'update-modifystamps nil t)

The nil argument to add-hook is just a place holder. We care only about the last argument, t, which means “change only the buffer-local copy of first-change-hook.”

The problem with this approach is that if you make ten changes to the file before saving it, the modifystamps will contain the time of the first change, not the last change. Close enough for some purposes, but we can do better.

This time we’ll go back to using local-write-file-hooks, but we’ll call update-modifystamps from it only if buffer-modified-p returns true, which tells us that the current buffer has been modified since it was last saved:

(defun maybe-update-modifystamps ()
  "Call 'update-modifystamps' if the buffer has been modified."
  (if (buffer-modified-p)
      (update-modifystamps)))
(add-hook 'local-write-file-hooks 'maybe-update-modifystamps)

Now we have the opposite problem from simple approach #1: the last-modified time isn’t computed until the file is saved, which may be much later than the actual time of the last modification. If you make a change to the file at 2:00 and save at 3:00, the modifystamps will record 3:00 as the last-modified time. This is a closer approximation, but it’s still not perfect.

Theoretically, we could call update-modifystamps after every change to the buffer, but in practice it’s prohibitively expensive to scan through the whole file and rewrite parts of it after every keystroke. But it’s not too expensive to memorize the current time after each buffer change. Then, when the buffer is saved to a file, the memorized time can be used for computing the time in the modifystamps.

The hook variable after-change-functions contains functions to call after each buffer change. First let’s make it buffer-local:

(make-local-hook 'after-change-functions)

Now we define a buffer-local variable to hold this buffer’s latest modification time:

(defvar last-change-time nil
  "Time of last buffer modification.")
(make-variable-buffer-local 'last-change-time)

The function make-variable-buffer-local causes the named variable to have a separate, buffer-local value in every buffer. This is subtly different from make-local-variable, which makes a variable have a buffer-local value in the current buffer while allowing other buffers to share the same global value. In this case, we use make-variable-buffer-local because there is no meaningful global value of last-change-time for other buffers to share.

Now we need a function to set last-change-time each time the buffer changes. Let’s call it remember-change-time and add it to after-change-functions:

(add-hook 'after-change-functions 'remember-change-time nil t)

Functions in after-change-functions are passed three arguments describing the change that just took place (see the section called Mode Meat in Chapter 7). But remember-change-time doesn’t care what the change was; only that there was a change. So we’ll allow remember-change-time to take arguments, but we’ll ignore them.

(defun remember-change-time (&rest unused)
  "Store the current time in 'last-change-time'."
  (setq last-change-time (current-time)))

The keyword &rest, followed by a parameter name, must appear last in a function’s parameter list. It means “collect up any remaining arguments into a list and assign it to the last parameter” (unused in this case). The function may have other parameters, including &optional ones, but these must precede the &rest parameter. After all the other parameters are assigned in the normal fashion, the &rest parameter gets a list of whatever’s left. So if a function is defined as

(defun foo (a b &rest c)
  ...)

and is called with (foo 1 2 3 4), then a will be 1, b will be 2, and c will be the list (3 4).

In some situations, &rest is very useful, even necessary; but right now we’re only using it out of laziness (or economy, if you prefer), to avoid having to name three separate parameters that we don’t plan to use.

Now we must revise update-modifystamps: it must use the time stored in last-change-time instead of using (current-time). For efficiency, it should also reset last-change-time to nil when it is done, so if the file is subsequently saved without being modified, we can avoid the overhead of calling update-modifystamps.

(defun update-modifystamps ()
  "Find modifystamps and replace them with the saved time."
  (save-excursion
    (save-restriction
      (save-match-data
        (widen)
        (goto-char (point-min))
        (let ((regexp (concat "^"
                              (regexp-quote modifystamp-prefix)
                              "\(.*\)"
                              (regexp-quote modifystamp-suffix)
                              "$")))
          (while (re-search-forward regexp nil t)
            (replace-match (format-time-string modifystamp-format
                                               last-change-time)
                           t t nil 1))))))
  (setq last-change-time nil)
  nil)

Finally, we wish not to call update-modifystamps when last-change-time is nil:

(defun maybe-update-modifystamps ()
  "Call 'update-modifystamps' if the buffer has been modified."
  (if last-change-time      ;instead of testing (buffer-modified-p)
      (update-modifystamps)))

There’s still one important thing missing from maybe-update-modifystamps. Before reading ahead to the next section, can you figure out what it is?

The problem is that every time a modifystamp gets rewritten by update-modifystamps, the buffer changes, causing last-change-time to change! Only the first modifystamp will be correctly rewritten. Subsequent ones will contain a time much closer to when the file was saved than when the last modification was made.

One way around this problem is to temporarily set the value of after-change-functions to nil while executing update-modifystamps as shown below.

(add-hook 'local-write-file-hooks
          '(lambda ()
             (if last-change-time
                 (let ((after-change-functions nil))
                   (update-modifystamps)))))

This use of let creates a temporary variable, after-change-functions, that supersedes the global after-change-functions during the call to update-modifystamps in the body of the let. After the let exits, the temporary after-change-functions disappears and the global one is again in effect.

This solution has a drawback: if there are other functions in after-change-functions, they’ll also be disabled during the call to update-modifystamps, though you might not intend for them to be.

A better solution would be to “capture” the value of last-change-time before any modifystamps are updated. That way, when updating the first modifystamp causes last-change-time to change, the new value of last-change-time won’t affect any remaining modifystamps because update-modifystamps won’t be referring to last-change-time.

The simplest way to “capture” the value of last-change-time is to pass it as an argument to update-modifystamps:

(add-hook 'local-write-file-hooks
          '(lambda ()
             (if last-change-time
                 (update-modifystamps last-change-time))))

This requires changing update-modifystamps to take one argument and use it in the call to format-time-string:

(defun update-modifystamps (time)
  "Find modifystamps and replace them with the given time."
  (save-excursion
    (save-restriction
      (save-match-data
        (widen)
        (goto-char (point-min))
        (let ((regexp (concat "^"
                              (regexp-quote modifystamp-prefix)
                              "\(.*\)"
                              (regexp-quote modifystamp-suffix)
                              "$")))
          (while (re-search-forward regexp nil t)
            (replace-match (format-time-string modifystamp-format
                                               time)
                           t t nil 1))))))
  (setq last-change-time nil)
  nil)

You might be thinking that setting up a buffer to use modifystamps involves evaluating a lot of expressions and setting up a lot of variables, and that it seems hard to keep track of what’s needed to make modifystamps work. If so, you’re right. So in the next chapter, we’ll look at how you can encapsulate a collection of related functions and variables in a Lisp file.