-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
i have a small problem with the Latex Bundle. When using Typset & View
the popup window immediately closes after compile, if no error is
thrown. If a warning is displayed, you can only see that there are
warnings happening, but not where and why. Is there a possibility to
have the windows stay on screen in that case?
Bundle Version is... today.
Greetings
Florian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGImiC8RlGMqQ8m7oRAi2JAJwNnScqERFZMoJwpj/OZ7iwQ0azYgCgih+3
V086jilrx9abBJEFXvBevY4=
=BJt/
-----END PGP SIGNATURE-----
>Simon: How feasible is it to break this
>bundle into two parts? Will that put us ahead or behind of where we
>are with the current stand-alone bundles?
Very feasible, and the combined bundle is ahead of the two standalones... although there are points where they need to
merge/work out which solution is best.
>It sounds like most of us on on the same page, here. I think it'd be
>nice if we could agree on a single AS3 and a single Flex bundle to
>focus our efforts on so we have something to congregate around.
>Nominations?
Personally I don't mind. I'd be happy to see it broken up on the grounds that the bundle title is far far too long at the
moment ;) One thing I'd be concerned about is a possible duplication of build and help commands and their associated
TM_BUNDLE_SUPPORT/bin and lib files. But this is coming from a bundle developer perspective and we should focus on the
end user so can't be used as a reason not to.
Allan - any chance of getting a TextMate icon for .mxml files?
Context:
I needed to insert tex files which filenames contained spaces into my
document. LaTex can handle this efficiently if quotes are provided in
the \include (like in \include{"bla bla/bla bla"}).
For easy moving along my document, I intended to use the "Open
Included File" command. But that command doesn't handle the quoted
filenames, as the quotes are taken into account as normal characters.
So here I am with a line to be added to that command in order to
correct that misbehaviour:
10: ...
11: if options.empty?
12: print "Did not find any appropriate item to open in #{ENV
['TM_SELECTED_TEXT'] ? "selection" : "current line" }"
13: else
14: options[0].each{|el| el.gsub!(/(^\")?(\"$)?/, '')} #<--
Here it is!
15: filepath = `kpsewhich #{e_sh options[0]}`.chomp
16: if filepath.empty?
17: ...
I don't know how to commit changes in a bundle (according I am
allowed to!). So now it's up to you, folks, to add it to the repository.
Note that I quickly and unformally tested it, and everything seems ok.
Xavier Cambar
Hi all, I'm a Textmate newcomer. I'm using it to write my dissertation
in Latex. I ditched TexShop and I really love Textmate. I've watched
the video tutorial, read the documentation and have everything setup
and working. I have a master file and the compilation works
flawlessly.
The one thing I haven't been able to use is the \ref{} and \cite{}
completion. I have a bib file linked to the master file and my
bibliography shows fine when I compile the document. I just can't get
completion to work. Same thing with \ref{}, I added colon (:) to the
set of word characters but nothing. When I'm in a \ref{} or \cite{}
and press escape, nothing happens, I press option-escape and nothing
happens. Type the first few letters and press escape, nothing. If I'm
outside of \ref{} or \cite{} and type eq: and then escape I DO get
completion to work but not if I'm inside of the {}!!!!
If I'm anywhere outside an {} and press option-escape I get:
Label based on current word.. 1
Citation based on current work... 2
but if I choose either I get a crosshair pointer, what is this for?
I'm running Textmate version 1.5.4 (1360) and both the Lattex bundle
and support folder are the latest from SVN. Mac os X 10.4.8.
Thanks for your help,
Andres
--
Andres Gonzalez-Mancera
Biofluid Mechanics Lab
Department of Mechanical Engineering
University of Maryland, Baltimore County
andres.gonzalez(a)umbc.edu
410-455-3347
> Hi,
>
> I found a tiny error. Here the corrected utf-8 version of gspell.
>
> BTW In addition to that it is very easy to write out all google
> suggestions delimited by a '|' within the multiple word spell
> checking. With the help of a small command which shows this list as
> pull-menu you can edit each error very handy ;)
>
> Cheers,
>
> Hans
Thanks Hans, before reading your recent replies with the attached
files, I had already started work on UTF-8 version with environment
variable support (I receive the list in digest form, so I'm not
always up to date with the activity here.) I'm not quite sure if my
contribution is any better or worse than yours because I essentially
cannibalised the HTML bundle for encoding and decoding UTF-8 for POST-
ing and GET-ting with Google's servers. As a result my effort relies
on entities.txt existing in the Support directory in the Textmate
bundle (this means that I can no longer supply it as a singular
tmCommand), I genuinely do not know if this is a better method for
handling this sort of thing - perhaps someone on this list could help
clarify.
Incidentally, I think there was an error in the original version
which was inherited by the version you've supplied - the final tab
stop was not being preserved, to correct this remove the line 'text
+= "$0"' and replace 'print $text' with 'print "#{$text}$0"'.
[The GSpell bundle is available here][1]
[1]: http://homepage.mac.com/andy.herbert/.Public/GSpell.tmbundle.zip
I have been running into a problem with Textmate that for me, anyway,
is a major hurdle. When I'm editing an HTML document, and I'm using
Textmate's project drawer, I often want to use the open document as a
basis for other documents. I go to "Save As..." and name the file, and
hit enter. In almost every other Mac OS X program that I know, that
command simply creates a new document with the old document as the
starting point.
However, with Textmate's project drawer, the old file has essentially
been renamed by the new one. I have to go back and re-add the old file
to have it show up in the Project drawer again.
I have searched the archives of the Textmate list, and one other
person has mentioned it - about a year ago. Some of the suggestions
included hiding the program and bringing it back, re-booting the
program, hiding the drawer - nothing works at all for me. I can't even
drag the old files form the finder, I have to go to FIle>Add.
So my question is: is there any hope for this bug to be resolved? Are
there any other fixes that I may not be aware of? I dunno - I would
think this would be a rather glaring problem that more people would be
clamoring to have fixed. I'm not a hardcore coder or anything - just
someone who writes his own HTML. It just seems sort of... well,
primary.
I do appreciate the power that Textmate has, and I can understand how
useful it can be to people's workflows. But every time I try to "get
into" it, something basic like this comes up as a roadblock and puts
me off from wanting to use it. (See my old discussion about the Open
Document in Running Browser command, which sadly still does absolutely
nothing) I want to love Textmate, I really do. Just any help at all
would be appreciated.
BTW: I'm on a MacBook Pro running OS 10.4.9 and using Textmate build 1.5.5/1368
I've just been trying TextMate, trying to move away from TextEdit and
TextWrangler. One thing which is really bugging me is the way it underlines
hyperlinks on the 'Plain Text' setting. If I wanted that kind of behaviour
I'd use Microsoft Word! Is there a way I can set it up so that plain text is
exactly that, completely plain vanilla typing?
Thanks,
--
J. Simon van der Walt ----- Composer
<http://www.jsimonvanderwalt.com>
Is there a limit to the size of a plist for tm_dialog? If so, is
there a workaround? I think I'm hitting a limit, if I take this
shell escaped output and manually trim it, I can run it as a shell
script that seems alright:
/usr/lib/ruby/1.8/rexml/encoding.rb:22: command not found: /
Applications/TextMate.app/Contents/PlugIns/Dialog.tmplugin/Contents/
Resources/tm_dialog -mp \<\?xml\ version\=\"1.0\"\ encoding\=\"UTF-8
\"\?\>'
'\<\!DOCTYPE\ plist\ PUBLIC\ \"-//Apple\ Computer//DTD\ PLIST\ 1.0//EN
\"\ \"http\://www.apple.com/DTDs/PropertyList-1.0.dtd\"\>'
'\<plist\ version\=\"1.0\"\>'
'\<dict\>'
' \<key\>photosets\</key\>'
' \<array\>'
[...hugefrickin'SNIP...]
' \<key\>title\</key\>'
' \<string\>Vista\ Point\</string\>'
' \</dict\>'
' \</array\>'
'\</dict\>'
'\</plist\>'
' select_photoset
/tmp/temp_textmate.1kkRWq:88:in /bin/bash: -c: line 1: unexpected EOF
while looking for matching `''
/bin/bash: -c: line 4: syntax error: unexpected end of filecall'
from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/
progress.rb:36:in /bin/bash: -c: line 1: unexpected EOF while looking
for matching `''
/bin/bash: -c: line 3: syntax error: unexpected end of filecall'
from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/
progress.rb:49:in /bin/bash: -c: line 1: unexpected EOF while looking
for matching `''
/bin/bash: -c: line 3: syntax error: unexpected end of filefork'
from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/
progress.rb:47:in /bin/bash: -c: line 1: unexpected EOF while looking
for matching `''
/bin/bash: -c: line 3: syntax error: unexpected end of filedialog'
from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/
progress.rb:40:in
Hello,
I noticed that my TextMate updated this morning to Version 1.5.5
(1383). Along with this came a new feature in the HTML Bundle which
I have found is causing me some annoyances. The feature I am talking
about is in response to ticket 20CC5FF4.
I am using PHP with Smarty as my template engine, and previously I
would include <!--{literal}--> in my code to escape Smarty parsing on
script blocks. Now when I do this the entire block of code becomes
commented out. While this is not a crucial bug it is a new annoyance
for me as it is very useful to have syntax highlighting on script
blocks.
Here is an example of my code:
<!--{literal}-->
<script language="javascript">
function foo() {
return "bar";
}
</script>
<!--{/literal}-->
If you require more information please just let me know. If anyone
has any idea how to fix this I would greatly appreciate it.
Thank you.
---
Philip Plante
913-302-9933
mail(a)pplante.com
