The developers of the GTK GUI library Geany uses (and indeed the C language it
uses) have in their wisdom decided that programs must always follow the locale
set by the LANG environment variable and do not allow program control. The
concept of wanting, for example, an IDE in English to match
I can confirm that this is the correct form.
--
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/2871#issuecomment-913039436
@eht16 Thanks for giving it a try. Yeah, the find changes should do nothing on
Windows but the updated readtags library might so good to know it didn't cause
any problems.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@Skif-off
“Зацикливать поиск по документу” is the most appropriate translation for
“Always wrap search”.
`Find` also will try to find from the end when searching backwards.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
`Зацикливать поиск`? These are different things.
We have two ways: from the beginning or from the current place. Without cycles.
> Продолжить поиск с начала / конца?`
What logic? In this window we will see two buttons: `Cancel` and `Find`.
`Cancel` is a cancel, `Find` will try to find from the
https://github.com/geany/geany/blob/41624c411702d29834da0ff926f3c9f7c895bb47/po/ru.po#L340
Should be: `msgstr "Зацикливать поиск по документу"`
https://github.com/geany/geany/blob/41624c411702d29834da0ff926f3c9f7c895bb47/po/ru.po#L344
Should be: `msgstr "Зацикливать поиск по документу"`
@eht16 That’s right. I was looking through all settings and didn’t recognize
this option because of its incorrect Russian translation: “Всегда искать с
начала файла”. Correct would be “Зацикливать поиск по документу”. Another
problem is that there is no obvious way to change UI language in
Closed #2887.
--
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/2887#event-5256424440
We already got that feature: enable "Always wrap search" in the preferences
dialog.
--
You are receiving this because you are subscribed to this thread.
Reply to
LGTM, compiled and tested on Windows (even the change in the `find` command is
not relevant there) and still works fine.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
It would be better to add to the search and replace dialog an option whether to
wrap around the document (continue from the beginning when the end is reached
and vice versa). Asking it each time is inconvenient and makes Geany unusable.
--
You are receiving this because you are subscribed to
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/1108
-- Commit Summary --
* SpellCheck: Add notes about maintaining personal dictionaries
-- File Changes --
M spellcheck/README (18)
-- Patch Links --
> Agreed, would you mind extending this PR?
@eht16 yeah, sure, I will do it on Monday.
--
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/pull/1106#issuecomment-912961664
> > how do you build Geany? I assume in a Mingw64 shell against
> > "mingw-w64-x86_64-*" packages? I'm wondering why it didn't crash for me.
>
> @eht16 yeah, I have built Geany from Mingw64 shell against /mingw64/lib and
> /mingw64/include, i.e against mingw-w64-x86_64 packages. I recently
> how do you build Geany? I assume in a Mingw64 shell against
> "mingw-w64-x86_64-*" packages? I'm wondering why it didn't crash for me.
@eht16 yeah, I have built Geany from Mingw64 shell against /mingw64/lib and
/mingw64/include, i.e against mingw-w64-x86_64 packages. I recently changed my
This is the corresponding PR to Geany https://github.com/geany/geany/pull/2590
to switch the Windows builds to x86_64 and GTK3.
Main changes:
- the GTK (and other dependencies) bundle is now created for the x86_64 platform
- the new parameter -x allows to run script on a Linux system using
The long line marker can only be displayed properly when using a fixed width
font, i.e. a monospace font.
For all other font types, each columns might have a different width and so
there is no fixed vertical line possible across multiple lines.
If you choose a monospace font, I assume the long
Ubuntu regular is not a monospaced font, so there is no specific pixel position
to draw a vertical line that is the same column in all lines, it depends on the
content of the line. IIRC the position used is a line of spaces which will
compress in a non-monospaced font.
If you really want to
Closed #2886.
--
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/2886#event-5256363161
Tested on Windows, also against a x86_64 build and works.
However, Geany didn't crash on my system without the change. I still consider
the change as correct.
@vlvlbel for my curiosity, how do you build Geany? I assume in a Mingw64 shell
against "mingw-w64-x86_64-*" packages? I'm wondering
I am currently running Geany 1.36 on Linux Mint.
It seems that the column size doesn't scale properly, or possibly at all, when
you change your font size or font face.
I changed my editor font to Ubuntu Regular 14pt and found that the drawn line
from Long line market, set at 72 columns, drew
21 matches
Mail list logo
