Hi,
I will be really nice to have the feature "go to column" to be able to easily go to a specific column (say 1500) for text files with long lines (usually data exchange files)
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/869
the geany sidebar are arrange by tabas.. but cannot be reordened and
if there more thant 3 tabs the vision are limited of thems due labels of each are too large
and if the sidebar are in vertical/horizontal there a waste of space
my suggestion its to optionally only show 3 firts letters or icon only like does with normal tool bar
i'm particular want to know how to only load 3 firts letters to cheap the space in small screen
![geanywastedspace](https://user-images.githubusercontent.com/1571724/33734675-92686202-db63-11e7-97e6-1f6209548df8.gif)
![geanywastedspacetabs](https://user-images.githubusercontent.com/1571724/33734676-928e706e-db63-11e7-94f6-48a95ce95d13.gif)
--
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/1711
I am really enjoying using Geany and congratulate you on its richness of functions but there is one thing that makes me curse:
I have to close the "find" pop-up dialog each time that I select a new area of text to find and then re-open it by clicking "find" or ctrl-f.
I have been used to using TexPad which re-writes the new find text each time without having to close the pop-up.
Thank you for your great efforts.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/758
I have a large Java file (4.8MB). If I insert a new <b><big>{</big></b> near the start of this file, the run time for the parser becomes very long (5 minutes or so) - while the parser is running the editor is unusable. Is there some way to prevent this from happening? By parser I mean the code that determines the coloration of the keywords, strings, etc. <b>Thanks!</b>
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/791
This means that you can't do any work in Geany until you close the external diff viewer. This seriously reduces the usefulness of the otherwise great feature of being able to use an external diff viewer.
The external diff viewer is spawned here:
https://github.com/geany/geany-plugins/blob/master/geanyvc/src/externdiff.c…
Looks like the problem might simply be solved by calling `g_spawn_async` instead of `g_spawn_sync`.
--
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/539
Please tell me if there is some way I can make the line marker (the cross) on line number 1, shown below,
![smallcross](https://user-images.githubusercontent.com/7548378/34533758-859ab0ce-f0b3-11e7-8b06-f04f7bd0e48e.png)
larger as it is very difficult to find visually.
--
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/1733
As pointed out in #1218, currently the Windows nightly builds are not really compabitle with the release installers (line end character detection, strange warnings about image loading, maybe more).
Currently, the nightly builds are created with a very old toolchain (gcc 3.x) and probably outdated GTK stack.
Ideally, we use https://github.com/geany/geany/blob/master/scripts/cross-build-mingw.sh also for the nightly builds with newer Mingw toolchain and maybe even use NSIS to create full installers.
--
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/1241