Skip to content

Commit

Permalink
edits
Browse files Browse the repository at this point in the history
  • Loading branch information
kjhealy committed Feb 29, 2016
1 parent d9b78fc commit 4b6eb54
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion plain-person-text.md
Expand Up @@ -366,7 +366,7 @@ clean:
Note that the `pandoc` commands are interpreted single lines of text, not several lines separated by the `<return>` key. But you can use the `\` symbol to tell `make` to continue to the next line without a break. With this Makefile, typing `make pdf` would take all the `.md` files in the directory one at a time and run the pandoc command to turn each one into a PDF, using the [APSR](https://www.apsanet.org/utils/journal.cfm?Journal=APSR) reference style, my latex template, and a `.bib` file called `socbib-pandoc.bib`.

You shouldn't use this `Makefile` blindly. Take the time to learn how `make` works and how it can help your project. The [official manual](https://www.gnu.org/software/make/manual/) is pretty clear. Make's backward-looking chain of prerequisites can make it tricky to write rules for complex projects. When writing or inspecting a `Makefile` and its specific rules, it can be helpful to use the `--dry-run` switch, as in `make --dry-run`. This will print out the sequence of commands `make` would run, but without actually executing them. You can try this with the `Makefile` in @lst:makefile in a directory with at least one `.md` file in it. For example, look at what `make pdf --dry-run` or `make docx --dry-run` or `make clean --dry-run` do.
You shouldn't use this `Makefile` blindly. Take the time to learn how `make` works and how it can help your project. The [official manual](https://www.gnu.org/software/make/manual/) is pretty clear. Make's backward-looking chain of prerequisites can make it tricky to write rules for complex projects. When writing or inspecting a `Makefile` and its specific rules, it can be helpful to use the `--dry-run` switch, as in `make --dry-run`. This will print out the sequence of commands `make` would run, but without actually executing them. You can try this with the `Makefile` in @lst:makefile in a directory with at least one `.md` file in it. For example, look at the list of commands produced by `make pdf --dry-run` or `make docx --dry-run` or `make clean --dry-run`.

The particular steps needed for many projects may be quite simple, and
not require the use of any variables or other frills. If you find
Expand Down

0 comments on commit 4b6eb54

Please sign in to comment.