It's 2023. It should work better in dark mode out-of-the-box, without requiring the user to manually search the Internet, download/edit/copy config files.
1. At least one colour theme for dark mode should be included by default, without requiring the user to visit https://www.geany.org/download/themes/
2. A colour scheme for dark mode for the output panels should be included by default, and either let the user select it in the Preferences or automatically use it in dark mode, not [telling users to write a CSS file for it](https://github.com/geany/geany/issues/2520).
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3407
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3407(a)github.com>
The idea is inspired by #3407 I agree with - some users prefer dark themes and Geany currently doesn't ship with any dark editor theme and cloning and copying themes from geany-themes is an extra step which may discourage less experienced users. One option would be to have one "blessed" dark theme that we'd ship with Geany - I'm just afraid of the amount of discussion it would require to agree on the "right" colors :-) (see #3013, and these were only 4 colors)
So what about taking all the themes from geany-themes and copying them under Geany's `data/colorschemes`? I think the development github repo of geany-themes could stay as it is, we'd just update the themes in Geany once per release similarly to ctags or Scintilla (in fact, I have been doing the very same thing for the macOS release for many years).
The pros I see are:
1. Copying the themes is done once by us and doesn't have to be done N times where N is the number of Geany users
2. Users don't have to discover the geany-themes repo and can try various themes out of the box - especially useful for someone evaluating Geany whether it's a good editor for him/her
3. Theme files are small so no big problem distributing them in the release tarball
4. The extra work needed to copy-over all the themes from geany-themes is small so it's not a big maintenance burden (and probably not a big deal if it gets forgotten for some release)
Are there any cons? What do you think?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4035
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4035(a)github.com>
This patch:
- adds a scripts/update-themes.py script copying themes with compatible licenses (themes with no explicit license are skipped for now)
- copies these themes under data/colorschemes
- adds lgpl-2.0.txt, lgpl-2.1.txt, gpl-3.0.txt to data/colorschemes to cover themes not falling under Geany'sGPL 2.0 or later
Fixes #4035.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4044
-- Commit Summary --
* Add themes from geany-themes
-- File Changes --
M data/Makefile.am (43)
A data/colorschemes/abc-dark.conf (120)
A data/colorschemes/abc-light.conf (120)
A data/colorschemes/bespin.conf (121)
A data/colorschemes/black.conf (125)
A data/colorschemes/cyber-sugar.conf (135)
A data/colorschemes/darcula.conf (149)
A data/colorschemes/dark-colors.conf (136)
A data/colorschemes/dark-fruit-salad.conf (121)
A data/colorschemes/dark.conf (120)
A data/colorschemes/delt-dark.conf (106)
A data/colorschemes/earthsong.conf (120)
A data/colorschemes/epsilon.conf (117)
A data/colorschemes/evg-ega-dark.conf (148)
A data/colorschemes/gedit.conf (120)
A data/colorschemes/github.conf (122)
A data/colorschemes/gpl-3.0.txt (674)
A data/colorschemes/grey8.conf (116)
A data/colorschemes/hacker.conf (116)
A data/colorschemes/himbeere.conf (135)
A data/colorschemes/inkpot.conf (118)
A data/colorschemes/kugel.conf (132)
A data/colorschemes/lgpl-2.0.txt (480)
A data/colorschemes/lgpl-2.1.txt (501)
A data/colorschemes/matcha.conf (130)
A data/colorschemes/mc.conf (117)
A data/colorschemes/metallic-bottle.conf (115)
A data/colorschemes/notepad-plus-plus.conf (122)
A data/colorschemes/oblivion2.conf (120)
A data/colorschemes/one-dark.conf (148)
A data/colorschemes/pygments.conf (131)
A data/colorschemes/retro.conf (115)
A data/colorschemes/sleepy-pastel.conf (102)
A data/colorschemes/slushpoppies.conf (120)
A data/colorschemes/solarized-dark.conf (147)
A data/colorschemes/solarized-light.conf (147)
A data/colorschemes/spyder-dark.conf (118)
A data/colorschemes/steampunk.conf (123)
A data/colorschemes/tango-light.conf (120)
A data/colorschemes/tinge.conf (128)
A data/colorschemes/ubuntu.conf (116)
A data/colorschemes/vibrant-ink.conf (123)
A scripts/update-themes.py (106)
-- Patch Links --
https://github.com/geany/geany/pull/4044.patchhttps://github.com/geany/geany/pull/4044.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4044
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4044(a)github.com>
Hi,
I could not find documentation on how to change the blinking rate of the cursor, in what configuration file would that be or is this something to submit as a feature?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3410
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3410(a)github.com>
Dear Geany-team,
I have **_added functionality_** to `print_external`. More specific, I have included/aligned most of the replacements that are present in the build dialog box:
- replace `%d` with the absolute path
- replace `%e` with the filename (excluding extension)
- replace `%f` with the filename (including extension)
- replace `%p` with the absolute path/filename (including extension)
This would permit to use external print commands like:
`cat "%p" | prt1403 -e -y -u PYNCKELS -j %e -o "%p".pdf -`
which would create an output as shown in the joined file.
During development, I have noticed a file `config~`. I have **_added this name_** to `.gitignore`
I would be much obliged if you could accept this PR.
[hellowrl.f08.pdf](https://github.com/user-attachments/files/18974393/hellow…
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4250
-- Commit Summary --
* Add print_external macros %e %d
* Add config~ to files to ignore
* Add %d %e %p to print_external, align meaning of %f with build
-- File Changes --
M .gitignore (1)
M src/printing.c (25)
-- Patch Links --
https://github.com/geany/geany/pull/4250.patchhttps://github.com/geany/geany/pull/4250.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4250
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4250(a)github.com>
ralf3u created an issue (geany/geany#4251)
When coding in the editor I can press the shortcut `Toggle Sidebar` to let appear the sidebar, so I can see editor&sidebar side by side. The focus is then still in the editor. I can change the size of the width of editor&sidebar by moving the vertical separating line with the mouse. When I press again the shortcut `Toggle Sidebar`, then the sidebar disappears. I like this behavior. But sometimes I would like to toggle between only editor and only sidebar, so I see only one of both, editor or sidebar.
**Remarks**
- The shortcut `Toggle between only editor and only sidebar` should not take care if the message window is enabled or disabled.
- If the shortcut `Toggle between only editor and only sidebar` is pressed, then the shortcut should first verify if one of both (editor or sidebar) is disabled. If this is not possible to code because the editor can't be disabled, then maybe this could be a solution: If the shortcut `Toggle between only editor and only sidebar` is pressed, then the shortcut should first verify if either sidebar is disabled or sidebar has a width of 100%.
- If the shortcut `Toggle between only editor and only sidebar` is pressed, and if there is a toggle, then the focus should also toggle (if it toggles to only editor, the focus or rather the cursor should be in the editor; if it toggles to only sidebar, the focus should be in the content area of the sidebar).
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4251
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4251(a)github.com>
Thanks to Geany-Preview (https://github.com/xiota/geany-preview), one can code within Geany on one side the code in the editor and see in the same window on the other side, in the sidebar, a preview of the code. Geany gives the possibility to switch with a shortcut to the editor and Geany gives the possibility to switch with a shortcut to the sidebar, but with different shortcuts (https://www.geany.org/manual/current/index.html#focus-keybindings). Better would be to use always one shortcut to toggle editor/sidebar.
--
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/2914
ralf3u created an issue (geany/geany#4252)
When coding in the editor I can press the shortcut `Toggle Sidebar` to let appear the sidebar, so I can see editor&sidebar side by side. The focus is then still in the editor. I can change the size of the width of editor&sidebar by moving the vertical separating line with the mouse. When I press again the shortcut `Toggle Sidebar`, then the sidebar disappears. I like this behavior. But sometimes I would like to toggle between editor&sidebar and only sidebar.
**Remarks**
- Yesterday I opened the issue 4251 at Geany. It is about the shortcut `Toggle between only editor and only sidebar`. The shortcut is different than this shortcut.
- The shortcut `Toggle between editor&sidebar and only sidebar` should not take care if the message window is enabled or disabled.
- If the shortcut `Toggle between editor&sidebar and only sidebar` is pressed, then the shortcut should first verify if sidebar is disabled. If sidebar is disabled, then nothing should happen.
- If the shortcut `Toggle between editor&sidebar and only sidebar` is pressed, and if there is a toggle, then the focus should also toggle (if it toggles to editor&sidebar, the focus or rather the cursor should be in the editor; if it toggles to only sidebar, the focus should be in the content area of the sidebar).
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/4252
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/4252(a)github.com>