Re: [Github-comments] [geany/geany] Save main and project configuration whenever documents are opened/closed (#2114)

2019-08-04 Thread Enrico Tröger
@elextr what do you mean exactly? Should we add a listener on `project-save` or should we extend the documentation of `project-save`? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/2114#i

Re: [Github-comments] [geany/geany] Plugin-API: extended project API (#2234)

2019-08-04 Thread LarsGit223
@codebrainz, @elextr: ok, reverted the change. codebrainz is of course right regarding the independence that usage of accessor functions is giving us. But regarding the names of the functions we should make up our mind now / within this PR. -- You are receiving this because you are subscribed

Re: [Github-comments] [geany/geany] Plugin-API: extended project API (#2234)

2019-08-04 Thread Matthew Brush
IMO, a better name for the functions would be nice (since changing later breaks plugins), but at the very least the doc-comments should be more detailed to better explain what the functions do without referring to other stuff that isn't linkable inside the plugin API docs. -- You are receiving

Re: [Github-comments] [geany/geany] Save main and project configuration whenever documents are opened/closed (#2114)

2019-08-04 Thread elextr
Documentation I meant. The description of `plugin_save` on [this](https://www.geany.org/manual/reference/pluginsignals_8c.html#ac093c4c2a6ef1ed7c35e5736a27d7f27) page that lists when it happens. -- You are receiving this because you are subscribed to this thread. Reply to this email directly o

[Github-comments] [geany/geany] "regular expression is too large" error is not visible (#2244)

2019-08-04 Thread Chris Graham
When a "regular expression is too large" error happens, you may not see the cause of the error, because the explanation shows horizontally after the regular expression, which as we know, is too large. This error message seems to be generated by PCRE. Perhaps if the error message is too large to

Re: [Github-comments] [geany/geany] "regular expression is too large" error is not visible (#2244)

2019-08-04 Thread elextr
regular expression doing what? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2244#issuecomment-518058266

Re: [Github-comments] [geany/geany] "regular expression is too large" error is not visible (#2244)

2019-08-04 Thread Chris Graham
Just a Search->Find operation. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2244#issuecomment-518058371

Re: [Github-comments] [geany/geany] "regular expression is too large" error is not visible (#2244)

2019-08-04 Thread elextr
Ahhh -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2244#issuecomment-518058435

[Github-comments] [geany/geany] Easier project creation (#2245)

2019-08-04 Thread Chris Graham
Hi, I'm coming from TextMate 2 on Mac, and TextMate does a great job with projects - by essentially making it invisible (frictionless). You just open a folder, and that folder automatically becomes a project. Geany could easily do something similar in my opinion. I don't know if the GNOME file p

Re: [Github-comments] [geany/geany] Easier project creation (#2245)

2019-08-04 Thread elextr
There are three or four project plugins available for Geany which implement various versions of the "one directory" paradigm. Perhaps you should check out those. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://gith