Hi,
what is the best form, to change/adapt the highlighting of ons own
often-used functions?
E.g. if I have a Perl sub called `i` (printing some debug-info to
stdout) and to be used e.g.
i 'Starting ifgrp store ...';
And if would like to have these lines formatted like a comment (grey,
italics) so that it survives changes in the Perl-Bundle including
reinstallations of TM2. Where and how would someone define that?
My guess is, to place it in my own Bundle and to use something like
begin = '^\s*';
end = ';\s*$'; # trailing white space may occure
But I can't figure out the details.
Thanks and kind regards, Ingo
--
Ingo Lantschner
Hi,
The “Commit” command in the git bundle no longer works for me.
If I run “Show Uncommitted Changes”, the git bundle properly displays the
diff. However, if I run the “Commit” command, it instead displays: "Working
directory is clean (nothing to commit)”.
So the repro steps are:
1. Make a change to a file
2. Run `git diff` or “Show Uncommitted Changes” to verify that a change has
been made
3. Run the “Commit” command
Is anyone else experiencing this issue?
Thanks,
Charles
On 01.01.2014, at 22:50 , "T. Zha" <zmail(a)tzha.net> wrote:
> Thanks for the information. I?ll try what you suggested. Any suggestion of the best source to download the epstopdf package?
If you have downloaded MacTeX, the package is included in the standard installation. All you need to do is use \usepackage{epstopdf} in the preamble and that's it.
I'm not using Matlab, just gnuplot, xfig and other simple graphing tools, but with the exception of gnuplot, they all feature pdf+latex output (meaning that the software creates a .tex file which you need to include and a pdf file, this way you can use latex commands in labels and such).
Max
Hi all and a very great / happy new year to all of you.
My name is Gabriel and I’m a very beginner both as a programmer and with TextMate.
TM is one of the few editor I have found which is accessible to the VoiceOver technologies
I have to use as I’m totally blind.
My problem has to do with using TM to write and test Python scripts.
I have this simple one:
# begin
a =input(“name? ")
print a
# end
I press Bundle… python… run script and getting this error message:
***
Running “untitled”…
Python 2.7.6
Theme:
nome
EOFError: 'EOF when reading a line'
module body in untitled at line 1
a =input("nome")
copy output
Program exited with code #1 after 0.41 seconds.
***
That’s sounds strange as the script has no mistakes.
Could you please help me to found how to solve this issue?
Thanks.
Gabriel.
All my source code is on a centos virtual machine, which I access over an
AFP share.
When I have a file open in TM2, TM is not able to detect that its been
changed.
This happens often when I switch git branch.
If I open a terminal and run 'ls' on the file, at this point suddenly TM
realises its changed and reloads it.
Can anyone offer an explanation for this?
I figured maybe its some form of fstat cache kicking in, either in OSX or
due to the way the AFP share has been configured, but I cannot find any
other apps behave the same way (ie, Sublime Text detects it has changed
immediately)
Pardon me for being a bit sentimental, but as a recent TextMate 2 adopter, I find that, quite aside from the technical improvements and the ability to run happily on Mavericks, I'm loving the new interface. When working on a small screen especially, I really appreciate the ability to maintain an all-in-one layout. With multiple documents opening as tabs, and the results window as a right pane, I'm so much more agile than in the past. This is a marvelous transformation. Thanks and a happy new year - m.
--
matt neuburg, phd = matt(a)tidbits.com, http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do
iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
Hi,
currently i don’t know why building text mate from source did not work for me.
My Setup is :
- source checked out from git with all submodules
- latest os x Maveriks 10.9.1
- neded dependencies are installed via brew
- my ninja target is TextMate/run
after clean and build from text mate i get the following error
https://gist.github.com/tfcoding/8195924
so it would be great if somebody could say why this error appears..
thx
Tim
In one of the recent updates (I think), the default behaviour when hitting
return inside a new set of braces seems to have changed.
Previously opening a pair of braces and hitting return would result in the
following:
{
// caret here
}
Now I get:
{
// caret here}
This is affecting all the grammars I commonly use - PHP, CSS, JS but
presumably is global.
Did I inadvertently change a setting somewhere or is this a change of the
default TextMate behaviour that I missed?
Either way, is there a way to return to the old behaviour? I have done a
few searches and seen some mentions in certain languages that you may be
able to build a snippet to fire on enter if the syntax supports specific
enough scoping but I'm failing to get it to work for me.
Dom
On 01.01.2014, at 07:00 , textmate-request(a)lists.macromates.com wrote:
> Actually I would recommend you and everyone to use the ?latex? engine instead of pdflatex.
I'm very well-versed in LaTeX, and I started with the non-pdf latex many moons ago. If it were up to me, I'd use xelatex because of its superior handling of fonts, but the arxiv doesn't support it and most collaborators don't know about it or care to use it. (The arxiv still on TeX Live 2011, too.) pdflatex is the de-facto standard for good reason.
> With latex, you can typeset eps figures directly without converting it to pdf figures and the resulting pdf file has a much sharper resolution than those produced by pdflatex applied to pdf figures, especially when you use the beamer for presentation.
Actually, eps is a format of the past, most programs (e. g. xfig) can output either directly to pdf or a pdf/LaTeX combo. Even if you get eps output (e. g. from gnuplot's using the eps+latex output), loading a single package (epstopdf) takes care of the on-the-fly conversion (which does *not* reduce the resolution, I think it just encapsulates the eps file into a pdf wrapper). This reduction in quality only happens if someone manually converts the eps file to pdf with the wrong tool in the wrong way.
During typesetting, you lose pdfsync which is a very handy feature (clicking in a location in the pdf file sends you to the corresponding line in your latex code). Moreover, pdf files which are generated from the intermediate dvi files often have lower quality (e. g. font rendering is worse, text no longer is searchable and hyperlinks may stop working).
I've only dealt with one journal that used latex instead of pdflatex (and another one which strangely enough doesn't seem to use latex at all on its backend).
If latex works for you, fine, but I don't understand why you force others to cling to the old. (I would not force my students to use TeX in any particular way.) Especially when it seems to be due to just not knowing about well-known solutions to old problems.
Max
