Things like Kramdown IALs, for example. Apex can handle a lot of (but not all) of Pandoc's special syntax, including cite-proc and bibliography support, but using Pandoc means you don't get features from Kramdown or mmark. Pandoc is über-powerful, but for 80-90% of simple Markdown->HTML cases, I think Apex is going to offer everything Pandoc does plus the benefit of extensions from processors it doesn't handle, and where it does handle them, you have to choose `--from markdown_mmd` or `--from gfm` --- with Apex you can use both mmd and gfm syntax at the same time with one unified parser.
Yeah, that's how I felt about CommonMark, too (but I've come around). The thing I'm shooting for is not a new standard, it's a tool that implements all of the existing "standards." I'm not creating new syntax or enforcing new rules, just making a tool that means you don't have to think about which processor you're using and what extensions you might be giving up by choosing one over another.
It definitely is not. nvUltra is mostly out of my hands right now, my own projects (including Marked 3) are what I'm doing while waiting for the last pieces to come together.
I do a couple of podcasts, and one of them (Systematic) regularly interviews people who aren't terribly technical. I use Ecamm Call Recorder with Skype, and even when the remote interviewee is not prepared to record, I can get both sides of the conversation on separate tracks for EQ and mixing. I do request they have a small, quiet room, and a ban on any headphones with inline mics (like iPhone earbuds). I can usually make a headset work if they don't have a decent mic, though it takes a lot of EQ work and sometimes sucks even after editing.
For the record (from the author), 98% of my traffic is from Mac users, so I don't usually specify. I do, however, state in the second paragraph that it's very specific to ScreenFlow.
Thanks. I was not intending to sound overly snarky. I think perhaps only people outside a circle notice the assumptions made by people within it.
For example, it's usually easy to identify material written by people in the USA - they're more likely to assume their readers are within the USA. People in South America, Europe, and Asia seem to assume their readers could be anywhere.
Similarly with tech, though I think we all assume everyone knows what we're talking about, no matter where they are. : )
I had no idea what ScreenFlow is, other than a camelcased bonding of two common words. Yes, you may say, I could have looked at that link, find that it takes me to iTunes, and then intuit we're talking OSX ... but a) I was on mobile so it wasn't a simple hover, b) as you note it's an en passant reference in the second paragraph.
EDIT: Oh, and c) the page title is 'Tips for Screencasting'
I made doing because I get manic and don't even realize I'm switching to a new task until I've already forgotten what I was doing before. It's probably not an issue for most people. So, for me, I have Day One pop up every hour and ask me what I'm doing, which then gets converted to a "WWID" file in nvALT via the library in doing (and Hazel). If I do remember to track between tasks, I just jot it off on the command line.
I love the idea of a timer, though. I do use Timing to do something similar. http://timingapp.com/
And the organization by nested CSVs has some great potential for longer-term data collection.
Hello.
Thanks for sharing! I also found the BBedit plugin, so that I can edit it from the TaskPaper link above. Here is a simple AppleScript to install it, when you don't have administrative rights on your user account:
do shell script "cd ~/Downloads/doing-master; gem install doing" with administrator privileges
Pretty sure it says iOS Text Editor roundup. Syntax highlighting is in there, other code-specific features are listed under additional features because there's really only two "code" editors in the mix.
