public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Daniel Staal <DStaal-Jdbf3xiKgS8@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: ANN: pandoc 1.15.1
Date: Thu, 22 Oct 2015 22:24:36 -0400	[thread overview]
Message-ID: <E3A66936FA55968ECC185F1E@[192.168.1.50]> (raw)
In-Reply-To: <9e8030bd-8388-4cf7-88c9-ab29283e067b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

--As of October 22, 2015 6:36:01 AM -0700, John Muccigrosso is alleged to 
have said:

> FYI, I'm on Mavericks and getting pandoc through homebrew. Up to the
> latest  version with no problems.

--As for the rest, it is mine.

Mavericks is a couple generations newer than what I've got.  (You could 
actually upgrade to El Capitan if you wanted...)  I've got a couple 
problems trying that:  First off, my XCode install is broken, and I can't 
download the right version to fix it, since the latest version doesn't work 
with my OS.  Secondly, I've got an interesting disk setup - the OS + apps 
are on a small SSD, with my user files on a large HDD.  Homebrew is large, 
and installs to the system disk - filling it, last time I tried anything.

It's not that big a problem, really.  I mostly use Pandoc as a 
Markdown/HTML to 'simplified' HTML processor for FanFiction.net and a 
couple other similar sites, so most of the advanced features are things I 
can't use even if I wanted to.  But I like to stay up to date and try 
things on occasion.  ;)  So, I just wanted to know if this was a conscious 
choice or if it was just that something built against newer libraries 
unintentionally.

Daniel T. Staal

---------------------------------------------------------------
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---------------------------------------------------------------


  parent reply	other threads:[~2015-10-23  2:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 17:17 John MacFarlane
     [not found] ` <20151016171741.GA34974-jF64zX8BO08aTFSqC7bH4WZHpeb/A1Y/@public.gmane.org>
2015-10-18  1:58   ` dmccunney
     [not found]     ` <CAF4AJDx7mpk=+vJLCRkjzqZuantOPtud4P06ELqTAT4mP+a+kQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-18  5:49       ` John MacFarlane
2015-10-21 15:11   ` Thell Fowler
     [not found]     ` <3fdb7c66-d11d-4164-bd97-721290625e4f-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-10-21 20:36       ` John MACFARLANE
2015-10-22  1:29   ` Daniel Staal
2015-10-22 13:36     ` John Muccigrosso
     [not found]       ` <9e8030bd-8388-4cf7-88c9-ab29283e067b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-10-23  2:24         ` Daniel Staal [this message]
2015-10-23  3:07           ` John MacFarlane
2015-11-15 22:40     ` John MacFarlane
     [not found]       ` <20151115224049.GA18767-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2015-11-15 22:55         ` Daniel Staal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='E3A66936FA55968ECC185F1E@[192.168.1.50]' \
    --to=dstaal-jdbf3xikgs8@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).