Re: [Github-comments] [geany] Parsing long files (#791)

2015-12-12 Thread Jiří Techet
@philiprbrenan Great to hear! Even though the original patch wasn't quite right as Colomban noticed, the updated version should fix the performance issue too. --- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/791#issuecomment-164158340

Re: [Github-comments] [geany] Limiting the columns searched (#806)

2015-12-12 Thread elextr
@b4n, is that bytes or code points? (but certainly *NOT* glyphs, ie display columns) --- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/806#issuecomment-164211853

Re: [Github-comments] [geany] Bolding the line containing a find result. (#805)

2015-12-12 Thread Matthew Brush
+1 --- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/805#issuecomment-164212117

[Github-comments] [geany] Limiting the columns searched (#806)

2015-12-12 Thread philip r brenan
Please consider making it possible to add a pseudo line, as on line 1536 in the screen shot, on which I could use a selection to indicate the only columns that I want find to search Thanks!

Re: [Github-comments] [geany] Bolding the line containing a find result. (#805)

2015-12-12 Thread elextr
Agree that the default selection highlighting can be a bit hard to see sometimes, but you can change it to be more visible in the colour scheme (or `filetypes.common` for the default). At the moment Scintilla only allows one style for the number margin, so you would have to request the feature

Re: [Github-comments] [geany] Limiting the columns searched (#806)

2015-12-12 Thread elextr
The concept of a `column` is too specific to a particular filetype, or file, or even section of a file (comma separated, whitespace separated, code point ranges, glyph ranges) for this to be provided in core. But somebody could implement it as a `column operations` plugin perhaps. --- Reply to

Re: [Github-comments] [geany] Limiting the columns searched (#806)

2015-12-12 Thread Colomban Wendling
Not mentioning this can be achieved with some regex search, like e.g. `^.{150}.{0,3}yN` (searches `yN` in columns 151-156) --- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/806#issuecomment-164208518

[Github-comments] [geany] Bolding the line containing a find result. (#805)

2015-12-12 Thread philip r brenan
Please consider bolding or otherwise highlighting the number of the line containing the result of pushing the Find Next button as it is sometimes quite difficult to locate the result of such a push

Re: [Github-comments] [geany] Selecting whole lines (#800)

2015-12-12 Thread Colomban Wendling
If all you're interested about is whether the selection consists solely of whole line, maybe you'd be interested to see that the statusbar indicator for the selection indicates something different when only whole lines are selected: it displays the number of selected lines, with a `L` suffix

Re: [Github-comments] [geany-plugins] Autoclose puts )) when I type ( (#319)

2015-12-12 Thread Ricardo Pérez
@codebrainz no, that's the first thing I checked. The builtin autoclosing is off for all type of brackets (, {, [, ' and ". --- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/319#issuecomment-164202981

Re: [Github-comments] [geany] Selection without losing the existing selection (#804)

2015-12-12 Thread elextr
The selections are managed by Scintilla, it would need to be requested there first. Since nested selections is not a common concept you would need to explain (to Scintilla) how it should work. --- Reply to this email directly or view it on GitHub: