In the previous version of TextMate when I submitted a highlighted set of
queries to MySQL it would execute them all in order and show the results.
In the new version it only seems to execute the first SQL statement out of
the highlighted group. This is a big problem for me because I only use
TextMate to edit and submit stored procedures which require at least three
separate statements to be submitted (delimiter change, my stored procedure,
delimiter change back.) Does anyone know of a way to fix this in the new
version? Or if not can someone point me to link of the previous version so
I can reinstall it?
Thanks
--
Dave
i have 3 mac computers, and i updated textmate to the latest version, one by
one. seems that mtasc is not working anymore, i get a colored blank swf all
the time.
is working for you, macuser?
I've installed, deleted the symbolic link, installed again, but still
not working.
edit in textmate is in the menu, but clicking it just makes a ping
noise.
suggestions?
TIA
Hello,
I'm running build 1405 and when trying to use the "Show Changes"
feature, when doing a svn log on my project I get the following:
svn: invalid option character: c
Type 'svn help' for usage.
Anybody else experiencing this?
Thanks
When trying to configure the SQL Bundle, I get the following error in
my console.log, http://pastie.caboo.se/77638. I'm using a fresh
install of Textmate v1405. No other textmate plugins are installed
besides the ones that are installed by default.
Hi,
in 1.5.5 and 1.5.6 is a bug in the "Find in Project" Dialog. Here is
how you can reproduce it:
- open a project
- open "Find in Project"
- set "Find:" to aaa.bbb
- set "Replace:" to ccc.ddd
- activate an other TM window (e.g. the project window)
- re-activate the "Find in Project" dialog
- doubleclick bbb from the "Find:"
- copy
- doubleclick ddd in the "Replace:"
- paste
bug: a blank is inserted before the pasted bbb in the "Replace:" field
cheers,
Alex.
I had a few days left of my trial period when I received a software
update and I haven't been able to open PHP files anymore with that
version.
I tried to downgrade and the newest version that can handle PHP-files
is Version 1.5.5 (1368).
What happens when newer versions try to open a PHP-file they open
them without any syntax colouring, stay up for a few seconds and crash.
The following attachments are the crash log and an example PHP-file.
Is the PHP-bundle doing something nasty or am I doing something wrong?
Regards,
Stefán Vignir Skarphéðinsson
Attached is a patch file containing the changes between the CVS
version of the Latex bundle and my version. They are as follows:
1a. Improve the parsing of %!TEX lines, so that it conforms to the
behaviour of TeXShop. Previously it was too strict about the format;
in particular it demanded a single space following the = sign, rather
than arbitrary whitespace. (Oddly, a single space before the = sign
*is* required.)
1b. Do not ignore "file not found" errors in options.rb. (Why was this done?)
2a. The second group of changes concerns the error handling in the
'Typeset & View' command. Previously, detection of errors depended on
parsing the output of the TeX command. However, it is difficult or
impossible to do this reliably, because of the variety of forms that
error messages can take. The new code also looks at the exit value of
the tex process.
2b. While working on the latexErrWarn.py script, I noticed that the
code detecting the -v (verbose) option was broken. I have fixed it;
but, to conform to existing behaviour, this option is no longer passed
to the script.
3. Allow per-file setting (in a %!TEX line) to override the global
$TM_LATEX_PROGRAM setting. For backwards compatibility reasons, an
exception is made for latexmk. There is a new option
$TM_LATEX_COMPILER which does over-ride everything; this should be the
recommended way of using frameworks like latexmk in the future.
Eventually the latexmk exception should be removed.
Robin
A new version of Latex Watch is available, which fixes a number of
bugs. It's available here:
http://www.puffinry.demon.co.uk/LaTeX%20Watch%202.5.dmg
Latex Watch takes a lot of the hassle out of using Latex, by quickly
updating the document preview whenever you save a change to your
source file. It saves you having to manually recompile all the time,
and it's also quite a bit faster too. See the included help file for
more details.
Changes since 2.4:
- Delete .watcher_pid file on exit. (I think this was broken by 2.3.)
- Fix bug introduced in 2.4 that broke TeXShop updating.
- Use a sanitised name for the .foo.* files, because format names containing
spaces don't seem to work (so we would fail for filenames with spaces in).
- Change into the working directory, rather than using the full path, to
avoid problems caused by special characters in the name of some ancestor
directory.
- Quote Applescript strings, so that filenames containing special characters
(backslash and double quote) will not cause Applescript errors. (They do
still cause problems with PDFSync in Skim: see
https://sourceforge.net/tracker/?func=detail&atid=941981&aid=1753415&group_…)
- Catch the obscure case where the filename ends in ".tex\n", which
would previously cause mysterious-looking problems.
- Remove the 'hide extension' attribute on the .tex file, if TeXShop is
used as the viewer, otherwise updating will fail for interesting reasons
that I won't go into here.
Robin
Hi,
Since the last update I'm having problems with the ActionScript
bundle and XTrace. All my debugging code now gets printed out in the
flash movie rather than in the XTrace window as it used to before.
I think I've done all the necessary steps:
1. Add my folder in the security settings in Flash
2. Fire up XTrace
3. Add the trace argument to mtasc.yaml
Firstly nothing displayed in the preview window. The .swf file ran
fine in a browser but not under TextMate. I modified the build
script (point c below) to represent the file as a proper URL rather
than a file:// path and this worked, but I still don't get any debug
out, nor do I get a security warning.
I made a few tweaks to the mtasc build script:
a. Add the command it used to build the swf as a comment in
underneath the HTML
b. Allow for the 'app' yaml statement to be an array of files rather
than a single file
c. Allow me to prefix a location to the swf file, such that the
output HTML is:
http://localhost/~gaby/game/blah.swf
rather than
/Users/gaby/Sites/game/blah.swf
Which made the preview work.
I'm really stuck here as I found the XTrace output invaluable,
whereas the in-swf version is next to useless as the important data
always runs off the edge of the movie! Help! I'm going mad!
Gaby
--
Junkets for bunterish lickspittles since 1998!
http://www.playr.co.uk/
