I belive this issue came with geany 2.0, but I am not sure.
The default configuration for the geany status bar is: disabled. Verify "show status bar" in the Preferences, is disabled:
![2023-11-28-103001_670x564_scrot](https://github.com/geany/geany/assets/906376/bd5cc2e8-8506-48b4-a075-c727d1afb020)
This is how geany looks before using "toggle All Additional Widgets" Function:
![2023-11-28-103322_829x834_scrot](https://github.com/geany/geany/assets/906376/81120114-b5fc-42bf-b642-cb2676c350f5)
Using the "View -> Toggle All Additional Widgets":
![2023-11-28-103339_829x834_scrot](https://github.com/geany/geany/assets/906376/3d084c07-c562-4a16-a5e4-a8bcdfb73333)
Until here everything is working.
Now if the "View -> Toggle All Additional Widgets" is again executed, geany shows a empty "status bar" at the bottom:
![2023-11-28-104315_829x834_scrot](https://github.com/geany/geany/assets/906376/f9d042b9-c141-4bcc-a3cb-d572b2e9edf4)
Now in this issue state, closing geany and reopening again, open geany again in the "desired" state, without showing the "status bar" at the bottom.
Please take a look at it.
Thanks.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3706
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3706(a)github.com>
Wish for an item in the file tab's context menu to open the file's containing folder and locate the file.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3704
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3704(a)github.com>
I realized today there can be an issue in Geany core, as text files which inadvertently contain character '\0' (NUL character) in the middle of it (for instance, a log file), are only read (or represented) until that point. I have tested both Geany 1.38.0 and Geany 2.0, and both of them behave in the very same way.
Comparatively, I have tried other editors, like vim, nano, Kate or the ancient NEdit, and no one of them suffer from this bug.
Could you fix it, please?
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3700
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3700(a)github.com>
Hi all,
Love Geany so far. However, I wanted to inquire on how to move the Terminal to the top and always open this at launch of Geany? Basically, the screenshot below. Any help is appreciated. Thanks!
![image](https://github.com/geany/geany/assets/115644052/30104a44-6d9d-45c0-9f15-1fcdf754cc85)
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/discussions/3705
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/repo-discussions/3705(a)github.com>
The xterm is small without configure it, and I do not like to make a .Xdefaults config for xterm any more. So I want replace the `xterm` with well work's `gnome-terminal`.
In `Preferences -> Tools -> Terminal`:
1. when I set as `gnome-terminal -e "/bin/sh %c"`, and click the **RUN** botton in toolbar to execute, the gnome-terminal is show, but the RUN botton can not display as an "STOP" icon, that's say I can not stop the running application by click the RUN button.
2. when I set as `gnome-terminal -x "/bin/sh %c"`, it failure to lanuch.
I want click the button to run, click again to stop.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3703
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3703(a)github.com>
I was working on a C program in linux, and realized C++ would be a better fit. So I copied the program and gave it the .cpp extension. then I spent a bunch of time figuring out all the weird errors i was getting, before realizing the file retained the build commands from gcc.
The program has the same file name, only the extension had changed. new files with different filenames did not have this issue.
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3525
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3525(a)github.com>
#### filetypes.pascal
- add line comments
- pair the 'fpc' compile command with another common Free Pascal utility [^1], 'instantfpc', to build and run the current file in a single step
#### filetype_extensions.conf
- add Lazarus project files (*.lpr)
[^1]: https://wiki.freepascal.org/InstantFPC
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/3694
-- Commit Summary --
* Update Pascal filedef and extension mappings
-- File Changes --
M data/filedefs/filetypes.pascal (4)
M data/filetype_extensions.conf (2)
-- Patch Links --
https://github.com/geany/geany/pull/3694.patchhttps://github.com/geany/geany/pull/3694.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/3694
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/pull/3694(a)github.com>
Geany (v1.38 here) already opens the Compiler tab if a build command fails. It is also aware of the lines that denote errors. However, it does not scroll to the first error but simply opens the tab if it's not open and that means that usually(?) it's at the very bottom of the output showing the return value and "Compilation failed."
When using the build commands to actually compile something I am almost always interested in seeing the first problem that occurred. So I kept scrolling up which depending on the verbosity of the output is quite ineffective and stupid and I think that is a quite typical task. In some situations, when "misusing" Geany's build system, it might not be the best option but I could not come up with one so far.
Therefore, I propose that Geany should jump to the first error when opening the Compiler tab due to a build error.
Thanks to another issue on github I have discovered the `Build/Next Error` functions that can be bound to hotkeys and that's kind of good enough for me but if you don't see any good reasons why it would be unwanted I could take a look into making a PR. It might actually be so trivial for anybody with a prepared build environment for Geany that I wouldn't feel sorry if somebody beat me to it ;)
--
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/3699
You are receiving this because you are subscribed to this thread.
Message ID: <geany/geany/issues/3699(a)github.com>