Folks,
I wasn't aware that there is a cutting edge version of the cutting
edge version.
I just downloaded that and installed it (a little bit against the
"never change a running system" theory).
TM and latex compilations still work fine, but I get an error message
now, which I don't know what it means:
/Users/clausman/Library/Application Support/TextMate/Support/lib/tm/
process.rb:125: warning: Insecure world writable dir /usr/local/bin in
PATH, mode 040777
Does either of you have any pointers?
Thanks for your help,
Claus
On 19-Nov-08, at 12:09 PM, textmate-request(a)lists.macromates.com wrote:
> Message: 4
> Date: Tue, 18 Nov 2008 21:36:09 +0100
> From: Alex Ross <tm-alex(a)rosiba.com>
> Subject: [TxMt] Re: Latex bundle troubleshooting II
> To: TextMate users <textmate(a)lists.macromates.com>
> Message-ID: <D64FBDD2-B3B6-4F0C-91CF-E5D584E8F3DA(a)rosiba.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes
>
>
> On Nov 18, 2008, at 9:14 PM, Guido Governatori wrote:
>
>>
>> On 19/11/2008, at 4:58 AM, Alex Ross wrote:
>>
>>>
>>> On Nov 18, 2008, at 5:40 PM, Achilleas Lazarides wrote:
>>>
>>>> Hello again,
>>>> Seems I am still having some trouble with the latex bundle.
>>>> Basically, the first time I attempt to typeset after launching
>>>> textmate, I
>>>> get:
>>>>
>>>> ==================================================
>>>> The current PATH is:
>>>>
>>>> /usr/bin
>>>> /bin
>>>> /usr/sbin
>>>> /sbin
>>>> Please add the directory containing ?kpsewhich? to PATH in
>>>> TextMate's Shell
>>>> Variables preferences.
>>>>
>>>> Alternatively, the PATH can be retrieved from Terminal but this
>>>> requires a
>>>> relaunch:
>>>> (button to perform this operation)
>>>> ==================================================
>>>>
>>>> Now as a matter of fact the correct path is present in my shell
>>>> variables in
>>>> textmate's preferences (in "shell variables" under "advanced"), as
>>>> opposed to
>>>> just /usr/bin, /bin and sbin as mentioned in the message;
>>>> furthermore, it is
>>>> already in my usual PATH. If I do click on the button, it quits and
>>>> restarts
>>>> and everything is ok. Checking the preferences, a new PATH var has
>>>> been added,
>>>> containing my shell path. This addition occurs even if the exact
>>>> same path
>>>> variable is already present in textmate's preferences.
>>>>
>>>> If I now quit and restart textmate, the same process is repeated,
>>>> and a new
>>>> path variable added to the preferences before I can typeset
>>>> (identical to the
>>>> other ones already there), and everything works after that, until I
>>>> quit
>>>> again, and so on.
>>>>
>>>> This did not happen before I updated my latex and support bundles.
>>>>
>>>> Maybe I'm just being thick, but I can't see what is going on, and
>>>> this is
>>>> starting to get annoying. Any ideas?
>>>
>>> Update TextMate to bleeding edge by ?+Click (Option+click) the
>>> ?Check for updates?? button in TextMate's Software Update
>>> preference pane.
>>>
>>
>> I had the same problem and updating to the cutting edge did not
>> help.
>> I had to include /usr/texbin in the path in ~/.MacOSX/
>> environment.plist
>
> Updating to cutting edge is not enough. You have to ?+Click (Option
> +Click) the ?Check now? button in the Software Update prefpane.
> This downloads a special TM build that corrects a bug with the way
> TextMate puts Shell Variables into the environment. After this,
> setting ?PATH? in the Shell Variables section of preferences is
> enough.
>
> ?Alex
The show current scope shortcut (ctrl+shift+p) is not working for me in
TextMate and has not done so for a long time. Using Gerd Knops excellent
KeyBindingsEditor shows no such binding in TextMate. The system dictionary
binds it to moveUpAndModifySelection: which is indeed the action I get in
TextMate. Anyone knows what's up with that?
--
Sven Axelsson
++++++++++[>++++++++++>+++++++++++>++++++++++>++++++
>++++<<<<<-]>++++.+.++++.>+++++.>+.<<-.>>+.>++++.<<.
+++.>-.<<++.>>----.<++.>>>++++++.<<<<.>>++++.<----.
hi there,
I've made this feature request for improving the latex bundle and got
a reply that maybe the user discussion list would be more appropriate.
So here it is:
pstricks remains extremely useful and pdflatex seems to be the future
of LaTeX, although it does not support pstricks directly.
There is a simple and elegant way of having then coexist, which is to
use the pst-pdf package, which defines a new environment to wrap
pstricks figures. However, this now requires that we compile the ps
and pdf parts separately as follows:
latex <file.tex>
dvips -Ppdf -o <file-pics.ps> <file.dvi>
ps2pdf -dAutoRotatePages=/None <file-pics.ps> <file-pics.pdf>
pdflatex <file.tex>
This is properly documented in
http://tug.org/PSTricks/main.cgi?file=pdf/pdfoutput
The LaTeX bundle should be extended with a new test to see if the
pst-pdf package is loaded and perform the steps above, removing the
.ps file after the last step.
Has anyone been able to extend the latex bundle with a way to handle pst-pdf?
Thanks
Denilson
Hi,
I've one Mac (10.5.5) where HTML CodeCompletion does produce the
following error:
sh: : command not found
/Users/Wolfgang/Library/Application Support/TextMate/Support/lib/ui.rb:
86:in /bin/bash: -c: line 0: unexpected EOF while looking for matching
`''
/bin/bash: -c: line 2: syntax error: unexpected end of filemenu'
from /Users/Wolfgang/Library/Application Support/TextMate/Support/
lib/ui.rb:81:in /bin/bash: -c: line 0: unexpected EOF while looking
for matching `''
/bin/bash: -c: line 2: syntax error: unexpected end of filemenu'
from /Users/Wolfgang/Library/Application Support/TextMate/Support/
lib/codecompletion.rb:213:in /bin/bash: -c: line 0: unexpected EOF
while looking for matching `''
/bin/bash: -c: line 2: syntax error: unexpected end of fileinitialize'
from /tmp/temp_textmate.bx693a:3:in
What's going wrong on this machine?
Wolfgang
On 17 Nov 2008, at 04:36, Allan Odgaard wrote:
> For reasons unknown to me, your setup has TM pick the Support folder
> included with TM rather than the one you svn checkout.
Aha! It turns out that my .bash_profile was setting both
TM_SUPPORT_PATH and TM_PLUGIN_PATH for some reason. Those lines have
been there a while, perhaps a very early version of TM or some plugin
required that?
Anyway, I commented out those two lines and TM is now using the
correct support folder and I can once again run perl scripts!
Thanks so much for helping to track this down,
- d
Allan,
Here are the versions I have:
$ cat /Library/Application\ Support/TextMate/Support/version
9280
$ cat /Applications/TextMate.app/Contents/SharedSupport/Support/version
9279
The perl script I'm trying to run is pretty minimal:
#!/usr/bin/perl
print 123;
For the heck of it I removed:
/Library/Application Support/TextMate
~/Library/Application Support/TextMate
I also deleted TextMate.app and downloaded a fresh copy. The perl
script then ran!
I then downloaded the cutting edge version of TextMate, and the perl
script still ran.
I then followed the instructions in the wiki to checkout bundles via
subversion, and restarted TextMate. Once again the perl script would
not run, and yielded the same error:
-e:2:in `require': no such file to load -- /Applications/TextMate.app/
Contents/SharedSupport/Support/lib/tm/executor (LoadError) from -e:2
Removing:
/Library/Application Support/TextMate
and restarting TextMate, the perl script once again worked.
It looks like something may be broken in Support version 9280?
- Dave
I'm very proud to announce the release of PySmell v0.7.2, now with
extra goodness.
Changes:
* TextMate's dialog no longer errors when dealing with a huge number
of entries.
* New --input allows mutation of existing PYSMELLTAGS file; useful
to run after a file is saved
* Analyze the current file when detecting completion type; more up-
to-date suggestions
* TextMate now completes a word rather than re-writing it.
* TextMate honours TM_PYTHON - no need to set PATH
* Fixes in pysmell.vim by Krzysiek Goj; Thanks!
* Bundle ez_setup for people that don't have setuptools.
* Use argparse.py rather than hand-rolled option parsing
* Fixed issue 18 (tabs)
PySmell is an auto-completion library for Python, meant to be plugged
in different editors. It uses static analysis to generate a TAGS file
for your code, and uses that to give you suggestions. It's very fast
--- suggestions are instantaneous and analyzing Django 1.0 takes ~15
seconds.
Download from PyPI: http://pypi.python.org/pypi/pysmell/
Issue tracking at Google Code: http://code.google.com/p/pysmell
Development at GitHub: http://github.com/orestis/pysmell/tree/master
Installation:
"python setup.py install", then copy pysmell.vim, pysmell.el in the
relevant places, or double click PySmell.tmbundle.
More instructions included in README.markdown.
Thanks,
Orestis Markou
--
orestis(a)orestis.gr
http://orestis.gr/
When coding in AS3 in TextMate I like to put in some nice JavaDoc
style comments:
/**
* Fetch up a dice from the server
* @param Number dice_num Which dice to get (1-6)
* @return NetDice Populated dice info object
* @access private
*/
All well and good. I put a tab after the keyword declaration, so I'd
type:
@param<tab>Number<tab>dice_num<tab>etc...
For the first row. When I try to populate the return value:
@return<tab>...
The value gets automatically converted into this:
@↩
Why does this happen? What can I do to turn it off? My workaround is
to type this instead:
@return<space><tab>...
The go back and delete the space but that's just a PITA. Any
suggestions?
G.
--
Being drunk is feeling sophisticated without being able to say it.
http://www.playr.co.uk/
On Nov 16, 2008, at 7:00 AM, Allan Odgaard wrote:
> When the path contains ‘TextMate.app’ then it is a sure sign of not
> being up-to-date (since it favors the Support folder inside
> TextMate.app).
>
>> [...] At revision 10740.
>
> We’re at r10812, but it’s now http://svn.textmate.org/trunk/
>
> See http://lists.macromates.com/textmate/2008-October/027271.html
> for how to relocate.
Great, thanks Allan!
I've just relocated my /Library/Application Support/TextMate/ to the
new svn repository, and updated so I'm now at revision 10812 (feels
good to be up to date once again).
TextMate tells me it's at cutting edge version 1464.
I then reloaded bundles, restarted TextMate for good measure, and
tried once again to use the Perl bundle's Run command on my script,
but I'm still getting:
-e:2:in `require': no such file to load -- /Applications/TextMate.app/
Contents/SharedSupport/Support/lib/tm/executor (LoadError) from -e:2
Might my ~/Library/Application Support/TextMate/ folder be messed up
somehow? Is there a way to reset it yet preserve the themes and
bundle's I've added and created?
