Apologies if this is already open, couldn't spot a relevant ticket mentioning "tab" and "save".
Also apologies if this seems basic, and I realise the save options are on the main file menu and the main one has the usual keyboard shortcut -- I'm just used to right-clicking on tabs to perform file operations in other editors, and the tab right-click menu in Geany [1.37.1] already has Open and Close actions on it. Could it perhaps have the other key file operations between them, please?
..
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3074
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3074(a)github.com>
1. Create a file in /tmp
2. Try to do a diff/* for that file
--
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/503
This is an already reported issue here https://github.com/geany/geany/issues/1376, I am using a dark theme in my machine and when a program returns a compiling error, it becomes hard to read those error with dark theme enabled. Please add a way to change the font and foreground/background color of the compiler tab similar to the vte's terminal.
--
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/2427
Remove deprecated symbol `tm_get_real_path()` from `tagmanager/tm_source_file.c`. It is replaced with `utils_get_real_path()` in `utils.c`. Not used by any known plugins. See #3019.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3024
-- Commit Summary --
* Remove deprecated symbol: tm_get_real_path
-- File Changes --
M src/tagmanager/tm_source_file.c (24)
M src/tagmanager/tm_source_file.h (6)
M src/utils.c (12)
-- Patch Links --
https://github.com/geany/geany/pull/3024.patchhttps://github.com/geany/geany/pull/3024.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/3024
Recreated #3003 which was closed for some reason
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/3014
-- Commit Summary --
* session.conf split follow-up #3
-- File Changes --
M src/keyfile.c (68)
M src/keyfile.h (2)
M src/search.c (5)
-- Patch Links --
https://github.com/geany/geany/pull/3014.patchhttps://github.com/geany/geany/pull/3014.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/3014
Replacing some text in the whole session can be accidentally clicked too easily and the result might not want the user wanted to do.
So ask for confirmation *before* potentially all files in the session will be modified.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3033
-- Commit Summary --
* Add a confirmation dialog on search & replace for the whole session
-- File Changes --
M src/search.c (9)
-- Patch Links --
https://github.com/geany/geany/pull/3033.patchhttps://github.com/geany/geany/pull/3033.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/3033
Normally the comments are not rigid. If you can introduce a subset of markdown to it, such as `inline code` or `underline`, it will be clearer and more comfortable.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3118
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3118(a)github.com>
There are several problems with how we handle anonymous tags which this pull request tries to resolve:
1. Anonymous tags are currently determined based on how these tags are named by ctags which may not be completely reliable and unnecessary. ctags now has XTAG_ANONYMOUS flag we can query and determine whether a tag is anonymous or not based on that. Our fortran parser didn't report XTAG_ANONYMOUS so it has been updated to do so.
2. In order to store the information about anonymous tags, this pull request renames the unused `pointerOrder` member of TMTag (see the corresponding commit about more details to `flags` and uses one bit to indicate whether a tag is anonymous. This is technically a API change but since pointerOrder always contained 0 and was unused (or maybe used by some super-old parser 15 years back), it doesn't really matter (no g-p plugin uses this field).
3. With the introduction of the new cxx parser, anonymous tags are reported as `__anonNUM` - before they were reported as e.g `anon_struct_NUM` - i.e. they contained information about the type in their name which made them easier to identify in the symbol tree. This pull request adds back this naming.
4. In addition to (3), the NUM in the previous parser was global for all types - i.e. tags were named as `anon_enum_1`, `anon_struct_2`, `anon_enum_3` which is a bit strange as it suggests there are 3 enums but there are 2 instead. This pull request makes these numbers per-type so the above becomes `anon_enum_1`, `anon_struct_1`, `anon_enum_2`.
5. This pull request sets the name of anonymous tag if it's followed by the corresponding typedef tag and the typedef tag is removed. For instance, for `typedef struct{int a} Foo;` you would previously get an anonymous tag for the struct under which `a` would be shown and then separately tag `Foo` as a typedef. After this patch, you get a tag `Foo` for the struct with `a` as its member and the anonymous name is dropped which makes things much clearer in the sidebar.
And finally, thanks to the fact that we do renaming of anonymous tags ourselves now, the last diff against ctags main can be dropped so we can use the upstream version without any modifications and the patch file isn't necessary any more. Hurray!!!
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3059
-- Commit Summary --
* Rename pointerOrder TMtag member to flags
* Use XTAG_ANONYMOUS in Fortran parser
* Add a flag representing anonymous tags
* Determine anonymous tags based on name only when necessary
* Consistently rename anonymous tags and drop the last ctags diff
* Add type information to anonymous tags
* Rename anon types based on the typedef name if present
-- File Changes --
D ctags/ctags_changes.patch (24)
M ctags/main/parse.c (6)
M ctags/parsers/geany_fortran.c (6)
M src/editor.c (6)
M src/tagmanager/tm_ctags.c (147)
M src/tagmanager/tm_parser.c (22)
M src/tagmanager/tm_parser.h (2)
M src/tagmanager/tm_source_file.c (23)
M src/tagmanager/tm_tag.c (16)
M src/tagmanager/tm_tag.h (13)
M src/tagmanager/tm_workspace.c (6)
-- Patch Links --
https://github.com/geany/geany/pull/3059.patchhttps://github.com/geany/geany/pull/3059.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3059
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3059(a)github.com>
Replaces [#2986](https://github.com/geany/geany/pull/2986).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3097
-- Commit Summary --
* Imports Asciidoc lexer from Lexilla 5.1.4
* Enables Asciidoc lexer
-- File Changes --
M data/filedefs/filetypes.asciidoc (50)
M scintilla/Makefile.am (1)
M scintilla/lexilla/include/LexicalStyles.iface (27)
A scintilla/lexilla/lexers/LexAsciidoc.cxx (393)
M scintilla/lexilla/src/Lexilla.cxx (1)
M src/highlighting.c (2)
M src/highlightingmappings.h (33)
-- Patch Links --
https://github.com/geany/geany/pull/3097.patchhttps://github.com/geany/geany/pull/3097.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3097
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3097(a)github.com>