Yeah, a few keyboards have that label, but it's traditionally the option key and it can be confusing to call it alt because of the way it doesn't always map to windows/unix keyboards. (My 2017 MBP calls it option.) Regardless, Save As is definitely shift-cmd-S by long-standing usage.
Thanks
ahoy folks. i did a quick search through the sourcecode for transparency features. it seems there's an opacity attribute in the themes. i'm totally new to the editor, but i'm very eager to switch to an editor supporting window transparency - i do a lot of re-drafting, and it is so helpful on small screens to be able to see previous drafts
without investigating the opacity attr further, is this feature implementable in MacDown?
But dialog prompts, the preference panes, and other menu windows are not transparent / opaque. Only the editor windows have the transparency feature. MacOS Terminal and iTerm have these features, and TextMate2 used to have it too.
IMHO, it seems many users consider transparency a cosmetic frill, but I have come to rely on it for the practical reason that laptop screens are small, and being able to "see through" the current editor to a previous draft means I can revise and redraft without having to alternate through screens. I cannot be the only one who sees the practical value of transparency features.
I've tried installing both via the zip download and homebrew
That basically says it can't be opened because the developer can't be verified.
Oh sorry, ignore me.. It's possible in the security settings to tell it to open it
1 reply
Hey All,
I got a silly question. Whenever I type in the editor, the preview jumps to the top of the page. Is there a setting that enables me to have the preview stay at the exact location which I have scrolled to? Linking the scrolling in the editor to preview doesn't really work either as I always end up in a section completely different to the one I am editing. I think its due to pictures and tables having different heights than in the editor.
Best,
Philipp
I'm loving MacDown after being a Mou user for a long time. Thanks for it!
A few wishes:
- It does a lot better job than Mou at keeping the editor and preview in sync, but this breaks down when there are <!-- --> comments in the .md.
- The reason I have comments in the Markdown is that I'm writing a small book along with a presentation together in the same document. I comment out the slides and then extract them with a few lines of awk to a new Markdown file. :-) So... presentation features would be a great addition! I used to use DeckSet, but it doesn't do MathML or graphviz, both of which I need.
- It'd be great to be able to scale images and graphviz charts!
- Layout is a bit problematic in landscape mode. It's usable for my slides, but barely.
THANKS!
Does any one use this on Apple Silicon native?
I notice that my file types for .md files (which MacDown is set to open as the default app) show up in the Finder as "md 文件". That seems inappropriate for my English-language system. I also wonder if this is goofing up quicklook in Catalina. If the extension is "markdown", the file type gets reported as "Markdown" and ql works fine, but it's not working on ".md".
I love MacDown! One thing I really want is a toolbar button/menu item to create a new table--the table syntax is so complex and fussy, and frankly I seem to always forget it, then have to look up on the help page. All it would need to do is put down maybe a 3x2 table, with the headers, and then a left, centered, right justified column.
@PeterKieu I have been using MacDown without issue on my M1 -- as long as it works on Rosetta, I don't see any pressing need for native--it is not a huge hungry application, and M1 Macs run even Intel software quite fast.
Hi All -- first off, I just want to express extreme gratitude for this project. MacDown has been my favorite markdown editor for at least 5 years running.
Secondly, I discovered a (possibly obscure) bug that I'd like to share:
When I drop an image file onto the editor, MacDown adds a HUGE block of text (maybe corresponding to every byte of data in the JPEG file?) into my document. There's no way to undo, and I have to select+scroll down the whole way to fix the issue.
Secondly, I discovered a (possibly obscure) bug that I'd like to share:
When I drop an image file onto the editor, MacDown adds a HUGE block of text (maybe corresponding to every byte of data in the JPEG file?) into my document. There's no way to undo, and I have to select+scroll down the whole way to fix the issue.
Perhaps that should be on by default tho. Just a thought