Adds optional linewrapping in the status-, compiler- and message-tab of the message window.
Mainly useful with a vertical layout, but still has some issues:
- on_width_change() is called continuously while resizing the message window,
(I did not notice any impact on CPU usage though).
- when changing the setting, messages already present are not wrapped / unwrapped,
only newly printed ones.
- when resizing the window, messages already present are wrapped only until
a new line would be required (but new messages work fine).
- Only very minor, but GTK word wrap treats the minus preceding command line arguments
as separate words (-> 'gcc -Wall' can become 'gcc -\nWall')
I hope it's not rude to make a pull request directly without first opening a corresponding issue.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1383
-- Commit Summary --
* Add option for linewrapping in message window
* Correct minor inconsistency: return type not on same line as function
-- File Changes --
M data/geany.glade (96)
M doc/geany.txt (4)
M src/keyfile.c (2)
M src/msgwindow.c (57)
M src/msgwindow.h (2)
M src/prefs.c (7)
M src/ui_utils.h (1)
-- Patch Links --
https://github.com/geany/geany/pull/1383.patchhttps://github.com/geany/geany/pull/1383.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/1383
if there is 1 button for build and run ,like in codeblocks it would be nice so i tried this command but did not work.
to set build commands ;
g++ -Wall -o "%e" "%f" && "./%e"
can some one point out which command line should i write ?
--
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/1327
While using Geany in Gnome I found that sometimes code navigations was slow,
changing to a new line o making selections were reflected after aprox 1 second
on the screen.
Just opening a file and navigating doesn't trigger this problem, after editing,
saving or selecting some text the issue shows up.
I have other setup of Stretch with MATE desktop and the problem isn't there.
I also compiled a clone of the geany github repo and I was able to reproduce the
problem (in Gnome).
(I filed a bug report to the debian package)
--
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/1532
For some reason I don't yet know, Travis fails fairly randomly building GP: I seen problems with `dh-marshal` (possibly due to out-of-tree build? but why is it random?) and now with WebHelper's enums (there doesn't seem to be an error but the enum types are missing (although they are present in Git).
--
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/650
I use geany with webhelper on debian 8.3 x 32.
On my previous PC (also with debian 8) I had the same problem but it disappeared after update of debian, geany and plugins.
Now I have new laptop with up-to-date debian and with the same problem. I have geany ver.1.26 and webhelper ver. 1.26+dfsg-1.
No difference which site or local html file I use, webhelper itself works great. But when I press web inspector button or choose 'inspect element' from right-click menu, geany immediately crashes.
If I start geany from terminal. after the crash I see:
> a@b:~$ geany
Segmentation fault
a@b:~$
Geany is the best lightweight IDE ever and I hope You'll help me to solve the problem.
TY in advance!
---
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/412
The current highlighting of dark blue (as opposed to black when not selected) is very difficult for me to see I imagine there's something I can edit, but there's nothing in the documentation and playing with brace_good in filetypescommon didn't appear to achieve much
Using geany 1241
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/885
Most likely the string doesn't make sense to be transalted
--
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/587
I'm using Geany 1.30.1 on Windows 7.
After happily editing a file over some time, suddenly Geany refuses to save it with this error message:
I know that Windows sometimes grabs a lock on a file when I'm just looking at it with another tool, but I am pretty sure that the only way I'm operating on this file since the last bootup of my machine, is by editing it in Geany. Still, for the safe side, I run the [Handle](https://technet.microsoft.com/en-us/sysinternals/bb896653) utility to see whether someone has a handle to either the file or the directory where the file is in - nothing. I also used Geany's "File/Properties" to check, whether maybe the file secretly became readonly; this is also not the case. Finally I turned on the gio_unsafe_save_backup and tried again, but same result. Note that it is a local file, so there can't be network issues involved either.
Then I tried "save as" with "rename", to store it under a new name in the same directory. This was refused with the same error message. I could see that the file got renamed, but still had the old content. This is weird: If the cause would be a directory lock, the rename should ALSO have failed.
Needless to say that it is not a disk space problem either.
I resolved the problem temporarily by using the following strategy:
1. Using "Save as" to save it to a completely different directory.
2. Copying the file back (on the command line)
3. Closing the Buffer in Geany
4. Reopening it
I then checked with my remaining open files in Geany. Modifying the buffer and saving, caused the same error with two of the files, while it worked fine with two others. One of the two where the error occured too, belonged to a different directory, while all the others - including those which could be saved - belonged to the same directory as the file where the problem occured initially.
I don't see yet in what respect the two files which did not have the problem, differed significantly from the two files where the problem occured.
Closing Geany, starting it, and I can continue editing like normal, but my feeling is that it will be only a question of time until the problem occurs again. Is there anything I can do to help the Geany developers to nail down the cause of this strange 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/1500