BlogLiterately 0.5.2 → 0.5.2.1
raw patch · 3 files changed
+9/−5 lines, 3 filesdep ~base
Dependency ranges changed: base
Files
- BlogLiterately.cabal +2/−2
- CHANGES +4/−0
- doc/BlogLiteratelyDoc.lhs +3/−3
BlogLiterately.cabal view
@@ -1,5 +1,5 @@ Name: BlogLiterately-Version: 0.5.2+Version: 0.5.2.1 Synopsis: A tool for posting Haskelly articles to blogs Description: Write blog posts in Markdown format, then use BlogLiterately to do syntax highlighting, format ghci sessions, and upload@@ -48,7 +48,7 @@ location: http://patch-tag.com/r/byorgey/BlogLiterately Library- Build-Depends: base >= 4.0 && < 4.6,+ Build-Depends: base >= 4.0 && < 4.7, process, filepath, directory,
CHANGES view
@@ -1,3 +1,7 @@+0.5.2.1: 19 September 2012++ * bump base upper bound to <4.7+ 0.5.2: 20 August 2012 * improvement to behavior of --upload-images flag: cache uploaded
doc/BlogLiteratelyDoc.lhs view
@@ -225,13 +225,13 @@ Uploaded images, and their associated server URLs, will be tracked in a file called `.BlogLiterately-uploaded-images`. A given image will-only be uploaded once, even across multiple runs of @BlogLiterately@.-In practice, this means that the @--upload-images@ option can be left+only be uploaded once, even across multiple runs of `BlogLiterately`.+In practice, this means that the `--upload-images` option can be left on while uploading multiple draft versions of a post, and only new images will be uploaded each time. Note, however, that images are tracked by *file name*, not contents, so modifications to an image (while leaving the name the same) will be ignored. As a workaround,-delete @.BlogLiterately-uploaded-images@ (or just the entry for the+delete `.BlogLiterately-uploaded-images` (or just the entry for the modified image), or give the modified image a different name. A few caveats: