-
-
Notifications
You must be signed in to change notification settings - Fork 11.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't see context menu in Postbox email #30
Comments
I spent some time looking at this, and it seems like I can probably get Markdown Here working with Postbox, with limitations -- I can't figure out how to open a new tab with the options in it, so there might be no options. (They'd still be accessible through the built-in config editor, but that's not very friendly.) I'll see what I can do to get it working in some released form before my 30-day trial is up. ...Which highlights a big problem here: If I can't run the app, I can't test the extension. I looked on their website for an email address to see if I can get a developer license from them, but I couldn't find one (irony!). I'll try to send them a tweet. |
Adam. Many thanks. It's not hugely urgent for me, but I think that a lot of people are switching from TB to PB, as a supported fork of TB. Also it's got some pretty good features, so I think quite a few "power users" on Mac will (as I did) move up from Mac Mail. |
It sure doesn't work in all rich edits, but... holy smokes! It works in Evernote! Nice find. Evernote seems to use the same rich-edit method that the webmail editors do: an This is why I left Markdown Here enabled for all domains instead of restricting it to Gmail, Yahoo, Hotmail -- I hoped that it would work in unexpected places. Until now, I had only discovered Google Groups (which uses an identical editor to Gmail). But this is a separate thing altogether, so super rad. I'll make a note in the README and store description about this. (And I'll mention that code blocks don't work quite right -- seems like newlines are stripped from the I must admit that Evernote won't become a first-class supported app. I don't use it and won't test it regularly. But create an issue if you see it break and I'll try to sort it out. |
I've checked in some changes that allow for basic use of Markdown Here in Postbox. You can try it out if you pull head code and use an extension proxy file to point to The options page doesn't work, and it might never. I'll try to contact Postbox (again) for assistance with that, but no promises. I'll probably put out a release with this support in a couple of weeks (i.e., whenever the current release gets through the Mozilla review queue). |
Version 2.6.1 has been released, with basic support for Postbox. Functionality caveats can be seen here: It will take some time for the release to clear Mozilla review, but until then it can be downloaded here: Closing this issue. Please open a new one if something goes wrong. |
Adam _not_work.Cheers On Wed, Aug 29, 2012 at 9:10 PM, Adam Pritchard [email protected]:
|
Thanks for the heads up. I bet that some day Keep will support rich text. If it uses Gmail style then Markdown Here will work, but not if it uses Google Docs or Google+ style. |
Hi
I'm using the Postbox email client on MacBook Air. I'm running the latest version of Mountain Lion, the lastest version of Postbox (3.0.5) and the latest Markdown Here add-in (2.5.2). I've installed MDH, restarted Mailbox several times and can't see the context menu when I "right click" (ctrl-click). I've made sure that Mailbox is properly closed in between restarts. Rich text editing (html editing) is enabled for all my email accounts.
I've just also tried disabling MDH, restarting PB and then re-enabling it and restarting. No good. And also removing and re-installing MDH... no good.
I appreciate that Mailbox isn't quite the same as Thunderbird, but with the recently announced dev freeze on TB a lot of people are now using it. It seems to work with most TB add-ins, for instance I'm using Lightning calendar with it, with no problems.
Thanks
Mark
The text was updated successfully, but these errors were encountered: