Hi!
I just want to let you know. I just tried Geany, and I'm not able to scroll the text with touchscreen. Otherwise, looks interesting, but it's a critical problem for me, so I have to stick with something else for now.
Geany v1.33 32-bit on Windows 10 1803 64-bit
--
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/1977
Geany is my all-time favourite IDE for C, C++, Python, HTML, JavaScript and just about anything else that requires a high-powered text-editor. Thanks!
What would make Geany even better is if part of the main toolbar (maybecould be used to add additional buttons for build commands that aren't just 'Build' or 'Compile'. Just like the build commands are customisable, I'd like to add toolbar buttons for custom per-project build commands that I use often. Maybe make it a plug-in!
Thanks for a great IDE! 😄
--
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/1550
>From my early tests it works fine loading and saving embedded NUL bytes, but I expect many features not to work properly (although e.g. regex search seems happy, yet displaying results not so much). It however should help getting to a point where these could be handled properly, and is handy also for slightly broken files and alike.
Anyway for now such files are loaded read-only and display a warning to the user to avoid most problems.
Related to (and should fix for the most part) #618 and #1708 (and possibly others).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1709
-- Commit Summary --
* Avoid weird length value
* Add sci_set_text_with_length()
* Don't cut the loaded data at the first NUL when passing it to Scintilla
* Don't cut UTF-8 documents at the first NUL byte when saving them
* encodings: Accept NULs when validating UTF-8
* Properly load files with embedded NULs
* Show an infobar for files with embedded NULs
-- File Changes --
M src/document.c (58)
M src/documentprivate.h (1)
M src/encodings.c (118)
M src/encodingsprivate.h (2)
M src/sciwrappers.c (10)
M src/sciwrappers.h (2)
-- Patch Links --
https://github.com/geany/geany/pull/1709.patchhttps://github.com/geany/geany/pull/1709.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/1709
Support here is *optional*, as in it does *not* require even the GIR M4 macros to be available -- but then the generated build system can't generate GIR. This avoids a hard dependency on GIR for the cost of a configure-time conditional with basic fallback definitions.
As stated in the first commit, it's mostly ripped off Peasy, maybe there are additional change required, but it seems to mostly work. However, I see a lot of scary warnings like these:
```
…/doc/geany-sciwrappers-gtkdoc-tmp.h:25: syntax error, unexpected '*', expecting ')' or ',' in 'void scintilla_object__GI__MARK_set_text (ScintillaObject *sci, const gchar *text);' at '*'
…/doc/geany-sciwrappers-gtkdoc-tmp.h:25: syntax error, unexpected ')', expecting ',' or ';' in 'void scintilla_object__GI__MARK_set_text (ScintillaObject *sci, const gchar *text);' at ')'
…/doc/geany-sciwrappers-gtkdoc-tmp.h:43: syntax error, unexpected '*', expecting ')' or ',' in 'void scintilla_object__GI__MARK_start_undo_action (ScintillaObject *sci);' at '*'
…/doc/geany-sciwrappers-gtkdoc-tmp.h:64: syntax error, unexpected '*', expecting ')' or ',' in 'void scintilla_object__GI__MARK_end_undo_action (ScintillaObject *sci);' at '*'
…/doc/geany-sciwrappers-gtkdoc-tmp.h:84: syntax error, unexpected '*', expecting ')' or ',' in 'void scintilla_object__GI__MARK_set_marker_at_line (ScintillaObject *sci, gint line_number, gint marker);' at '*'
```
@codebrainz @kugel-
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1112
-- Commit Summary --
* Add support for building GIR
* Force enabling GObject-Introspection for distcheck
-- File Changes --
M Makefile.am (2)
M configure.ac (12)
M doc/Makefile.am (69)
-- Patch Links --
https://github.com/geany/geany/pull/1112.patchhttps://github.com/geany/geany/pull/1112.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/1112
It would be nice to have and option in Preferences > Interface to support headerbar so that we:
a) gain some screen real state
b) make Geany look like a modern GTK3 app
It could be a simpler start where the window decoration top bar goes away and the menu and top icon bar (which are on the same 'line' in my geany configuration) move to the top border.
Or ideally a more thorough GUI refresh, maybe moving the Menu to a hamburger (but keeping the shortcuts to no change in day-to-day use to hardcore users), keeping the single-line icon bar, maybe coming up with a symbolic icon set (like GIMP did, for instance).
Sharing some thoughts. I use geany daily and it is starting to look a bit dated - it would be nice to have a visual refresh. The GTK3 port done a few years ago would probably enable this.
--
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/2061
Hello Geany developers,
I have some questions about configuring auto-completion, may I ask if you could help?
1. Is there a setting to always show suggestion list (the popup menu)?
In docs, the menu does not pop up, unless I press for `Ctrl-space`. However I write docs a lot, so it would help me if the menu is shown. I tried to find, but couldn't find a setting.
2. The initial list does not always offer all phrases. Is there a setting to change that?
For example, I often have to press `Ctrl-space` _twice_, in order to show all phrases.
Thank you very much,
--
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/2071
**Problem**
Whenever I create a new project, the `Set Build Commands` dialogue is populated with the standard Geany build commands. For example `Compile: g++ -Wall -c "%f"`.
All my projects use the same build tools, which are more elaborate than the standard ones. I use explicit `make` commands for compiling single files as well as building the entire project. Configuring the dialogue in exactly the same way for each new project is time-consuming.
**Geany manual**
The [Build menu configuration]( https://www.geany.org/manual/current/index.html#id154) section in the manual seems to suggest that by placing a `[build-menu]` section in` filetypes.cpp`, then custom entries for the `Set Build Commands` dialogue can be configured to be the same for all new projects. However, this does not happen.
**My Current Workaround**
I have made a template for the `[build-menu]` section. When I create a new project, I copy the` [build-menu]` section to the `newproject.geany` file.
**Request**
It would be convenient if there was a way to use a template to populate the build commands dialogue at the point of project creation.
**My System**
```
~$ geany -V
geany 1.29 (built on 2016-11-16 with GTK 2.24.31, GLib 2.50.2)
~$ uname -a
Linux debian-deskside 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u5 (2018-09-30) x86_64 GNU/
```
--
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/1975
In Elm-community it is the norm to use a command `elm-format` to automatically format the file according to formatting standards.
While I can add this command to Build Commands and then run it, after that I need to either
A) press Ctrl-R and answer the prompt to reload the file
B) wait until Geany detects that file has changed and answer the prompt to reload the file
To use `elm-format` properly there should be an option for Geany to reload the file after running the build command without any prompts.
--
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/1983