I use Scrivener iOS to produce Markdown articles to run through Jekyll for my web site, at the rate of about 5 or 6 articles per week. I export the compiled file into Dropbox, where Jekyll on my Mac can see and compile it.
One tiny thing that would be ever so useful would be to be able to specify that the output extension is “md” rather than “txt”, especially since Dropbo in their “wisdom” have changed Save to Dropbox so that you can no longer rename the extension.
Another small thing would be in Command-K, to split a page, whatever they’re called. When I create a new page, I do Command-N for new, type in a header with pound signs, Command-A Command C to copy it, and Command-O, which creates the page, names it in the page list, and puts the cursor in the page. I Command -V and am ready to type the new section.
Sometimes I have written a bit before I realize I want the new section, so I type a header into the text, select it, and Command-K to split the page. In that instance, the cursor does NOT go into the page. It would be great it if would do so.
In addition, if. that we’re being addressed, Command-K does not work if there is nothing below the selected part. I believe that it should, placing just the selected part on a new page and again putting the cursor at the end of it.
Right, you can only customise the file extension for TXT files on the Mac. I don’t think it would hurt to have a toggle for .md specifically, in that section of the compile settings that somewhat pertains to Markdown authoring, I’ll put it on the list for consideration.
In addition, if. that we’re being addressed, Command-K does not work if there is nothing below the selected part. I believe that it should, placing just the selected part on a new page and again putting the cursor at the end of it.
No, that’s intentional. You can’t break a straw into two straws from the very end of it. The process that you are describing, where one is writing and comes to a new section break in their mind, has always been to use ⌘N (same for Mac). This incidentally does not have the issue with the cursor getting lost. Just hit the shortcut, type in “# The Heading”, press return and continue writing.
Split is better if you get two paragraphs into a new section before realising that’s what you did, you know?
Hi Amber. Thanks for adding the md for consideration.
Since in Markdown I usually want the heading in the output, I have to do Command N, type New Section Command A Command C return Command V.
With Command K, I’m not breaking the straw from the end. I type the header ## Next Section, select it and then Command-K. If there is a blank line after the header, or two paragraphs, it everything from the selection down goes into the new section, and the selected bit becomes the title of the new section in the outline. Saves me all that copy-pasta.
So there is content: the heading itself. Since there is content, and no reason NOT to, I respectfully submit the idea for reconsideration. It’s convenient and no more surprising than having it just do nothing. Thanks!
Now I have to go look to see how you typed that cool command-N
Since in Markdown I usually want the heading in the output, I have to do Command N, type New Section Command A Command C return Command V.
Have you considered changing the compile settings so that the item name is printed as the Markdown heading? Here is a simple example of how that could be done:
Scomp File
Title: Markdown
Author: AmberV
# Apply Markdown headings to all folders, respective to their indent level.
Folder Titles:
Level 1: '# <$title>'
Level 2: '## <$title>'
Level 3: '### <$title>'
Level 4: '#### <$title>'
Level 5: '##### <$title>'
Level 6: '###### <$title>'
# Top level text items will have a title, but all other items nested at lower levels will not.
Text Titles:
Level 1: '# <$title>'
# Some Markdown editors do not work well with typographic punctuation.
Transformations:
- Dumb Punctuation
With Command K, I’m not breaking the straw from the end. I type the header ## Next Section, select it and then Command-K.
Ah, I see what you mean, and yes, I think what you are saying does make sense, since logically the command considers the true split point to be on the left edge of the selection, not the right (otherwise it wouldn’t work!).
Now I have to go look to see how you typed that cool command-N
I use a text expansion utility on the Mac, but I bet you could set up substitutions on iOS for those. For me, I type in &cmd and that gets replaced with the symbol. You can copy and paste the Unicode symbols from this page.
Thanks for reconsidering, and for the tip! I do think I have an appearance file that does that, and have somehow settled back into default. I’ll try to relearn what I can do.
