Hey, I checked that one. This seems not be true for my 0.20 install. I had stuff like this ;-) in doc strings and comments.
Genay made no difference between doc strings, comments and regular code. As long as it was there, the auto-close detected the ) in ;-) and left it open. Greetings Philipp On Sat, Jan 29, 2011 at 8:08 PM, Lex Trotman <[email protected]> wrote: > On 30 January 2011 05:53, Philipp Kalder <[email protected]> wrote: > > Hello Lex, > > I very much appreciate your willingness to help. > > I have to apologize for being so blind. I completely ignored what you had > > to remind me of: > >> > >> You are aware that closing brackets ([{< only closes unmatched open > >> brackets so if a matching close is found none will be added? > >> > > > > The main file I was concerned about, is a 1400 lines script that's part > of a > > set > > of files working together. Their functions being accessed through calls > to a > > WSGI Server. > > It's live, in a productive environment serving more than 300.000 calls a > > day. > > If a function in it would be faulty, than the whole thing wouldn't work. > > That's what > > I've seen happening and that's what I assumed. Even though not all > functions > > are used > > (some are for debugging purposes). I was wrong. > > Here is what I did: > > I was thinking that just part of the script in question wouldn't help. > > If all brackets would be consistent, then it would just work. I tried > taking > > two > > functions out of it, pasting them into a new file and saved it. Testing > it, > > as expected, showed > > auto-closing working properly. And then it struck me, I tried it in the > > first line of the > > original file, in the middle of it and on the last line. On the last line > > the parenthesis was auto-closed. > > So all I have to do now is find the faulty function/line of code in 1400 > > lines ;-) > > One question though is left: Would an opening bracket in some comment or > > commented out/disabled function cause this for the rest of the file as > well? > > The brackets must have the same styling so as brackets in comments > have different styling they don't count > > Cheers > Lex > > > So far I have narrowed it down to a function. Trying 'base64.b64decode(' > > prior to the > > def statement does not close it, trying the same right under the last > line > > of this function > > prior to the next def statement closes the parenthesis. I'm not sure what > > this tells me, but . . . > > I guess that's my puzzle to solve. > > Thank you very much for exchanging views with me. > > Regards, > > Philipp > > > > > >> > >> Really need minimal example of non-working file. > >> > >> Cheers > >> Lex > >> > >> > >> > But that's something I get along with. > >> > That and the copy paste behavior is just something I'll get used to. > The > >> > copy/paste is more of an inconvenience > >> > than the issue with parenthesis. > >> > Regards, > >> > Philipp > >> > On Thu, Jan 27, 2011 at 12:08 AM, Lex Trotman <[email protected]> > wrote: > >> >> > >> >> On 24 January 2011 00:23, Philipp Kalder <[email protected]> > >> >> wrote: > >> >> > Hello, > >> >> > sorry for the delay. > >> >> > The indentation is not a problem anymore. As I stated in one of my > >> >> > previous > >> >> > emails, there > >> >> > seems to have been a problem with 'detecting from file'. Every > >> >> > indentation I > >> >> > do now works > >> >> > as I want it to. > >> >> > Only thing that remains is the behavior for parenthesis. But I > guess > >> >> > I'll > >> >> > just cope with it. > >> >> > I can post the filetypes.python, as well as the filetypes.common if > >> >> > you > >> >> > still like to see them. > >> >> > As for the code I'm sorry to say that can't post even parts of it. > I > >> >> > use > >> >> > Geany at work and the > >> >> > code is for our internal systems. > >> >> > Thanks so far > >> >> > Phil > >> >> > > >> >> > >> >> Hi Phil, > >> >> > >> >> Sorry your email got lost in the inbox. I don't quite understand > what > >> >> is happening wrong with the brackets, can you describe it again. > >> >> > >> >> Cheers > >> >> Lex > >> >> _______________________________________________ > >> >> Geany mailing list > >> >> [email protected] > >> >> http://lists.uvena.de/cgi-bin/mailman/listinfo/geany > >> > > >> > > >> > _______________________________________________ > >> > Geany mailing list > >> > [email protected] > >> > http://lists.uvena.de/cgi-bin/mailman/listinfo/geany > >> > > >> > > >> _______________________________________________ > >> Geany mailing list > >> [email protected] > >> http://lists.uvena.de/cgi-bin/mailman/listinfo/geany > > > > > > _______________________________________________ > > Geany mailing list > > [email protected] > > http://lists.uvena.de/cgi-bin/mailman/listinfo/geany > > > > > _______________________________________________ > Geany mailing list > [email protected] > http://lists.uvena.de/cgi-bin/mailman/listinfo/geany >
_______________________________________________ Geany mailing list [email protected] http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
