Commit Graph

36 Commits

Author SHA1 Message Date
T. Joseph Carter
4d7b33f79e Add irssi and tin helper scripts to archive 2015-10-28 16:47:33 -07:00
T. Joseph Carter
4067fed090 Missed part of A2CLOUD's serial mapping for ADTPro 2015-10-28 16:46:32 -07:00
T. Joseph Carter
39b5475400 Serial terminal tools for archive 2015-10-28 16:46:01 -07:00
T. Joseph Carter
53a4be37e6 Add raspbian-update to archive
This one is also used by A2SERVER, and of course by Raspple II.  It's
owner should be Raspple II probably, but it belongs in the archive for
all three.
2015-10-28 16:37:55 -07:00
T. Joseph Carter
91b54a8c5d Missed this for ADTPro 2015-10-28 16:37:26 -07:00
T. Joseph Carter
a2809e85e9 Add image utility scripts to archive 2015-10-28 16:36:05 -07:00
T. Joseph Carter
7eeed445e5 Add other A2CLOUD files to archive 2015-10-28 16:34:12 -07:00
T. Joseph Carter
b1204b1860 Add ADTPro scripts to the archive 2015-10-28 16:32:15 -07:00
T. Joseph Carter
9d1868139a Add the MOTD files 2015-10-28 16:31:17 -07:00
T. Joseph Carter
e8f1ff4a88 Add emulators to archive 2015-10-28 16:30:02 -07:00
T. Joseph Carter
845425a3c5 Add cppo to archive 2015-10-28 16:27:57 -07:00
T. Joseph Carter
a47744dd07 Er, put supdir in right place 2015-10-28 16:27:15 -07:00
T. Joseph Carter
60d54a6d19 Fix the remaining fixme's
Note: I've been using kramdown to generate HTML, and kramdown generates
id tags for headings automatically.  Redcarpet does not, and in fact
Redcarpet (the official GFM implementation) does not support any
alternative means of specifying id, class, or other HTMLish things.  In
other words, redcarpet is extremely limited compared to kramdown.

So just use kramdown right?  Well it's not that easy.  Kramdown can
parse GFM, but it has some bugs when doing so.  For example, when fixing
these last fixmes, I had some level three headings, `### stuff`, which
were rendered as `<p>### stuff</p>` rather than `<h3>stuff</h3>`.  Sigh.

When rendering the HTML using kramdown's own syntax variant, it did this
right.  But kramdown's variant has some subtle differences in things
like fenced code blocks.  GitHub will not render kramdown's fenced code
bocks properly, and kramdown will not render GitHub's fenced code blocks
properly unless set to parse GFM.

In terms of source code, that only matters for README.md, since GitHub
only renders README.md for you.  You can't get it to render other .md
files even if you want it to.  That said, using two different Markdown
variants causes problems with confusion regarding what is and isn't
valid Markdown syntax.  As it is, vim doesn't fully recognize either
syntax using any syntax plugin I've tried.  And the precise syntax used
on the GitHub website is obviously going to be GitHub's.

All of this to basically more eloquently say, DAMMIT JOHN GRUBER!  He
readily acknowledges the limitations of the reference implementation of
Markdown, suggests anyone who wants to improve the syntax go and do so,
yet stubbornly refuses any effort to standardize these extensions.  He's
encouraging a thousand niche forks, but actively trying to sabotage any
standardization.  This is a widely acknowledged irritation with the
Markdown family of markup languages.

My notion going forward is that we should assume README.md is in GFM,
and all other .md files are Kramdown format.  If I can come up with a
clever way to indicate this syntactic difference, I will.
2015-10-27 17:57:59 -07:00
T. Joseph Carter
d4cf59675c Remove a few stray backslash escapes 2015-10-27 17:36:52 -07:00
T. Joseph Carter
91a5a8774f Include the comments on the open thread 2015-10-27 17:20:51 -07:00
T. Joseph Carter
819210be14 Links are done save for the open thread links 2015-10-27 15:55:01 -07:00
T. Joseph Carter
8134d83866 Swap h2 and h3. 2015-10-27 03:07:31 -07:00
T. Joseph Carter
274ce16f37 Convert underline emphasis with h2 2015-10-27 03:05:47 -07:00
T. Joseph Carter
c8fd83af34 Much more link fixing, also use auto-id anchors 2015-10-27 02:55:43 -07:00
T. Joseph Carter
81d5faf516 Move TOC to top; begin cleaning up links 2015-10-27 01:27:25 -07:00
T. Joseph Carter
f761664f38 Remove the tag cloud 2015-10-26 20:14:36 -07:00
T. Joseph Carter
e8bbf7c672 Most of the way finished cleaning up index.md now! 2015-10-26 20:11:16 -07:00
T. Joseph Carter
5e6bc9129f Remove all the spans 2015-10-26 18:00:01 -07:00
T. Joseph Carter
01460fac5a Remove <small> tags 2015-10-26 17:38:30 -07:00
T. Joseph Carter
5d5fbaa446 Remove more cruft, mostly article microformat tags 2015-10-26 17:37:19 -07:00
T. Joseph Carter
f00306e7d3 Remove HTML5 footers and a stray section tag 2015-10-26 17:21:48 -07:00
T. Joseph Carter
4ba1c55784 Remove comment links 2015-10-26 17:19:32 -07:00
T. Joseph Carter
440c331c69 Remove HTML5 header tags 2015-10-26 15:18:24 -07:00
T. Joseph Carter
1d59599f95 Remove HTML5 article tags 2015-10-26 15:17:33 -07:00
T. Joseph Carter
ba17773fad Remove all remaining {: ...} extension syntax 2015-10-26 02:15:52 -07:00
T. Joseph Carter
dd91fc930c Remove HTML comments and link targets 2015-10-26 02:11:26 -07:00
T. Joseph Carter
20c2669283 YouTube iframes converted to Markdown 2015-10-26 01:55:21 -07:00
T. Joseph Carter
88cb99fe4a Automate removing {: ... } cruft we can't use 2015-10-23 19:38:20 -07:00
T. Joseph Carter
bb3fbd9ea1 Cleaned up the first article
This is going to take some doing.  :)
2015-10-23 19:33:57 -07:00
T. Joseph Carter
77abf32fca No, {:foo} syntax is not supported, begin removal 2015-10-23 19:06:25 -07:00
T. Joseph Carter
b347331074 First rough pass at Ivan's A2CLOUD page
This is ugly, full of HTML, and I'm not sure the CSS classes work with
GFM's renderer.
2015-10-23 18:58:53 -07:00