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
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
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
Since GTK+ 3.20 the scrollbar does not update or only updates erratically. This affects the editor window and doesn't happen for all files.
I bisected a specific gtk commit and will also open a bug report there.
---
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/1002
[Appstream metadata](https://www.freedesktop.org/software/appstream/docs/chap-Metadata… is an xml file that allows your application to be visible to application stores like gnome-software (KDE discover) and really makes it easy for people on Linux to browse, install and now even write reviews for your app. This patch adds a (mostly working) appdata file and makes it known to Makefile.am. Comments inside the appdata file indicate where this could use some love, e.g. with 16:9 screenshots instead of 4:3 links taken from the geany website. The other info (optional) is to add the main dev's email (or whoever maintains the appdata file upstream) as the update_contact (also added as a comment).
Hope you find this useful. Thanks!
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1142
-- Commit Summary --
* Add appdata file and make it known to Makefile.am.
-- File Changes --
M Makefile.am (3)
A geany.appdata.xml (34)
-- Patch Links --
https://github.com/geany/geany/pull/1142.patchhttps://github.com/geany/geany/pull/1142.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/1142
One thing that drives me crazy is how when I have files associated with Geany, if I double click on them to open them, it will open the file in another Geany instance on *another* desktop instead of on the *current* desktop. This was one thing I took for granted when I was using gedit.
I have searched and found someone that suggested somehow using a unix socket file that is named based on the current desktop number, but I have not been successful in doing so. In fact, their solution seemed to lead to some loop that would keep spawning new Geany processes, bringing the OS to a near halt.
Can something like this be *baked in* to Geany so that no special setup or configuration is necessary? If there is a good reason not to, is there an official solution to this somewhere (that works)?
---
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/1025
Geany has some bug in full screen on OSX, like if you open the search window you can't close the full screen with the green button or the search window doesn't close anymore... and some crash when you try to save the project (always on full screen)
---
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/1046
Fixes issue #1000 . Geany now correctly autocompletes LaTeX macros.
The difference in behaviour can be illustrated with the following document:
````latex
\newcommand{\macroname}{}
% The following occurrences of \macro are now autocompleted to \macroname
\macro
\alpha\macro
% The following is no longer autocompleted to macroname
macro
% Example with @
\newcommand{\@anothermacro}{}
% Gets autocompleted
\@another
````
The tests were updated to accept this behaviour (since macro tags now start with `\`).
This also identifies macros defined with `\let`, `\newlength` and environments defined with `\renewenvironment`.
Finally, `@` can be used sometimes in a macro name and mostly any character can be used in a label. I added `:@` to wordchars so that they can be used in autocomplete.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1011
-- Commit Summary --
* '\' is included in macro tag.
* Updated copyright.
* Made indentation consistent with the rest of the project.
* Correctly separates LaTeX words.
* Environments can be defined with \renewenvironment as well.
* Correctly add macro tags.
* Macros can also be defined with \let
* Removed my copyright since I don't even know if I could add it.
* Updated tests to include \ in macros.
* Recognizes new lengths as macros.
-- File Changes --
M src/editor.c (31)
M tagmanager/ctags/latex.c (338)
M tests/ctags/3526726.tex.tags (4)
M tests/ctags/bug2886870.tex.tags (6)
M tests/ctags/intro_orig.tex.tags (6)
-- Patch Links --
https://github.com/geany/geany/pull/1011.patchhttps://github.com/geany/geany/pull/1011.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/1011