Typeset and View works fine. But, I just found the solution - I had checked out the complete set of bundles via svn, and I had not done an svn update since two or three days. I just did an svn update, and reloaded the bundles, and now the Latex preferences dialog shows up. Sorry for the false alarm. I'm still learning TextMate, and I have barely begun to grok the ins and outs of bundle management. Bundles are both the blessing and the curse of TextMate.

Kevin Horton

On 6 Aug 2007, at 20:43, Brad Miller wrote:

Kevin,

Does the Typeset & View command work for you? Both commands reside in the same directory, so if you get the same kinds of error, specifically texMate.py not found then I think your bundle may be corrupt somehow.

Brad

-- Brad Miller Assistant Professor, Computer Science Luther College

On 8/6/07, Kevin Horton khorton01@rogers.com wrote: I tried to go to the preferences dialog in the Latex bundle, and nothing happens. I see "/bin/bash: line 3: configure.py: command not found".

Kevin Horton Ottawa, Canada

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512

guerom00 wrote:

Same here… How do you “svn update” ? I'm clueless with this thing…

If you have subversion installed (and have a working checkout in /Library/Application Support/, which is the standard) then open the Terminal (in Applications/Utilities) and type this line:

svn up "/Library/Application Support/TextMate"

Otherwise this link should get you started: http://lists.macromates.com/pipermail/textmate/2007-August/021331.html

TextMate was recently updated, maybe this works in the current version. Try checking for updates in "Preferences".

Hope this helps, Simon - -- + privacy is necessary + using http://gnupg.org + public key id: 0x6115F804EFB33229

On Aug 8, 2007, at 9:16 AM, guerom00 wrote:

Simon Ruderich <simon@...> writes:

...

If you have subversion installed (and have a working checkout in /Library/Application Support/, which is the standard) then open the Terminal (in Applications/Utilities) and type this line:

svn up "/Library/Application Support/TextMate"

Thanks :) Here is what I receive

[rom:~] rom% sudo svn up /Library/Application\ Support/TextMate Password: subversion/libsvn_wc/lock.c:678: (apr_err=155005) svn: Working copy '/Library/Application Support/TextMate/Bundles' is missing or not locked

Do you have anything under /Library/Application Support/TextMate? What do you get if you do: svn status /Library/Application\ Support/TextMate

??

TIA

Haris Skiadas Department of Mathematics and Computer Science Hanover College

On Aug 8, 2007, at 9:44 AM, guerom00 wrote:

Charilaos Skiadas <cskiadas@...> writes:

...

Do you have anything under /Library/Application Support/TextMate? What do you get if you do: svn status /Library/Application\ Support/TextMate

I remember now : I keep my bundles in ~/Library/Application Support/TextMate/Pristine Copy/Bundles

That's really not the place to keep bundles checked out from subversion: http://blog.circlesixdesign.com/2007/03/02/textmate-bundles-explained/

So now, I receive :

[rom:~] rom% svn up Library/Application\ Support/TextMate/Pristine\ Copy/ subversion/libsvn_subr/utf.c:466: (apr_err=22) svn: Can't convert string from 'UTF-8' to native encoding: subversion/libsvn_subr/utf.c:464: (apr_err=22) svn: Library/Application Support/TextMate/Pristine Copy/Latex.tmbundle /Snippets/\begin{}?\226?\128?\166\end{}.tmSnippet

This is gonna drive me nuts… I can feel it… I seem to remember reading a workaround for this UTF-8 problem but it involves environnement variable in bash. I use tcsh…

You need to set the environment variable: LC_CTYPE to have value: en_US.UTF-8 You can probably find out how to do this in tcsh. The following should do it, according to: http://wings.buffalo.edu/computing/ Documentation/unix/tcsh.html

setenv LC_CTYPE en_US.UTF-8

Typing simply "setenv" should show you the variables you have available.

TIA

Haris Skiadas Department of Mathematics and Computer Science Hanover College

On Aug 8, 2007, at 10:18 AM, guerom00 wrote:

Charilaos Skiadas <cskiadas@...> writes:

...

setenv LC_CTYPE en_US.UTF-8

That did it. Unfortunately a svn update didn't solve any of the problems I have with TextMate…

For various reasons I have missed the beginning of this thread, so I am not sure what the problems you are having are, but they are likely caused by one of the following:

Outdated Support directory Out of date copies of bundles or support directory under ~/Library/ Application Support or /Library/Application Support

I'll look into that.

Thanks a bunch.

Haris Skiadas Department of Mathematics and Computer Science Hanover College

On Aug 8, 2007, at 10:33 AM, guerom00 wrote:

Well… A lot of bundles require a ENV["TM_SUPPORT_PATH"] + "/lib/dialog.rb" which does not exist… Latest svn repository have indeed a dialog.py file…

I'm not sure where the problem is…

The problem is that those bundles are not up-to-date. This file no longer exists, and all bundles in the repository have been updated to use ui.rb instead, IIRC. So the problem is simply that you have local version of the bundles, that have not been updated. The simplest solution, unless you have personal bundles and changes etc, is to just remove everything from ~/Library/Application Support/TextMate, then to download the latest TextMate (Version 1.5.6 (1414), came out about 2 days ago) and you should be good to go. If you have personal bundles but no personal changes, move those bundles out of that directory first, and then bring them back at the end.

Have you checked out the full subversion repository, or just bits and pieces? If so, are all the pieces in the same place, or do you have some under /Library/Application Support/..., others under ~/Library/ Application Support/Bundles etc?

Haris Skiadas Department of Mathematics and Computer Science Hanover College

On Aug 8, 2007, at 11:38 AM, guerom00 wrote:

Charilaos Skiadas <cskiadas@...> writes:

...

The problem is that those bundles are not up-to-date.

Hmmm I thought this “svn update” would take care of that. I'm a little bit lost…

It will have updated the things that reside in the directory where you did the update. However, this might not be all the bundles, and it might also not include the support directory. If you have versions saved under /Library/... or ~/Library/.... (but not Pristine Copy), then they will take precedence over whatever is in the Pristine Copy. The precedence is prescribed in the article I linked to in one of the previous posts.

I'll look into it. Thanks :)

Haris Skiadas Department of Mathematics and Computer Science Hanover College

Here's one quick thing to check since you say you have (against all advice) checked out your bundles to Pristine Copy...

Look in ~/Library/Application Support/TextMate/Pristine Copy/Bundles/Latex.tmbundle/Support/bin

If you do not see configure.py in that directory then you have not updated properly.

Brad

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512

guerom00 wrote:

Thanks :) Here is what I receive

[rom:~] rom% sudo svn up /Library/Application\ Support/TextMate Password: subversion/libsvn_wc/lock.c:678: (apr_err=155005) svn: Working copy '/Library/Application Support/TextMate/Bundles' is missing or not locked

??

TIA

Whats happens if you open this directory in the Finder. Does it exist? What is the output of these two lines in the Terminal? Type enter after each of them.

svn info "/Library/Application\ Support/TextMate"

svn status "/Library/Application\ Support/TextMate"

If you don't made any changes to your subversion checkout you can safely remove this TextMate directory and type the following:

svn co http://macromates.com/svn/Bundles/trunk/ "/Library/Application Support/TextMate"

This will download a new checkout of TextMate Bundles.

Hope this helps, Simon - -- + privacy is necessary + using http://gnupg.org + public key id: 0x6115F804EFB33229