The latest TextMate (1.5.1) broke TmCodeBrowser (empty display), and
a small change was required. Please update TmCodeBrowser from here:
http://www.cocoabits.com/TmCodeBrowser/
Gerd
Just want to aplogize to all for the multiple posts that went to the lists.
I vey rarely use the gmail web interface and I guess it really shows. ;-)
Sorry for the multiple posts.
-Ron
P.S. Web browsers are no substitute for a good mail application. ;-)
(For Brad, mostly),
I have a slight issue with posting the blog on WordPress. I'm using a
standard template, and I'm able to connect to the blog's XMLRPC
("Fetch Posts" works like a charm). However, when I try to post, I
get the following:
/usr/lib/ruby/1.8/xmlrpc/create.rb:195:in `conv2value': Wrong type
NilClass. Not allowed! (RuntimeError) from /usr/lib/ruby/1.8/xmlrpc/
create.rb:106:in `methodCall' from /usr/lib/ruby/1.8/xmlrpc/create.rb:
105:in `collect' from /usr/lib/ruby/1.8/xmlrpc/create.rb:105:in
`methodCall' from /usr/lib/ruby/1.8/xmlrpc/client.rb:408:in `call2'
from /usr/lib/ruby/1.8/xmlrpc/client.rb:399:in `call' from /Library/
Application Support/TextMate/Bundles/Blogging.tmbundle/Support/lib/
blogging.rb:363:in `post_or_update' from /tmp/temp_textmate.D5IM07:3
I'm at r3460. Any ideas?
Shiran
That did the trick. Thanks for a great and useful bundle.
Shiran
> OK-- found the issue and checked in a fix for it (revision 3461).
>
> Thanks,
> Brad
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
In my attempt to shoehorn together a Lang Grammar for Textpattern from
scratch ( "scopeName = source.txp" , and NOT "text.html.txp" ) I ran
into a couple of problems.
I also took a peek at how it's done in the MT Bundle, but I decided,
it's best to start from scratch.
Note.:I'm not a programmer, just a beginner of TM, usually as I
understood, this should then go into the developer mailing list, but
since I am not a developer, I decided then to post first here.
I'll summarize my observations and obstacles below:
1) grammar Scope consideration
Textpattern's syntax is very similar to Html, there is single tags (self
enclosing ) and container tags.
However, the total code blocks, used in forms and pages can get rather
complex, since in many cases you can have funny nested language
constructs that can not be matched with any of the present grammars
regex constructs.
EXAMPLE.: <li <txp:zem_nth step=1
of=2>class="odd</txp:zem_nth><txp:zem_nth step=1
> ><txp:if_article_list>activea</txp:if_article_list> </txp:zem_nth>
<txp:zem_nth step=1 of=2>"</txp:zem_nth>><txp:permlink><txp:title
/></txp:permlink></li>
(Note.:Note the second bracket after the zem_nth closing tag, the code
sample for Txp form above will parse a perfectly valid XHTML, once the
request is returned from the Server)
You can see the pref snippet that I used to test the above below.:
Sample.:
{ name = 'keyword.control.txp';
match =
'(["|\s]?<txp:.+\s/>["|\s]?|["|\s]*?<txp:.+>["|\s]*?|["|\s]?</txp:.+>["|\s]?)';
},
(works, but not with the complex constructs, like mentioned above.)
Problem.: Some of these instances make it difficult to construct the
regular expressions.
Possible Solution.: Could be excluded with negates whenever occurs
(That would be rather hackyish and not elegant)
2) Furthermore the reason, why I opted for a "source txp.scope" rather
then the other easier and integrable solution and attempt everything
from scratch, is that there is not a real hierarchy between html and txp
forms and pages, so I thought it would be more expandable and extensible
in that way.
Question: Is that so ?
Or am I terribly wrong ?
3)Question: Is the p.list format going to change to a xml format for the
Language grammars. ?
4) I made two variants of a preliminary bundle for the Grammar, would it
make sense to submit those to repository, once they reach an acceptable
stage ?
5) I'm a little perplexed with the Theme Editor, and in particular the
context of Theme names, Theme Scope names and the corresponding scope
selectors in the Language Grammar and prefs.
For Instance, for the above p.list value/pair keyword.control.txp, I did
not have a blank element of keyword control in the list.
I thought at first, that (after reading the manual ) I should have a
blank keyword control element (in the Fonts and colors pane ) and then ,
for my above purpose, I create a keyword.control.txp scope selector,
that I style for the above purpose, but that doesn't appear to seem so.
Is it correct to suspect that the element names themselves are
irrelevant for the inner functioning of the language grammar ?
I hope that this was not too long and thank you in advance for reading
this and possibly have an answer to my questions.
So for I am pretty much amazed with the editor.
regards, marios
- --
marios at CSSDelyrium
requests
http://www.consking.com/contact
________________ __ _
/ ___/ __/ __/ _ \___ / /_ ______(_)_ ____ _
/ /___\ \_\ \/ // / -_) / // / __/ / // / ' \
\___/___/___/____/\__/_/\_, /_/ /_/\_,_/_/_/_/
/___/
-----BEGIN PGP SIGNATURE-----
Comment: This might change in the future
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEb5b18tSzPOYuZvQRAiZQAKCwWFXNOAKxOT5tWGfLlbYaIQV/WgCffa8u
esaTuzI4S4IbS7pS1oP/d/c=
=Yz4x
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
For a new language Grammar I have set up a couple of test bundles that
try different variations of a grammar style, so I stumbled over some
'cases' where an actual name rule at the pattern root level of the
syntax would not be recognized at all.
EXAMPLE.:
{ name = 'entity.tag.plugin.single.textpattern';
match =
'<txp:[a-z]{3}(_([a-z0-9]{1,15}))(_([a-z0-9]{1,15}))?\s{,4}(\w{1,45}="\w{,15}"\s{,8}){,7}/>';
},
Basically I want to use the above rule to isolate any single self
enclosing language plugin tags tags from regular txp language tags and
give it a scope.
It doesn't work, I tested the above reg ex with find/replace and it does
what I want, but it doesn't work inside the Language grammar.
For the rest of the tags, I use the usual word boundaries rules with a
piped group of tag names, as in html.
So I suspected, that something like that is not allowed maybe.(Onigoruma ?)
NOTE.: I didn't use any back references there,just to simplify the case
What am I doing wrong?I'm using cutting edge with all bundles installed.
Are there any limitations, about regexes in a Language syntax at all,
that I don't know about ?
regards, marios
-----BEGIN PGP SIGNATURE-----
Comment: This might change in the future
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEecTQ8tSzPOYuZvQRAvFfAKC0GqIf+7jSwwA/QSxJ4s855PFe2QCeLyXQ
ZFDWslm9wtXRuIKriJZZa/E=
=VGAC
-----END PGP SIGNATURE-----
I have enabled the Smarty bundle, but have an issue.
I use <% for open, and %> for close. Im not sure exactly all the
places I need to change this in the smarty bundle, or what the proper
format would be. I tried playing around in the bundle, but no matter
what I did I couldn't seem to get it correct.
If anyone could provide some guidance, that would be very helpful :)
Eric Coleman
Hi everybody,
do not get me wrong about this post, but I was wondering if someone
could
help me writing this TMscript. Or maybe it is honest to say write
this script.
The idea is the following:
- I have a big LaTeX project, so I divided the report in several
documents.
- Let's say:
- master.tex
- part1.tex
- part2.tex
- Basically master.tex includes all following documents, so in case I
would typeset
the master.tex file I would get the whole document.
- There is a TM-function which allows me to set the master file in my
project, so that
typesetting any file (for example part1.tex) actually typesets the
master.tex file.
- But this takes time so it would be nicer to typeset just the file I
am working on right now.
- My Idea is:
1) change the first line of part1.tex (and or part2.tex) to %%
TM_LATEX_COMMAND%% Head include %%
2) add a line in the master.tex somewhere after \begin{document} : %%
TM_LATEX_COMMAND%% Head %%
3) when typesetting the script looks for the line (see (2)).
4a) if there is no "%%TM_LATEX_COMMAND%%Head%%" it will go on like
it does right now
4b) if there is the line "%%TM_LATEX_COMMAND%%Head%%" then I takes
the lines before
" %%TM_LATEX_COMMAND%% Head %% " and puts them on top of the
typsetted file. It also
adds an \end{document} and then typesets all.
- what I do not know is how pdfsync works then, but since I do not
know how to write this little
script I could not try out.
It would be great if someone could help me or send the website where
this is already posted.
However, I would also appreciate some helpful comments on how to
write the script by myself.
Tanks
Christoph
~~~~~
Christoph Biela
cbiela(a)gmail.com
