Greetings from the South :-)-O,
I occasionally want to pipe JSON (or XML, or other formats) like
csvjson file.csv | mate -
It does display the file but as plain text.
How can I make TextMate2 figure this out by itself? Or from the command
line (mate -t JSON - does no do that)? Or where can I read this up?
greetings, el
--
Dr. Eberhard W. Lisse / Obstetrician & Gynaecologist (Saar)
el(a)lisse.NA / * | Telephone: +264 81 124 6733 (cell)
PO Box 8421 /
Bachbrecht, Namibia ;____/
The rc.19 update reset quite a few of the TextMate preferences. For example:
* All variables I’ve added are gone
* The side the file browser is shown on reset
* Same with the command output window
* TextMate thinks the shell support is not installed
These are a few things I’ve just noticed.
--
/Jacob Carlborg
TextMate version: 2.0-rc.15
macOS Sierra: 10.12.6 (I also see this behavior on Mohave)
List of source files overlap the title bar when scrolled:
[image: Screenshot 2018-11-13 12.10.34.png]
(Sorry if this is a duplicate. My last attempt to send seemed to fail, but I can’t be sure it didn’t get through.)
In recent versions of various Apple programs, including Safari, Preview and iBooks, when you go into full screen mode, the sidebar hides itself until you roll over the edge of the screen with the cursor. I sometimes use Textmate on a laptop with a relatively small screen, and increasingly use it in split-view mode on my iMac, and in those cases things get a bit cramped, so it would be nice if the file browser in Textmate behaved in the same way.
I had thought that I remembered when the Apple programs started doing this that I read about it being trivial to implement if you were using auto-layout, but I’ve Googled it and done a cursory search in the developer docs, and it seems I imagined this, so perhaps this is an unreasonable request, in which case, dismiss it from your minds.
And yes, I know that lots of people really hate this behaviour, so if it could be implemented at all, it would need to be one of those things you need to use defaults write to enable.
Thanks for considering my suggestion.
Nigel
(I’m also sorry if I’ve asked this before, put it down to failing memory in old age if I have.)
I’ve created a new theme by adopting the theme Mac Classic that is shipped with TextMate. The original Mac Classic is a light theme, this new theme is adopted for the dark mode setting in macOS Mojave.
Since I’m not a designer I took an engineering approach to creating this theme. I took the basic colors for background, foreground and similar from Xcode. Then I wrote a script that parses the Mac Classic theme file, extracts the colors, converts the colors to HSB and adjusts the saturation and brightness. Then it writes the new colors back to an a new file. I then did some tweaks manually for some colors. I think it turned out pretty good. The theme is available here [1].
[1] https://github.com/jacob-carlborg/mac-classic-dark
--
/Jacob Carlborg
The rc.15 build has the file bowser with new source list style. The color of a selected item in the file browser can be quite difficult to see sometimes (depending on what’s behind the window). I’ve included three screen shots, from TextMate, Xcode and Finder. The location of the selection was the same for all application (the same thing behind the window). What’s behind the window is my desktop with a blue color. In the TextMate screen shot it’s the “package.d” file that is selected.
This is on macOS 10.13.
--
/Jacob Carlborg
By default TextMate won’t show hidden files (files starting with a dot) in the file browser. It’s possible to configure TextMate to show some of these files anyway, I’ve done that for files like .travis.yml. When doing a project wide search it won’t search those files, even though they’re visible in the file browser. Is that a bug, missing feature or an additional setting?
--
/Jacob Carlborg
I noticed that the bottom right and left corners of the TextMate main window is not rounded any more. I think this happened in the rc.14 release. The problem occurs on High Sierra but not on Mojave.
--
/Jacob Carlborg
An idea for a minor feature would be to be able to set a light and dark editor theme. When the OS appearance change it would change to a matching theme for the editor.
This was just and idea I had, would be pretty low on the priority list.
--
/Jacob Carlborg
I just updated to TextMate rc.14, which contains the overhauled file browser. I would really like if the "source list” style could be brought back.
--
/Jacob Carlborg
Is there a way to make * include hidden files in Find All dialog?
Currently I have to use {.*,*} to get the needed result but it's not very convenient to type that every time I do a search.
Another nice little tweak would be to search * instead of using the last glob pattern when you leave the glob field empty. And even better would be to make this default pattern configurable. That way I could've just emptied the glob field when I want to search {.*,*}
Thanks.
Sometimes when I'm working on a project and jump between branches TM suddenly stops scrolling to the current file when I press "Go to current file" (⌃⌘R) even though the file gets selected.
This is happening for a few months already. I usually fix this by restarting TM, but it's not the best workaround since I lose all the undo history.
Am I the only one getting this? Or I'm just the only one getting annoyed by this?
Hi,
This is starting to bug me. I think this started after I tried using the CTags bundle, but a while back the symbol selector on the bottom-right of each window is populated with the full text of the current file instead of the actual syntactic symbols. Any pointers on how to fix this?
Thanks
I recently read this post [1] where it shows how to define a regular expression (using the PCRE) syntax that looks very much like a proper grammar. A reduced example for the post looks like this:
/
(?(DEFINE)
(?<addr_spec> (?&local_part) @ (?&domain) )
(?<local_part> (?&dot_atom) | (?"ed_string) | (?&obs_local_part) )
(?<domain> (?&dot_atom) | (?&domain_literal) | (?&obs_domain) )
)
^(?&addr_spec)$
/x
The three capture groups “addr_spec”, “local_part” and “domain” would be the grammar rules. It uses the (?&name) syntax to refer to another subgroup. TextMate does not support that syntax but supports the following syntax: \g<name>, which the documentation refers to as Subexp call [2]. This syntax seems to have the same semantics. (DEFINE) is something that seems to be PCRE specific and basically means that the following patterns will not be tried to match. It basically gives a place to define subpatterns. I didn’t find anything corresponding in the TextMate regular expression syntax but defining an optional group can be used as a workaround.
Here’s an example where I tried this technique to match a module declaration in the D language:
(?:
(?<module_declaration>(?<module>module)\s+\g<module_fully_qualified_name>\s*;)
(?<module_fully_qualified_name>\g<module_name>|\g<packages>\.\g<module_name>)
(?<module_name>\g<identifier>)
(?<packages>\g<package_name>|\g<package_name>\.\g<packages>)
(?<package_name>\g<identifier>)
(?<identifier>\w+)
)?
\g<module_declaration>
This is exactly according to the specified grammar [3] and it seems to be working as expected. Not sure if the optional group workaround causes some performance implications.
This technique seems like it could be a viable alternative to supporting variables in the TextMate grammar as has been discussed before. What’s missing from this to make it really useful would be something like (DEFINE) in PCRE and a place in the TextMate grammar to place generic patterns used in multiple rules, like a pattern for identifiers.
[1] https://nikic.github.io/2012/06/15/The-true-power-of-regular-expressions.ht… <https://nikic.github.io/2012/06/15/The-true-power-of-regular-expressions.ht…>
[2] https://macromates.com/manual/en/regular_expressions <https://macromates.com/manual/en/regular_expressions>
[3] https://dlang.org/spec/grammar.html#ModuleDeclaration
--
/Jacob Carlborg
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:
http://en.wikipedia.org/wiki/Indent_style#Whitesmiths_style
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!
Dear all,
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?
Thank you!
I use Textmate to prepare material for classes I teach. Most of what I do
is to write explations formatted with Github version Markdown. When OS 10
came out the formatting failed to produce the styled image. Has anyone else
had this problem?
—Lewy
--
Sent from my icebreaker in the Bering Strait
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?
--
/Jacob Carlborg
HI:
I installed textmate a few evenings ago and it appeared to be working, but then I went to Finder to preview some Matlab files (.m) and when I clicked on them in the Finder Window Preview Panel (not to be confused with Preview the app), it shows the text that is in the file, but NOT like it used to. Instead of the normal OS-X white background and black text, it shows the text in the same colors and format as TextMate! (Black background, white and drab brown and green text for quoted text etc. ).
How did this happen, in that all I did was install TextMate from the download link.
I’m not feeling a warm fuzzy when an application I install that modifies an operating system function and appearance, when I’m not thinking it should.
Thanks!
Herbert U. Fluhler
256-651-5673 [C]
The feature of wrapping comments (even when line wrap is off) doesn’t work well with my work flow.
Suggestion: Add a preference to not do this.
Otherwise a question: Is there a way to turn this off?
