I'm trying to work up a command to call ant with for my Java bundle.
I'm confused by the dual-pane window that's displayed. The bottom
looks to be just the entire output of the command with line numbers in
the gutter. The top I just don't grok, however.
It may be that I'm completely missing the point of the command output
window; if so, please set me straight. :-)
Does the pattern matching expect every single line to match the
pattern? For example:
/path/to/file:1: error on line 1
/path/to/file:2: warning on line 2
"ant -emacs" has output like this:
>>>>begin
[...]
compile:
Compiling 1 source file to
/Users/blalor/devel/java/portal/ConsumerCustomCommands/build
/Users/blalor/devel/java/portal/ConsumerCustomCommands/src/com/
deltafaucet/portal/commands/profile/AprimoAccountListener.java:30:
cannot resolve symbol
symbol : class Foo
location: class
com.deltafaucet.portal.commands.profile.AprimoAccountListener
private static Foo bar = new Baz();
^
/Users/blalor/devel/java/portal/ConsumerCustomCommands/src/com/
deltafaucet/portal/commands/profile/AprimoAccountListener.java:30:
cannot resolve symbol
symbol : class Baz
location: class
com.deltafaucet.portal.commands.profile.AprimoAccountListener
private static Foo bar = new Baz();
^
<<<<end
I'm not sure what the command output window is trying to accomplish...
I've got my command set up like this:
Before running command: Save modified files in project
Command(s): ant -s build.xml -emacs
Standard input: None
Standard output: Show in separate window
Pattern: ^(/[^:]+):(\d+):(.*)$
Format string: $3
File register: 1
Line: 2
Column:
This causes the command window to look like this:
I would expect that the top part of the window would only show the
lines that matched the regexp, at a minimum, but I really think it
should perhaps highlight the line, make it clickable (to jump to the
source), etc.
I think what's needed (for compiles, anyway) is to have the command
output displayed in a pane in the project window (say, at the bottom)
and display each line of output from the command. Each line that
matches the regexp should appear in a different color, and, if the
line, and possibly column, are given as registers, the top part of the
project window should jump to the line and file, leaving the lower pane
in place. I tend to keep my code windows up so that they take up most
of the screen real estate (especially with the project drawer open).
The command window really gets in the way. But I think it's a step in
the right direction, because I want to be able to jump to a line in the
file.
--
__ ____
/ / / __/ Brian Lalor
/ _ \/__ \ blalor(a)bravo5.org
/_.__/____/ http://bravo5.org/
Slightly improved C/C++/Objective-C bundle:
<http://www.cjack.com/tm/C.tmbundle.zip>
* Keyword corrections for all languages.
* Move to a more conventional black-on-white color scheme.
* C++ inherits from C to make this more manageable. Although C++ is not
a strict superset of C, the differences are extremely slight (for the
purposes of TextMate, at least).
* That's all for now.
I'm happy to coordinate further improvements to the C bundle; you're
also welcome to grab my changes and post your own version if you
prefer. Highlighting could be further improved. There are a zillion
useful macros and snippets to be written. Makefile syntax could be
factored out into a "Unix" bundle, one that would also support the
myriad shell scripting formats.
Allan/Macromates folks, please consider including at least the keyword
modifications in future versions of TextMate.
Share and enjoy,
Chris
I'm trying to use Profont, but if I type an f followed by an i, the
spacing goes crazy, ie. the letters move close together, but the cursor
moves as if the spacing was normal. This happens only for f and i, and
I haven't seen this in any other apps using ProFont.
Is anyone else having the same problem?
Thanks,
Andrew
Hello,
First thanks to Allan for all the great work on TextMate ^o^.
Sorry if any of you in the mailing list do not like long mails. If you
do not want to read it, just jump to the next mail in you mail box ;-)
And sorry for putting so many things in one mail, but one mail is
easier to skip or remove than 3 or 4 ;-)
So there are my list of remarks about TextMate. They do not mean that I
do not like them program. On the contrary, I just want it to be even
better ^o^. Feel free to criticize any of them (except the first one).
First, I do not really care if the preferences are in there own dialog
box or in the menus. In the menus, it has the advantage of being faster
to change. But with the feature list that will certainly grow in the
future, some things will certainly have to be put in a separate dialog
box. (And no, do not reply to this paragraph, as it has already become
a troll on this mailing list ;-))
'Re-open with encoding' is great but the encodings list is quite short.
UTF-32 is not even there. If someone works a little with Japanese text,
he will need Shift-JIS and EUC-JP. Someone with Chinese text might want
Big5. Even a westerner wanting to use the euro symbol might want
ISO-8859-15. The best would be to be able to add or remove encodings in
the list. The same thing would be great in the 'Save' dialog (the list
should be the same in both places and be editable at both places). And
adding it in the 'Open' dialog would be great too.
Little bug : if we select 'other' in the View->Tabs Size menu, nothing
happens. There should be a dialog box asking for the number of spaces
you want.
An other little problem I have is the drawing of CJK characters. These
characters are wider than latin characters and as they are drawn today
in TextMate, a character may overlap with the previous and next one. In
terminals, this is generally handled by making them double-width. In
SubEthaEdit, it is quite strange as they are not fixed size at all,
some are larger than others. If you want any screenshot, example, just
ask.
Note that I am in no way good in Chinese, Japanese or Korean, I just
made a few Ruby scripts to help me train my Japanese, and they do
include some Japanese characters.
For the ligatures problem, if it has not been corrected in the sources
yet, it's quite easy to correct:
If you want ATSUI not to use common english ligatures (fi, fl):
ATSUFontFeatureType type = kLigaturesType;
ATSUFontFeatureType selector = kCommonLigaturesOffSelector;
ATSUSetFontFeatures(myATSUStyle, 1, &type, &selector);
and if you do not want any type of ligature:
ATSUFontFeatureType types[9] =
{
kLigaturesType,
kLigaturesType,
kLigaturesType,
kLigaturesType,
kLigaturesType,
kLigaturesType,
kLigaturesType,
kLigaturesType,
kLigaturesType
};
ATSUFontFeatureType selectors[9] =
{
kRequiredLigaturesOffSelector,
kCommonLigaturesOffSelector,
kRareLigaturesOffSelector,
kLogosOffSelector,
kRebusPicturesOffSelector,
kDiphthongLigaturesOffSelector,
kSquaredLigaturesOffSelector,
kAbbrevSquaredLigaturesOffSelector,
kSymbolLigaturesOffSelector
};
ATSUSetFontFeatures(myATSUStyle, 9, types, selectors);
Some info there :
http://developer.apple.com/documentation/Carbon/Conceptual/
ATSUI_Concepts/atsui_app_features/chapter_9_section_15.html (be
careful, the feature selector names on this web page are not all good)
It will also disable ligatures for Hindi or Arabic script, but as
TextMate's goal is not seem to be a multi-lingual editor... (but it
would be great if it could at least manage the CJK characters well ;-))
Last thing: having a direct link to
http://lists.macromates.com/mailman/listinfo or at least to the
archives of the mailing list
(http://one.textdrive.com/pipermail/textmate/) on TextMate's web page
would really be great. I only found it after subscribing to the mailing
list, in the mail asking for confirmation.
Cheers,
Vincent Isambart
Interarchy supports ediiting files over sftp. It would make me überhappy is
TestMate would support this feature. I asked the Interarchy developer what
details you would need to know to make this work. He replied with the links
to the info below.
I know you intend to support editing files over sftp with TextMate in
version 1.1, but I like Interarchy and adding compatability to work with
Interarchy looks pretty simple. So pretty please with sugar on top, add
this feature. :-D Thanks,
Simon
------ Forwarded Message
From: Peter N Lewis <peter(a)stairways.com.au>
Date: Thu, 7 Oct 2004 10:06:08 +0800
To: Simon Dorfman <Simon(a)SimonDorfman.com>
Subject: Re: Edit with... TextMate
>I want to ask the developer of a new text editor (TextMate macromates.com)
>to support your "Edit with..." feature. What does he need to know to make
>it jive with Interarchy?
The details are at:
http://www.merzwaren.com/external_editor.html
and Bare Bones' original specification is at:
http://www.barebones.com/support/developer/odbsuite.html
If they drop me a line when it is implemented we'll be happy to add
TexMate to our list of possible editors.
Enjoy,
Peter.
--
<http://www.stairways.com/> <http://download.stairways.com/>
------ End of Forwarded Message
I just downloaded TextMate and am pretty happy with it. Since it is a
Cocoa app, all of the standard MacOSX key bindings come with it! I've
used emacs as a text editor for years and can't break away from the
basic editing commands.
I created my own TextMate keybinding file, as noted in the help section,
and resolved an issue with '^f' not being bound to 'move cursor
forward'. The only other thing that I can't seem to figure out is '^y'.
When used with '^k' I should be able to 'kill' to the end of a line,
then 'yank' that text out of the kill ring. It's a quick and dirty
cut-and-paste option that's very much ingrained. I can't find any key
bindings that override this behavior, but it doesn't seem to work.
Any ideas?
Thaddeus
Or whatever you want to call it, being able to open a file from the
project drawer in a separate window. Sometimes I want to look at things
side by side.
Some file names can be long, and others are deep in a folder structure.
Where the width of the file draw doesn't allow for the full name of a
file to be displayed, it would be handy to have a tooltip appear with
the full file name.
drew.
I've been trying out TextMate to decide whether it's worth purchasing.
One thing has happened twice when writing php with it. My best guess is
that it's an encoding problem of some sort. For some reason when I
create new document in TextMate SOMETIMES php refuses to parse the
document at all, in fact even if I try inserting some test html code,
it also doesn't parse. What I end up with in the browser is an empty
page. Viewing the source reveals this to be so. I've tried reopening
the document with new encoding from the file menu... I've also reverted
to trying to convert the encoding in bbedit and yet it still doesn't
load in the browser. This only happens sometimes. Other times, there
are no problems with the php file. I've combed through the faulty files
for script errors and debugged the code thoroughly, it isn't a problem
with the code. So far I haven't been able to pinpoint what the
difference is between the files that have no problems and the faulty
ones. The ONLY solution was completely writing the exact same code in a
new document in bbedit.
I want desperately to leave bbedit for textmate, but this issue is a
major bump in the road for me. Anybody else have a similar problem? Any
suggestions? Maybe something I'm missing?
Thanks
Mike
Other comments have been made about them being non-standard. I don't
see a problem with that, they behave differently than other
implementations. My only comment is the amount of space the take up.
They really seem unnecessarily large particularly along the vertical
axis. Something more along the proportions of the items on the
bookmarks bar in Safari would be most welcome!
I agree that not having the Prefereces... command is bad, in that it's
confusing.
Having said that, I understand why it's not there.
So, to please both camps, have the Preferences... menu item launch a
help window/assistant that explains the preferences philosophy of
TextMate, along with visuals on where to find them (the specific
menus), and how the TextMate approach makes sense for what TextMate
does.
That will eliminate the number one problem encountered by new users,
and also get them quickly up to speed about TextMate's underlying
philosophy.
"Show, don't tell."
Regards,
Eric Ocean
Hello all,
It's clear that the more familiar you are with regular expressions, the
more productive you can be with TM. If you could use some additional
help (beyond what's already in the TM help), here is a site that I've
found useful:
http://www.regular-expressions.info/
I'm sure others will have some favorite regex sites/books of their own
to recommend.
Cheers,
-jeff
Well this will certainly be fixed in the upcoming version (Justin
already said so) and he pointed out what was wrong but here is how you
can easily get HTML syntax working now:
Go to:
/Applications/TextMate.app/Contents/SharedSupport/Bundles/
HTML.tmbundle/Syntaxes/html.plist
then edit lines 62 and 64 by swapping the styles and script names. It
should look like this in the end:
/*{ name = "Embedded JavaScript"; backgroundColor = "#E5E5E5"; begin
= "<(?i:script)\\>"; end = "</(?i:script)>"; },*/
{
name = "Embedded CSS"; backgroundColor = "#E5E5E5"; begin =
"<(?i:style)\\>"; end = "</(?i:style)>";
patterns = (
{ include = "CSS"; }
);
},
Later,
Eric Curtis
Is there a way to do incremental search in Textmate, where the display
scrolls to the closest match as you're typing in the search term, ala
"Quick Search" in BBEdit or Ctrl-S in Emacs?
Ben
When you have a block of text like this:
<ul>
<li><a {if $section eq "orders-pending"}class="current" {/if}
href="/admin.php/orders-pending">Pending Orders</a></li>
<li><a {if $section eq "orders-pending"}class="current" {/if}
href="/admin.php/orders">Search Orders</a></li>
</ul>
the </ul> doesn't register as a closing tag because it is not at the
same tab level as the <ul>. In other words, the above doesn't work, but
this does:
<ul>
<li><a {if $section eq "orders-pending"}class="current" {/if}
href="/admin.php/orders-pending">Pending Orders</a></li>
<li><a {if $section eq "orders-pending"}class="current" {/if}
href="/admin.php/orders">Search Orders</a></li>
</ul>
James.
Hi
First of all, TextMate is great work. I only had to try it out for a
few seconds and it was instantly obvious to me that TextMate just
_feels_ great to use. It's powerful yet doesn't feel clunky or
bloated, unlike some other editors which shall not be named.
The only thing missing for me to be able to use it in my day-to-day
work is the possibility to have projects synchronize with an
ftp-server. I'm a web developer, and most of the time I work against a
remote ftp-server (not always, but quite often).
The only editor I've found that does this in a simple fashion is
Dreamweaver MX, which, while not terrible as a code editor, it isn't
exactly optimal either.
I hope ftp-support is added soon, not just being able to edit a remote
file, but actually being able to associate a project with an ftp
account. Because, then I'd have no reason to use Dreamweaver MX again,
instead of using it all the damn time.
Best regards,
Tomas Jogin, Sweden
http://jogin.com/weblog/
I've got a rough cut at python support bundle[1]. It includes syntax
and three snippets: klass, def and deff. The snippets rely on a de
facto python standard of 4-spaces for indentation. I'll keep making
minor updates, but feel free to use it in the future TextMate releases.
The editor is rather neat so far. Keep up the good work.
[1] http://glyf.org/TextMate/pythonsyntax.tgz
---
Philip f
Greetings,
(this was cc-ed to feedback(a)macromates.com and contains screenshot
attachments, which I hope the ML server won't strip out).
A little background first: I'm a long time BBEdit user, I think that
it's a great product but I also think that it really starts to show its
age. It really looks like the BareBones guys are trapped in the
technology they used from day 1 and that if they'd want to get fresh,
they'd have to restart from scratch, which they probably won't. That's
why TextMate looks promising, and because it's built on top of modern
technologies it has the potential to become really great.
However, this v1.0 looks like nothing more than a good draft to me.
Yeah, shoot me, but that's David's hyping machine fault... :p
So here's a first batch of random comments about my first impressions.
They are mostly cosmetic and usability related, since I didn't really
used the product a lot yet, but I'm pretty sure I'll have some more as
time goes by.
- Ok so, I'm one of those who was very surprised not to find a
preferences dialog. When you think about configurability, you usually
think about preferences. I just saw a post about this on the MacroMates
blog, so let's just avoid this subject right now.
- Now let's go straight to the GUI itself. Here's a screenshot of a
TextMate default window (with my own default background color):
What I see here:
+ The color contrast between the gutter and the text area is pretty
low so the distinction is hard.
+ The gutter can only have 4 digits line numbers (no, files larger
than 9999 line are not that rare).
+ The (orange) wrap column line is almost invisible.
+ The lower status bar has loads of useless empty space.
+ The empty corner at the intersection of the scroll bar looks, well,
empty.
Here's my (photoshop) take on this:
+ A simple gray line to separate the gutter from the text area.
+ The gutter is a bit larger to allow 5 digits line numbers.
+ The outside limit of the wrap line is drawn in the same color than
the text area but with a lower brightness (that's currently how BBEdit
8 does it, it looks really nice imho).
+ The status bar is collapsed and put at the same level than the
horizontal scroll bar, saving lots of empty space. The left indicator
is the current line number, the right indicator is the column number
(again, that's how BBEdit does it, but they do it for a good reason).
Small icons could be added to make this more obvious.
+ No more weird empty corners.
Doesn't this look much tidy and cleaner like that ?
Let's move on to the project window. Here's how a basic project
currently looks in TextMate:
What we have here:
+ Weird looking tabs. They're not even tabs actually, and they really
look like they're quick hacks to me.
+ Weirdly sized icons in the drawer list.
+ (same comments than above for the text window itself).
Here's my take on this:
+ Tabs looking like tabs (actually stolen from NetNewsWire and
resized a bit).
+ Smaller icons in the drawer list allowing for a more balanced look
(quite impressive to see what a couple more pixel space can do uh ?).
+ Folder name is bold.
+ (same modifications than above to the text window).
Let's move on to features:
- Find and replace feature:
+ There should be a "Use selection for replace" menu shortcut.
+ There should be a "Replace" menu shortcut.
+ There should be a "Replace all" menu shortcut.
+ There should be a "Replace and find next" menu shortcut.
All these would allow to perform basic search & replace operations
straight from the keyboard, *without* having to open the find panel at
all.
- I guess that you guys already know that and are already preparing
something to fix this problem, but I'll say it anyway: having to
manually go and edit plist files from the guts of the app to have some
decent colors (relax, I'm kidding, I just don't like thos ugly black
backgrounds) is ridiculous. Tell me you're working on something before
I start my own Cocoa 'tmbundle' editor.
- Something which I found pretty weird: each tmbundle defines its very
own color settings right ? So if I want to have the same background
color for *all* languages I have to change *all* tmbundle syntax files,
right ? Wouldn't it be much simpler to have "default" settings which
each tmbundle would inherit from and could then override or not ? So
just like CSS elements can inherit from their parents, a syntax file
could either inherit attributes from the defaults, or override with its
own values. That would greatly simplify the whole coloring settings I
think. Thoughts ?
- Another pretty obvious one: there is no "function popup", or any
other way to quickly navigate through the list of functions or methods
of a code file, or the structure of a markup file.
- Snippets are great, but the snippet menu is already pretty crowded. I
think that allowing snippets to be grouped in families (based on the
tmbundle they're coming from, to begin with) or categories or whatever,
could help minimize the clutter. Ditto for macros and commands.
- How about the ability to have the snippets, macros and commands in a
palette ?
- How about giving some basic abilities to a command to specify when it
is actually applicable ? A command menu item (or palette entry ;))
could then be disabled if it is not. For example, the "Compile" command
does not make sense for a '.html' file, or the "Reload in Safari"
command does not really make sense for a '.rb' file.
- Being able to write commands in something else than shell scripts
could be cool. Like, being able to directly write applescript instead
of having to go through 'osascript' commands.
- Hey, you seem to have pretty good text editing widget (that
OakTextView thingy), so why not also use it for command editing ? Heck,
why not even also use it for colored regexp editing in the find panel ?
- Detail: it seems like a lots of ATSUI related debug messages are
still being sent to the console.
- Snippets, macros and commands are good ways to automate a lot of
stuff, but are there any plans to allow TextMate plugins, for those
tasks which would require an elaborate GUI ?
Oh, and one final comment: I *R*E*A*L*L*Y* *H*A*T*E* the icon. It's
butt ugly. Really. Heck, you have John 'Magic' Marstall on the mailing
list, I'm pretty sure he could do something about this :))
--
Luc Heinrich - lucsky(a)mac.com - http://www.honk-honk.com
Hi,
I've searched the documentation and the list archive for any mention
of "invisibles", i.e. the ability to show tabs and spaces, a la
BBEdit's "Show Invisibles" and "Show Spaces" or SubEthaEdit's "Show
Invisible Characters". Now, maybe it's there, but I can't find it; in
that case I'd appreciate a hint.
If not, and since we're supposed to send feature requests to the
list, that would be mine.
Best, Mic
Can anybody get this to work? Is it not implemented yet or am I just
screwing up?
Ian.
#ifndef __COMMON_SENSE__ | Ian Phillips
#include <std_disclaimer> | http://ianp.org
#endif
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 7.10.2004, space aliens observed Mats Persson saying:
>I just downloaded the PHP & Smarty syntax bundle, and found that it
>too was based on a dark background. Can someone please explain this
>seeming 'obsession' with dark backgrounds when 99% of all other apps
>are the basic white background with black/coloured text ???
A lot of people who spend the day writing on a Computer prefer dark
backgrounds because for them it is less tiring. Dark text on white
background works well on paper, because paper reflects light and doesn't
emit it. A screen, however, emits light, which makes white really
bright.
I prefer dark backgrounds and find them more readable and a lot less
tiring for the eye than bright backgrounds.
lucas
- --
"No one ever attains very eminent success by simply doing what is required of him; it is the amount and excellence of what is over and above the required that determines greatness."
-- Charles Kendall Adams
-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 3.2.2
iQA/AwUBQWVAErXYdom/dB2cEQKdlwCfVX4ysljltPmUtOZ/LKK4iPFBU+IAnAxE
ZRSqSwv9Hgm01hqqihT5ohPE
=9naC
-----END PGP SIGNATURE-----
(pardon my english)
Having seen the 'rails_setup.mov' I thought Textmate's interface would
be more Xcode like, but I see that you finally opted for something more
Mail.app like. I wonder why, I see the splitview metaphor more adequate
for Textmate.
OS
Cmd-E to enter search string is a nice start.
Cmd-Opt-E to enter replacement string.
Cmd-... to replace and find next
Cmd-... to replace all
I use these commands more than almost any other when editing text. To
have to use a dialog to enter the replacement string...to have to use
the mouse to replace next...ouch. That's a big showstopper for me.
Oh...and why does 'Ignore Case' get greyed out when you use regular
expression (and yet maintain the state last set to, as though it's
either locked on or off)?
--
(-, /\ \/ / /\/