The docs state that if you have a visual diff tool installed, like meld, running VC->*->Diff will use that tool. This appears to work for VC->File->Diff, but not for VC->Directory->Diff, which spits out the default diff output.
Thinking that GeanyVC was using `git diff`, I tried overriding the `git diff` with:
git config --global diff.external meld
but this has no effect, since GeanyVC appears to ignore git's `diff.external` setting, preventing the use of a visual diff tool.
--
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/573
Parses [Fountain](https://fountain.io/) screenplay format and adds scene headers to the symbols list.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2952
-- Commit Summary --
* <a href="https://github.com/geany/geany/pull/2952/commits/8a84b3b5bb0abdf2385b160244…">Add Fountain screenplay parser</a>
-- File Changes --
M ctags/Makefile.am (1)
M ctags/main/parsers_p.h (1)
A ctags/parsers/geany_fountain.c (92)
M data/Makefile.am (1)
A data/filedefs/filetypes.fountain (32)
M data/filetype_extensions.conf (1)
M src/filetypes.c (2)
M src/filetypes.h (1)
M src/symbols.c (10)
M src/tagmanager/tm_parser.c (5)
M src/tagmanager/tm_parser.h (1)
M src/tagmanager/tm_parsers.h (3)
-- Patch Links --
https://github.com/geany/geany/pull/2952.patchhttps://github.com/geany/geany/pull/2952.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/pull/2952
These changes do not affect current usage.
* Make StashPref and StashGroup publicly accessible so lookup functions
to make Geany preferences available to plugins can be added later.
* Add comment field to StashPref.
- stash_group_add_comment()
* Add double key type:
- utils_get_setting_double() in utils.c
- stash_group_add_double() in stash.c
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3000
-- Commit Summary --
* Modify/Extend Stash Settings API
-- File Changes --
M doc/stash-example.c (19)
M src/plugindata.h (2)
M src/stash.c (125)
M src/stash.h (47)
M src/utils.c (55)
M src/utils.h (2)
-- Patch Links --
https://github.com/geany/geany/pull/3000.patchhttps://github.com/geany/geany/pull/3000.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/pull/3000
This PR exposes the StashPref struct to the plugin API. They can later by looked up by name with `stash_group_get_pref_by_name()`. The caller needs to have a pointer to the StashGroup that contains the desired pref, so this isn't currently very useful. But it is needed to further extend stash settings without changing the existing API. (Key comments, override settings, config/session split.)
* `union Value` is also made public. I don't know how to code it to keep it in `stash.c`.
* Is there a better name for `stash_group_get_pref_by_name()`?
* Existing code using stash settings should continue to work.
* StashGroup will be exposed in a later PR.
Example use of the new lookup function:
```C++
StashPref *pref = stash_group_get_pref_by_name(group, "price");
msgwin_status_add("%s = %f", pref->key_name, *(gdouble *)pref->setting);
```
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3008
-- Commit Summary --
* Stash Settings: Expose StashPref to plugins, look up by name
-- File Changes --
M src/plugindata.h (2)
M src/stash.c (52)
M src/stash.h (36)
-- Patch Links --
https://github.com/geany/geany/pull/3008.patchhttps://github.com/geany/geany/pull/3008.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/pull/3008
Currently geany updates geany.conf with info about window position and
geometry. These vary across different machines and cause diffs that
are meaningless.
--
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/1392