After using Geany for almost a day using the Solarized Dark theme, I felt that the text in Geany was slightly harder to read than in Notepad++, an editor I've been using for the past couple years. At first I thought I was imagining things, but after taking screenshots from each editor and comparing them side-by-side with a magnifying glass, I finally figured out why: the font rendering in Geany is ever so slightly darker (or thinner?) than the font rendering in other code editors like Notepad++. Here is the comparison:
Notepad++ is on top and Geany is on the bottom. It is barely noticeable in the image above, but if you zoom in and use the eyedropper tool you will find that the colors in Geany are darker than the ones in Notepad++:
Maybe I'm just more sensitive to this than others, but after spending a day editing code containing lots of strings using the Solarized Dark theme, I find that the code in Geany is slightly harder to read.
I'm not sure how to categorize this because I suspect it is related to the native font rendering engine that is used in Geany.
---
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/1066
Currently, if a link is clicked in the markdown preview, said link is opened in the preview tab itself, instead of calling my main browser.
This might be the desired outcome for relative links, but in my case opening youtube in the embedded browser led to audio glitches and then a nice crash.
Maybe a configurable option? Or absolute links in browser, relative in preview?
Thanks for your work, guys.
--
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/544
I have been using geany with the vimode plugin. Just wanted to share a few places where I found bugs.
1. I am not able to enter normal mode whenever the number lock is on.
2. when I delete a line using the command `dd` the page shifts down till the point the cursor is at the top. Whereas it should have gone the line below and not shifted the page, And when I undo after deleting the line (I have seen this behavior in this particular case only) the cursor goes to the bottom of the document.
--
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/1136
Anyone had a try to see how much work it would be to adjust geany to gtk4?
Or optionally have it?
--
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/2713
If a assign a keyboard shortcut for generatin an itemize or enumerate environment, the result is
```
\begin{itemize}
\it
\end{itemize}em
```
where the correct output should be
```
\begin{itemize}
\item
\end{itemize}
```
Steps to reproduce:
* Assign some keyboard shortcut for itemize (or enumerate).
* Press that combination of keys.
My version of Geany is 1.33 (the one shipped with recent Debian-ish distributions), the LaTeX plugin version is 0.7.
--
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/1071
# When the "Markdown" plug-in is enabled, opening a markdown file containing "@@markdown@@" always freezes.
---
## usage environment
- Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20191125)
- $ uname -r
5.3.0-24-generic
- geany 1.37 (git >= 5cc69b3d) (Dec 9 2019 以降に次を使用してビルドGTK 3.24.12, GLib 2.63.1)
- libwebkit2gtk-4.0-dev/focal,now 2.26.2-1 amd64
I built and installed the Markdown plugin using webkit2gtk.
---
## Reproduction method:
Enable the "Markdown" plug-in in the "Geany" app.
$ geany test.md
Enter "@@markdown@@".
-> As soon as the last “@” was entered, the “Geany” app froze.
--
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/936
Hi, this is happening in Ubuntu 20.04, compiled version of geany 1.37.1. I'm a long time user of Geany, and I've always compiled from source. Compilation was fine, as usual.
╭─nalonso@satellite ~
╰─$ geany
[1] 1884036 segmentation fault (core dumped) geany
╭─nalonso@satellite ~
╰─$
If I open documents everything works fine.
Maybe unrelated, but Geany is taking a whole lot more time to load with a lot of documents. I use to have 30 or more files opened, mostly YAML and Dockerfiles, but up to 1.36 Geany was lightning fast even with all those documents open.
--
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/2736
This happens with erlang files, just erlang files
Im on 1.37. If im not wrong, this didnt happened on 1.36...
It looks (erlang file):
It should look (python 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/issues/2650
I am looking for some kind of "Console View" like it is available for example in Eclipse.
Currently a terminal / shell opens when executing a script in Geany. In this shell one can see the process streams stdout and stderr and can write to stdin of the new process.
However, I would rather eliminate this new terminal window popping up and changing focus each time I launch a script in Geany.
I think it is better to have the process communication (stdout, stdin, stderr) embedded in a view within Geany like it is done in many IDEs. The different streams could be colored e.g. stderr in red and stdin (input from the user) in green.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/675