Please consider adding snippets to word completions so that when I want <b>lambda</b> acted on as a snippet, I would be able to type <b>lam</b>, choose from the possible completions, and then if I chose <b>lambda</b> from the list with the <b>tab</b> character, the snippet would be completed to get <b>𝝺</b>
Thanks for your consideration of this matter.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/717
The following crash happened recently several times without noticeable reason:
It's Geany 1.25 on Windows, Java 1.7
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/795
…and fix the current documentation not to lie to the reader :)
AFAIK this still isn't configurable by color shemes (IIUC only *named styles* and *named colors* are supported), but not configurable at least from *filetypes.common*.
@codebrainz assigning to you as I would thing you are the most colorscheme-literate of us.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/917
-- Commit Summary --
* Fix documentation about translucency settings
* Make the search marker translucency configurable
-- File Changes --
M data/filetypes.common (9)
M doc/geany.txt (22)
M src/highlighting.c (6)
-- Patch Links --
https://github.com/geany/geany/pull/917.patchhttps://github.com/geany/geany/pull/917.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/917
Hi,
in Geany 125 ("Veed") there is a typo in the LaTeX code completion
The command \Longleftrightarrow is misspelled as \Longlettrightarrow
This error actually persists since several years :-)
Interestingly enough, the same bug was found in Kile https://bugskdeorg/show_bugcgi?id=136961
Could be that they started from the same databases for code completion
Thanks for correcting that
N
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/888
Lex Trotman wrote
> Yes **untitled.xxx (where xxx is the file extension)
> has to be in the first three lines and only the
> first occurrence is replaced**. *This has nothing to do
> with templates, its a new-file save feature, and it
> does not appear to be documented,* **can you raise an
> issue so its not forgotten.**
More at http://news.gmane.org/gmane.editors.geany.general
11 nov 08:36 2015 Lex Trotman [Geany-Users] Geany templates
From: Lex Trotman <elextr@...>
Subject: Re: [Geany-Users] Geany templates
Newsgroups: gmane.editors.geany.general
Date: 2015-11-11 07:36:03 GMT
Richard H
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/753
I have no autocomplete functionality at all. This is repeated on two different machines with identical versions: geany 1.25, GTK 2.24.28, Glib 2.44.1, Xfce 4.12, Linux 4.2.3-1-ARCH
Tried with java, python, bash, and html.
No plugins are installed and autocomplete is turned on in preferences:
Geany starts without any errors:
$ geany -v
Geany-INFO: Geany 1.25, en_US.UTF-8
Geany-INFO: GTK 2.24.28, GLib 2.46.1
Geany-INFO: System data dir: /usr/share/geany
Geany-INFO: User config dir: /home/magyar/.config/geany
Geany-INFO: System plugin path: /usr/lib/geany
Geany-INFO: Added filetype Cython (61).
Geany-INFO: Added filetype Clojure (62).
Geany-INFO: Added filetype CUDA (63).
Geany-INFO: Added filetype JSON (64).
Geany-INFO: Added filetype Scala (65).
Geany-INFO: Added filetype Genie (66).
Geany-INFO: Added filetype Graphviz (67).
Geany-INFO: unknown : None (UTF-8)
Syntax highlight works just fine:
But no autocomplete.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/710
For a verilog file, the variables list parses the old (1995) style verilog module declarations. Verilog 2001 enhanced the syntax and seems to confuse Geany....
1995 syntax:
module (foo, bar, buz);
input foo; // foo port
output bar; // bar port
output buz; // buz port
reg buz; // buz variable
2001 syntax:
module (
input wire foo, // foo port is a wire
output wire bar, // bar port is a wire
output reg buz // buz port is a variable
);
// note: the "wire" is optional and the ports could have been declared with or without
Geany variables list seems to get confused by the 2001 style. It seems to parse the wire keyword as the variable name if I keep the optional "wire" keyword:
If I omit the "wire" keyword, Geany still gets confused, but in a different way. It seems to parse every other variable and then parse the "input" or "output" keywords as variables in some cases:
If someone who knows the code base can even point me to the module(s) doing the parsing for the variables, I may be able to help create the fix/enhancement for this. I'd be happy to try anyway. I am not familiar with the Geany code base so just getting started seems like an insurmountable task.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/670
@techee would you be opposed to this if I were to make a pull request? I remember you said before you never implemented it because you wanted to keep the plugin simple [citation needed], but if I were able to make a simple enough patch that used GFileMonitor to watch the top directory, would be OK with it?
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/332