Uhmm.... how do I start column typing? Can't find it in the menu's...
Sorry for something which is probably straightforward, but I really
can't seem to find it.
--
Joost Schuttelaar
Hello,
I'm trying to open all .txt files with TextMate. In the finder, I select a
.txt file, hit Control+i to get info. Then I select TextMate as the app to
open it with, then I click "Change All". After clicking "Change All"
TextMate disappears as the "Open With" app and is replaced by the text: "Not
applicable". If I close the info box and double click on the .txt file, I
get this error: "The operation could not be completed. An unexpected error
occurred (error code -10660)." If TextMate is already open, a double click
on the file in the Finder opens fine. But if TextMate is closed, it shows
this error.
Does anyone know how to fix this?
I think it may have been caused by renaming the beta versions of TextMate to
names like "TextMate1.01b3". Maybe the Finder got confused about which app
was THE TextMate to open with. I now only have the newest 1.02 version in
the Apps folder.
Any help much appreciated. Thanks.
Simon
I'm a newbie textmate user, and unfamiliar so forgive me if this has
been covered before.
When double-clicking on whitespace to select and then moving the mouse
to text (to select by word) it's very annoying to me that the word at
the other end of the whitespace is selected. I've seen this behavior
in M$ products and it drives me nuts. Am I the only one?
To me it's obvious that if I double click something and then move left
that it's wrong for something rightwards to become selected.
I'm sure I'll learn to cope, but I thought I'd ask about it.
I'm still getting used to it, but I think I like TextMate. :)
I installed the SQL bundle, but it didn't do it for me. At some point
I'll have to go make a syntax file that supports Oracle PL/SQL (since
that's what I edit mostly these days).
cheers
Patrick
Hi,
I'm using TextMate for my Getting Things Done (GTD) stuff. Is anyone
else out there doing the same? I'm just getting started and would love
to see how others are using TM for GTD. How do you set up your file
structure? How do you name and keep track of your files, actions, and
projects, etc.? I can see how it would be useful to be able to do such
things as link from a URI in a text (markdown) file directly to a
browser. As well as things like creating links to other local (project)
files ala voodoo pad, and moving chunks of text to other files whilst
sprinkling them with some meta data.
Then they are things like aggregating lists to create contextual lists
and so much more I can imagine but not conceive of programatically.
I just found this:
http://www.rousette.org.uk/blog/archives/2004/11/28/rails-gtd-
application/
and I know bsag has other discussions about TM GTD in her blog. As well
as Daniel Von Fange's neat little tricks:
http://www.braino.org/blog/archives/001512.phphttp://www.braino.org/blog/archives/001440.php
Admittedly I haven't played much with these, but I do remember having
some problems with TM finding my Ruby install.
-t
I'm resending this letter from the 3th of November just as a friendly
reminder and for all those who have joined the list since the
previously mentioned date.
----------->8-----------
There is really only one rule (apart from normal netiquette) I want you
to uphold:
When you write a _new_ letter to this mailing list, _don't_ use “reply”
on an existing letter (to get the To: filled in).
It screws up threading!!!
If you're using Mail.app, you can control-click the “To” of an existing
letter and select “New Message” to get a compose window with the “To”
header filled in.
Threading is a very useful feature, and especially for me with this
mailing list, since it's basically an archive of user feedback, and I'd
like for the table-of-contents to show _every_ thread, which it
currently doesn't, when one thread contain 2-3 _different_ subjects,
because people have used reply (then it only show the first subject).
So PLEASE remember _not_ to use reply (for new letters)!!!
Was there any resolution on the subject of canceling the incremental
search via the navigation keys? I believe that I never heard any
support for leaving it as it is, with several supporters for having
only backspace edit the search string. Is this on your todo list, or
will it stay as it is?
Thanks,
Wayne
Hi,
I'm using TextMate for my Getting Things Done (GTD) stuff. Is anyone
else out there doing the same? I'm just getting started and would love
to see how others are using TM for GTD. How do you set up your file
structure? How do you name and keep track of your files, actions, and
projects, etc.? I can see how it would be useful to be able to do such
things as link from a URI in a text (markdown) file directly to a
browser. As well as things like creating links to other local (project)
files ala voodoo pad, and moving chunks of text to other files whilst
sprinkling them with some meta data.
Then they are things like aggregating lists to create contextual lists
and so much more I can imagine but not conceive of programatically.
I just found this:
http://www.rousette.org.uk/blog/archives/2004/11/28/rails-gtd-
application/
and I know bsag has other discussions about TM GTD in her blog. As well
as Daniel Von Fange's neat little tricks:
http://www.braino.org/blog/archives/001512.phphttp://www.braino.org/blog/archives/001440.php
Admittedly I haven't played much with these, but I do remember having
some problems with TM finding my Ruby install.
-t
Thanks to Xavier Noria for his bug list for the Perl bundle. I have
fixed some of them in a new version (see the wiki, or my page
http://math.sfsu.edu/hsu/textmate for the archive and details.
Here are the fixes:
adjusted $foo{bar} so the first brace isn't highlighted
q qq qw qx quoting recognized
POD recognized (from =head1 to =cut)
__END__ __DATA__, __FOO__ all recognized
added Perl to One-liner command
Known problems:
many autoquotes not highlighted right: here-docs not quoted,
hashkeys in => notation.
I invite anyone else to take a crack to getting the autoquotes right,
in the cases that Xavier noted. (I am travelling for the next three
weeks!)
The problem with doing here-docs right is that the start and end
delimiters change with each case, so we'd have to use backreferencing
in the 'end' parameter, and I don't think that's currently possible.
- Eric
ps. I wonder how hard it would be ( maybe for 2.0! :) ) to have TM
simply use vim syntax files, or some other well-worked format...
--
Eric Hsu, Assistant Professor of Mathematics
San Francisco State University
erichsu(a)math.sfsu.edu
http://math.sfsu.edu/hsu
Paul Nordstrom August wrote:
> FTP in the drawer... yes please! (Hope that's SFTP as well.)
There's a way to fake it somewhat :)
Open the files from the FTP server as you would normally, they're then
stored in /private/tmp/501/Cleanup at Startup/ or so as files. If you
put those files in a project *and* open tabs for them in the project so
they are read, you can close the original windows, and only work on
what's in the project.
Alas, you cannot successfully save, close and open the project lateron,
and moving things around in folders won't work either; I only use it
when I know I'll be editing the files for an hour or more or so.
Regards,
Martin
Hello
Maybe this is not a bug, but when I open a .ini file from the project
drawer, one click doesnt open it - i have to double click it - and then
it opens in a new window instead of the same window as the rest of the
files in the project. Is this a bug?
Regards
Duarte Carrilho da Graca
Allan,
> Added a dock menu with New, New Project, and Open….
Thanks so much for adding this! Certainly one of the features I
personally missed from SubEthaEdit. With that said, I wonder if it might
make sense to make the menu more consistent with SEE? For instance, SEE
has "New File" instead of "New". They also use "Open file..." instead of
"Open.." IMHO, I think that SEE's wording/ellipses choices look better,
but that may be familiarity talking.
> The Text -> Change sub menu now also appears in the context menu (when
> there is a selection). Also, suggestions for spellings no longer
> appear if the selection contain newlines or tabs (previously it only
> looked at spaces).
This is also a welcome change. However, I think that instead of
"Change", which is ambiguous, you should use "Convert" or "Format" as in
the attached Service menus.
Thoughts?
Chris
--
Do the evolution. Get Firefox!
<http://spreadfirefox.com/community/?q=affiliates&id=5&t=4>
Quote of the moment: /If you can't describe what you are doing as a
process, you don't know what you're doing./— W. Edwards Deming
I just built beta 11. If there are no problems this will be released
later today as 1.0.2 which should be the last in the 1.0.x series,
meaning that I'll shift priorities a bit and focus on larger
improvements for the 1.1 release.
Basically it just means that having the 1.0.2 out as “official” with
most obvious fixes done, I'll be more comfortable rewriting major parts
of TextMate even if it means the source will be in a non-functional
state for a couple of days -- but I'll still release betas as often as
it makes sense, and I'm aware of the requests expressed on this list.
was wondering if TextMate could throw a warning if the key-equivalent
you're assigning to a command will wipe out a pre-existing
key-equivalent. From what I've observed, if you add a key-equivalent
[that already exists] to a command then the command works --as
expected-- in that key-equivalent, silently overriding what was there
before. Hopefully not something too difficult? I guess that would be
helpful for macros too.
Kumar
Hi Allan,
If possible, could you make the Replace field the next tabindex after
the Find field? Right now it lands on the Sigma button, meaning I have
to double-tab to get to the Replace field.
Thanks!
Chris
--
Do the evolution. Get Firefox!
<http://spreadfirefox.com/community/?q=affiliates&id=5&t=4>
Quote of the moment: /"Accept that some days you are the pigeon, and
some days you are the statue."/— David Brent, Wernham Hogg
I woundered if it was possible to change the shortcut for "Insert
closing tab". cmd-opt-. isn't working on my keyboard layout. As I
understant it, opt-'.' is '>' so cmd-opt-'.' is understood as cmd-'>'
I get this problem all over the system.
Anyway, how about just cmd-'.' ? I know it's a reserved shortcut for
cancel but in a sense, it 'stop' a block. And there is no use for a
cancel in text editing. And beside, cmd and '.' and very close
toghetter while opt is all the other way of the space bar on small
keyboards ( original g4 and I think powerbook/ibook too )
> Date: Mon, 6 Dec 2004 13:10:05 +0100
> From: "Fred B." <fredb7(a)starflam.com>
> I started using Fugu with this release.
> Connecting locally to my server and editing using TM working fine.
Just so you know, rc2 is out now. It has fixed some problems that rc1 had.
Carl
HTML folding does not work properly in a very simple hand-written HTML
page. This is a movie depicting what happens:
http://www.hashref.com/textmate/tmbug_html_folding.mov
There I try to hide three blocks:
1. The "body" CSS element is correctly folded
2. The "style" tag is not
3. The "head" tag is not
-- fxn
Python folding seems half implemented, it does not work. As you can see
in this shot:
http://www.hashref.com/textmate/tmbug_python_folding.png
There's no mark for classes for instance, and more important if you
click on the marks to fold functions nothing happens.
-- fxn
I love the scratch macro and the ability to replay it with a keyboard
shortcut. How about a "replay last used macro"?
E.g., let's say I have a saved macro that I don't want to assign a
keyboard shortcut to, but which I do want to use over and over again
for a stretch in a document. Right now I've got to pick it out from
the menu each time.
If we had a "replay last used macro" I could just hit that keyboard
shortcut repeatedly. It could probably even replace "replay scratch
macro" and still have the same effect when the last used macro
happened to be scratch.
Thoughts?
A few issues in the syntax highlighting done by Perl's bundle.
The first one I think it's typically hard to get right: here-docs are
not recognised. This not only means that they are not colourised as
strings, but that their content can fool the rest of the highlighting,
for instance if there's an unbalanced quote. (Sometimes a fake comment
can help there though.)
POD sections are not recognised either, so not only they are not
coloured but Perl keywords are highlighted in regular English (for, if,
while, ...).
On the other side, hash elements are no correctly highlighted. In
$foo{bar} = "baz";
the red for variables goes beyond the "{" and stops at the "r":
$foo{bar
If "bar" is quoted the highlighting is correct though, curlies in black
and the string in green.
In the broken example I'd expect the curlies in black, and the key in
green because it's autoquoted by Perl. Green to the left of =>s would
be good as well, as words there are also autoquoted. Both conventions
for autoquoted stuff are followed by CPerl and the Perl mode for Vim.
q(), qq(), and their variants are not highlighted as strings either.
-- fxn
I just purchased TextMate and found some apparent bugs editing Perl and
Python. Which is the right address to report them?
-- fxn
PS: I would have liked new releases could have a new trial period. I
bought a license without being able to compare the current version with
the initial one.
>I just purchased TextMate and found some apparent bugs editing Perl and
>Python. Which is the right address to report them?
The language bundles are currently maintained by volunteer work. I
contributed the Perl bundle and according to
<http://wiki.macromates.com/textmate/show/Bundles102>, a bunch of
people contributed different Python bundles. Probably the best place
for bundle bug reports is this mailing list, with a subject like Perl
Bugs or something else clever to divert people who don't care.
What are the Perl bugs? They might be due either to my bundle or
underlying problems with TM.
- Eric
--
Eric Hsu, Assistant Professor of Mathematics
San Francisco State University
erichsu(a)math.sfsu.edu
http://math.sfsu.edu/hsu
Hi,
I would like to highlight the syntax as shown in the attached picture.
However, this matches the wrong brackets. Anyone any idea how I could go
about to better highlight this?
I guess it boils down to a not powerful enough syntax highlighting scheme
though :(. The thing I want to do is something like:
- match commands (begin with '\' followed by a word
- this can be followed by [\w+]
- and this can be followed by {.*}
And what I would like to do is apply the global patterns to the '.*'
mentioned above, and if nothing global matches, then apply a color.
Jeroen.
PS. I seem to remember something about using groups to define different
colors in a pattern, but I forgot how that works. Can anyone tell me how
that works and/or add that to the wiki ? :)
