When I type in Geany, the letters often take time to appear. For instance, let's say I type 6 characters in 2 seconds. Those 6 characters will appear one at a time, perhaps taking 2.5 or even 4 seconds to appear. This is a serious usability issue, and I have used Geany for a long time but never experienced it before.
This happens at varying degrees of severity on most files I work with. Will update if I discover anything new about the problem.
## Some info:
- OS: Opensuse Tumbleweed
- Geany: 0.32
- CPU: Intel Core i3-7100, Intel HD Graphics
- Desktop Environment: GNOME 3.26
- GTK theme: Adwaita
Let me know if you need anything more or have any suggestions! Even if you don't have suggestions or solutions, comment if you are having the same problem.
--
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/1787
20:49:15: Geany INFO : Geany 1.27 (git >= ad354b7), en_AU.UTF-8
20:49:15: Geany INFO : GTK 3.10.8, GLib 2.40.2
Ignore the commit, Geany Git is actually 27628c0 (I thought we fixed needing to re-configure to get the git version?)
After using Geany for a while sometimes when switching tabs only the line with the flashing caret displays the new file, then after a while some more displays etc.
If I move the cursor into the edit widget it all updates.
Its like Scintilla is not getting the correct triggers to cause full update.
This doesn't happen with all tabs, but the ones edited most.
@b4n any suggestions where to look?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/807
# Abstract
When naming a variable something that isn't ASCII, but is still a valid Python3 identifier, the variable doesn't show up in the symbols list.
## Problem Info
### Test case:
```python
#!/usr/bin/env python3
# coding: utf-8
correct = bool()
对不对='对' if correct else '错'
```
Load up that file in Geany, then open the Symbols tab.
### What I expected to see
"correct" and "对不对" both show up in the Symbols list.
### What happened
Only "correct" shows up in the Symbols list.
## Extra info
1. <output>geany 1.27 (built on 2016-04-17 with GTK 2.24.30, GLib 2.48.0)<output>
2. OS: Ubuntu 16.04.1 LTS
--
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/1337
This code adds the name "HEADER_TEMPLATE" to the variables list in the side bar:
```
HEADER_TEMPLATE = '''
==============
|{:^15}| {}
==============
'''
```
However this code does not:
```
HEADER_TEMPLATE = '''\
==============
|{:^15}| {}
==============
'''
```
Running Linux Mint, Geany 1.29, Python mode.
Thanks for all your work! Keep it up!
--
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/1390
Using python, this code should only report 1 variable.
```
data = dict(
en = "beer",
de = "bier",
es = "cerveza"
)
```
But 4 variables are reported in the sidebar:
Thanks for all your work!
--
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/1417
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
Geany is an excellent tool but gdb support unfortunately does not support cross-debugging, which is a rapidly growing need. I certainly don't want to be forced to use some ugly mastodent like eclipse just for that.
This patch is very short, so it seems that there is little functionality missing to achieve this. Would it be possible to integrate something like this into geany-plugins?
http://faumarz.blogspot.fr/2014/03/gdb-and-geany-ide-remote-cross-debugging…
Thanks.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/303
Currently
```
!commit abcd123
```
generates a URL for that commit.
It would be good if say
```
!issue 1234
```
would link to the issue/pr 1234.
Although pull requests show a URL like `geany/geany/pull/1234` it seems they will also be found with `geany/geany/issues/1234` the same as other issues, so the code just needs to be the same as `!commit` code but with URL base `https://github.com/geany/geany/issues` and limiting the argument to decimal numbers.
--
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/infrastructure/issues/3
In Geany the name `instance` is highlighted as a type
```C++
class c {
int i;
public:
c( int j ):i(j){}
int f(){ return i; }
} instance{1};
c another{1};
```
Note github has it correct.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/892
Hi,
At the moment Linux users are essentially left to wait until their respective distribution's repositories are updated and the new release of Geany is added. This process is so tedious, however, that for most non-bleeding edge distributions one has to wait months or years for this to happen (by which time usually an even newer release of Geany is out). So what I propose is that you's provide your own AppImages for Geany. AppImages, for those of you that are unaware, are a type of cross-distribution packaging format that need no special tools (like no special package manager to manage the packages) in order to be run. They merely need to be marked executable (with `chmod +x`) and run (with `./<AppImage>` where `<AppImage>` is the AppImage's filename, including its file extension). They are essentially self-mounting image files with an internal file system that contains all the files required to run the program they provide (which in this case would be Geany, of course).
I have created my own AppImage for Geany (which you can find [here](https://bintray.com/fusion809/AppImages/Geany#files)) but as you might notice it is presently out of date (version 1.28, versus the latest release of 1.29) as the Debian packages (and no this does not mean that this AppImage will only run on Debian systems, it will run on Arch Linux, Fedora, Gentoo, openSUSE, etc. as well) I built it from are presently out-of-date (although no doubt they will be updated soon). Plus my AppImage is built using Debian (Jessie) ingredients so it doesn't work on systems older than Jessie, while it is possible that you's could create a more flexible AppImage. You's could use your Travis CI artefacts instead of the Debian packages I use to build the AppImage, hence providing the very latest (more up-to-date than I could ever hope to provide) build of Geany. The way I uploaded my Geany AppImage to Bintray is using Travis CI, so they both easily integrated with one another. Alternatively you could upload the AppImages to the releases page of this GitHub repository.
If you need help with this I am more than willing to help, although I do believe @probonopd will be far more helpful than I, due to his superior knowledge of AppImages (after all he is the one that created the format).
Thanks for your time,
Brenton
--
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/1303