I am having trouble using the subversion bundle in textmate after my
upgrade to leopard. I did a clean install of leopard and TM, and
haven't added any bundles, just using the default configuration.
Here are the troubles I am seeing, is anyone else having this issue /
know how to fix it?
when I try to commit a file i get this error:
ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
Permission denied, please try again.
ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
Permission denied, please try again.
ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
Permission denied (publickey,password,keyboard-interactive).
svn: Commit failed (details follow):
svn: Connection closed unexpectedly
I have seen some stuff on ssh-askpass, but it looked like this was
supposed to pop up a window for me to type my password in? that didn't
happen...
when i try to "blame":
NoMethodError
reason: undefined method `+' for nil:NilClass
trace:
/Applications/TextMate.app/Contents/SharedSupport/Bundles/
Subversion.tmbundle/Support/format_blame.rb:49
/Applications/TextMate.app/Contents/SharedSupport/Bundles/
Subversion.tmbundle/Support/format_blame.rb:43:in `each_line'
/Applications/TextMate.app/Contents/SharedSupport/Bundles/
Subversion.tmbundle/Support/format_blame.rb:43
when i try to "log":
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
1.8/rexml/source.rb:226:in `pos': Illegal seek (Errno::ESPIPE) from /
System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/
rexml/source.rb:226:in `current_line' from /System/Library/Frameworks/
Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/rexml/parseexception.rb:
44:in `line' from /System/Library/Frameworks/Ruby.framework/Versions/
1.8/usr/lib/ruby/1.8/rexml/parseexception.rb:28:in `to_s' from /
Applications/TextMate.app/Contents/SharedSupport/Support/lib/escape.rb:
30:in `htmlize' from /Applications/TextMate.app/Contents/SharedSupport/
Bundles/Subversion.tmbundle/Support/svn_helper.rb:90:in
`handle_default_exceptions' from /Applications/TextMate.app/Contents/
SharedSupport/Bundles/Subversion.tmbundle/Support/format_log_xml.rb:171
REXML::ParseException
There are some things that work, like "status", "info", but it's
pretty much unusable if I can't get it to commit... Anyone have any
ideas?
-Josh
I have a very simple command
names=( $TM_SELECTED_TEXT )
for name in ${names[@]}
do
touch $TM_DIRECTORY/$name.php
done
basically you select a list of text
about
policies
hours
contact_us
and it generates a php page for each item in the current directory -
it does that well enough, what would be truly excellent (and I think
this is easy) is to gather all those pages into a scratch project - I
actually have a laundry list of things I'd like it to do (all likely
pretty easy IMHO) but I really don't want to seem greedy - I
appreciate the effort everyone on this list puts out on a daily basis..
saul - visualchutzpah.com
hi there
I am a TextMate user in a primarily Vim development shop writing php
and html. Vim does this thing where it adds a new line to the end of
any files it saves. Here is an example, foo.txt was made with Vim,
foo2.txt was made the TextMate.
Desktop jachin$ vi foo.txt
Desktop jachin$ mate foo2.txt
Desktop jachin$ hexdump foo.txt
0000000 66 6f 6f 0a
0000004
Desktop jachin$ hexdump foo2.txt
0000000 66 6f 6f
0000003
Where this cases a problem is with subversion. We are starting to see
a lot of svn diffs with:
No newline at end of file
Files are showing up as modified that, for all practical purposes, are not.
One solution would be to just have all the Vim developers to :set
noeol, but Vim is the standard text editor here and all other text
editors must conform.
I was hoping TextMate would have a preference setting under "Text
Editing" or "Advanced"->"Saving".
Also one more wrinkle, sometimes, even the "Vimers", do not want that
final line break (in the case of some html files), so a perfect
solution would allow us to set this behavior on a file type basis.
Is there a way to hook into the save command through a bundle?
Are there any other ideas any one has for a solution?
Thanks
-jachin
Hello all,
I use TextMate to create PDFs with LaTeX. I've configured TextMate to
use pdflatex as the compile engine (TM_LATEX_COMPILER=pdflatex and the
default engine in the LaTeX preferences is pdflatex too). That works
fine.
Today I had to use for some reason the package epsfig and TextMate ran
everytime latex instead of pdflatex. Finally I forced the use of
pdflatex with the "%!TEX TS-program = pdflatex" directive in the tex
file.
Is there an explanation for that behaviour and maybe a solution for
that? (I found 3 postings here which are somehow related to that
problem, but because I'm not an expert, I didn't get the clue, which
might be in there.)
Thanks for your attention
Juergen
--
Juergen Arndt
Hi all
I was recently working on a LaTeX project, when suddenly I got this
message at the start of the log window:
"There was a problem reading the preferences file, continuing with
defaults"
After it, I get one run with zero errors. I don't think the problem
lies in my tex-file, since it used to work fine before. I tried
repairing permissions and tried updating my bundles which was to no
avail. Anybody out there experiencing the same. I'm using the newest
build (1436) of Textmate and check out the whole trunk including all
bundles and support folders via svn to /Library/Application\ Support/
TextMate. I'm currently at the newest checkout 8446. I can change the
settings in my LaTeX preferences and they stick, so why can't the
typeset engine read my preferences?
Thanks for any help
Oliver
The comments defined via TM_COMMENT_START I use with 'command' /
but how do I comment/uncomment using the pattern defined in
TM_COMMENT_START_2 ? I tried all key combinations I could imagine and
googled, no luck.
regards
--
Roberto Saccon
http://rsaccon.com
I am having a strange problem with Typeset & View that makes no sense
to me. It works fine in simple documents with the same preamble, but
not on a longer one. The document typesets as it should, but the
focus does not change to Skim. I get the following error:
sh: -c: line 0: syntax error near unexpected token `(' sh: -c: line 0:
`dvips QuantumCalculus.dvi -o QuantumCalculus.ps' sh: -c: line 0:
syntax error near unexpected token `(' sh: -c: line 0: `ps2pdf
QuantumCalculus.ps' sh: -c: line 0: syntax error near unexpected token
`(' sh: -c: line 0: `/Applications/Skim.app/Contents/Resources/
displayline 177 "QuantumCalculus.pdf" /Users/jenny/Desktop/Pending/
QuantumCalculus.tex'
A fatal error occured, log file is in QuantumCalculus.log
I have tried changing the viewer, but the error message is essentially
the same. The focus remains in TextMate, the typeset document is
correct, and there are no errors in the log file.
I created a new version of the same document by pasting in small
section after section to find the problem. It typeset perfectly each
time, all the way through to the end. The two files are identical and
one works, the other doesn't. Naturally, I began using the second,
but after a dozen or so uses of Typeset & View, it gave me the same
error message as above.
Thanks for the help,
Jenny
I cant work out the regex in the c bundle
but basically i need to be able to get function definitions that look
like this into the symbol list.
void test(int *a,
int b)
{
}
can anyone help ?
It seems like the mootools bundle wrongly scopes variables named the
same as methods in mootools' classes as methods.
Example:
http://pastie.textmate.org/private/nsry0oftvpsfftyul6lslw
(make sure you use a theme like Blackboard which highlights js)
As you can see the map variable is highlighted, and wrongly scoped
like support.class.array.js.mootools.
Unfortunately I'm still very new to TextMate language grammars and
not very confident with mootols, so I'm not sure I'm in a position to
file a patch. The way to fix this thought, I presume would be to look
for a leading '.'(dot) instead of word boundary for all class
methods. Something like:
match = '(?<=\.)(map|forEach|...)\b';
The mootools bundle is Joe Maller, is he still around here available
to fix?
Regards,
Peter Haza