Hi,
There were a number of QuickTime tutorialsI watched a month or so ago
showing how to use TextMate (general editing info: autocompletion, tag
balancing, keyboard equivalents, etc.) that were of interest to me as
a long-time BBEdit user who's begun the switch to TextMate.
I can't remember how I got to them, but I thought it was via
macromates.com, but I can't find them any more. Googling "textmate
videos" brings up lots of stuff, but not the ones I'm looking for.
The person doing the walkthroughs had a northern European accent; he
was very soft-spoken (but had very good English). Does this sound
familiar to anyone?
--
Regards,
Christopher Mackay
I'm facing compiling problems after the TM update to 1.5.8 (bleeding
edge).
I save my tex-files in my project in Latin1. As soon as i open a new
file in the project and want to compile it, i get the following error
message.
"LaTeX Error: Command \textcurrency unavailable in encoding T1"
When i save the file with "save as" and make sure TM saves it in
latin1, and i close the file, then the compile process suceeds. I'm
sure I haven't faced this problem with 1.5.7. When i downgrade to this
version, everything works fine. as soon as i upgrade, i have this
problem.
I think TM wants to save everything in utf8. At least i realised that
former latin1 docs were saved as utf8. In the prefs pane > advanced>
saving there is "latin1" listed under "file encoding".
Hope somebody can help me
Is there anything further on this issue? I'm experiencing the same results
for a fresh checkout from an svn+ssh repo, performed through TM.
> On 24 Jan 2008, at 21:59, dave.myron wrote:
>
> >> [...] the default values for the above should become:
> >>
> >> svn log --xml --limit 15 -vr HEAD:1 \
> >> «file» 2>&1 | ruby -- "${TM_BUNDLE_SUPPORT}/format_log_xml.rb"
> >>
> > Digging up an old thread here, but I'm getting these same problems
> > with the
> > latest TextMate and the latest Subversion bundle.
> >
> > When I run the second command above (the *parsed* one with defaults)
> > [1] I get
> > the same *REXML* error [2].
> ... [show rest of quote<http://www.nabble.com/Subversion-bundle-problem-td13754459.html#>
> ]
>
> So you can reproduce the error outside TextMate?
>
> > However, if I change it to this (two-liner) it
> > works just fine (of course, it doesn't show in TM...):
> > [...]
> > The error with the rescue block uncommented:
> > /opt/local/lib/ruby/1.8/*rexml*/source.rb:226:in `pos': Illegal seek
> > (Errno::ESPIPE)
>
> It would appear the *REXML* *parser* treats the IO object as more than
> just a pipe (i.e. it tries to seek).
>
> Try instead of using '</tmp/test.log' do: 'cat /tmp/test.log|ruby …',
> see if that changes things. Also try change '2>&1' to '2>/dev/null' in
> the version that fails for you in Terminal.
>
--
Dana
I'm a new TextMate user trying to write a simple bundle command to launch my g++
builds from TextMate. Leaving out the stuff to HTMLify the results (which
doesn't seem to make a difference to this bug), it looks like this:
cd ${TM_PROJECT_DIRECTORY}
./build.sh
Where build.sh is a script which calls make on a series of makefiles, checking
the result each time. It works fine if I call it from the command line. But
when I trigger the command in TextMate, the compiles work fine, but ar calls
("ar crv") to build the library fail pretty consistently with errors like this:
ld: in ../hw_nmtlib_core.a(__debug_frame), not a valid archive member
The error is apparently in the .a file, as executing build.sh from the command
line will still generate the error, until you force it to regenerate the .a file.
I'm hoping someone has an idea what might be going on here, because TextMate
will be a dream if I can get this working properly.
Thanks,
Sol
hi all,
while switiching documents in Latex the following happens.
Hitting the ENTER-key on my keyboard as my cursor is somewhere in the
name of a document (like \input{moretexthere.tex}) results in 'popping-
up' the file 'moretexthere.tex' together with a warning in a yellow
area:
-:14: warning: Insecure world writable dir /Users/.....etc..path...
in PATH, mode 040777
-:18: warning: Insecure world writable dir /Users/.....etc..path...
in PATH, mode 040777
The path stops at a folder where (eventually - 4 subdirectories
deeper) the document I'm working on is located.
Can I improve my settings so that this warning dissappears?
I've seen this mentioned before but couldn't find the thread. My
TextMate.app is located in /Applications and the folder I'm working in
is somewhere in ~/Documents and this all with up to date software and
so on.
Thanks for any reply,
Gert
I was wondering if it was possible to map a key (I'll choose [enter])
to the following procedure:
go to the end of the line (given by a particular column) via tabs and
enter two backslashes and return.
alternatively, if the distance to the given column is less than some
number K, go to the next line, tab over T many tabs, hit two
backslashes and return.
The main use of this for me would be inside the align environment, and
within tables--that way the layout of the align's lines appear
consistent automatically, instead of me having to do it by hand.
Evan
--------------------------------------------------
Cole's Law:
Shredded cabbage goes great with shredded carrots and
mayonnaise.
TextMate suddenly has problems saving files in latin1 encoding (which
I must use if I collaborate with others). Even though TextMate tells
me it saves the file in latin1, upon checking with TextWrangler, it is
clear that they are not saved in the correct format.
The only workaround is to avoid using special characters (like umlaute
or accents). This happens with extremely simple one-file projects as
well as more difficult projects.
Is it possible to downgrade to an older version of TextMate?
Max
Dear All,
I just encountered something of which I think is a bug in the latex bundle.
When using a directory and file structure like this
main.tex
|
---subdir
|
-----submain.tex
|
-----subcontent.tex
where main.tex has an \input{subdir/submain} and submain.tex contains a
\input{subdir/subcontent.tex} the show outline function gives me an error
that the directory
xyz/subdir/subdir/... could not be found (which, as a matter of fact is
correct since it does not exist). To my impression the parser forgets to cut
off the first part of the path in \input{} when in a subdirectory.
For generating a LaTeX file this works fine. Any help or hint would be
greatly appreciated.
Kind regards,
Nima
--
View this message in context: http://www.nabble.com/Latex-Bundle---Bug-in-Show-Outline-tp20909194p2090919…
Sent from the textmate users mailing list archive at Nabble.com.
