I opt for using black theme while using geany. But it is not a good idea to use black theme to print. I wonder is it possible to create a separate and independent theme for print? say,
view : white on black
print: black on white
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3083
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3083(a)github.com>
If a variable name ends with "type", the symbol parser recognizes a symbol which does not exist. As an example, see the following code below:
> procedure plot_labels(iy,iy2: stipint; labtype: stipint);
const
c_marker_type=1;
var
locdbg: boolean;
{actual code}
end;
Which creates two functions: plot_labels (correct) and 1 (this is incorrect). See screenshot below:
--
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/1409
The class / method hierarchy in Ruby files is parsed incorrectly if assigning the result of an `if` / `else` block:
After removing the assignment, all methods are grouped under the enclosing class, as expected:
Tested with the very latest state of the `master` branch (as of 2018-01-18), Arch Linux up to date. Might be related to #587.
--
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/1744
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3081
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3081(a)github.com>
This prevents a potential crash if `sidebar_update_tag_list()` is called with update=true and document=NULL.
Found this by accident while testing the tag tree filter PR.
Currently, this is no problem as `sidebar_update_tag_list()` is not called with update=true and document=NULL but just in case it might happen.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3080
-- Commit Summary --
* Update doc->priv->tag_tree_dirty only if doc is set
-- File Changes --
M src/sidebar.c (2)
-- Patch Links --
https://github.com/geany/geany/pull/3080.patchhttps://github.com/geany/geany/pull/3080.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3080
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3080(a)github.com>
Maybe have a unit test for this?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/349#issuecomment-1003760117
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/349/1003760117(a)github.com>
Closed #349.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/349#event-5832799965
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issue/349/issue_event/5832799965(a)github.com>
Good, one more mysterious bug away.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/349#issuecomment-1003737635
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/349/1003737635(a)github.com>
It does!
I guess we can close this now.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/349#issuecomment-1003735268
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/349/1003735268(a)github.com>
Is it possible to implement persistent blocks in Geany? Got used to them since Turbo/Borland Pascal and Delphi. :)
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3079
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3079(a)github.com>