Textmates:
I would like to run a simple python program in Textmate
name = raw_input('What is your name?\n')print 'Hi, %s.' % name
Is this possible?
Thanks....
Bill
--
Bill Gibson
John Converse Professor of Economics
Economics
UVM
Burlington, VT 05405
On the web: www.uvm.edu/~wgibson
Is there a way to clear the key equivalent filed in bundle editor?
(I already know how to remove from bundle source)
Elia
—
☁ @elia <http://twitter.com/elia> (twitter) ✎ elia(a)schito.me (gtalk)
☎ (+39) 348/9051393 perlelia(a)gmail.com (FaceTime)
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
I have same problem as Chris Fonnesbeck with TM2 (9100). Dragging over a long selection shows intermittent skips in highlighting. Selecting by clicking at the beginning, then shift-cliking at the end does not show the problem.
> From: Chris Fonnesbeck <fonnesbeck(a)gmail.com>
> Subject: [TxMt] Scrolling highlight bug in TM2
> Date: May 14, 2012 12:40:50 PM AKDT
> To: TextMate users <textmate(a)lists.macromates.com>
> Reply-To: TextMate users <textmate(a)lists.macromates.com>
>
>
> Running a recent build of TM2, I notice a bug in the highlighting behavior when making a scrolling selection. That is, when I select and drag using a mouse or trackpad, the parts of the editor that are highlighted is inconsistent. Chunks of unhighlighted area appear within a highlighted section. This appears most often when reaching the bottom of the screen, and the text scrolls upward.
Running a recent build of TM2, I notice a bug in the highlighting behavior when making a scrolling selection. That is, when I select and drag using a mouse or trackpad, the parts of the editor that are highlighted is inconsistent. Chunks of unhighlighted area appear within a highlighted section. This appears most often when reaching the bottom of the screen, and the text scrolls upward.
Here is a short video screen capture showing the behavior: http://cl.ly/3S131O0F321i230l3x2T
Running Version 2.0 (9113).
--
Chris Fonnesbeck
Nashville, TN
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
I'm updating my Markdown bundle to better handle GitHub-style fenced code blocks like so:
```ruby
foo = { bar: true }
```
The grammar is simple enough for one language:
ruby_block = {
begin = '^```ruby.*$';
end = '^```.*$';
patterns = ( { include = 'source.ruby'; } );
};
However, I'd like to support any language. I tried the following, but it doesn't appear to work (and I'm not sure why):
code_block = {
begin = '^```(\w+).*$';
end = '^```.*$';
patterns = ( { include = 'source.\1'; } );
};
Is something similar possible / supported?
Thanks!
-Tyson
I'm confused as to what I should be doing to get the latest available build
for TextMate 2.
I'm currently using 9090 which is what the menu update check says is the
latest, but see posts referring to higher numbers.
I am very new to TextMate. Thanks for your patience.
--
View this message in context: http://old.nabble.com/Latest-available-build-for-TM-2-tp33763656p33763656.h…
Sent from the textmate users mailing list archive at Nabble.com.
