Hi, altogether
I finally finished with the Textpattern Bundle.I ran into a couple of Issues both TM related and about the subject itself. It would have been definitely needed, that I ask for help or suggestions on this mailing list, but on the other hand, I can not get any serious work done, if I not completely isolate myself.
And here it is.
A detailed Article,about the main features of the Bundle
<a href="http://www.consking.com/article/">A detailed Article,about the main features of the Bundle</a>
DOWNLOADS TXP TextMate Bundle
TXP TextMate Theme
http://www.consking.com/file_download/19 http://www.consking.com/file_download/20
Although I did some testing on a large pile of sample files, feedback is always appreciated.
It might be a good Idea maybe at some point to put that into the repository.
Let's just see What Allan says first.
regards, marios
On Jun 16, 2006, at 00:10, marios wrote:
I finally finished with the Textpattern Bundle.
Great work! I've wanted something like this for a while, and I even started working on a Textpattern-bundle myself, but as I am pretty lazy I never did more than some basic sloppy matching and set up a few snippets. Your bundle is a *lot* more complete that anything I would have come up with, and so is the documentation for it.
Thank you!
Update
Since I forgot to edit the UUID Theme and the Theme Name key, use the download links below. Sorry for that.
DOWNLOADS TXP TextMate Bundle
TXP TextMate Theme
http://www.consking.com/file_download/19 http://www.consking.com/file_download/22
The current version of this bundle only works without scope interference with the XHTML bundle, If I change the Include value to text.html.basic I can not get the generic repos (which are aimed to fetch the plugin tags) items to work. the html bundle will match those as HTML tags and others as well.
Would it be possible, may be to add the following include statement into the patterns array of the syntax of the html bundle,
eg.: something like this: { name = 'text.html.txp'; match = '(</txp:.*?>|txp:.*?|txp:.*?\s{,8}/)'; },
as I couldn't really find any other way to avoid the interference. May be there is a better way to do this but I just throw the above together as a quick fix.
I really never took into account the html bundle, so now I'm stucked with above interference,
Sorry for the silly mistake with the Theme Name and the UUID, that I forgot to change,
regards, marios
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Knut Erik Andersen wrote:
On Jun 16, 2006, at 00:10, marios wrote:
I finally finished with the Textpattern Bundle.
Great work! I've wanted something like this for a while, and I even started working on a Textpattern-bundle myself, but as I am pretty lazy I never did more than some basic sloppy matching and set up a few snippets. Your bundle is a *lot* more complete that anything I would have come up with, and so is the documentation for it.
Thank you!
Tenthumbs, thanks a lot for your positive feedback, and sorry for not responding earlier.
An new version of the bundle is available, I recommend, that you throw the old Bundle away and double click the new one. As a matter of fact, I have yet to receive any external evaluation results, which means, allthough it works fine on my local install of TM even with any randomly grabbed templates,with mixed html and txp tags, I have no way to verify weather it works correctly on other TM installs.
Would it therefore possible for you, to confirm the former and tell me if you still have the same problems with your HTML not showing up, or any other observations, that came accross ?
On 22/6/2006, at 1:02, marios wrote:
[...] An new version of the bundle is available, I recommend, that you throw the old Bundle away and double click the new one.
Just FYI it should be possible to double click the new bundle w/o thrashing the old one first.
It will ask if it should overwrite the old one, which it will then do -- but only the parts in “Pristine Copy”, so if there are local customizations made, these should survive the upgrade.
Allan Odgaard wrote:
On 22/6/2006, at 1:02, marios wrote:
[...] An new version of the bundle is available, I recommend, that you throw the old Bundle away and double click the new one.
Just scanning quickly the mailing list topics, I came across one, where the phenomenon of invisible bundle Items in the Bundle Editor have been reported, in case the Bundle was build on cutting Edge, whereas the Third party User version was a prior build around 948. So , what would be interesting to find out, is:
Did this occur because Users attempted to manually place those Bundle Items in /path/to/TextMate.app/Contents/SharedSupport/Bundles
instead of ~/Library/Application Support/TextMate/Bundles, or is it in fact a compatibility Issue between those Bundle versions and TM Builds ?
regards, marios
Just FYI it should be possible to double click the new bundle w/o thrashing the old one first.
It will ask if it should overwrite the old one, which it will then do -- but only the parts in “Pristine Copy”, so if there are local customizations made, these should survive the upgrade.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On 22/6/2006, at 1:28, marios wrote:
Just scanning quickly the mailing list topics, I came across one, where the phenomenon of invisible bundle Items in the Bundle Editor have been reported, in case the Bundle was build on cutting Edge, whereas the Third party User version was a prior build around 948. So , what would be interesting to find out, is:
Did this occur because Users attempted to manually place those Bundle Items in /path/to/TextMate.app/Contents/SharedSupport/Bundles
instead of ~/Library/Application Support/TextMate/Bundles, or is it in fact a compatibility Issue between those Bundle versions and TM Builds ?
It is a compatibility issue, more specifically, new items are created with a type-specific extension like tmSnippet, tmCommand, tmLanguageGrammar, etc. -- r948 only load files with a plist extension.
Renaming the items would solve the compatibility problem, but now that r1103 is the latest official release, I don’t see any reason to maintain backwards compatibility for bundles.
Allan Odgaard wrote:
On 22/6/2006, at 1:28, marios wrote:
Just scanning quickly the mailing list topics, I came across one, where the phenomenon of invisible bundle Items in the Bundle Editor have been reported, in case the Bundle was build on cutting Edge, whereas the Third party User version was a prior build around 948. So , what would be interesting to find out, is:
Did this occur because Users attempted to manually place those Bundle Items in /path/to/TextMate.app/Contents/SharedSupport/Bundles
instead of ~/Library/Application Support/TextMate/Bundles, or is it in fact a compatibility Issue between those Bundle versions and TM Builds ?
It is a compatibility issue, more specifically, new items are created with a type-specific extension like tmSnippet, tmCommand, tmLanguageGrammar, etc. -- r948 only load files with a plist extension.
Renaming the items would solve the compatibility problem, but now that r1103 is the latest official release, I don’t see any reason to maintain backwards compatibility for bundles.
I'm lucky to have that information confirmed, since it resolves all the confusion that came up with all those Users that never came to see the Bundle Items.
One last thing that I would like to ask regarding this matter:
In case someone had installed a cutting Edge Bundle, but had a r948 build, and he then updates his Install to latest cutting Edge, would that specific Bundle then show up correctly after updating ?
My guess is , it should, but just to confirm, I'd be glad to hear about it.
thanks a lot in advance, regards marios
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Jun 22, 2006, at 01:02, marios wrote:
Would it therefore possible for you, to confirm the former and tell me if you still have the same problems with your HTML not showing up, or any other observations, that came accross ?
I just downloaded the latest version, and it seems to work fine. as long as I have it set to use your included versions of the html-bundles. If i set it to use the ones i have checked out from svn, nothing gets colored. I have cutting edge TextMate, if that matters. I have come a cross one error in the language module: txp:link_to_prev has become txp:link_to_previous, which is a tag I can't find in the tag index at textpattern.net. I never used that tag, so I can't say which is correct, tho. I haven't had a lot of time to play around with the new functionality yet, but it sure looks great.
Regards Knut Andersen
On Jun 22, 2006, at 08:37, Knut Erik Andersen wrote
I just downloaded the latest version, and it seems to work fine. as long as I have it set to use your included versions of the html- bundles.
I forgot to mention one oddity: If text isn't immediately following an opening <p>, but is entered on a new line, it causes all content below the paragraph-tag to lose it's syntax colouring.
Regards Knut Erik
Knut Erik Andersen wrote:
On Jun 22, 2006, at 01:02, marios wrote:
Would it therefore possible for you, to confirm the former and tell me if you still have the same problems with your HTML not showing up, or any other observations, that came accross ?
I just downloaded the latest version, and it seems to work fine. as long as I have it set to use your included versions of the html-bundles. If i set it to use the ones i have checked out from svn, nothing gets colored.
Would it be possible for you to send me the code portion of your settings from within your TXP Language Grammar, below line 158 or post it here ?
I have cutting edge TextMate, if that matters. I have come a cross one error in the language module: txp:link_to_prev has become txp:link_to_previous, which is a tag I can't find in the tag index at textpattern.net. I never used that tag, so I can't say which is correct, tho.
That was a silly mistake from my side, the former is the correct one and is defined in the corresponding wiki page like that, Thanks for pointing that out.
I haven't had a lot of time to play around with the new functionality yet, but it sure looks great.
Regards Knut Andersen
regards, marios
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Knut Erik Andersen wrote:
On Jun 22, 2006, at 08:37, Knut Erik Andersen wrote
I just downloaded the latest version, and it seems to work fine. as long as I have it set to use your included versions of the html-bundles.
I forgot to mention one oddity: If text isn't immediately following an opening <p>, but is entered on a new line, it causes all content below the paragraph-tag to lose it's syntax colouring.
I tried to reproduce that problem on my TM install, and I again could not, but I'd be interested to see if I can reproduce it. Again would it be possible to see a code example and which where the corresponding Settings.
It could also be, that it is something completely irrelevant with those settings, that has to do with Bundle versions on different Builds, but just to see, if I can reproduce this, that would be great. It doesn't have to be today.
best regards, marios
Regards Knut Erik ______________________________________________________________________ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
marios wrote:
Knut Erik Andersen wrote:
On Jun 22, 2006, at 08:37, Knut Erik Andersen wrote
I just downloaded the latest version, and it seems to work fine. as long as I have it set to use your included versions of the html-bundles.
I forgot to mention one oddity: If text isn't immediately following an opening <p>, but is entered on a new line, it causes all content below the paragraph-tag to lose it's syntax colouring.
I tried to reproduce that problem on my TM install, and I again could not, but I'd be interested to see if I can reproduce it. Again would it be possible to see a code example and which where the corresponding Settings.
It could also be, that it is something completely irrelevant with those settings, that has to do with Bundle versions on different Builds, but just to see, if I can reproduce this, that would be great. It doesn't have to be today.
Just taking a look at relevant lines, I realized, that I made a mistake with in the comment: It reads:
{ comment = 'NOTE:Default is text.html.strict2 which was taken as is from SVN,if you do not want this then comment it out in the front with xxx and uncomment the patched html.basic 2version by removing the xxx in the front.Be carefull, that you dont accidentally remove a single quote,since plist files do not like that'; }, { include = 'xxxtext.html.basic2'; }, { include = 'text.html.strict2'; }, { comment = 'CAUTION:Do not use the above strict xhtml.1 version, this was left here only for testing purposes'; include = 'xxxtext.html.xhtml.1-strict';
Note, the line, that says: Do not use the "above" strict...., whereas it should say: Do not use the "below" strict....
Shortly: include = 'xxxtext.html.xhtml.1-strict'; can not be used with this bundle, as it is incompatible with the Language Grammar. May be that seemed to have confused Users, and they included 'text.html.xhtml.1-strict' instead of text.html.strict2, or text.html.strict, where the latter two are the correct ones.
regards again, marios
best regards, marios
Regards Knut Erik ______________________________________________________________________ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On 22/6/2006, at 22:10, marios wrote:
Shortly: include = 'xxxtext.html.xhtml.1-strict'; can not be used with this bundle, as it is incompatible with the Language Grammar. May be that seemed to have confused Users, and they included 'text.html.xhtml.1-strict' instead of text.html.strict2, or text.html.strict, where the latter two are the correct ones.
Actually, TM only ships with text.html.basic -- this is the one I actively support, so I would recommend everything derived from HTML base their work / include this one, rather than the two ‘strict’ grammars in the repository.
Allan Odgaard wrote:
On 22/6/2006, at 22:10, marios wrote:
Shortly: include = 'xxxtext.html.xhtml.1-strict'; can not be used with this bundle, as it is incompatible with the Language Grammar. May be that seemed to have confused Users, and they included 'text.html.xhtml.1-strict' instead of text.html.strict2, or text.html.strict, where the latter two are the correct ones.
Actually, TM only ships with text.html.basic -- this is the one I actively support, so I would recommend everything derived from HTML base their work / include this one, rather than the two ‘strict’ grammars in the repository.
I actually couldn't make the Grammar work with a default text.html.basic, since it will mistakenly match txp tags, the way they are.
Would it be possible to include an include statement, like the one I included in the patched version ? Just one quick question, some default assorted Grammars, have disappeared from the Bundle Editor after the last Software update to r1112. Although they are there in their default locations, they just don't show up in the Bundle Editor.
Thanks also for the mention on the biog, I really do appreciate that.
regards , marios
On 22/6/2006, at 23:01, marios wrote:
Would it be possible to include an include statement, like the one I included in the patched version ?
Not sure exactly which one you are referring to.
However, you can add “disabled = 1;” to the rule to disable it. You shouldn’t prefix it with X’es, as that’ll just give run-time errors (for “language not found”.)
Just one quick question, some default assorted Grammars, have disappeared from the Bundle Editor after the last Software update to r1112.
Which ones?
Although they are there in their default locations, they just don't show up in the Bundle Editor.
Only the languages? If it is the languages you copied to your own bundle, it is because you did not give the copies a new UUID then -- i.e. use duplicate in the bundle editor (rather than copy on disk.)
-
Allan Odgaard -
Knut Erik Andersen -
marios