Hi All,
I patched the ant bundle as described in a post earlier in January which fixes the build command but the build target command is not working.
After selecting the target text "main" in the build.xml file and then Ant->build target, I get the following error.
/tmp/temp_textmate.9KC3Zv:33: undefined method `attributes' for nil:NilClass (NoMethodError)
Any ideas what might be wrong, or maybe there is new bundle I could get?
Thanks in advance.
Is there any way to parse the open document (via regex search) and
return the results as choices for TextMate::UI.complete?
The command might search for "\$TM_\w+" so each time I want to type
$TM_SOMETHING I could get a list of completions built from what I've
typed elsewhere in the document.
I've got a basic TextMate::UI command up and running
<http://pastie.textmate.org/421465>, and as for a parser I've been
using this command: <http://pastie.textmate.org/421473> to complete
stuff thats been indented by 4 tabs (only bummer about this command is
that the document needs to be saved).
I'd love to combine these commands, but since I don't know Ruby I
don't have any idea what to do. (I scraped both those commands off
this list).
Thanks in advance.
I think the problem is "pstricks". If this package is involved, TM
uses automatically "latex" although "pdflatex" is set as default
engine. You can try it with this small example:
\documentclass{scrreprt}
\usepackage{auto-pst-pdf}
\usepackage{pstricks}
\begin{document}
Hallo
\end{document}
The package "auto-pst-pdf" should make using "pstricks" with
"pdflatex" possible but TM doesn't consider this. The only way I
found to avoid this is using the line
%!TEX TS-program = pdflatex
at the beginning of the code.
If there's anyone who has a better idea - I'm open for suggestions.
Am 19.03.2009 um 19:25 schrieb Allan Odgaard:
> On 19 Mar 2009, at 03:21, Gewitterbukk wrote:
>
>> [...] For example when I'm using packages like "auto-pst-
>> pdf" or "pstricks" TM uses "latex" to compile although "pdflatex" is
>> set as default engine.
>
> It tries to be smart, seeing that ‘pstricks’ works with postscript,
> not PDF. But I assume auto-pst-pdf makes it work with PDF or similar,
> and the command should either be even smarter, or not smart at all!?!
>
>> When I try to compile LaTeX-Code for the first time, I get the window
>> which is shown in the screenshot "pic1" attached in the appendix of
>> this mail.
>
> You say “for the first time”, does that mean the error is gone if you
> compile again, or that you resolved the problem?
Dear TextMate/LaTeX specialists!
I consult you because I've got a problem with setting up TextMate
(TM) for LaTeX correctly. At the moment TM seems to choose between
using "latex" or "pdflatex" by itself independent of the default
engine setting. For example when I'm using packages like "auto-pst-
pdf" or "pstricks" TM uses "latex" to compile although "pdflatex" is
set as default engine. This results in problems like everyone can
imagine. The only way to avoid this is inserting the line "%!TEX TS-
program = pdflatex" at the beginning if the LaTeX code. But that's
not the general idea I think.
When I try to compile LaTeX-Code for the first time, I get the window
which is shown in the screenshot "pic1" attached in the appendix of
this mail. Up to now I've pressed the button "Set PATH and Relaunch".
Just because I don't know what "kpsewhich" means and where it is to
find. Maybe that's the crunchpoint. After that the Terminal starts,
sets the PATH and TM restarts. But it doesn't work correctly in my
opinion. "Pic2" shows my LaTeX preferences. My current PATH is "/bin:/
sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/texbin". The shell
variables are shown in "pic3". I'm using Mac OS 10.4.11, TeXLive 2008
and the current version of TM.
I would be very lucky if someone could help me by letting me know the
right settings.
Thanks a lot beforehand!
Best regards from Germany
A. van Ohlen
Guys,
I'm trying to create a completion command for the C language, using
D2. For that purpose, I wrote a function using TextMate::UI.complete.
It looks almost like that:
#!/usr/bin/env ruby
require ENV['TM_SUPPORT_PATH'] + '/lib/web_preview.rb'
require ENV['TM_SUPPORT_PATH'] + '/lib/textmate.rb'
require ENV['TM_SUPPORT_PATH'] + '/lib/ui.rb'
currentWord = ENV['TM_CURRENT_WORD']
# Build the list of completion choice.
choices = [{'display' => 'hal_Aa'}, {'display' => 'hal_Ab'},
{'display' => 'hal_Abc'}]
# Display the completion popup.
options = {:extra_chars => '_', :case_insensitive => false}
TextMate::UI.complete(choices, options)
When I call this TM command, it works fine, but pressing the '_' key,
while the popup is displayed closes it and cancels the completion.
This is not the behavior I expect as '_' has been added to the extra
chars.
Does someone know how to have the '_' character being considered as
part of the word?
BTW, in my preferences, the "Word Characters" field is "_". I don't
know if this impacts.
Best regards,
Mathieu
___________________________________________
Mathieu Godart
Skype: mathieu_godart
MSN: mathieu_godart(a)hotmail.com
ASIC Integration Manager
Coolsand Technologies
___________________________________________
The Hyperlink Helper bundle's Wrap Selection as Link will default to
"http://some-site.com/" if it can't find something else to link to (e.g.
something on the clipboard). Unfortunately, some-site.com is a real site
which people probably don't want to link to by accident.
RFC 2606 <http://www.rfc-editor.org/rfc/rfc2606.txt> states that example.com
can be used, and if someone does indeed go to example.com, they don't
get surprised.
I'm sending this info because the "Send Feedback..." portion of TextMate
brought up a page that suggested Bundle bugs to be discussed here. I don't
know if the current behavior is considered by others to be a bug, but we
had a near miss that almost caused some-site.com to be linked to in our
production web pages. We'd definitely have preferred example.com to
be in our pages had we not caught the mistake.
--
Cliff Matthews <ctm(a)sceim.net>
formerly ctm(a)ardi.com
Thanks, that's been fixed. Must be an artifact of using the bundle
editor. I guess I just wait now? The patch remains at
http://pastie.textmate.org/416564
>
> ---------- Forwarded message ----------
> From: Daniel Stockman <daniel.stockman(a)gmail.com>
> To: TextMate users <textmate(a)lists.macromates.com>
> Date: Sat, 14 Mar 2009 19:35:24 -0700
> Subject: [TxMt] Re: Updating Javascript bundle?
> On Mar 14, 2009, at 3/14 6:54 PM, Michael Newton wrote:
>
>> Okay, I've created a patch using the instructions in the wiki article;
>> I've used SVN a fair bit, but never touched git so I'll leave that to
>> folks more knowledgeable than me. The diff file is here:
>> http://pastie.textmate.org/416564
>>
>> Let me know if there's any other way I can ease the addition of this
>> patch to the code base.
>
> Beware doubly-encoded ampersands in the diff (&amp; => &)
>
--
Michael Newton
http://mike.eire.ca/
Hi
first of all, congratulations for this fantastic enrichment of the
already genial project drawer. I did instaled Project+ and it worked
well (and I got really impressed) the first time. But after
installing and restarting and running it again it failed, TM shows the
classic project drawer, not the new enhanced one. You can touch round
the preferences of Project+ but it ignores them. But vuala! I opened
with mate several files from the terminal: "m *.json" and Project+
appeared, funnily both modes were present at the same time, the
classic one an the new one. Then I close and reopen my project and it
worked well.
The conclusion: you need to reopen a project to make Project+ to
became live.
- juan falgueras
The AppleScript window object in TextMate 1.5.8 (under Mac OS 10.5.6)
seems to be broken. I get get the window name and bounds, but not the
window document:
tell application "TextMate" to return (document of front window)
=> NOTHING
Compare this to TextEdit, which has a similar dictionary:
tell application "TextEdit" to return (document of front window)
=> document "foo.txt" of application "TextEdit"
Am I doing something wrong?
Regards,
Alan
--
Alan Watson
http://www.alan-watson.org/
Fo those of you using Consolas...
Microsoft's version of Consolas displays on the Mac and in TextMate
with an incorrect line-height, most clearly exhibited in selected
text, highlighted lines, and spelling error underlines. This makes
writing in Consolas irritating to me.
The version of Consolas that ships with BBEdit has a correct line
height but no italic or bold variations, which also irritates me.
If you extract BBEdit's Consolas from its package contents, install it
and disable Microsoft's "regular" weight, Leopard seems to use the
correct line-height information from BBEdit's version and apply it to
Microsoft's italic and bold weights.
Now Consolas is beautiful.
Sources:
<http://bandes-storch.net/blog/2008/12/21/consolas-controlled/>
<http://www.command-tab.com/2008/12/16/consolas-cursor-fix/>
