With TM2 nice and stable at release candidate 23, and with a major feature of TM being bundles of user-built snippets and commands, it would be much appreciated to have a UI for editing bundles.
Just supporting
1. Drag snippets between existing folders and
2. Right click “create new folder”
Alongside the existing make new, copy UUID and show in Finder features these two would be a major advance in usability.
Even if it was restricted to user-managed bundles (if the concern is to much product support from breaking updates to centrally managed bundles in the first instance).
Hi,
Programming for R (stats package) the user often wants to select a whole function (usually in order to execute it in R)
my fun <- function(param,..){
# your code
}
cmd-shift-B will select the next-out level of brackets, and, if repeated, will eventually select the outer-most brackets. But to execute the function, one needs to select the whole of that first line of the function definition.
Is there a command to do that?
the command would function like repeated executions of cmd-shift-B until the there is no outer bracket to find, then expand the selection to include ^ of the first line
Is it possible to get a TextMate 1.5 syntax coloring theme into TextMate 2.0, and if so, how?
Jerry
P.S. Just wondering why there is no theme editor in TM2.
Hello,
My end goal is that I want to tell textmate to ignore some directories (or include) when finding files using “Open Quickly”
I skimmed the source code and saw that I might be able to use some kind of settings:
static std::map<std::string, NSString*> const map = {
{ kSettingsExcludeDirectoriesInFileChooserKey, kSearchExcludeDirectoryGlobsKey },
{ kSettingsExcludeDirectoriesKey, kSearchExcludeDirectoryGlobsKey },
{ kSettingsExcludeFilesInFileChooserKey, kSearchExcludeFileGlobsKey },
{ kSettingsExcludeFilesKey, kSearchExcludeFileGlobsKey },
{ kSettingsExcludeInFileChooserKey, kSearchExcludeGlobsKey },
{ kSettingsExcludeKey, kSearchExcludeGlobsKey },
{ kSettingsBinaryKey, kSearchExcludeGlobsKey },
{ kSettingsIncludeDirectoriesKey, kSearchDirectoryGlobsKey },
{ kSettingsIncludeFilesInFileChooserKey, kSearchFileGlobsKey },
{ kSettingsIncludeFilesKey, kSearchFileGlobsKey },
{ kSettingsIncludeInFileChooserKey, kSearchGlobsKey },
{ kSettingsIncludeKey, kSearchGlobsKey },
};
However, I don’t know where I would set these. I believe there may me some kind of file I can place at my project root to define these, but I’m unable to determine what the name of this file should be or the format of the file.
Any help would be appreciated.
Thanks!
1. Use app "Check for Upgrade" to upgrade to RC 20/21/22, Cmd+F to bring up
Find dialog window, unable to display/type non-English characters (such as
Chinese, Japanese) in Find and Replace text box, have to un-focus input
area to show the characters. No problem for English characters.
2. Manually upgrade by downloading RC 20/21/22 from Github, and replace
existing TextMate.app in Applications. Cmd+F (or select Find... from Edit
menu) will not bring Find dialog window.
Rolled back to RC 19, solved the problem.
--
Sent from my mobile. Ignore the typos unless they're funny.
--
--
Sent from my mobile. Ignore the typos unless they're funny.
Hi all,
There is some problems with expressions in f-strings in the Python bundle.
One is that escape-completion does not work inside them at all.
The other is that syntax highlighting often fails. For example for these:
f"{2 * 37}"
f'{person["name"]}'
f"{'Eric Idle'}"
In neither of these f-strings the braces or expressions are highlighted.
Does anybody know how to fix these? I guess it’s just some small adjustments to the syntax bundle but it’s a rather daunting list of regular expressions in there.
F-strings are a great enhancement to Python and it could be great to have them probably supported.
I have created issues on https://github.com/textmate/python.tmbundle/issues/ for both problems.
Best regards,
Tuk
I have a bundle for linting JavaScript and I'm having trouble figuring out
how to handle JavaScript embedded in HTML. Currently, I'm expecting that
the `source.js` refers to a full file. This creates an issue since
`source.js` is also part of the scope when JavaScript is embedded in HTML,
causing my bundle to lint a full HTML document. Is there a way to configure
the bundle to ignore embedded JavaScript, or to dynamically switch to
linting only the embedded JavaScript?
This the bundle: https://github.com/ryanfitzer/eslint.tmbundle
Hi All,
Sorry for troubling you.
I am trying to build TextMate from source, since I would like to add couple of features, key bindings etc.
I have done literally everything as specified on this page:
https://github.com/textmate/textmate#readme
I have downloaded latest XCode online tools on my latest patched version of macOS Mojave.
Also, I see that Apple has upgraded my Ruby to the version 2.3.
However, anytime I run:
./configure && ninja
I get the following output:
———————————
rm /Users/sinisa/razno/zez/textmate/Frameworks/SoftwareUpdate/fixtures/secret.pem
bin/gen_build:487:in `rename': No such file or directory @ rb_file_s_rename - (build.ninja~, build.ninja) (Errno::ENOENT)
from bin/gen_build:487:in `atomic_write'
from bin/gen_build:567:in `block in <main>'
from bin/gen_build:538:in `chdir'
from bin/gen_build:538:in `<main>'
./configure: line 99: 19128 Segmentation fault: 11 ninja Frameworks/encoding/src/frequencies.capnp.h
./configure: line 100: 19179 Segmentation fault: 11 ninja Frameworks/plist/src/cache.capnp.h
bin/create_default_bundles_tbz: line 21: 19193 Segmentation fault: 11 ninja "$bl”
—————————
What should I do ????
Many, many thanks in advance …….
--
Sincerely,
--
Sinisa Milivojevic <sinisa(a)cytanet.com.cy>
MySQL Developer
Larnaca, Republic of Cyprus
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ /
/ /|_/ / // /\ \/ /_/ / /__
/_/ /_/\_, /___/\___\_\___/
<___/ www.mysql.com
Hi All,
I’m currently preparing my new machine to replace my old MacBook Air 2015 as a development machine. My new machine is a Mac Mini 2018.
I’m unable to save files in TextMate (the editor I do all my code in). Got the following error :
The document “untitled.txt” could not be saved
Please check console output for reason.
I don’t see nothing special in the console log. I tried all the steps in https://alexwlchan.net/2016/05/os-x-hates-textmate/ to no avail.
Anyone has any idea?
Thanks,
Yann Bourdeau
yann.bourdeau(a)noviflow.com
Hi,
Please forget about my previous mail. I have solved my issue after finding it was working on another user account.
I had a bundle modification on callback.document.Export instead of callback.document.will-save to trim the trailing white space.
Thanks
Yann
Hi All,
I am looking for someone that can merge the pull request below.
The grammars of Textmate is used by Github.
Sadly the grammar for the Scheme language colors square brackets red (as an
error),
and there are lots of Scheme implementations that allow squares.
That makes it jarring to read source files on Github.
A kind soul has found the error, fixed it and submitted a pull request.
Unfortunately the grammars don't live in the main Textmate repo,
so pull request are easily missed. This one is a couple of years old.
It would be greatly appreciated by the Scheme community, if this could be
merged.
Thanks in advance.
https://github.com/textmate/scheme.tmbundle/pull/9
/Jens Axel Søgaard
Default is "ruby 2.3.7p456"
>
> Today's Topics:
>
> 1. Re: Bundle support plist broken on Mojave (Philippe Huibonhoa)
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 30 Jan 2019 20:54:44 -0800
> From: Philippe Huibonhoa <phuibonhoa(a)gmail.com>
> To: TextMate users <textmate(a)lists.macromates.com>
> Subject: [TxMt] Re: Bundle support plist broken on Mojave
> Message-ID:
> <CABF6MVzbki=T+-DZ18Sg1AmJA+K2Jw7=WoYHDG+buNo+H9jHOg(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Does Mojave still have Ruby 1.8 available? I have bundle files
> referencing /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby
> but that directory does not exist. I'm not sure how to proceed, since this
> does break some functionality.
>
> On Sat, Dec 15, 2018 at 12:29 AM Jacob Carlborg <doob(a)me.com> wrote:
>
>> On 15 Dec 2018, at 09:13, Allan Odgaard <mailinglist(a)textmate.org> wrote:
>>
>> The problem is that many bundle commands need ruby 1.8, so the bundle
>> support code needs to remain compatible with 1.8 as well.
>>
>> This is support code has been written by a dozen different people over
>> several years, I have no plans of rewriting it all to be compatible with
>> both ruby 1.8 and 2.x, which in itself is not a fun excercise, not even
>> sure we can make the plist extension compatible with both versions of ruby
>> without switching to a version written entirely in ruby.
>>
>> Understandable. I?ve been wanting to completely re-implement the support
>> code with support for 2.0 now for a while. But I?ve never prioritized it.
>>
>> My advice: If you want to use ruby 2.x for your custom commands, don?t use
>> the support code.
>>
>> Yeah, in fact, most of my commands are written in Ruby 2.0 but one of them
>> is using Ruby 1.8 to be able to use the completion window.
>>
>> In this case I see now that TextMate.detach is simple enough to copy to
>> the bundle and remove the dependency on TextMate::UI.
>>
>> In retrospect we probably shouldn?t have made a ?shared support?
>> directory, at least not without much much stricter discipline, as now we
>> have a ton of legacy stuff that is pretty difficult to get rid of, because
>> we have no idea about which third party bundles rely on it.
>>
>> The support code, at least the Ruby code, could be implemented as a
>> separate gem. Then it could be versioned like any other gem. I have a
>> bundle [1] where the whole Support directory is organized as a Ruby gem. It
>> uses Bundler and several gems as dependencies. The gems are bundled
>> directly in the Support directory and included in the Git repository. This
>> works out quite nicely.
>>
>> [1] https://github.com/jacob-carlborg/GitLab.tmbundle/tree/master/Support
>>
>> --
>> /Jacob Carlborg
>>
Hi,
a simple question, but I cannot find ;)
When moving your cursor via arrow keys over a (HTML) tag, the corresponding
beginning or ending tag is highlighted in yellow! So I assumed TM is able to
select and / or change the tags at once.
But unfortunately I cannot find the command. Hope someone can help me.
== feek
--
Sent from: http://textmate.1073791.n5.nabble.com/textmate-users-f3.html
Hello
I am new to Textmate and grammars syntax but i want to fix a bug with a grammar used by GitHub for highlighting of SaltStack files.
The grammar in question is this one ( https://github.com/saltstack/atom-salt/blob/master/grammars/yaml.cson ) and the problem is comments that span multiple lines don't get handled correctly so i fixed the regexp but the more i looked at the problem i don't think any comments are really being handled as the grammar expects because of an "include" that's overriding the local comment definition.
As i said, i'm no Textmate/Grammar expert but with some fumbling around i think the problem occurs due to a repository entry that calls:
{
'include': 'source.python'
}
This external grammar file has its own agenda when it comes to comments and lines matching the "#" type pattern. I think this included grammar is taking priority over the patterns/captures defined in the above .cson file. I believe it might be this pattern ( https://github.com/textmate/python.tmbundle/blob/master/Syntaxes/Python.tmL… ).
If i comment/delete the 'include': 'source.python' from the "jinja-control" repository then my regexp change works and comments look as expected.. but obviously I've crippled the other highlighting brought with the python include.
So at this point i'm stuck. I have no idea how the order or precedence works and how i should resolve this conflict ?
Can someone explain please why the include is doing this and whats the way for me to ensure my local definitions to be enforced ? I tried moving my pattern to the top of the .cson, tried to make the regexp more explicit and increase the name depth in case any of those were the magic but no luck.
thank you.
Hello everyone,
I would like to start contributing to TextMate development. Are there any guidelines that I can use to get familiar with the codebase or where would be a good starting point for making sense of the codebase, since it is fairly mature.
Best,
Farhan
In rc.22 have we removed the document proxy icon so classically part of document based apps?
That's always been one of the most Mac things and TM's support of it has always been a blessing.
Also, looks like Bundle Editor window's drawer is a victim of deprecation with dark mode ...
... time to move to split views ¯\_(ツ)_/¯
The Git commit dialog is slightly broken in the latest release, 2.0-rc.22. In the table view showing all change or untraced files it says “Button” on each line between the checkbox and the icon. I’ve attached a screen shot below. This occurs on macOS High Sierra but now on Mojave.
--
/Jacob Carlborg
With the latest update of TextMate, 2.0-rc.22, the text color of a selected item in the Open Quickly dialog is black. I guess it’s supposed to be white. This makes it a bit difficult to read on the blue background.
Running on macOS High Sierra. It has the correct color on Mojave, both in light and dark mode.
--
/Jacob Carlborg
Hi. Let's say I have 3 commands and they all use `callback.document.will-save` as semantic class. What is the order of execution? or How can I set the order? In my experience, the last created command runs first. I'm not quite sure about it. I've been trying to improve my Python formatter bundle. I have some tasks to do in order. Couldn't figure out exactly the execution order of it.
Thanks
---
Uğur "vigo" Özyılmazel
https://github.com/vigohttps://gitbook.com/@vigohttp://ugur.ozyilmazel.com | @vigobronx
http://devpod.org | @podcastmaster
http://gelistiriciyiz.biz | @gelistiriciyiz
On Wed, Nov 28, 2018 at 5:00 AM <textmate-request(a)lists.macromates.com>
wrote:
> I do a lot of find using the "In Folder" setting.
>
> The only easy way to bring it to the from is cmd-F, but this re-sets the
> "In: <where>" dropping down to the default, which is document.
>
Does cmd-shift-F work for you? That should set the window to "In:
{Project}". There is a Find in Folder menu command, as well, which doesn't
have a default keybinding, but that's easy to change in the Keyboard System
Preferences.
Today I noticed that clicking the SCM icon in the bottom right of the
file browser no longer does anything (it used to filter the view to
include only those files with a specific SCM status). Maybe this is
related to the recent changes in the file browser?
Everything else regarding SCM (using Git in my case) still works as
expected, including the SCM badges on the icons in the file browser.
Using TextMate 2.0-rc.14
Cheers,
Stefan
I’ve noticed in some cases the file browser doesn’t show the files within a folder when that folder is expanded. Navigating inside that folder shows the files and when I navigate back the files are visible again.
--
/Jacob Carlborg
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?