Skip to content
Commits on Jun 13, 2014
  1. @uwiger

    Merge pull request #30 from esl/uw-br-fix

    use <br /> instead of <br></br>
    uwiger committed Jun 13, 2014
Commits on Jun 12, 2014
  1. @uwiger

    use <br /> instead of <br></br>

    uwiger committed Jun 12, 2014
Commits on Apr 25, 2014
  1. @uwiger

    Merge pull request #28 from ehedenst/utf8-readme-fix

    Fixed bug where utf8 was being passed as package when writing the README...
    uwiger committed Apr 26, 2014
Commits on Apr 24, 2014
  1. @ehedenst
Commits on Feb 21, 2014
  1. @uwiger
  2. @uwiger

    bw-compat handling of encoding

    uwiger committed Feb 21, 2014
  3. @uwiger

    Merge esl and uwiger versions of edown

    Also, the unicode changes don't work in R15B. Made code sense
    whether the encoding-capable functions are available and act appropriately.
    uwiger committed Feb 21, 2014
  4. @uwiger

    re-generated docs

    uwiger committed Feb 21, 2014
  5. @uwiger
Commits on Dec 23, 2013
  1. @uwiger

    Merge pull request #27 from eryx67/master

    support unicode
    uwiger committed Dec 23, 2013
  2. @eryx67

    support unicode

    eryx67 committed Dec 23, 2013
Commits on May 24, 2013
  1. @uwiger
Commits on Mar 25, 2013
  1. @uwiger

    Experimental: Add option to name branch for top_level_README

    See #8
    
    If {top_level_readme, {Path, URL, Branch}} is specified, edown will
    use Branch instead of deriving the current branch when linking to
    the top-level README file.
    uwiger committed Mar 25, 2013
  2. @uwiger
Commits on Mar 19, 2013
  1. @uwiger
Commits on Mar 7, 2013
  1. @uwiger
  2. @uwiger
Commits on Mar 6, 2013
  1. @uwiger
  2. @uwiger
Commits on Feb 10, 2013
  1. @seth

    Handle explicit code blocks separately from edoc generated blocks

    Explicit code blocks (e.g. ```CODE''' in edoc) use an intermediate
    'pre' tag and are now rendered using Github Flavored Markdown "fenced"
    code block style. Using the markdown code block as opposed to 'pre'
    tags avoids needing to escape content in the block and slightly
    improves the readability of the generated markdown.
    
    The edoc generated function and type spec descriptions use a 'pre_pre'
    tag. The code now assumes that the pre_pre elements contain code with
    anchor tags for linking, but no other HTML tags. Special processing is
    added to wrap the 'pre_pre' blocks in '<pre><code>' tags and to
    translate angle brackets in the body of such tags to the appropriate
    HTML entity (&gt;, &lt;).
    
    This patch also adjusts newline behavior for generated markdown.
    Paragraphs now begin/end with a single \n. As a result, the formatting
    of ol and ul lists in markdown is improved.
    seth committed Feb 2, 2013
  2. @seth
  3. @seth
Commits on Feb 4, 2013
  1. @uwiger

    Merge pull request #22 from seth/sf/use-rev-parse

    Use git rev-parse to obtain current branch name
    uwiger committed Feb 4, 2013
Commits on Dec 21, 2012
  1. @seth

    Use git rev-parse to obtain current branch name

    Obtaining the current branch name using describe is roundabout and the
    tokenization that includes '/' is broken for any branch with '/' in
    its name (a common git practice). Using `git rev-parse --abbrev-ref
    HEAD` seems to provide the current branch name in an easy to parse
    fashion.
    seth committed Dec 20, 2012
Commits on Jul 17, 2012
  1. @uwiger

    Issue #20: default branch to master

    uwiger committed Jul 17, 2012
Commits on Jul 9, 2012
  1. @uwiger

    newer rebar

    uwiger committed Jul 9, 2012
Commits on Jul 4, 2012
  1. @uwiger

    Merge pull request #19 from RJ/patch-1

    Add {registered, []} tuple to edown.app.src
    uwiger committed Jul 4, 2012
  2. @RJ

    Add {registered, []} tuple to edown.app.src

    Missing 'registered' tuple in the app file causes `rebar generate-upgrade` to fail,
    when this app is included in a release.
    RJ committed Jul 4, 2012
Commits on May 12, 2012
  1. @uwiger

    Expand double-newlines, then collapse double 'p' tags

    This commit replaces #xmlText{} entries containing only two newlines
    (after stripping away spaces) with a 'p' tag. Afterwards, the
    markdown/3 function traverses the tree and removes 'p' tags
    followed by another 'p' tag.
    
    After this, it seems ok to remove the trailing space previously
    added by edown_xmerl:brstrip().
    uwiger committed May 12, 2012
  2. @uwiger

    reverting brstrip change

    uwiger committed May 12, 2012
Commits on May 11, 2012
  1. @uwiger

    brstrip(): replace with NO space

    uwiger committed May 11, 2012
  2. @uwiger
Commits on May 10, 2012
  1. @uwiger

    Merge pull request #1 from norton/dev

    Use git-describe to get git branch
    uwiger committed May 10, 2012
  2. @norton
Commits on May 8, 2012
  1. @uwiger
Something went wrong with that request. Please try again.