TextMate

textmate@lists.macromates.com

10171 discussions

by Yann Bourdeau

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

5 years, 10 months

LaTeX issues with “Include Image” (drag-n-drop item)

by Dustin Wheeler

5 years, 10 months

Re: LaTeX issues with "Include Image" (drag-n-drop item)

by Dustin Wheeler

5 years, 10 months

Merging Pull Request

by Jens Axel Søgaard

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

5 years, 10 months

Re: Bundle support plist broken on Mojave (Philippe Huibonhoa)

by Greg

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 >>

5 years, 10 months

Select /modify begin and end tags in HTML

by feek

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

5 years, 10 months

TextMate grammar help - stopping repository pattern includes overriding ?

by Scott McGillivray

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.

5 years, 11 months

Contributing

by Farhan Ahmed

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

6 years

Document Proxy Icon Gone?

by じょいすじょん

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 ¯\_(ツ)_/¯

6 years

Commit dialog slightly broken

by Jacob Carlborg

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

6 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

TextMate