There are 3 tiny things that can be easily implemented in Geany:
1. Having %f, %d, %e, %p, %l in context command (just as in Compile/Build/Run).
2. Having three context commands (they would be roughly corresponding to the Compile/Build/Run) mapped e.g. to Ctrl+F1, Ctrl+F2, Ctrl+F3. Now we have one and only context command.
3. Having possibility to process multiline selection, if context command equal to the naked "%s". Now we can process only one line of selection.
---------------------
I try and show how the context command can be used with all its beauty.
Imagine we have a Python module under testing in Geany. And it is called with parameters. And the parameters are changed from time to time.
Goings to Run command setting every time are tiresome. And dull nuisance when we have this cool CONTEXT COMMAND.
All we need is to make a multiline Python comment in our module (let it be mymodule.py) containing something like:
```
""" BEGIN OF TEST BLOCK:
mymodule.py testpar1
mymodule.py testpar1 testpar2
mymodule.py testpar1 testpar2 testpar3
etc.
END OF TEST BLOCK """
```
... and to set THE CONTEXT COMMAND equal to
python3 %s
After that we select a line with current test parameters and call the context command from popup menu or with hotkey.
By this we get a batch of self-documented test cases directly inserted in the code!
By this we don't touch RUN settings of other Python modules. It seems to be the main advantage of this.
mymodule.py could be smartly replaced with "%f" if Geany allowed it. It would enable independence of code on renaming, moving to other platform and so on. After all, it's shorter than "my_supposedly_gigantello.py"
---------------------
Now about the issue.
If we key mapped CONTEXT COMMAND to Ctrl+F1 (or even F1, leaving to Geany only menu to call its help), then it works. Sometimes, however, it works not.
For example, select the following
` #include`
and call the context command from popup menu - it will process the "#include" OK.
But Ctrl+F1 ignores our hotkeying it.
It occurs every time when we selected something more complex than just a word.
-----------------------
It is not awfully good if we would try the above example of using CONTEXT COMMAND.
-----------------------
--
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/1807
There below is a zip file providing a context help on Tcl/Tk commands and keywords while editing Tcl script in Geany IDE.
By context help I mean the following: while editing a file.tcl in Geany you can set the caret on desirable Tcl command/keyword and press Ctrl+F1 (or F1, if you map it to Geany's context action) - after that you should get a help (man) page for the Tcl command/keyword.
Man pages of www.tcl.tk are remarkable with their giving a separate man page (as html file) for each single entry. So, we can organize their viewing on context base.
And Geany is remarkable with its customizing options and one of them is a context action. The action may be tuned and called for a word or text selection from popup menu or with a hotkey.
-------------------------
Now let's customize Tcl/Tk context help in Geany IDE. As a bonus you'll get a menu of commands to use in Geany IDE unrelated to Tcl/Tk directly, thus Geany and Tcl/Tk would **help each other** as declared.
Please try this:
**1**. If you do not have Tcl/Tk on your system, install it from [www.tcl.tk](http://www.tcl.tk). Linux users have it preinstalled, most likely.
**2**. Unpack the below attached zip to save files:
```
e_help.tcl
e_menu.tcl
run_pause.bat
run_pause.sh
```
into some directory, e.g. /home/me/UTILS
**3**. Go to Geany's menu 'Edit/Settings', then to 'Tools' page and enter in the 'Context action' field:
```
wish /home/me/UTILS/e_menu.tcl "s=%s"
```
**4**. In /home/me/UTILS/e_help.tcl change the lines containing:
```
set my_browser "...put your browser as last here, others may be removed..."
```
**5**. In /home/me/UTILS/e_menu.tcl change the lines containing:
```
run_pause.sh (for Linux)
run_pause.bat (for Windows)
```
so that they were the full pathnames:
```
/home/me/UTILS/run_pause.sh
/home/me/UTILS/run_pause.bat
```
-------------------------
Uff. Now you should be able to call the context help. While editing your Tcl/Tk script, select a Tcl/Tk command or simply place the caret on it and call "Context action" from popup menu. You should see something like:
where 1st line calls Tcl/Tk help for "selection" (i.e. foreach, string, grid, panedwindow etc. - about 200 Tcl/Tk man pages and 26 pages of Tcl keywords from A.htm to Z.htm)
Other lines execute "selection" as an executable program by itself and by shell in console, with or without waiting their completion.
---------------------
[tcl_and_geany.zip](https://github.com/geany/geany/files/1818354/tcl_and_gea…
--
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/1808
Adding this as a comment, for anyone similarly affected.
Geany was using ~20% CPU, constantly and consistently when idle -- when launched from the XFCE "Whiskers" menu (which is the way I normally start it), but NOT from terminal (e/g/ xfce4-terminal)!
Solution: edit the Whiskers menu launcher for Geany >> uncheck "Use startup notification." Geany CPU usage (Geany idle) now 0%.
--
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/1819
Geany Version: 1.33, OS: Fedora 27 Reproducable: yes
When the Colour Picker is clicked on a sample, I am logged out. The issue triggers abrt, which after a few minutes asks if I would like to report the bug. I press report and a trace is started. It then comes back stating there is nothing in the trace to report. As long as this tool is not used, everything works fine.
--
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/1818
This prevents loading a spurious tag for the format specifier line, as well as fixing loading of CTags format with a format specifier line.
Before this change, the file pointer was rewound after reading a format specifier line; but this had various unwanted side effects depending on the recognized format:
* For TagManager and Pipe formats, it led to loading a tag named after the format specifier (e.g. a literal `# format=tagmanager`). This was fairly harmless and only introduced a spurious tag seldom even used because `#` isn't usually considered for looking up completions.
* For CTags format, having an explicit specifier led to failure to load the file in most cases because the specifier line would be parsed but doesn't usually follow the format's requirements, leading to early abortion loading that file. On some very specific specifier lines actually following CTags format, it could have led to loading a spurious tag instead.
Fixes #1814 and closes #1816.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1817
-- Commit Summary --
* Skip the format specifier when loading a global tag file
-- File Changes --
M src/tagmanager/tm_source_file.c (5)
-- Patch Links --
https://github.com/geany/geany/pull/1817.patchhttps://github.com/geany/geany/pull/1817.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/1817
The manual includes this section describing how to start a tag file:
> The first line of global tags files should be a comment, introduced by # followed by a space and a string like format=pipe, format=ctags or format=tagmanager respectively, these are case-sensitive. This helps Geany to read the file properly. If this line is missing, Geany tries to auto-detect the used format but this might fail.
This is wrong for ctags files because after reading the ```# format=ctags``` line the file is rewinded. And then ctags parsing aborts on the very first line because it is expecting a different format. It only skips ```!_TAG_``` lines.
On recognizing ```!_TAG_``` lines the tag file format is set to ```TM_FILE_FORMAT_CTAGS``` so tag file authors should be instructed to only use such lines for ```ctags``` files and not lines starting with ```#```.
--
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/1814
On import of a global tags file, do not rewind the file if the first line is ```# format=ctags```. Otherwise the import would abort on the first line and 0 symbols would be imported. Fixes #1814.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1816
-- Commit Summary --
* tagmanager: do not rewind file on '# format=ctags'
-- File Changes --
M src/tagmanager/tm_source_file.c (9)
-- Patch Links --
https://github.com/geany/geany/pull/1816.patchhttps://github.com/geany/geany/pull/1816.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/1816
I send 2 commits first for markdown plugin , which seems to me that can be cherry-picked and the second for webhelper which also use the same webkitgtk but it is not completed ! , please just look for the first commit, first.
Thanks.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/656
-- Commit Summary --
* [markdown] Use webkit2gtk3 (webkit2 API)
* [webhelper] Use webkit2gtk3 (webkit2 API)
-- File Changes --
M build/markdown.m4 (4)
M build/webhelper.m4 (4)
M markdown/src/viewer.c (7)
M markdown/src/viewer.h (2)
M webhelper/src/gwh-browser.c (74)
M webhelper/src/gwh-browser.h (2)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/656.patchhttps://github.com/geany/geany-plugins/pull/656.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-plugins/pull/656
When tabbing through the interface to change the currently focused widget, one gets stuck when reaching the overview.
Steps to reproduce:
1. Enable Overview plugin
2. Get keyboard focus to the message window (e.g. click on one of the status lines)
3. hit <kbd>Shift+Tab</kbd> twice: first one will reach the msgwindow's tab itself (e.g. "Status"), second will reach overview
At this point, it's not possible to move anymore using <kbd>Tab</kbd> or <kbd>Shift+Tab</kbd>. I don't believe this is on purpose, or has any usefulness as the overview isn't editable.
Proposed fix: mark the overview itself as not focusable (`gtk_widget_set_can_focus(self, FALSE)`) so it's skipped over. Alternatively, if you want to e.g. allow arrows to move in the overview, make sure to left focus cycling through.
--
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/731
Sometime in the last month scrolling through tabs stopped working.
v. 1.33
Linux.
--
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/1815