I have installed and activated the spell check plugin. However, the misspellings get not updated automatically on modifying one's text. For example, if I type a misspelled word, it does not get marked with the red curly underline. The only way to get it marked is to switch the language, e.g. back and forth, or simply by clicking Tools -> Spell Check -> Default (en_GB) (assuming writing in English). Al new misspellings get only marked if I switch the spell check language again.
--
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/988
If I open a second instance of Geany, copy something to the clipboard, close that instance, and then try and paste into that second instance, nothing happens. This is using the drop-down menu, the context menu, and ctrl+v.
However, I can then paste into other applications and it works fine.
So somehow there is some issue with Geany accessing clipboard data from a closed version of itself that other applications don't suffer.
--
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/2503
Hi,
I'm using Ubuntu 20.04 with the dark theme, but the compiler output is difficult to read.
Can I fix that?
--
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/2520
make err:
src/UniqueString.cxx:31:1: error: function 'Scintilla::UniqueStringSet::UniqueStringSet()' defaulted on its redeclaration with an exception-specification that differs from the implicit declaration 'Scintilla::UniqueStringSet::UniqueStringSet()'
UniqueStringSet::UniqueStringSet() noexcept = default;
^
Makefile:972: recipe for target 'src/UniqueString.lo' failed
make[3]: *** [src/UniqueString.lo] Error 1
make[3]: Leaving directory '/home/sugon/geany.git/scintilla'
Makefile:996: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/sugon/geany.git/scintilla'
Makefile:583: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/sugon/geany.git'
Makefile:468: recipe for target 'all' failed
make: *** [all] Error 2.
Env:
Linux localhost.localdomain 3.10.0-2.nd7.33.mips64el #1 SMP PREEMPT Mon Mar 25 14:44:24 CST 2019 mips64 mips64 mips64 GNU/Linux
g++ (GCC) 4.9.3 20150626 (NeoKylin 4.9.3-3)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
gcc (GCC) 4.9.3 20150626 (NeoKylin 4.9.3-3)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
--
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/2518
geany -V: geany 1.35 (kompiliert am 2019-07-01 mit GTK 3.24.8, GLib 2.60.2)
pkg-config --modversion gtk+-3.0: 3.24.10
pkg-config --modversion gtk+-2.0: 2.24.32
uname -r: 5.2.11-arch1-1-ARCH
I try to explain it: In geany the underline is not visible its shown as a space. If you open the same
text in an other editor the underline is present.
With this bug its impossible to use geany as an editor, especially not as a developement tool.
e.g.:
original: BASH_CMDS: a bash_variable
geany: BASH CMDS: a bash variable
hex-editor: 42 41 53 48 5F 43 4D 44 53 3A 20 61 20 62 61 73 68 5F 76 61 72 69 61 62 6C 65 0A
Kind regards, Walter
--
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/2287
Adds the CMark source into the plugin tree to be used when there is no `libcmark` package available using `pkg-config`. At present, my distro only ships the `cmark` utility but not the accompanying library or development packages, as well I do not believe msys2 provides a CMark package for Windows, so for now it will remain embedded as a backup.
The version embedded is v0.28.3, from commit 9f8ef820301951f36301c1a40d036cafeaa78619. A few trivial changes were made to allow libcmark to compile without its original CMake infrastructure. Only `cmark.h` and `cmark_version.h` were modified.
TODO: create a patch so the simple changes to upstream CMark library can be mechanically applied to newer versions.
All future complaints/requests about supporting various Markdown extensions should be addressed directly to the [CommonMark Project](http://commonmark.org/).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/747
-- Commit Summary --
* Markdown: replace Discount and PEG Markdown with CMark
-- File Changes --
M build/markdown.m4 (54)
M markdown/.gitignore (3)
M markdown/Makefile.am (8)
A markdown/cmark/COPYING (170)
A markdown/cmark/Makefile.am (43)
A markdown/cmark/blocks.c (1218)
A markdown/cmark/buffer.c (279)
A markdown/cmark/buffer.h (82)
A markdown/cmark/case_fold_switch.inc (4327)
A markdown/cmark/chunk.h (120)
A markdown/cmark/cmark.c (43)
A markdown/cmark/cmark.h (647)
A markdown/cmark/cmark_ctype.c (44)
A markdown/cmark/cmark_ctype.h (26)
A markdown/cmark/cmark_version.h (7)
A markdown/cmark/commonmark.c (475)
A markdown/cmark/config.h.in (76)
A markdown/cmark/entities.inc (2138)
A markdown/cmark/houdini.h (51)
A markdown/cmark/houdini_href_e.c (100)
A markdown/cmark/houdini_html_e.c (66)
A markdown/cmark/houdini_html_u.c (149)
A markdown/cmark/html.c (341)
A markdown/cmark/inlines.c (1342)
A markdown/cmark/inlines.h (21)
A markdown/cmark/iterator.c (121)
A markdown/cmark/iterator.h (27)
A markdown/cmark/latex.c (453)
A markdown/cmark/main.c (189)
A markdown/cmark/man.c (252)
A markdown/cmark/node.c (858)
A markdown/cmark/node.h (93)
A markdown/cmark/parser.h (39)
A markdown/cmark/references.c (146)
A markdown/cmark/references.h (41)
A markdown/cmark/render.c (185)
A markdown/cmark/render.h (50)
A markdown/cmark/scanners.c (13513)
A markdown/cmark/scanners.h (55)
A markdown/cmark/scanners.re (320)
A markdown/cmark/utf8.c (317)
A markdown/cmark/utf8.h (24)
A markdown/cmark/xml.c (170)
D markdown/peg-markdown/LICENSE (88)
D markdown/peg-markdown/Makefile.am (29)
D markdown/peg-markdown/README (1)
D markdown/peg-markdown/README.markdown (213)
D markdown/peg-markdown/markdown_lib.c (181)
D markdown/peg-markdown/markdown_lib.h (27)
D markdown/peg-markdown/markdown_output.c (1121)
D markdown/peg-markdown/markdown_parser.leg (774)
D markdown/peg-markdown/markdown_peg.h (72)
D markdown/peg-markdown/odf.c (181)
D markdown/peg-markdown/odf.h (11)
D markdown/peg-markdown/parsing_functions.c (117)
D markdown/peg-markdown/parsing_functions.h (17)
D markdown/peg-markdown/peg-0.1.9/Makefile.am (10)
D markdown/peg-markdown/peg-0.1.9/compile.c (717)
D markdown/peg-markdown/peg-0.1.9/leg.c (1209)
D markdown/peg-markdown/peg-0.1.9/leg.leg (292)
D markdown/peg-markdown/peg-0.1.9/tree.c (352)
D markdown/peg-markdown/peg-0.1.9/tree.h (108)
D markdown/peg-markdown/peg-0.1.9/version.h (3)
D markdown/peg-markdown/utility_functions.c (206)
D markdown/peg-markdown/utility_functions.h (74)
M markdown/src/Makefile.am (15)
M markdown/src/viewer.c (36)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/747.patchhttps://github.com/geany/geany-plugins/pull/747.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-plugins/pull/747
To make the support of 4k-monitors on Windows perfect, only larger toolbar icons would be needed. Maybe a set of the doubled size that simply could be selected in the preferences would be sufficient, if the detection of a 200% zoom level is not possible yet.
--
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/1957
I wrote a script (with a companion C program) to list the Scintilla lexer properties.
I think it would be good if we would document the properties so users get an overview of the available properties.
So far I couldn't make up my mind how and where to use this information best.
A few ideas:
1. bundle the script and program with Geany in the `scripts` folder and use it to generate a copy&paste ready snippet for the main documentation (to be inserted at https://www.geany.org/manual/index.html#lexer-properties-section)
2. put the script, program and the resulting data in the wiki and add a link in the main documentation
3. something else
Generated list of properties (format can be adjusted according to the target use):
https://gist.github.com/eht16/bcc86f9bd2970099f2025a759c28c83b
Any opinions?
--
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/2517