Hello,
I want to know how I can disable CSS completion ? I hate this ^^
Also, I do'nt know if this is a completion. But when I write "border" for example, I've a list with all border in CSS file. I wish that this list does not appear.
Thank.
On Tue, 07 Apr 2009 12:57:06 +0200, jerome wrote:
Hello,
I want to know how I can disable CSS completion ? I hate this ^^
Also, I do'nt know if this is a completion. But when I write "border" for example, I've a list with all border in CSS file. I wish that this list does not appear.
just disable auto-completion of symbols in the preferences dialog, Editor tab, Completions tab, "Automatic Symbol completion".
Regards, Enrico
Enrico Tröger a écrit :
On Tue, 07 Apr 2009 12:57:06 +0200, jerome wrote:
Hello,
I want to know how I can disable CSS completion ? I hate this ^^
Also, I do'nt know if this is a completion. But when I write "border" for example, I've a list with all border in CSS file. I wish that this list does not appear.
just disable auto-completion of symbols in the preferences dialog, Editor tab, Completions tab, "Automatic Symbol completion".
Regards, Enrico
Geany mailing list Geany@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany
If I disable completion, my others types of file (PHP, SQL, etc.) is affected, but I want disable symbol just for CSS file.
It's possible ?
On Wed, 08 Apr 2009 11:41:34 +0200 jerome mister.jerome@gmail.com wrote:
If I disable completion, my others types of file (PHP, SQL, etc.) is affected, but I want disable symbol just for CSS file.
It's possible ?
From my best knowledge its not possible to toggle this based on used
filetype without patching Geany.
Regards, Frank
I find Geany constantly performing expansions of the words 'for' and 'if' whenever I try to write a plain-text email, or when I'm inside a code code comment block. It would be nice to tell Geany "Don't help me when I'm writing this kind of code".
I would love to see something like Textmate's scope-based completion here. You can achieve this in TM by specify snippets in the "source.c" scope, which presumable ignores expansions inside "source.c.comment" (or "comment.c").
But easier said than done: to implement scopes you would have to piggyback on the Scintilla lexer, generating the scopes while it does highlighting, or map the scopes to the lexer output after it has done its work.
On the up-side, a scope system would unlock a world of possibilities for per-scope build commands, shortcut keys, snippets, syntax, highlighting, and indentation rules. For instance, you can customize the indentation in "source.php" and have those rules apply to all the PHP blocks embedded in HTML documents. It's quite powerful.
Best, Maris