My complaint is that the MultiMarkdown support was removed from the auto-updating Markdown bundle, and that the MultiMarkdown bundle is not available through the current bundle support in TM2.

Hence without any action on my part, a lot of stuff broke on my system.

And installing a third-party bundle (eg yours) that isn't really supported any longer doesn't exactly give a warm fuzzy feeling, and is also beyond what a regular user should be expected to do.

There should have been an official (as in supported by the official bundle download support) MultiMarkdown bundle **BEFORE** removing MultiMarkdown support from the Markdown bundle. And a heads-up in the mailing list would have been nice too.

This is costing me time at an inopportune moment, so obviously I am not happy.

Let me take this opportunity though to say a big "Thank You!" to Fletcher. I am a big MMD fan!

Gerd

On Aug 27, 2012, at 2:06 PM, Fletcher Penney fletcher@fletcherpenney.net wrote:

I'm not sure exactly what you're referring to, but the MultiMarkdown "support" in the original version of the Markdown wasn't very good, and was *really* out of date. The last time I tried it, I couldn't even get it to work, and I know a thing or two about how MMD is supposed to work.... ;)

My bundle is a simply a fork on github of the original Markdown bundle that has been updated to work with MMD, and more specifically MMD 3. From looking at the github commits, I would presume that my bundle is what Michael is referring to. To be honest, I'm actually glad to see this change --- most of the support emails I get regarding the "MultiMarkdown" bundle are actually related to the original Markdown bundle that didn't seem to actually work with MMD very well. Once I point them towards the "official" MMD version, their problems are generally solved. You are, of course, free to fork it and make your own changes so that it suits your own needs better. Or just modify the version on your machine after you install it.

I don't use TextMate for writing Markdown/MultiMarkdown much any more (in favor of using my own app, MultiMarkdown Composer, that incorporated features that were impossible to implement under TM 1), so I'm not doing too much active development on the TM bundle side. I'm happy to take pull requests for changes/bug fixes, and I probably need to merge some of the subsequent updates from the original branch back into my fork at some point.

I have (briefly) tested my version with recent installs of TM 1 and TM 2, and it seems to be working on both versions, though I have not re-tested every single feature.

Fletcher

On Aug 27, 2012, at 2:49 PM, Gerd Knops wrote:

...

Nice one, remove the Multimarkdown support from the Markdown bundle without warning!

So where is this "own" bundle? Is tehre something newer than Fletcher's old bundle (which I am not a particular fan of for variuous reasons)?

Gerd

---

textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate

-- Fletcher T. Penney fletcher@fletcherpenney.net

---

textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate

On Aug 27, 2012, at 2:40 PM, Allan Odgaard mailinglist@textmate.org wrote:

On Aug 27, 2012, at 9:29 PM, Gerd Knops gerti-textmate@bitart.com wrote:

...

Hence without any action on my part, a lot of stuff broke on my system.

Given that the bundle was calling MultiMarkdown.pl (rather than, say ${TM_MULTIMARKDOWN:-multimarkdown}) I didn’t even think this stuff worked anymore.

Well... When I add custom stuff, I tend to create a new bundle called "xxx (Gerd)", with items depending on the original bundle's scope.

And since the "MultiMarkdown" Grammar disappeared, so did all the support in my bundle.

It is also confusing that Fletcher's bundle is called "Markdown" but defines the "MultiMarkdown" syntax. Not sure if it confuses TextMate, but it sure confuses me.

Also somehow the both Syntaxes now are broken (only the first line of code blocks is scoped as such).

[..]

I am sure you have the skill to checkout a previous version of the bundle ;)

;) I'd be way to worried to miss out on the cool new stuff others might contribute...

I'll figure it all out. Just not what I had planned to do today... :-(

Gerd

On Aug 27, 2012, at 3:40 PM, Allan Odgaard wrote:

...

And installing a third-party bundle (eg yours) that isn't really supported any longer doesn't exactly give a warm fuzzy feeling, and is also beyond what a regular user should be expected to do.

The MultiMarkdown support in the default bundle has never really been supported beyond the initial contribution. We can of course add Fletcher’s bundle to the index so users can install it via Preferences. I’m 95% done with the system that will allow third parties to add bundles to the index.

At one point, I thought there was an easy mechanism to choose between github forks of a particular bundle, e.g. to choose "fletcher/Markdown.tmbundle" from github instead of "textmate/Markdown.tmbundle". That was the whole reason I followed certain conventions on github that I may or may not have done otherwise. I thought, but could easily be mistaken, that this worked for a time in TM 1, but that was several years ago.

I recently reinstalled the OS on my development machine, and in order to get my bundle working in TM 1 and TM 2, I had to download from github and install "manually". I couldn't find another way to do it (though I admittedly didn't spend too long looking.)

Is there a plan to make it easier to find and choose amongst various forks of bundles that are stored on github? Or does each one have to have a unique name? What happens if someone else creates a MultiMarkdown.tmbundle before I do? How would I "oust" them within the TextMate GUI? Or if I fail to maintain my version, how does someone else oust me?

F-