Re: regex deconstructor

> > Based on how it works, indent applies to the next line and unindent > applies to the current line (in Atom). ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription

Re: regex deconstructor

I don't think you can double-indent, and you can't double-unindent, either, so the case/switch structure for instance is a bit of a hack that we had to compromise on. The problem with the indent/unindent applying to the current line is that the docs say that they apply to the _next_ line. It

Re: regex deconstructor

It kind of makes sense for the unindent to apply to the current line. Usually I think of the end of a block being at the same level as the start. I’ll take a look at the RegEx you provided. I read through it over the weekend and understand most of it. Stuff that is missing is the double indent

Re: regex deconstructor

It's also not clear from the documentation what triggers the current line to unindent. If you are typing "end repeat" for instance, the line will unindent, but the documentation states that the _next_ line will unindent. On Mon, Jan 29, 2018 at 9:20 AM, Mike Kerner

Re: regex deconstructor

I'm not sure why they have some of those the way they have them. The indent regex in ST is not well documented (that I can find). For example, I don't think "<" is a reserved character in regex, but ST requires you to treat it as you would in html, i.e. "" The first thing that I'm trying to do

Re: regex deconstructor

There are nice tests for indentation on Git for Livecode https://github.com/livecode/livecode-ide/tree/develop/tests/scripteditor/_indentation_tests especially the if variants are mind boggling Kind regards Bernd -- Sent from:

Re: regex deconstructor

I’ve only looked at the ST in this thread and the Atom version that is available inside the app. I’ve tried a little but have not seen clear documentation on how the various indent rules are handled. From how it works, if a RegEx is in both indent and unindent then the current line is pushed left

Re: regex deconstructor

@Brian, Which attempt are you talking about? We have two: The one I posted a couple of days ago is the proposed new one from King Keith at the ST newsgroup. The other is the one I wrote back in March and is in the livecode-sublimetext repo. The one for Atom is also one that I wrote after I

Re: regex deconstructor

I did take a look at Atom and is also has some duplicates in the increase/decrease sections. It seems to work to out dent the line. For example, if you type “switch” the next line will start indented one level. When you type “case” it moves that line out and the next one is indented. This

Re: regex deconstructor

On first look, I see the same terms in the increase and decrease RegEx. I’ll need to figure out where the Atom data is and look at it in my seat. Do you have any specific recipes that are not acting correctly that I could walk through? On Thu, Jan 25, 2018 at 6:44 PM Mike Kerner via use-livecode

Re: regex deconstructor

It's similar. It takes a bit of massaging to get one into the other, especially once you get into the more advanced regex because there are features that one supports and the other doesn't. ST's regex engine is customized more than Atom's is. Here's the proposed not-quite-final indent rules

Re: regex deconstructor

Is that the same stuff that Atom uses? I’m not that good at writing RegEx from scratch, but wouldn’t mind taking a look. I don’t have ST, so I wouldn’t be able to test there. On Thu, Jan 25, 2018 at 1:04 PM Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > Unfortunately I'm

Re: regex deconstructor

Unfortunately I'm trying to fix the indenting in ST, so I'm stuck with it. Then I asked for help. The help is definitely better than what I came up with, but I have a couple of things I want to fix. The help disappeared, and I'm having a hell of a time reading this because it uses some advanced

Re: regex deconstructor

That's because there are several flavors of RegEx. Nice huh? RegEx is in my opinion the top choice for inducing insanity. I have a utility where you type in what you start with and what you want to end up with and it tries to figure out the regex for it. It's less than perfect as you can

Re: regex deconstructor

It's amazing how much work it takes to learn enough about this topic to do something moderately dangerous. This is my nth attempt to fix the indenting of LC in Atom and ST. This time I got some help from King Keith at ST, but trying to make heads or tails of what he offered (that works better

Re: regex deconstructor

@Lagi, yes, exactly. I found another one last night: regex101.com/ That one is interesting because it seems to support some expressions that the others do not. On Wed, Jan 24, 2018 at 8:36 AM, Lagi Pittas via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Mike (Shirley? ;-)) > > I

Re: regex deconstructor

Hi Mike (Shirley? ;-)) I bought this years ago - it's brilliant and it builds a tree of what everything does https://www.regexbuddy.com/benefits.html click on the iamge on the right Kindest Regards Lagi On 24 January 2018 at 02:00, Mike Kerner via use-livecode < use-livecode@lists.runrev.com>

Re: regex deconstructor

Sorry Mike. To reply to the list I use the Nabble site http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html It displays the wrong author for the posts (the most recent author who posted to the list for all the posts) so I just looked at who Nabble indicated the author

Re: regex deconstructor

well that might do it. And don't call me "Richard". On Tue, Jan 23, 2018 at 6:12 PM, Martin Koob via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Richard. > > I found this site https://regexr.com when I was trying to make a regex > expression that I could use to find GLX calls I

Re: regex deconstructor

You could cut it down a bit more... [GgSs] would replace 2 lines Could also probably use... r(ef|op) (?!glx[Aa]pp_[GgSs]et[Pp]r(ef|op)\(.*\)) On Tue, Jan 23, 2018 at 5:13 PM Martin Koob via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Richard. > > I found this site