The unsaved files will not be available after an OS restart or crash. This behavior is seen in Mac, not sure about Windows. It's one capability I feel missing in Geany compared to Notepad++ in Windows and TextWrangler in Mac.
--
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/1603
On a vertical split screen the [end] key does not go to the end of the line of text.
[shift] + [end] **DOES** work but plain [end] key does not.
_Hope this helps
pj_
geany 1.33 (built on 2018-04-17 with GTK 3.10.8, GLib 2.40.2)
[geanytext.txt](https://github.com/geany/geany/files/2217075/geanytext.txt)
Release Linux Mint 17.3 Rosa 64-bit
Kernel Linux 3.19.0-32-generic x86_64
MATE 1.12.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/1901
I would like to be able to add something like pairtaghighlighter=#2f6f6f9f to a colorscheme.conf to prevent this from happening to me,
or in a separate file, the thing is to be able to change it somehow, without having to touch the code.
the truth is a little out of the color scheme
thank you.
--
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/760
Please take into account that the question mark is now a valid operator: a postfix operator.
--
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/1827
If you open up an Objective-C file with the ".m" extension, it will set the filetype to Matlab/Octave.
To fix it, you have to go to `Tools=>Configuration Files=>filetype_extensions.conf`. Then remove *.m from `Matlab/Octave=`.
To solve this, you'd have to check the code in the file, which I imagine would be a pain.
However, almost every Objective-C file will contain at least one `#import` or `#include`. You could probably just check if the file contains this.
I'm not sure which is more popular. If Matlab/Octave is more popular, then maybe it should be ahead of Objective-C files.
--
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/1896
I am actually working on issue/feature request https://github.com/geany/geany-plugins/issues/733.
I extended the workbench plugin and now it allows to create global and projects commands, to store the values in the projects and workbench file and to inherit global workbench commands to the projects. This are all workbench internal functions.
When it comes to actually execute a command I planned to use ```build_set_menu_item()```, ```build_activate_menu_item()``` and to introduce a new build source called ```GEANY_BCS_PLUGIN```. But just adding a new build source is not doing the job. I guess ```build_activate_menu_item()``` is simply ignoring a new value.
Also, the workbench plugin maintains several projects and that would mean to re-write the commands each time by calling ```build_activate_menu_item()```. And the functions doesn't seem to free old values by itself.
I came to the conclusion that for my approach (and maybe for other plugins) it might be more suitable to have a direct plugin call like
```
build_execute_command(BUILD_TARGET_COMPILER, command, workingdir);
```
The first parameter given should tell if the command output goes to the "Compiler" message window. An alternative value would be BUILD_TARGET_NEW_TERMINAL which means start a terminal and run the command in it. This seems to be what the groups ```GEANY_GBG_FT``` /```GEANY_GBG_NON_FT``` and ```GEANY_GBG_EXEC``` do today.
The API call should work in a Fire&Forget manner: parameters ```command``` and ```workingdir``` should be copied (if necessary). Then run the command as described above and once finished simply forget about ```command``` and ```workingdir```.
What do you think?
--
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/1897