When you cursor through a closing brace, TM highlights the opening one to
help you balance it.
Im assuming this feature is in TM Core and not provided by a bundle as such
Is there a way to also get TM to highlight the opening brace, when you
actually type the closing brace too?
Cheers
Hello there,
TextMate 2 removed the option of new-from-template, so with your help I
created a command. After updating to Yosemite and TextMate 2.0-beta.6 it
stopped working.
*Compressed version of the problem*
#!/usr/bin/osascript
tell application "System Events"
keystroke "p"
end tell
*Error:*
HTML5:63:122: execution error: An error of type -10810 has occurred.
(-10810)
HTML5 is the name of the command. I don't know what 63 and 122 refers
to, as there are only 18 lines in my command. Is it perhaps a
permissions problem?
All the best,
Rasmus
Does anyone have any SVG bundles they'd recommend? I am feeling a need to
get in amongst the SVG rather than staying in illustrator/omnigraffle and
on first inspection there are a number of bundles but all I've seen are
pretty aged and never had much activity.
Ken
Hi, I had two questions.
1- sometimes I cannot open a file in a tab. Even when I create a tab and press Open, text ate opens a brand new window. I would like to keep those files a tab away.
2- I want to create a bundle that will correct for the correct syntax (spelling and end brackets) for an XML like markup. I tried to look at how JSON and XML bundles were done but was overwhelmed. What's the best place to get started? The markup is called AIML 2.0
Thanks!
Matt Neuburg wrote:
> So what about the little arrow button at the bottom that opens the list of changed files and lets you show the diff as a separate window? m.
I've just received beta 6 (previously on beta 1), and it has changed a bit more. The drop-down to check/uncheck all has reappeared at the bottom of the Commit window: good change back to the previous UI - it was a bit hidden in the right-click menu on the grid. (Thanks to Michael Sheets for pointing that out to me).
The little arrow just hides and shows the grid. The cog drop-down only offers check/uncheck all. Maybe I'm missing something? Each file has a Diff button, but that opens the diff just for that file. If I've got lots of changes that's also a bit tiresome.
Ronald Wampler wrote:
> See http://lists.macromates.com/textmate-dev/2014-July/014989.html and https://github.com/textmate/textmate/pull/1249 for previous discussions.
Thanks for the pointers; they were helpful in understanding the aim of the changes. I see that the individual diffs are opened in a separate window but tied to the project, which makes sense. Following that idea, I guess what I would like to see is an option to open all of the diffs in one tab on that, i.e. the same as Command-Shift-A, Command-Y, "Diff with working copy (BASE)" and double-click the tab, which is my current dance that I have to remember to do before opening the Commit pane. Perhaps another option in the cog drop-down along with check/uncheck all?
I know that the "Previous Commit" messages are retained, which is a very useful feature that I've used for a long time. Opening and closing the commit pane to write a bit of a message in between reviewing code is still a bit tedious.
I saw also that Allan commented in the pull request:
> I’ve noticed that sometimes I need to include stuff from my source in the commit message, in which case I need to abort the commit (in order to get to the source), a downside of the sheet I hadn’t considered. But I’ll give it some more time, as it might not be that big of an issue in the long run.
This is basically the fundamental problem I am getting at. As I wrote above, the new pane in beta 6 is much better than it was in beta 1, and it could be improved further with an 'open all diffs' button, but in the end the modality means you cannot access the tabs. On the other hand, I also see Ronald's original point that you can end up with several Commit windows with the old UI. It happened to me occasionally too. Maybe we just need a preference setting to have it either way?
Allan Odgaard wrote:
> We already use an extenral window when showing uncommitted changes for Git which has the nice feature that line numbers (in that display) link back to the original documents. Additionally once TM supports re-running commands on changes, such output windows can be made ?live?.
Sorry Allan, I don't use Git so I don't understand what the links and 'live' windows means for the SVN Commit window, but it *sounds* good! :-)
Thanks all for your input and hard work.
Cheers,
Jonathan.
I joined the list just to say TextMate is looking great. Love the tabs,
love the direction the chooser windows are going in —it's all good.
Thanks for all the hard work!
I found the following bundle for Javascript's rapidly approaching ES6
standard:
https://github.com/Benvie/JavaScriptNext.tmLanguage
I like that it phrases things as being for Textmate *and then *Sublime but
the installation instructions are clearly Sublime centric. Anyway, just
wondering if there is going to be anything official for ES6 coming soon.
With transpilers reaching maturity the ability to program in ES6 has come
so I think having a good answer to this language choice will be important.
Ken
I have several favorites pointing to directories with very similar (or
even identical) names, so I usually rename the symlinks.
Since beta 5.4 the “Open Favorite” chooser window shows the name of the
directory the symlink is pointing to instead of the symlink's name. Was
this an intentional change?
Hi All,
I've been a Textmate user for a long time but I'm new here on the list. Recently the SVN commit pane changed from a dialog to a modal pane. I sent a message to feedback but was advised that I would be better raising it as a discussion here. I cannot find a previous thread that explains the design decision for the change.
I tend to open a full diff before starting the commit so that I can review my changes and write the commit message accordingly. Now I have to remember to double-click the tab of the diff file to move it to a separate window because the modality stops me from accessing the tabs. I also cannot browse the actual code on the tabs.
I presume that the modality change is to stop a novice from continuing to edit files before hitting Commit and therefore not necessarily committing everything? (I don't consider myself a novice). :-)
Cheers,
Jonathan.
