After #3013, the default color of `COLOR_DARK_RED` may no longer be "red". Would there be any objection to changing the enum in [msgwindow.h](https://github.com/geany/geany/blob/6856edd6511e8aa9a225098ac2…
* `COLOR_RED` → `COLOR_ERROR`
* `COLOR_DARK_RED` → `COLOR_ORANGE` → `COLOR_CONTEXT`
* `COLOR_BLUE` → `COLOR_MESSAGE`
The change would mostly be find/replace. Since these values are exported, the old ones would need to be retained and marked as deprecated. Plugins that would need to be updated: spellcheck, geniuspaste, project organizer, geanyctags, ¿geanypy?
>From [`msgwindow.c`](https://github.com/geany/geany/blob/6856edd6511e8aa9a225098ac2aab9171b10167f/src/msgwindow.c#L296-L305):
```C
case COLOR_RED: return &color_error;
case COLOR_DARK_RED: return &color_context;
case COLOR_BLUE: return &color_message;
```
--
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/3016
I'm closing this pull request in favor of #3018 which addresses the project creation problems I described here and doesn't change anything about projects themselves so it shouldn't affect anyone's workflow. Hopefully, it could be something we could agree on more easily.
--
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/450#issuecomment-978499937
Hi!
I would like to propose an enhancement/feature request:
* At the moment the recent files/projects are saved in geany.conf.
* I would like to save geany.conf in a revision control system, so I can share the configuration between different computers.
* The recent files from different computers lead often to merge conflicts of the configuration file.
* E.g. I do this very successfully with vi, one configuration over many computers.
Is is possible, to move the recent files/projects to a separate (local) state file?
Regards,
Mark
--
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/1763
When a new project is created, the "New Project" dialog should provide an option to copy the list of open files from the current project.
Usually I find myself opening files that are not actually relevant to the currently active project, until I decide that all those files belong to a different "topic" and decide to move them to a new Geany project. The simplest way to do this is to just "clone" the project, and then close the files that are not relevant in both old and new project. Unfortunately, Geany doesn't have a "clone" or "save project as" feature (as suggested in #2206), so I have to manually copy the `.geany` project file, rename it, open it with my *second* favorite editor (can't open it with Geany) and edit the name and base path, and then proceed to close the unneeded files. Having an option to "clone" the project (either through a "Save project as" menu entry as proposed in #2206 or through a "Keep files from current project" checkbox in the "New Project" menu) would simplify 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/3010
Move search positions and layout to session.conf
This will remember the x,y positions as well as the find/replace
dialog expanders as part of session.conf.
To implemenet this, a new interface configuration_add_session_group()
is created that connects a StashGroup to session.conf.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3003
-- Commit Summary --
* session.conf split follow-up #3
-- File Changes --
M src/keyfile.c (60)
M src/search.c (5)
-- Patch Links --
https://github.com/geany/geany/pull/3003.patchhttps://github.com/geany/geany/pull/3003.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/3003
For example:
- if I set the font "Ubuntu **Mono** Regular" with a size 12 and "Long line marker" column value to 80, then 80 characters will match "Long line marker"
- if I set the font "Ubuntu Regular" with a size 12 and "Long line marker" column value to 80, then 80 characters will **not** match "Long line 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/2811
>From https://github.com/geany/geany/pull/2953#issuecomment-964615464 thanks @xiota
As noted in the comment above, the return from `utils_write_file()` of `geany.conf` is not checked, but the return is checked for write of a project file.
As pointed out this seems inconsistent, is it deliberate and should it be changed?
--
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/2993