Hello
TM is really on of the best text editors, however, there is two
issues unresolved for (the) years (of SL) now.
Issue one is TextMate's spelling behaviour, i.e., the automatic
detection of the language of a written paragraph, see here:
http://lists.macromates.com/textmate/2009-November/029964.html
TM does not detect the language I am typing in, perhaps because it
uses a non-Apple document window. Anyway, always changing the
system language to get correct spell check on the fly (as
suggested in the thread) could hardly be a working solution. In
addition, quite often I write source documents in various
languages, e.g. English and German, and that makes a "one language
per document" unusable.
There has also been an issue with an advanced print dialogue (but
I cannot remember the posting). It is quite nice that TM adds
headers and footers, however, TM does not print coloured syntax,
and leaving a margin of about 1cm makes the printout unusable for
punching and filing. In addition, 11pt Monaco is quite good on my
screen but printing in that font size is rather a waste of space
on the page. Of course, I know, that one may produce a html
(nicely coloured, indeed), open that one in, say, Firefox, and
print the html page.
Anyway, I was wondering if there is any progress on these two
points, first, to get the apple multilingual spell check working,
second, to provide TM with a print preference to set things like
font, colours, and margins.
Any thoughts?
Regards
*S*
--
Sascha Vieweg, saschaview(a)gmail.com
Hi Everyone,
I am a big fan of textmate and been using it for last 6 years, and SQL
bundle was one of the main tools in my toolbox. However, after upgrading
To Lion I can¹t execute any queries and every time I try I get ³Bad
Handshake² error even though I can connect to mysql just can¹t browse data.
Any pointers on that would be greatly appreciated.
This are my settings:
MacOSX:
Lion 10.7.2 with xcode 4.1
Textmate:
Version: 1.5.10 (1631)
I¹ve removed everything from Preferences -> Advanced -> Shell Variables
Ruby
Running controll+R for this command: puts RUBY_DESCRIPTION returns
ruby 1.8.7 (2010-01-10 patchlevel 249) [universal-darwin11.0]
MySql
It was installed via brew
version: Ver 14.14 Distrib 5.5.15, for osx10.7 (i386) using readline 5.1
My.ini
[mysqld]
max_allowed_packet=64M
character-set-server = utf8
default-character-set = utf8
#This option makes InnoDB to store each created table into its own .ibd
file.
innodb_file_per_table
log-bin
log=/var/log/mysql/mysql.log
log-error=/var/log/mysql/error.mysql.log
log-slow-queries
bind-address=0.0.0.0
[mysql]
default-character-set = utf8
A small enhancement request....
Currently when you open a directory with TM2, it starts with an empty
untitled document. If you do not make any changes to this document, then
the first time you open another document, the empty one is discarded. Nice.
It would also be nice if there were a setting where when you close the last
tab in a window, instead of the entire window closing, a new untitled
document was used as a placeholder instead, just as when a folder is
originally opened. If you do indeed want to close the entire window then
you can use the ⇧⌘W "Close Window" command.
When I finish a task I tend to close the documents that I was working on
before starting a new task and I often find myself closing the entire
window unnecessarily.
Just a thought.
Thanks,
Curt
Hi,
TM2 still appears to have the same troublesome selection behavior TM1 has. As an example take this line in Perl:
die("$self failed to implement ".(caller(0))[3]);
Ideally I could select '$self' by double-clicking. For that to work I would need to tell TM2 that $ is a word character in Perl, per grammar word character definitions are needed. (That may be there already, but I can't find it being mentioned anywhere.)
Now double-clicking on 'self' and moving the mouse to the left to add the '$' doesn't work because it adds '("$'. TM2 should treat non-word characters as individual characters instead of grouping them together into a "word" when extending a selection that started with a double-click.
Similarly it is impossible to select 'caller(0)' by double-clicking 'caller' and extending to the right, instead one ends up with 'caller(0))['.
Gerd
Hi,
i just checked if skim and the sync with skim works, but it does not. Is there a way to solve this?
Best
--
Christian
-Because I'm the CEO, and I think it can be done.-
Steve Jobs, 2005
Something I'd like to see improved in TM2 is the visibility of the
current file browser root. Since I started working with TM2, I've
noticed several things about the file browser:
- I frequently glance at the file browser/project drawer to orient
myself, essentially answering "which project's window is this?"
- The "project" indication, the browser's current directory, is now
the smallest text on the page. (I use a larger font than the default
for the editing windows.) It's also tucked in the midst of a lot of
other stuff, making it hardre to quickly pick out.
- The current directory name is truncated by the buttons to its right
when the file browser pane is narrowed even a bit.
- Quickly inspecting the contents of the file browser is often not
illuminating. Imagine working with multiple Rails apps, multiple
git clones of the same project, etc.
- No location information is available when the drawer is closed. By
contrast TM1's default formatting of the title bar with "<icon>
<file> - <project>".
---------
On that last point, I note that the window title is now user-configurable in
.tm_properties; great news. However, I've not had any luck in
recreating TM1's behavior. For example, in ~/.tm_properties I have:
windowTitle = '${TM_DISPLAYNAME}\
${TM_PROJECT_DIRECTORY:+ - $TM_PROJECT_DIRECTORY}'
and in a project root directory, I have .tm_properties with:
projectDirectory = '${CWD}'
After restarting TextMate (is there an easier way to reload the
props?), it seems that TM_PROJECT_DIRECTORY is never set even when
projectDirectory has been set in .tm_properties. Am I just missing
something about projectDirectory/TM_PROJECT_DIRECTORY, or is this a
bug?
Thanks,
John
Hello all,
I'm having a problem with matching character pairs in TextMate 2, and I'm wondering if it's a known issue or something specific to my installation.
For example, if I open a JavaScript file and type the following:
$(#id_name)
and then go back and place my caret before the # sign, and type a single-quote (or any other matched pair), I end up with:
$(''#id_name)
with my caret now between the matched pair. Selecting all of #id_name before typing a quote character works properly, but obviously requires use of the mouse.
I've confirmed that this happens in JavaScript and Python, but not in CSS or HTML. In fact, in those languages, there appears to be no matched pairing happening at all.
I never really used the matched pairs in TM1, so mostly I'd like to know if there's a way to turn this feature off altogether, but I'm glad to provide any other information required. My .tm_properties file is extremely sparse, and I'm not using any 3rd party plugins.
-phil
Hi there,
It seems that when using dead keys in TM2, the initial keypress of the
dead key is interpreted as input. This creates a problem for functions
like wrapping selected text (with parens or braces) because rather than
wrapping the text with the appropriate character it replaces the
selection with the dead key character.
An example: I use the semicolon followed by j for inserting a left
paren. If I make a selection and do this, it replaces the selection
with the semicolon.
Any ideas?
Thanks,
Garrett Lancaster
