I'm using the 1.38.0-3 build and it appears, that after I've typed something inside editor widget, the mousewheel (classic 3 buttons wheel mouse via USB) is not working. It recovers, when switching windows and coming back to Geany.
--
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-osx/issues/34
On Linux, after copying a rectangular selection into the clipboard, it is possible to paste it into existing text while maintaining the rectangular structure (and not insert newlines where none existed before). On a Mac, this appears to be broken.
Geany 1.37
Using GTK+ v3.24.20 and GLib v2.66.0 runtime libraries
System Version: macOS 10.15.7 (19H15)
Kernel Version: Darwin 19.6.0
Example. I want to move the two lines of "hub." into the links above:
But when I do a rectangular select (using the mouse since the keys don't work.......that's a different issue), the result of pasting does not at all look like it would on Linux. It looks like this:
When it should look like 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/2685
I cannot see emoji characters in the editor. The emoji keyboard shortcut (Ctrl + Cmd + Spacebar) also does not work within this app. They can be pasted, and successfully copied back out, but they are invisible.
On macOS Big Sur 11.5.1, Intel chip.
--
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-osx/issues/27
Hi.
OS: Windows 7 64bits
Geany version: 1.26
In "Edit>Preferences>Files>Default encoding" I selected IBM850 as default encoding in all options, new files and open files, but all files are opened with 1252 encoding. With new files there is no problem.
Thank you.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/900
... that way new users don't have to be told to uncomment the heading as well as the setting they need, just the setting line.
And document this commenting behaviour in the manual.
--
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/2689
Any change this plugin will be upgraded to Lua 5.4.3 any time soon?
--
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/1133
If the long line marker is disabled in *Preferences* → *Editor* → *Display*, the keybinding for *Format* → *Join lines* doesn’t work.
Unlike *Reflow lines/block*, the *Join lines* operation does not need to know anything about long lines, so shouldn’t require the marker.
--
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/1591
### Suggestion
The debug information at `Help > Debug Messages` should report the Scintilla version Geany was linked against.
Lexilla should have its own entry as well, given its [divergent release cadence].
### Example
### Motivation
Issues could be more easily traced to a precise library version.
Users could locate this otherwise obscure information without leaving the app.
### Implementation
The main problem is how to expose the libraries' versions at compile time. I've had some luck with the following approach:
1. write a script to parse the content of `scintilla[/lexilla]/version.txt` and return the appropriate version (based on input) in semver format
2. call the script in `configure.ac` via the [`m4_esyscmd`] macro, assigning the script output to preprocessor definitions for each version
3. use the definitions in `src/libmain.c` to extend Geany's debug output
### Questions
My concern is that step _2_ may be disruptive to the build workflow. Some potential issues that come to mind:
- builds targeting Windows would need access to a POSIX shell (if they don't already . . . I've never tried to package Geany 😊)
- calling `m4_esyscmd` on a failing script does not crash `autoreconf` [^1]. But aborting in that case might be better than generating an incomplete `config.h` header
This thread is here to gather input, especially with regard to the acceptability of using `m4_esyscmd` in the build.
A search for similar topics found only an open RFC about [documenting lexer properties].
[^1]: "The error output of _shell-command_ is not a part of the expansion: it will appear along with the error output of m4." <https://www.gnu.org/software/m4/manual/html_node/Esyscmd.html#index-esyscmd>
[divergent release cadence]: https://groups.google.com/g/scintilla-interest/c/1VWWqoJ_kmA/m/mfqpF1tjAgAJ
[`m4_esyscmd`]: https://www.gnu.org/software/m4/manual/html_node/Esyscmd.html#index-esyscmd
[documenting lexer properties]: https://github.com/geany/geany/issues/2517
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3108
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3108(a)github.com>
Please consider adding an <b>Unflow paragraph</b> command - the opposite of
<b>Reflow Lines/Block</b> The use case for this is to make it easy to type in
<b>Geany</b> and then paste the results into the Gmail or Github editor
Incidentally, <b>Reflow Lines/Block</b> indicates that the conception of a
block of line is already endogenous to <b>Geany</b> and thus I believe that the
concept of extending the highlighting of lines to the line numbers columns
should be considered an extension of an existing capability
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/802
Hi,
I changed the shortcut of join lines to `Ctrl + J`, then tried to join lines.
Seems following behavior exists:
- It will join all following lines, till a line start with blank char (while space / new line).
- If the current line start with blank char, it won't join.
Is it possible to customize to following behavior:
- Only join current line and the next line, despite the content of this or next line.
This seems to be the behavior of vim with `Shift` + `J`.
--
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/2031