I've used Whitesmith bracing style for *decades*, and had it kinda-sorta working in TM 1.5.x, though not perfectly. Now I've lost those old settings and for the life of me can't figure out how to get it even close in 2.0. There's clearly something fundamental that I'm missing, but I've spent hours on this off and on over the past few months, and I'm guessing that someone who really understands the rules (and regex) better than I, could get me on the right path in short order. I'd definitely appreciate it.
For those (unfortunate souls) who are not familiar with Whitesmith:
Also, just as a general suggestion, it seems like it would be really helpful to have just a handful of "packaged" example indentation rules for the small handful of common bracing styles, i.e. Allman, K&R, Whitesmith, maybe Gnu. Of course it wouldn't be perfect for everyone, but it could be really helpful as a starting point. If you know of such a set of examples, please point me to them (yes, I've looked). Thanks!
Since I moved to a new laptop, I noticed a strange behavior with text-selection in TextMate version 2.0-rc.4 (on Mac OS 10.12.6).
Whenever I have a a text-file open in TextMate 2 and click outside of the window (to activate a terminal window, switch to another program, click on a menu item etc.), this ‘click’ will change my selection in the currently opened file.
So, instead of directly deactivating the window, it still takes the action as input for text-selection.
This is of course very annoying, as it constantly changes my selected text / moves the active line etc. without my intention.
It does not always happen, and does not replicate consistently.
Somehow it seems to depend on the time between my last action in the active textmate window and clicking outside of the textmate window.
Is this known behavior and is there a way to fix it?
I've been trying the public beta of macOS Mojave and noticed there are two issues with colors in TextMate.
* With a window open, and the File Browser visible, the color of the vertical line on the left side of the gutter view is darker than the one of the right side. On High Sierra these have the same color.
* When viewing a autocomplete popup/window from a bundle, that is a bundle that is using "TextMate::UI.complete". When selecting an item/row the foreground color doesn't change to white. This makes it a bit difficult to read the text. The same thing happens when selecting an item/row in the bundle editor.
These issues both appear in light and dark mode.
Since the application looks different compared to High Sierra, won't that be considered a bug in the operating system?
Some time ago I posted a SO question about an [issue](https://stackoverflow.com/questions/50412613/scopeattributes-with-mu… <https://stackoverflow.com/questions/50412613/scopeattributes-with-multiple-…>) I encountered while running both the Strip-Whitespace-On-Save and Ensure-Newline-At-EOF bundles (the latter being the recently added one).
Since that question didn't gather any feedback, maybe I'll have more luck here, hence the "repost".
The gist of the issue is that either 1) couldn't read the manual hard enough to find the correct syntax to use, 2) scopeAttributes really are limited to 1 (which I didn't expect when I spec-ed the attribute thingy in the SWOS bundle).
Thanks for your time !
I use an XHTML template language for my web applications that allows me to
define my own tags such as <s:embed>...</s:embed>. I set the language for
these files to HTML so that embedded stylesheets, scripts, etc. are
With HTML bundle update yesterday, these custom tags are now highlighted as
errors with the scope invalid.illegal.unrecognized-tag.html
This has worked great for me for at least the last eight years at least.
This new behavior is rather annoying.
Is there a way that I can avoid the HTML bundle flagging these custom tags
Are there any plans to bundle a more recent Ruby version in the app?
Ruby 2.5.1 is the latest.
Ruby 1.8.7 ships with the app.
The Ruby Core team has long ago stopped supporting 1.8.x.
They currently only support (security fixes, etc) Ruby 2.3 - 2.5 (and 2.6 preview).
I've been using a tooltip based linter for a while, and recently
occationally the tooltips seem to be sticking around. Has anything changed
with that API, intentionally or otherwise?
Is there a way to clear these tips without relaunching the app?
The follow steps are what I feel might cause the issue, but does not
reproduce regularly. Not sure how to help debug except describe that I
think Save a "lintable" file, switch tabs via the keyboard, then switch
again (possibly switch back?).
I'm using callback.document.did-save, callback.document.did-open as a
trigger, maybe its an edge case of $DIALOG tooltip
and callback.document.did-save or callback.document.did-open?
Thanks for looking,
Graham P Heath