What locale is your system using? Does the problem persist if the locale is
xx.UTF8?
--
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/2748#issuecomment-775571895
Sorry I didn't mean to say you had to build Geany as well, I was just saying
that the build dependencies for Geany seems to satisfy the build dependencies
for Geany-plugins. Although note that some individual plugins have additional
requirements and the plugin is disabled if not met, but the bu
v.1.37.1 on Win 10 (latest updates).
Steps to reproduce:
1. Create new text file tmp.txt.
2. Add "Lorem ipsum dolor sit amet," to the body and save.
3. (Optionally confirm UTF-8 encoding, this does not seem to be an internal
encoding issue.)
4. (Optionally -- reopen file to confirm it is working
@frlan commented on this pull request.
> @@ -87,7 +87,7 @@ static const gchar *translators[][2] = {
{ "sv", "Tony Mattsson " },
{ "sr", "Nikola Radovanovic "},
{ "tr", "Gürkan Gür "},
- { "uk", "Boris Dibrov
Ok, didn't know I needed to build Geany as well, I thought plugins build
process was independent from the main application's build.
Anyway, I had to install `libglib2.0-dev` together with `intltool`.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directl
Did you build Geany?
For me on Mint 20 having installed some build basics to make geany the plugins
"just works".
Since your autogen.sh didn't succeed because you need intltools I'm not
surprised that configure failed, synaptic tells me I have intltool and
intltool-debian packages installed.
Trying to build plugins on Mint 20.
Installed so far:
`autoconf automake libtool`
`./autogen.sh` returns the error: `./autogen.sh: 4: intltoolize: not found`
Instead, running `./configure` after having successfully run `autoconf` in the
root folder, gives the error:
```
./configure: line 1974: s
> I'm not very comfortable pretending a +30k -7k change still is 1.37.
Well branch the 1.37.2 off the commit before ctags maybe.
--
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/2747#issue
> Given the "only" other change is we have a new ctags
I don't think I'm gonna put the new ctags in a point release; although it's
fairly minor from a user perspective, I'm not very comfortable pretending a
+30k -7k change still is 1.37.
--
You are receiving this because you are subscribed to