Avoid creating documents immediately because there could be a modal dialog open. Modal code often assumes the current doc hasn't changed and calls `document_get_current` at different times.
Fixes #2599.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3395
-- Commit Summary --
* Open CLI docs only once main window is active
-- File Changes --
M src/socket.c (21)
-- Patch Links --
https://github.com/geany/geany/pull/3395.patchhttps://github.com/geany/geany/pull/3395.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3395
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3395(a)github.com>
Happens when Save As is used on the only empty new document, and a command line file replaces that document while the dialog is still open.
_Originally posted by @ntrel in https://github.com/geany/geany/issues/3388#issuecomment-1420621069_
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3414
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3414(a)github.com>
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
Add menu item.
Don't require line breaking or line marker to be set.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3402
-- Commit Summary --
* Add Format->Join Lines menu item
* Don't require reflow column width for Join Lines
-- File Changes --
M data/geany.glade (9)
M src/callbacks.c (6)
M src/keybindings.c (12)
-- Patch Links --
https://github.com/geany/geany/pull/3402.patchhttps://github.com/geany/geany/pull/3402.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3402
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3402(a)github.com>
### 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>
Hi i try to sign in mailing list but never retun if i am signed or not , and i cant send mail for required support , i would want active in geany 1.38 in linux mint , the tertiary higlights word in perl i tryed to modify filetypes.perl and create a section [keyword] and insert primary secondary and tertiary , and after i modify a file of my colorscheme himbeere.conf i insert a exadecimal value for ne color Gold and i tryed to play with this part of code keyword=berry;;true
keyword_1=keyword
keyword_2=cyan;;true
keyword_3=bluegrey
keyword_4=keyword_3 but nothing if i change keywor_1=keybord for example change in keybord_1=gold;;true it change color from berryto gold , whats wrong anyone can help me ? thanks
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3398
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3398(a)github.com>
- Ubuntu 22.04.2 LTS
- geany 1.38-1
When either typing or moving the cursor column location, the column indicator value change causes everything to the right of "col" to shift left and right. With a fresh install of geany from the ubuntu repo in a vm and no configuration of geany, the shift only occurs when the col count goes from 9 to 10. On my configured installation of geany, it shifts left and right on certain col values between 0 and 100. I compiled git source and got the same results as my normal install. I believe the git install is using my custom config.
I would suggest that this should not happen at all, not even when going from 9 to 10.
[geany-bug-statusbar-col.webm](https://user-images.githubusercontent.com/117…
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3409
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3409(a)github.com>
The common name for the macro to merely mark strings as translatable without actually making any call is `N_()`, not `_()`.
Also, streamline the way i18n is conditionally enabled, similar to what is done in src/support.h.
Follow-up to 3f8733f083e72be58e00ab2dde1e2584fe276cc5 and 201ac64545ea0d2857f55dcd7440b07a1672bbcb.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3408
-- Commit Summary --
* tagmanager: Use more common i18n macros
-- File Changes --
M src/tagmanager/tm_parser.c (500)
-- Patch Links --
https://github.com/geany/geany/pull/3408.patchhttps://github.com/geany/geany/pull/3408.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3408
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3408(a)github.com>