Just like many coders, I work with different languages at the same time. For example, there might be 2 opened files at the same time:
```
translations_en.php
translations_XX.php
```
Obviously, they will contain text in different languages. So if my spellcheck is set to EN, I will see all the words marked as mistakes right after switching to translations_XX.php, and vice versa. What's more, that file translations_XX.php usually contains extra text in English (especially true for comments, definitions, variable names, etc._, so even if I manually set spellcheck to XX language every time after switching to this file, many parts of text will be marked as incorrect anyways.
This could be easily solved by having an option to use 2 languages at the same time. I'm not sure how easy/difficult it is to implement, but such option exists in Claws Mail and it's amazing - if you set 2nd dictionary, spellcheck will only mark words as incorrect if they dion't math both of dictionaries.
Hope I explained it clearly enough...
--
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-plugins/issues/876
Apart from fixing a load of deprecation warnings on gtk3 this also fixes two gtk3 related problems in the treebrowser plugin:
- lines in the Treeview had a red color - now they are black like under gtk2
- the text field turned red if the path entered wasn't a valid directory - this did not work under gtk3 before but now it works
The gtk2 behavior is unchanged and there are also no functional changes.
If this get's merged PR #279 would become needless and could be closed un-merged.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/864
-- Commit Summary --
* treebrowser: fixed deprecated gtk calls for gtk3
-- File Changes --
M build/treebrowser.m4 (2)
M treebrowser/src/Makefile.am (6)
M treebrowser/src/treebrowser.c (237)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/864.patchhttps://github.com/geany/geany-plugins/pull/864.diff
--
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-plugins/pull/864
@LarsGit223 done, I also checked the "Allow edits by maintainers" which I think does something like allowing you to push to this PR or something like that.
--
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-plugins/pull/95#issuecomment-507390964
> Confusingly, doxygen seems to pickup the header's signature even though the doc comment is in the .c file.
I guess it makes sense since what's in the header is what the user can actually see/use.
--
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/commit/6e5ca69e2e9ddbfc2cc44527a1aa5fca8db09…
hm something slipped through. IIRC I changed it from gint to gboolean sometime during review process, and it seems I forgot the header. Confusingly, doxygen seems to pickup the header's signature even though the doc comment is in the .c file.
The header should probably be fixed to match the source file, since IIUC gboolean and gint are ABI-compatible?
--
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/commit/6e5ca69e2e9ddbfc2cc44527a1aa5fca8db09…