Some basic things I couldn't figure out:
-Is it possible to assign key shortcuts to "Syntax Highlight As" menu for different languages. Right now I launch TextMate & use it for writing quick scripts in the default New Document window which has no syntax highlighting and it is a pain to go to the menu and select the language.
-Going with the previous point, can we set the default Syntax Highlight language for the New Document.
-What's up with the Command Output Window. It has a huge empty White block on top & dragging the resize bar brings an empty grey block at the bottom. Unless I am missing something, it sure can use some redesign & have features like multiple buffers for each script/selection run but in an elegant configurable way and/or optional output appending in the same window with a divider etc.
On 29. jan 2005, at 7:41, Chu wrote:
-Going with the previous point, can we set the default Syntax Highlight language for the New Document.
This has been suggested recently, and put on the to-do by Allan.
-What's up with the Command Output Window. It has a huge empty White block on top & dragging the resize bar brings an empty grey block at the bottom.
I think those are known bugs, actually ;-).
On Jan 29, 2005, at 12:18, Sune Foldager wrote:
-What's up with the Command Output Window. It has a huge empty White block on top & dragging the resize bar brings an empty grey block at the bottom.
I think those are known bugs, actually ;-).
Actually, I think the OP is unaware that the top part is the parsed output and the bottom part is the raw output.
But there is a bug with regard to resizing, and this window has been heavily neglected -- unrelated to this post I actually did have it on the to-do for beta 4 (together with HTML output for commands), which is a “maintenance” release, meaning a lot of stuff gets fixed :)
On Jan 29, 2005, at 6:25 AM, Allan Odgaard wrote:
Actually, I think the OP is unaware that the top part is the parsed output and the bottom part is the raw output.
I've got two complaints about the command window. The first is parsed vs. raw output. I don't want two windows. I want a single window with the output marked up and clickable. For example, javac output consists of perhaps three lines when a compilation error occurs: [javac] /Users/blalor/devel/java/BeanShellServlet/src/org/bravo5/ BeanShellServlet/BeanShellServlet.java:31: cannot resolve symbol [javac] symbol : class HttpServletResponse [javac] location: class org.bravo5.BeanShellServlet.BeanShellServlet [javac] HttpServletResponse resp)
I really want to be able to click on the line number and still be able to see the rest of the error in context.
Also, when running a compilation that doesn't return immediately, TM completely hangs until the command is done. I'd like to see the command window update as the command outputs data.
On Jan 30, 2005, at 13:54, Brian Lalor wrote:
Actually, I think the OP is unaware that the top part is the parsed output and the bottom part is the raw output.
I've got two complaints about the command window. The first is parsed vs. raw output. I don't want two windows. I want a single window with the output marked up and clickable.
I'm hoping that this window will play a lesser role when I add HTML as output option (that was the main motivation behind the txmt:// URL scheme) -- so with this you can pretty much format/style it exactly as you want.
Also, when running a compilation that doesn't return immediately, TM completely hangs until the command is done. I'd like to see the command window update as the command outputs data.
Yes, that sucks a bit. For this reason I'm doing most of my builds from Terminal.app -- I really need to fix this ;)
-
Allan Odgaard -
Brian Lalor -
Chu -
Sune Foldager