Hi All,
I seem to be locked in a battle of wills with the project file drawer
(for lack of a better name). I remove references to sub-directories and
files, and well, the file drawer puts them back in. Repeat. Repeat.
Swear, and give round one to TextMate.
Anyone else battling with the drawer?
I got into this test of wills by dragging and dropping a directory tree
that looked like:
YYYY/MM and then removing references to a few YYYY/MM/img directories
and the occasional pdf file. Well, "removing" them very temporarily :)
Thanks,
Phil
On 13. Oct 2004, at 12:50, Dominique PERETTI wrote:
> - If you reopen in TextMate, it stills appear as UTF8... BUT if you
> reopen it in BBEdit, it opens as a MacRoman file (with accents wrong).
I don't have BBEdit, but I think BBEdit _always_ opens as MacRoman. And
you have to manually tell it to open it with the proper encoding (at
least that was my experience when I tried it >2 years ago, both my
iso-8859-1 and utf-8 files were all opened as MacRoman by BBEdit)!?!
> My guess is that TextMate is right at encoding the characters, but
> forgots to write the BOM right. I think so because I get the same
> wrong results in FlashMX
> if I save the file as utf8-(no BOM) from BBEdit.
The BOM is optional in utf-8, and generally you _don't_ want it, since
a) it makes no sense as there is no byte-order ambiguity,
b) it rules the nice property of utf-8 being compatible with ascii,
c) utf-8 encoding is really easy to recognize even without a BOM.
But if several programs only treat utf-8 properly when it has a BOM, I
will consider adding an option -- though I would recommend against
using it of course! ;)
Kind regards Allan
Hello all,
I'm loving TM even with it's little blemishes (like not printing!).
But here's a question:
How do I search for or replace text with a special character, such as
a <CR>? With UltraEdit I would use ^M or something like that. Does TM
offer the same sorts of things?
Thanks,
Patrick
I'm using TextMate as my Xcode external editor. This works pretty well,
but I have a couple of problems:
(1) TextMate doesn't seem to support the external editor interface.
Specifically, what seems to be missing is the ability to go directly to
a specified line when opening a file. This is described here:
http://www.codingmonkeys.de/techpubs/externaleditor/
pbxexternaleditor.html
Remarks Metrowerks state in their documentation that the IDE (here
Project Builder) uses the optional keyAEPosition parameter to tell the
editor the selection range. If lineNum is zero or greater, scroll the
text to the specified line. If lineNum is less than zero, use the
values in startRange and endRange to select the specified characters.
Scroll the text to display the selection. If lineNum, startRange and
endRange are all negative, there is no selection range specified.
Basically, intercept the odoc AppleEvent and read the optional
parameter for line number or selection information.
(2) When I open a TextMate document that I already have open, TextMate
creates a new window for it and leaves the old window open too. This
can be very useful under special circumstances, however -- more
frequently -- it just rapidly and pointlessly clutters up my desktop.
Creating a new window is useful, but should be an optional behavior.
Usually, what I'm trying to do when I open a document is navigate to an
existing window, relying on the standard Mac UI behavior. I will
frequently double-click a file in the Xcode project window to get back
to TextMate, most often a file I already have open.
Chris
I know this has been discussed, and a number of people have expressed
their view that the TextMate icon isn't too visually pleasing already.
However, using TM in anger today, I keep finding myself searching
frantically for the icon in the dock. It's so indistinguishable at a
small size that I literally find it hard to see.
So I guess my point is that it's easy to dismiss concerns over the icon
as a matter of taste. Unfortunately in this case, and certainly for me,
it's a matter of usability - the icon isn't doing its job.
See attached!
I think I'm going to hunt out an alternative to use in the meantime, but
I hope that's useful feedback.
drew.
Hello,
Early on the first day of this mailing list I sent an email about my
first impressions, both positive and negative, which generated a few
responses, including one from Allen I believe. That said I want to
highlight what for me, as an HTML coder, is the only major downfall
that has not been spoken about extensively:
> Dragging an image from the project pane into a HTML file should add
> something like <img src="eric.jpg" alt="eric" width="100" height="100"
> /> and not the actual source code of an image at the insertion point.
Now I have seen a few requests that suggest highlighting an image in
the project drawer should display the graphic file instead of the code
and I agree, however this is not the major hurdle in my book. We need
to be able to grab a file from the drawer and pull it into our html
code and have the correct width and height added automatically.
I have been letting this subject percolate for a few days in my head
and I just can not think of another workaround that would approach any
reasonable level of efficiency (I would love to hear some though). I
could make a macro and have it tab stop at the name, width, height and
alt however I am not going to know the width and height in 99% of the
cases. I personally would also like to have it automatically add the
file name without the extension as the alt tag though some might argue
that this will promote poor coding practices, I tend to label my files
with readable names...
Please take care of this ASAP...
Sincerely,
Eric Curtis
1.0.1b2 is out, if anyone disabled their auto-checks or similar... plus
it "only" checks every 8 hours or so.
--
Sune.
"Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn"
http://cyanite.org -- Content follows ;-).
FYI: RFC = Request For Comments.
Based on recent input I suggest that I add a new list of 'drag actions'.
This will be similar to commands in that it's just a shell command TM
will execute (with the normal TM-variables, adding one for the path of
(the) dragged file(s) and one for the modifier keys).
The output options will also be as for commands, although I'll be
adding a new output option: Insert as Snippet (this will be added to
all the shell executions where you can select what to do with the
output).
A drag-action can set a regex to be matched against the current file
and the dragged file, if both match, the drag action will be executed
(this should probably be a prioritized list instead of TM showing a
menu when multiple actions could be applied, since it's likely one
wants to do 'catch all' rules).
Additionally there should probably be an option to set whether the drag
action can work with multiple files (and if this is not set, it will be
executed once for every file).
Kind regards Allan
On 11. Oct 2004, at 8:36, Rob Bevan wrote:
> [...] I'd much prefer it if TextMate adopted the Xcode way of doing
> this: the syntax file defines the language (primitives, built-in
> classes, built-in methods, user functions, preprocessor directives,
> Numbers and operators: whatever) and the user gets to pick how they
> want those displayed [...]
Yes, as I thought I made clear on the ML, there will be separate style
sheets in a later version.
Though I don't think it is as simple as Xcode and just a few "global"
names, since TM has a rather free style to define syntax highlight,
like in the HTML syntax file where a stand-alone & gets a red
background, or the way that HTML uses color for markup when on its own,
but grey-tones when there is embedded scripting (and colors are than
reserved for scripts) -- plus when embedding stuff, the names would
clash (i.e. a string in HTML, and the embedded JavaScript, Ruby, PHP or
whatever, would be identical).
But the system I have in mind is similar to normal CSS, so it should
allow both catch-all rules and pin-pointing individual elements (and
put no restrain on which elements a syntax file can define).
Also, if I didn't mention this earlier, with the breakup of syntax and
style, the former will also be used to enable/disable stuff like spell
checking, foldings, smart-typing etc. for comments, strings, tags in
HTML, etc., mark filenames so that they can be "followed" in the editor
(#include, require(), <a href="...">, etc.), mark function prototypes
or sections so that they can appear in the highly requested function
popup a.s.o. -- and full recursion will also be supported (which may
also then make it possible to do a (clickable) bread crumb display of
context in the status bar).
I will also re-visit the folding marker-system -- so this is really a
major overhaul of the current system!
I'll probably dedicate a portion of the wiki to collect requests for
this system when the time is right -- currently I have a lot of other
things that needs to be "fixed" with TextMate before I can spend
resources on this new syntax system.
Kind regards Allan
