```
template <typename T> using Uptr = std::unique_ptr<T>;
```
Does not recognise Uptr as a typename;
---
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/975
Closed #452 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/452#event-15410956298
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issue/452/issue_event/15410956298(a)github.com>
The crosshatch (#) and asterisk (*) commands in Vim perform exact word searches. For example, with the cursor on "word", the asterisk would perform "/\<word\>" to search for the next exact occurrence of "word".
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1372
-- Commit Summary --
* Surround word with "\\<" and "\\>" for search_current().
-- File Changes --
M vimode/src/cmds/special.c (2)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/1372.patchhttps://github.com/geany/geany-plugins/pull/1372.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/pull/1372
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/pull/1372(a)github.com>
I was wondering if anyone would be interested in creating / adding on to an existing plugin.
I see there is an existing plugin called “Addons” which is for various small features added to Geany, maybe it can be added to this plugin if anyone is interested.
This plugin would allow user to setup a keybinding that would create divider/separator lines when the keybinding is applied.
User would be able to setup how they want the divider/separator lines to display visually and because each language has a different "comment" symbol, there would have to be a way for user to be able to set this up per language/file type.
EXAMPLES
(plain regular text file which does not require a comment symbol)
(not sure if any other users would find this useful, but ability to use this in plain text files for me would be very helpful)
txt
`######################################`
xml
`<!--#################################-->`
lua
`--#####################################`
Thank You
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1384
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany-plugins/issues/1384(a)github.com>
I'm a keyboard user with carpal tunnel. When I search for a string, half the time it's going to be above the cursor in the file. Unfortunately, the default option in the Question dialog is "Cancel":
I think a more useful default would be to Find again. If I want to Cancel, I'll press Esc. If I want to find again, I have to press two keystrokes (Alt+F, or Right Arrow then Enter). I know one extra keystroke is not much, but they add up.
Any thoughts on making `Find` the default?
--
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/1192
When the "Wrap search and find again?" dialog appears, it makes more sense to wrap instead of cancel the dialog by default (the dialog can always be canceled by Escape).
The implementation of this patch more or less duplicates the code of dialogs_show_question_full() and makes the Find button default. While it would be possible to add one more parameter to dialogs_show_question_full() controlling this behavior, there's currently no other use of this in Geany (in all other cases, the action button performs a destructive action so Cancel is default) so I believe having this local implementation of the dialog is a better option not complicating other uses.
Fixes #1192.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4042
-- Commit Summary --
* Make "Find" the default button in the wrap search dialog
-- File Changes --
M src/document.c (39)
-- Patch Links --
https://github.com/geany/geany/pull/4042.patchhttps://github.com/geany/geany/pull/4042.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4042
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4042(a)github.com>
Depends how much typical users are using the “Set Custom Command” dialog?
Can close this if no one is interested.
I noticed that there are not many visual indicators of what keybindings are set to “Send to Custom Command” tools.
-"Preferences - Keybindings" just shows generic “Send To Custom Command 1 - 9” with the keybindings
-"Set Custom Command" dialog just shows the command Labels
-The only place that shows both the names + keybindings together is the menu bar flyout but this is not a place where any setting/editing can be achieved.
The only thing I can think of is to maybe add a “Keybinding” column to the end of the “Set Custom Command” dialog?
ID / Command / Label / Keybinding
Not everyone might use Ctrl+1-9 keybindings where the keybindings are in a convenient numbered order 1-9.
This “Keybinding” column would let user know that when they are moving items up/down on the list that the actual keybinding are not moving with the actual command actions. The keybindings linked are fixed to 1-9 order.
I do not see anyone programming the ability to be able to actually set the keybindings from this dialog, which would update the keybindings shown in Preferences - Keybindings.
So the “Keybinding” column would be more static where it cannot be edited, but would just be an indicator of what keybindings are actually linked to those 1-9 positions.
Thank You
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/4067
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/4067(a)github.com>
**\[WARNING: Work in progress\]**
Add SystemVerilog support, which was relatively easy since both ctags and the lexer support it.
**Done:**
* [x] Create SystemVerilog filetype (with all the SystemVerilog keywords)
* [x] Add filetype to Geany source code (create GEANY_FILETYPES_SYSVERILOG et al, create tag map in tm_parser.c, etc)
* [x] Compile and test it
**TO DO:**
* [ ] Select which of the tag categories parsed by ctags to process in Geany
* [ ] Provide meaningful tag associations (tm_tag_\*_t) in tm_parser.c
* [ ] Arrange into groups and provide meaningful icons
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/4039
-- Commit Summary --
* Add SystemVerilog filetype
* !TODO! (WIP) SystemVerilog: provide appropriate Ctags
-- File Changes --
A data/filedefs/filetypes.systemverilog (62)
M data/filetype_extensions.conf (3)
M src/filetypes.c (1)
M src/filetypes.h (1)
M src/highlighting.c (2)
M src/highlightingmappings.h (7)
M src/tagmanager/tm_parser.c (60)
M src/tagmanager/tm_parser.h (1)
M src/tagmanager/tm_parsers.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/4039.patchhttps://github.com/geany/geany/pull/4039.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/4039
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/4039(a)github.com>
![src="https://user-images.githubusercontent.com/2157285/140661024-3df31…](http://src="https://user-images.githubusercontent.com/2157285/140661024-3df31d57-b8c0-486f-aa9c-d87ff8c0532f.png%22%3E){kind=link}
![src="https://user-images.githubusercontent.com/2157285/140660989-7f779…](http://src="https://user-images.githubusercontent.com/2157285/140660989-7f77901c-3f45-4ca1-a475-2c73d453a084.png%22%3E){kind=link}
![src="https://user-images.githubusercontent.com/2157285/140661000-748a0…](http://src="https://user-images.githubusercontent.com/2157285/140661000-748a08c8-246f-4fe7-a6be-b5efae10ba47.png%22%3E){kind=link}
![src="https://user-images.githubusercontent.com/2157285/140661031-4904f…](http://src="https://user-images.githubusercontent.com/2157285/140661031-4904f174-a6b5-42dc-8447-be71d03edfc7.png%22%3E){kind=link}