Branch: refs/heads/master
Author: Javier Mora <cousteaulecommandant(a)gmail.com>
Committer: Javier Mora <cousteaulecommandant(a)gmail.com>
Date: Fri, 01 Nov 2024 23:44:10 UTC
Commit: e1a5e9848ba014cc411f6aeb2f790e036613d2c6
https://github.com/geany/geany/commit/e1a5e9848ba014cc411f6aeb2f790e036613d…
Log Message:
-----------
Fix README: highlight code as such using ``code``
Code snippets in README(.rst) should use ``double backticks``
rather than `single backticks`.
Otherwise it's hard to tell apart code from text in the README render
(especially when it says "`code 1` or `code 2`").
Modified Paths:
--------------
README
Modified: README
14 lines changed, 7 insertions(+), 7 deletions(-)
===================================================================
@@ -91,26 +91,26 @@ N.B. Meson support is still incomplete and a work-in-progress.
Meson requires to chose a separate build directory. Either create
one, or let meson do it:
-`meson build` or `mkdir build; cd build; meson ..`
+``meson build`` or ``mkdir build; cd build; meson ..``
Either command will configure the build system. The system is probed
in many ways and system-dependant build files are created. This includes
location of dependencies and compiler and linker flags required for them.
-To build Geany, follow with a `meson compile -C build`
+To build Geany, follow with a ``meson compile -C build``
-To install Geany, follow the build with a `sudo meson install -C build`.
+To install Geany, follow the build with a ``sudo meson install -C build``.
-By default, meson will install Geany to `/usr/local`. A different
+By default, meson will install Geany to ``/usr/local``. A different
prefix can be selected at the initial command or via reconfiguration:
-`meson --prefix /opt build` or `meson configure --prefix /opt build`
+``meson --prefix /opt build`` or ``meson configure --prefix /opt build``
Geany has some selectable features that may reduce the required
build and runtime dependencies. See meson_optionts.txt for a full list.
-To turn a feature off, use `-D<feature>=false` when configuring the build,
-for example: `meson configure -Dvte=false build`
+To turn a feature off, use ``-D<feature>=false`` when configuring the build,
+for example: ``meson configure -Dvte=false build``
Using Autotools
+++++++++++++++
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: https://github.com/geany/infrastructure).
Branch: refs/heads/master
Author: Jiřà Techet <techet(a)gmail.com>
Committer: GitHub <noreply(a)github.com>
Date: Mon, 04 Nov 2024 15:13:53 UTC
Commit: c5d68efa7edb4c37af00283e0c684aa7365a61d0
https://github.com/geany/geany/commit/c5d68efa7edb4c37af00283e0c684aa7365a6…
Log Message:
-----------
Merge pull request #4029 from cousteaulecommandant/fix-readme-rst
Fix README: highlight code as such using ``code``
Modified Paths:
--------------
README
Modified: README
14 lines changed, 7 insertions(+), 7 deletions(-)
===================================================================
@@ -91,26 +91,26 @@ N.B. Meson support is still incomplete and a work-in-progress.
Meson requires to chose a separate build directory. Either create
one, or let meson do it:
-`meson build` or `mkdir build; cd build; meson ..`
+``meson build`` or ``mkdir build; cd build; meson ..``
Either command will configure the build system. The system is probed
in many ways and system-dependant build files are created. This includes
location of dependencies and compiler and linker flags required for them.
-To build Geany, follow with a `meson compile -C build`
+To build Geany, follow with a ``meson compile -C build``
-To install Geany, follow the build with a `sudo meson install -C build`.
+To install Geany, follow the build with a ``sudo meson install -C build``.
-By default, meson will install Geany to `/usr/local`. A different
+By default, meson will install Geany to ``/usr/local``. A different
prefix can be selected at the initial command or via reconfiguration:
-`meson --prefix /opt build` or `meson configure --prefix /opt build`
+``meson --prefix /opt build`` or ``meson configure --prefix /opt build``
Geany has some selectable features that may reduce the required
build and runtime dependencies. See meson_optionts.txt for a full list.
-To turn a feature off, use `-D<feature>=false` when configuring the build,
-for example: `meson configure -Dvte=false build`
+To turn a feature off, use ``-D<feature>=false`` when configuring the build,
+for example: ``meson configure -Dvte=false build``
Using Autotools
+++++++++++++++
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: https://github.com/geany/infrastructure).
Branch: refs/heads/master
Author: Jiřà Techet <techet(a)gmail.com>
Committer: Jiřà Techet <techet(a)gmail.com>
Date: Sun, 03 Nov 2024 16:54:00 UTC
Commit: fd70da00d9ae846b63d533f6d7d63dc3d96e0a5c
https://github.com/geany/geany/commit/fd70da00d9ae846b63d533f6d7d63dc3d96e0…
Log Message:
-----------
Fix current_scope value passed to tm_workspace_is_autocomplete_tag()
When the parser doesn't provide scope, symbols_get_current_function()
returns "unknown" in its tagname argument. We have to set it to NULL
in this case so tm_workspace_is_autocomplete_tag() works correctly.
Modified Paths:
--------------
src/symbols.c
Modified: src/symbols.c
3 lines changed, 2 insertions(+), 1 deletions(-)
===================================================================
@@ -1599,7 +1599,8 @@ static GPtrArray *filter_tags(GPtrArray *tags, TMTag *current_tag, gboolean defi
GPtrArray *filtered_tags = g_ptr_array_new();
guint i;
- symbols_get_current_function(doc, ¤t_scope);
+ if (symbols_get_current_function(doc, ¤t_scope) == -1)
+ current_scope = NULL; /* current_scope == "unknown" when not found */
foreach_ptr_array(tmtag, i, tags)
{
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: https://github.com/geany/infrastructure).
Branch: refs/heads/master
Author: Enrico Tröger <enrico.troeger(a)uvena.de>
Committer: Enrico Tröger <enrico.troeger(a)uvena.de>
Date: Sun, 03 Nov 2024 13:38:53 UTC
Commit: 0ba557bc401125a211bbd5d30703fd85c86c055c
https://github.com/geany/www.geany.org/commit/0ba557bc401125a211bbd5d30703f…
Log Message:
-----------
Add 2024 Geany e.V. General Assembly meeting
Modified Paths:
--------------
page_content/association.md
Modified: page_content/association.md
16 lines changed, 13 insertions(+), 3 deletions(-)
===================================================================
@@ -15,18 +15,28 @@ There are no plans to direct the development of Geany itself from the associatio
#### Upcoming meetings
-##### Geany e.V. General Assembly 2023
-Date: 26th November 2023 - 15:00 CET
-Location: Jitsi (ask the association board for details)
+##### Geany e.V. General Assembly 2024
+Date: 30th November 2024 - 15:00 CET
+Location: Hoepnerstraße, Leipzig, Germany and Jitsi (ask the association board for details)
Audience: association members
Agenda:
- General report
- Financial report
+- Election of the association board
#### Past meetings
+##### Geany e.V. General Assembly 2023
+Date: 26th November 2023 - 15:00 CET
+Location: Jitsi (ask the association board for details)
+Audience: association members
+Agenda:
+
+- General report
+- Financial report
+
##### Geany e.V. General Assembly 2022
Date: 19th November 2022 - 15:00 CET
Location: Hoepnerstraße, Leipzig, Germany
--------------
This E-Mail was brought to you by github_commit_mail.py (Source: https://github.com/geany/infrastructure).