When typing in a rectangular selection (ie on a vertical column of lines) hits the break column the last line is broken and the vertical selection is destroyed so further typing only happens on that last line.
Until Geany supports discontiguous multiple selections its not possible to continue the multiple typing if all lines are wrapped, so probably best for line breaking to check for multiple selections and not do the break so the users typing continues on all the lines, then they can break manually.
--
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/2051
Doing so drops the rectangular selection, and there is no obvious correct behavior for line breaking with a rectangular selection. So, just don't do line breaking in this case.
Fixes #2051.
@elextr please test :)
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2135
-- Commit Summary --
* Don't perform line breaking in rectangular selection mode
-- File Changes --
M src/editor.c (2)
-- Patch Links --
https://github.com/geany/geany/pull/2135.patchhttps://github.com/geany/geany/pull/2135.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/2135
I noticed that sometimes, maybe when moving a line down with alt+page_down, strange characters appear. I use geany 1.33 (built on 2018-04-16 with GTK 3.22.30, GLib 2.56.1) on Lubuntu 18.04.
I managed to take screenshots, with ctrl+z and ctrl+y I could look at the changes:
After using ctrl+d to duplicate a line, I tried to move it down.
After pressing alt+page_down to move it down, it looked like this:
I pressed alt+page_down multiple times and the characters changed:
I'm not sure if the steps I described above are correct as I can't remember such a sudden situation exactly.
I do not know how to reproduce this. Also, geany never crashed when it happened.
--
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/2066
I've installed the spell check plugin, here on Linux. I see in its Preferences dialog one can specify the folder to place the dictionaries in.
>From [this page](http://plugins.geany.org/spellcheck.html) I read:
> On Windows, you might need to install the dictionaries (the files containing the information for spell checking) manually. First, you need to download the dictionary files for the languages you want, e.g. from http://extensions.services.openoffice.org/en/dictionaries. Be sure to download the "Spelling" archives from this site. The downloaded archive should contain one or more .dic and .aff files.
> Instructions:
> Download the archive you want to use
> The downloaded archive with the extension .oxt is actually a ZIP archive, so extract it as usual (e.g. with 7-Zip or another ZIP unpacker). Extract the contents into a folder of your choice, e.g. C:dictionaries
> Then open to the Spell Check plugin preferences dialog in Geany and choose the folder you just created. You may need to restart Geany and then the installed dictionaries should be available
Admittedly, that's for Windows, not Linux, but I thought the procedure would be similar for adding dictionaries in Linux. So I first pointed the plug in to my existing LibreOffice dictionary folder. From trying spell check, I saw it didn't register. Then I copied the LO dictionary folder over to the geany home folder, to avoid permissions and file lock, but that didn't work either.
Is there any way to load custom dictionaries for this plug in?
Thanks!
--
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/1627
Some users seem to not know about how `PATH` lookup works. I haven't gone back and found all the related issues, but I remember discussing/explaining it numerous times as part of what seem like unrelated issues. I also remember numerous occasions where users had problems where part of the troubleshooting has been to check whether the build command works on its own, outside of Geany, which is effectively the same topic.
I'm creating this issue as a reminder to revise the documentation to go into more detail on how this mechanism works and how to configure it on various platforms.
Also related, but perhaps deserving its own separate issue, I think it might be useful to incorporate @elextr's [Build Menu Tutorial](https://wiki.geany.org/howtos/configurebuildmenu) directly into the main user manual as well.
--
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/2131
This prevents Geany from failing to run when it can't find the Glade/GtkBuilder UI for whatever reason.
Fixes #1702 indirectly.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1703
-- Commit Summary --
* Use GResource to load GtkBuilder XML UI file
-- File Changes --
M .gitignore (1)
M configure.ac (1)
M data/Makefile.am (5)
A m4/geany-gresource.m4 (7)
M src/Makefile.am (27)
A src/geany.gresource.xml (6)
M src/libmain.c (3)
M src/ui_utils.c (27)
-- Patch Links --
https://github.com/geany/geany/pull/1703.patchhttps://github.com/geany/geany/pull/1703.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/1703
when compiling......process failed(the system cannot find the file specified)
why??????????
Windows 8.1 64bit
Geany 1.26
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/766
The "Language Files" option of the Windows' installer only disables language files for Geany, but not for Gtk runtime. As a result, the installation takes 68.7 MB, 33.5 MB (49%) of which are MO files of Gtk in "share/locale" folder. However, the real issue is not the disk space but the fact that the interface becomes partially translated.
The same problem is with the installer for plugins.
--
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/2090
Two consecutive "go to matching brace" commands have to return us to the original position. After we moved to the matching brace, we still should see the same brace pair highlighted. All Scintilla-based editors have the problem. Scintilla doesn't necessarily return us to the initial position after the subsequent matching brace jumps. After the first jump Scintilla often highlights nearby brace pair. It is so because Scintilla attempts to place the cursor following to outside or inside braces logic. However, when the cursor is between two braces, Scintilla highlights only the first, left brace.
I will provide with two examples. (bold+italic parenthesis indicate the highlighted braces. The exclamation sign indicates the cursor position. )
First example: ( )( )
Place the cursor after the last brace:
( )_**( )!**_
do twice "go to matching brace" and we see the cursor before the fist brace.
**_!( )_**( )
Second example: (((( f1+1 )^f2)+( f3+1 ))^f4)
Place the cursor after the second brace.
(**_(!_**(( f1+1 )^f2)+( f3+1 )**_)_**^f4)
do twice "go to matching brace" and we see where the cursor is .
(((( f1+1 )^f2)+**_!(_** f3+1 **_)_**)^f4)
People who are used to work with other editors are confused. As a workaround, I made a LUA script that goes to matching brace and always keeps the same braces highlighted. (https://github.com/dyura/LUA-scripts-for-text-editors/blob/master/Geany/GoT…)
At the same time, I think that this problem should be solved at the project level.
--
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/1998