Hi all there
I am suffering an uncomfortable problem with TM scripts that depend on
Ruby and makes them unusable. Using for example Cmd-B in LaTeX
(toggle_style.rb -style=textbf), TM inserts instead:
no such file to load -- ubygems (LoadError)
Sometimes I fixed the problem renaming ~/Library/Application\ Support/
TextMate. Sometimes not.
I use an env
RUBYOPT=rubygems
- Juan F.
Hi all there
I am suffering an uncomfortable problem with TM scripts that depend on
Ruby and makes them unusable. Using for example Cmd-B in LaTeX
(toggle_style.rb -style=textbf), TM inserts instead:
no such file to load -- ubygems (LoadError)
Sometimes I fixed the problem renaming ~/Library/Application\ Support/
TextMate. Sometimes not.
I use an env
RUBYOPT=rubygems
- Juan F.
After a crash of my system disk yesterday and the ressurection of the
system today I'm getting the following error while trying to insert a
citation or label based on the current word:
\autoref{/tmp/temp_textmate.haeIjJ:4: command not found: kpsewhich -
show-path=tex
cha:auswahl_eines_loesungskonzeptes}
The thing is. It tells me about kpsewhich is not found but it was able
to insert the correct label.
When I fire up "which kpsewhich" in Terminal, I get the following
output:
> [Jan@iah] ~ > which kpsewhich
> /usr/local/texlive/2007/bin/i386-darwin/kpsewhich
Also I have no problem to compile my document.
Maybe it has something to do with PATH, but I'm not sure. Can anyone
give me a hint on this?
Thanks,
Jan
Am I correct in assuming that TextMate now supports synctex, and that
I need to download and install the latest LaTeX bundle in order to
have this functionality?
If so, how do I download/install this bundle?
Thanks
Geoff Vallis
I just grabbed the latest ruby.tmbundle from svn and put that in my ~/
Library/Application\ Support/TextMate/Bundles directory
When I try and run a test file with command-R I get the following
complaint
/Users/stu/Library/Application Support/TextMate/Bundles/Ruby.tmbundle/
Support/RubyMate/run_script.rb:1:in `require': no such file to load
-- /Applications/Editors/TextMate.app/Contents/SharedSupport/Support/
lib/tm/executor (LoadError) from /Users/stu/Library/Application
Support/TextMate/Bundles/Ruby.tmbundle/Support/RubyMate/run_script.rb:1
I have had a look around and sure enough can't find the files it is
referring to
require ENV["TM_SUPPORT_PATH"] + "/lib/tm/executor"
require ENV["TM_SUPPORT_PATH"] + "/lib/tm/save_current_document"
I am on the cutting edge 1.5.7 (1464) version.
Stuart
> From: Trevor Harmon <trevor(a)vocaro.com>
> Message-ID: <AA646749-1963-48F8-BA06-2DEEB46200DF(a)vocaro.com>
>
> I was thinking it might be cool if TextMate had visual tabs like
> OmniWeb or Shiira:
>
> http://www.mathgamehouse.com/images/phillryu/shiira2full.png
>
> But after testing the idea I've decided it just doesn't work with
> text. Web pages with graphics can be distinguished at thumbnail size,
> but source code files can't.
Reminds me of this:
http://basildoncoder.com/blog/2008/03/21/the-pg-wodehouse-method-of-refacto…
Be well,
Will :-}
Hello,
Maybe I'm just not understanding how it works, but while in an HTML document
I wanted to insert a DocType. I pulled up the Insert Bundle item window
(Ctrl-Cmd-T) and tried typing "doctype" to see if the shortcut came up, but
it did not. I just looked at the window again, and I see, right in the first
page of items "Insert DocType", but when I start typing "doctype" it goes
away, not matching what I'm typing. Am I missing something?
Thanks
John
In TextMate, buffer tabs are automatic: A new tab is always opened
whenever you click on a file in a project drawer. After a half hour of
navigating source code, I suddenly find dozens of tabs open at the top
of my editor window, but I can only see a few of them. This makes the
tabs feature basically unusable.
In contrast, web browser tabs operate quite differently. They're
manual instead of automatic: A new tab doesn't open unless you
explicitly open one. Until then, new data is displayed in the current
tab. TextMate's tab feature would be much more useful to me if it
worked this way --- the way web browsers do.
Does anyone prefer the current (automatic) behavior?
Trevor
So,
I've just installed the AS3 bundle from the repository in TextMate and
thought I'd share the steps I had to go through in order to make it
work, partially so I have a document explaining what I had to do (if I
need to do it again) and to help others who might be stuck.
Message for Simon Gregory: This was the bundle I downloaded from the
repository so it's possible that the svn version is b0rked... :(
I have an up to date version of TM on Leopard, and I used the "Get AS3
Bundle.sh" script that I downloaded a short while ago. Unfortunately
I couldn't find the site where it came from but it just appears to
grab the latest version from the repository by svn so it can't do that
much.
First, I got the wonderful error dialog:
> The “ActionScript 3” bundle located in ~/Library/Application Support/
> TextMate/Bundles could not be loaded and will be skipped. The
> contained info.plist appears to be corrupt or missing.
What's going on here? No idea. So I looked at the plist file in
question and found what looked like a half failed diff at the bottom:
<<<<<<< .mine
... some txt
=======
... other text
>>>>>>> .r10513
This is present in a bunch of files, I have so far found it in
build_with_fcsh.sh and asd.rb. Anywho, I took that out of the plist
file, probably breaking it slightly but at least TM now loads the AS3
bundle.
Next I created a new, blank AS3 project. Make a more or less empty
class and "Build with FCSH". Nothing, no output, no error, no
feedback, nothing. Build with MXMLC, a window pops up telling me
there's 0 errors and a successful build, but no .swf file was produced
in the deploy/ folder. Try the "Build (custom)" option, it tells me
the script is not executable. Joy. So I run the supplied compile.sh
script manually by opening the script and pressing Apple-R to run it.
TM alerts me that the script is not executable, so I make it so. OK,
so now it runs.
However, still nothing coming out of mxmlc, still 0 errors. What
happens when I run mxmlc on it's own? I get this wonderful error:
-bash: ./mxmlc: /bin/sh^M: bad interpreter: No such file or directory
Joy. That error is familiar, usually found when running a binary
built for a different architecture, but that wasn't the problem.
mxmlc turns out to be a shell script that runs slightly different
commands for windows and unix. Turns out that the default file
supplied by Adobe is also in DOS encoding (funny line endings). So,
open the file in vim and type:
# vim ./mxmlc
:set ff=unix
:wq
And the script now runs mxmlc properly. I also had to chmod a+x in
Flex/bin/* as well.
OK, so building in mxmlc now works but I know that it's slow and I'd
rather use fcsh to do my compiles. So I try building with fcsh and
get even less reponse, no progress bar, no iTerm window, nada. OK,
stay calm...
So I check the encoding of the fcsh script supplied by Flex, it too
was in DOS format so I converted it back to Unix. That script now
fires up the fcsh compiler so that part worked. Next, why was the
build command silently failing? Open up the Bundle Editor and edit
the "Build (fcsh)" command to show output as HTML. This revealed a
syntax error in the build_with_fcsh.sh script. Find the script, open
it in vim and I found the same sort of failed diffs as I found in the
plist file.
This time I just copied the r10513 file over the existing one:
# cd "/Users/gaby/Library/Application Support/TextMate/Bundles/
ActionScript 3.tmbundle/Support/bin/"
# cp build_with_fcsh.sh.r10513 build_with_fcsh.sh
Now the script works, fcsh works, mxmlc works and I have finally got
a .swf file being output into the deploy folder. Sorry for the length
of this rant but my hope is that if anybody else is fighting with AS3
under TextMate, hopefully this might shed some light on problems
they're having.
Gaby
--
Being drunk is feeling sophisticated without being able to say it.
http://www.playr.co.uk/
