I use the app Oyster on Mac to edit and debug regexs. It works nicely, but doesn’t properly predict what TextMate will do with a regex. Something that works in Oyster, does not in TextMate.
Has anyone using Mac found a regex editor that predicts TextMate?
Bob
-------------------
Robert J. Rockefeller
Richmond Hill, GA
www.bobrockefeller.com <http://www.bobrockefeller.com/>
I’m attempting to match the leading - characters in a Markdown list such as this:
---
What were the key things that drove me to make a switch?
- No Database -- you
- Tremendous Support -- the
- Sane Folder Structure -- everything
- Rapid Development -- there
- Blog Post Folders -- granted
- Asset Pipeline -- Grav
- Twig — yes
—
The regex that isn’t working looks like this:
{ name = 'text.html.markdown.list';
match = '(?<=\n)-(?= )|(?<!.)-(?= )';
},
What did I get wrong?
Bob
-------------------
Robert J. Rockefeller
Richmond Hill, GA
www.bobrockefeller.com <http://www.bobrockefeller.com/>
I just came across this because I have script called 'crypt'.
The Avian bundle has command with a scope selector
'attr.rev-path.crypt' which seems to trigger on any file called
'crypt' and prompts me to enter a password so that the file can be
encrypted.
I can easily disable this, but was just curious as to why it is there
in the first place.
Now we are in beta phase, I’ve stumbled a couple of times recently having multiple cursors and having commands fail, as this is not supported yet.
Not sure if this is tricky or not to enable.. I could see it could be, if a command does things that step on what the other “copies” are trying to do. Perhaps a “multiple-selection safe” button in the snippet or command to enable cases where the author thinks it should be as straight-forward as typing into a multiple selection (like, for instance, tag completion) would get this feature off the ground?
t
Is there any documentation of changes needed to convert 1.5 bundles to work with 2.0? I dragged the 1.5 bundle to TextMate 2 and it asks if I want to install it. Click OK and nothing seems to happen. The bundle is not installed and no errors on the screen or in the log.
Thanks,
John DeSoi, Ph.D.
Continue works on relaunch of TM here. And then I selected check on next relaunch and it went from, I think, two upgrades behind to beta 8. No problem her. On rMBP with up to date OS X.
Good luck.
Greg
> On Feb 4, 2015, at 4:00 AM, textmate-request(a)lists.macromates.com wrote:
>
> Date: Tue, 3 Feb 2015 18:34:09 -0800
> From: Matt Neuburg
> Subject: [TxMt] TextMate prompts for nonexistent update, interface has
> gone nutty
>
> I am getting a dialog asking me to update TextMate, but when I check for updates, there are none:
>
> But that's not the worst part. I click Continue, and the interface has gone crazy: the gutter is suddenly black, and it isn't using my preferred font any more. It's as if all my preferences had been overthrown. m.
Timfong88(a)gmail.com
Sent from phone
On Tue, Feb 3, 2015 at 6:39 PM -0800, <textmate-request(a)lists.macromates.com> wrote:
Send textmate mailing list submissions to
textmate(a)lists.macromates.com
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.macromates.com/listinfo/textmate
or, via email, send a message with subject or body 'help' to
textmate-request(a)lists.macromates.com
You can reach the person managing the list at
textmate-owner(a)lists.macromates.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of textmate digest..."
Today's Topics:
1. TextMate prompts for nonexistent update, interface has gone
nutty (Matt Neuburg)
----------------------------------------------------------------------
Message: 1
Date: Tue, 3 Feb 2015 18:34:09 -0800
From: Matt Neuburg
To: TextMate users
Subject: [TxMt] TextMate prompts for nonexistent update, interface has
gone nutty
Message-ID: <56DB986A-328A-487E-8948-E38DA272DE8D(a)tidbits.com>
Content-Type: text/plain; charset="us-ascii"
I am getting a dialog asking me to update TextMate, but when I check for updates, there are none:
But that's not the worst part. I click Continue, and the interface has gone crazy: the gutter is suddenly black, and it isn't using my preferred font any more. It's as if all my preferences had been overthrown. m.
--
matt neuburg, phd = http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 8! http://shop.oreilly.com/product/0636920034261.do
iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
Hello,
I am super new to posting to lists in general, so please excuse any
breach of etiquette.
I love TextMate, and have been a faithful user since way back. It
lacks for nothing, as far as I'm concerned, but I do have one
question.
Currently, I am using the Text bundle to trim trailing spaces on save.
The settings are like this:
Semantic Class: callback.document.will-save
Save: Nothing
Input: Document
Format: Text
Output: Replace Document
Format: Text
Caret Placement: Heuristic
This works beautifully. The only issue I have is that no matter where
I am in the document, after save my cursor (caret) is placed at the
very end of the document, and the document is scrolled to that point.
In a longer file, with frequent saves, I have to scroll back and find
my place every time.
I tried different options for Caret Placement and for Output (in the
bundle), but the result remains the same.
My question is twofold: is there something else I could be doing, and
also I'm curious if there are any plans to change this behavior (or
make trimming a built-in option, so to speak), to where the view
doesn't scroll? Seems like this is a common option to want to have.
Thank you!
- g
Hi,
I've noticed that selecting enclosing typing pairs is broken for HTML when
an open tag spans several lines. ie:
<div>*
<p id="paragraph"
class="content">
</p>
</div>
If you place the caret at * and select the enclosing typing pairs, the
selection closes at </p> rather than </div>. It doesn't happen however for
self closing tags:
<div>
<input id="field"
class="form-field"/>
</div>
I've looked into the HTML bundle but I'm not sure the typing pairs
references there are the culprit for this.
Could someone point me in the right direction to fix this issue? I'd be
glad to open a PR once I get it working.
Thanks!
