Hi *,
I’m running TM1 on my iMac with Mac OS X 10.6 and TM2 on the 10.9 MacBook. In TM1 I can export any (maybe modified) bundle by just dragging it from the bundle editor window to some finder location and will get an installable bundle like that one you sent. How do I do that in TM2?
-MWL-
In TM1 I can export any (maybe modified) bundle by just dragging it from the bundle editor window to some finder location and will get an installable bundle like that one you sent. How do I do that in TM2?
I don't remember that feature, but the bundle editor in TM2 has a Show In Finder or Show Info.plist command, and there's the bundle. m.
-- matt neuburg, phd = http://www.apeth.net/matt/ pantes anthropoi tou eidenai oregontai phusei Programming iOS 8! http://shop.oreilly.com/product/0636920034261.do iOS 8 Fundamentals! http://shop.oreilly.com/product/0636920034278.do RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
Am 2015-08-02 um 00:49 schrieb Matt Neuburg:
the bundle editor in TM2 has a Show In Finder or Show Info.plist command, and there's the bundle. m.
Sure; in the case of modified (that is, e. g., presumeably any self-developped) bundles one ge1ts even two: one in <~/Library/Application Support/Avian/Pristine Copy/Bundles/>, the other one in <~/Library/Application Support/Avian/Bundles/>, that one being the XML-represented diff („delta“) introduced by local modifications.
What I am looking for is a way to export the resulting bundle which should emerge from applying the delta bundle to the pristine one.
Regards from Ladenburg,
-MWL-
On 3 Aug 2015, at 22:59, Martin Wilhelm Leidig wrote:
What I am looking for is a way to export the resulting bundle which should emerge from applying the delta bundle to the pristine one.
There currently isn’t any way to export a merged bundle from TextMate but I’ll add it to next (nightly) build, likely available within the next 24 hours.
One thing I’ve wished for from time to time is the ability to “export” the custom elements (delta from the TM git base) of a bundle, into a new bundle. Possibly an idea in the same vein?
t
On Aug 6, 2015, at 9:42 PM, Allan Odgaard mailinglist@textmate.org wrote:
On 3 Aug 2015, at 22:59, Martin Wilhelm Leidig wrote:
What I am looking for is a way to export the resulting bundle which should emerge from applying the delta bundle to the pristine one.
There currently isn’t any way to export a merged bundle from TextMate but I’ll add it to next (nightly) build, likely available within the next 24 hours.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 6 Aug 2015, at 23:00, Tim Bates wrote:
One thing I’ve wished for from time to time is the ability to “export” the custom elements (delta from the TM git base) of a bundle, into a new bundle. Possibly an idea in the same vein?
I don’t understand this.
Are you talking about exporting just a single bundle item, like a command?
What does git or deltas have to do with exporting (from TextMate)?
On Aug 7, 2015, at 8:00 AM, Allan Odgaard mailinglist@textmate.org wrote:
One thing I’ve wished for from time to time is the ability to “export” the custom elements (delta from the TM git base) of a bundle, into a new bundle. Possibly an idea in the same vein?
I don’t understand this. Are you talking about exporting just a single bundle item, like a command?
Exporting everything that is different from the Textmate default version of the bundle.
So if the user edited a few commands, and created some new ones in (for instance the html bundle), this command would figure out which they were and export them to a new bundle.
The user would then have a “clean” html bundle, able to be kept up to date by textmate.
What does git or deltas have to do with exporting (from TextMate)?
I was trying to convey what the command would do. If the user had a forked version of a bundle that they were working on, and wanted to save their modifications from this fork into a new bundle and revert to the tracked Textmate version, this command would let them do so without losing their modifications, and without having to track these down one by one, which could be a pain if they were extensive.
Am 2015-08-06 um 23:00 schrieb Tim Bates:
One thing I’ve wished for from time to time is the ability to “export” the custom elements (delta from the TM git base) of a bundle, into a new bundle.
Well, the bundle in <~/Library/Application Support/Avian/Bundles/> _is_ the delta. TM should only be smart enough to apply it to some “pristine” bundle of the same name if there is one (or else to merge it with some delta bundle of the same name if there is one). Especially the latter one may very well be non-trivial, if not impossible, I concede.
On Aug 6, 2015, at 9:42 PM, Allan Odgaard mailinglist@textmate.org wrote: On 3 Aug 2015, at 22:59, Martin Wilhelm Leidig wrote:
What I am looking for is a way to export the resulting bundle which should emerge from applying the delta bundle to the pristine one.
There currently isn’t any way to export a merged bundle from TextMate but I’ll add it to next (nightly) build, likely available within the next 24 hours.
Wow. Did I mention that I love this list?
Regards from Ladenburg,
-MWL-
On 7 Aug 2015, at 19:40, Martin Wilhelm Leidig wrote:
There currently isn’t any way to export a merged bundle from TextMate but I’ll add it to next (nightly) build, likely available within the next 24 hours.
Wow. Did I mention that I love this list?
I didn’t manage to push a nightly build but I did do a “cutting edge” build which can be upgraded to by holding option down when clicking Check Now in Preferences → Software Update.
The build lack release notes but you can right-click bundles in the bundle editor and select Export Bundle…
On 7 Aug 2015, at 9:17, Tim Bates wrote:
Exporting everything that is different from the Textmate default version of the bundle.
So if the user edited a few commands, and created some new ones in (for instance the html bundle), this command would figure out which they were and export them to a new bundle.
The user would then have a “clean” html bundle, able to be kept up to date by textmate.
OK, I think this could be achieved if the bundle editor showed what items have local changes. Then a user would just move such items to a new bundle and revert to factory defaults for the original bundle.
Presently the bundle editor is too limited to do these things, but it is among the functionality considered lacking.
That kind of thing would be great. I think a little work on bundle editor would go a long way to getting a lot more activity in enhancing and sharing bundles. On Sun, 9 Aug 2015 at 12:54 Allan Odgaard mailinglist@textmate.org wrote:
On 7 Aug 2015, at 9:17, Tim Bates wrote:
Exporting everything that is different from the Textmate default version of the bundle.
So if the user edited a few commands, and created some new ones in (for instance the html bundle), this command would figure out which they were and export them to a new bundle.
The user would then have a “clean” html bundle, able to be kept up to date by textmate.
OK, I think this could be achieved if the bundle editor showed what items have local changes. Then a user would just move such items to a new bundle and revert to factory defaults for the original bundle.
Presently the bundle editor is too limited to do these things, but it is among the functionality considered lacking.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-
Allan Odgaard -
Martin Wilhelm Leidig -
Matt Neuburg -
Tim Bates -
Timothy Bates