Oops! From the time when I registered the highlighting for SCSS I remembered
only that I needed to copy the syntax file. Sorry about the false alarm.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I have copied syntax for C (filetypes.c) to filetypes.zsc.conf. However, when I
open a file with zsc suffix, there is no syntax highlighting. I know that their
(C and ZScript) syntax is close enough, and when I select the filetype manually
through the menu, the highlighting is working. I have
How real is this opportunity?
I know VS Code and Rider exist, but in the end I always go back to Geany
--
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/talks/issues/7
@codebrainz, @elextr, thanks, I didn't know that this option was also in
Project Properties and it overrode the one in "general" preferences.
Sorry about the insufficient information, usually I try to provide more
detailed info, I guess I was getting sleepy. Anyways, the "issue" was with me
Closed #2310.
--
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/2310#event-2652450441
In Preferences -> Files there is an option "Ensure new line at file end" that,
as far as I understand, is supposed to enable/disable adding of a new line in
the end of the file if the last line is not empty. However, even when this
option is disabled (unticked), if the last line is not empty
Currently when the option "invert syntax highlighting colors" is on and you
send a document to printer, white text on white background is printed. I
understand the part about [the background is deliberately forced to white to
avoid emptying the black toner
So that someone has a specific plan?
--
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/1854#issuecomment-387088294
> To be frank, Geany's autocompletion is very stupid and has no language
> specific understanding (for example name visibilities and scopes or non-top
> level names), it should not be the trigger for language specific
> autocompletions, they should replace the Geany autocompletion. I mostly run
> I would strongly suggest that the plugin should be shown to work first,
> before you worry about interacting with settings in Geany.
Why? Currently it works ok by way similar what I proposed here (except fact
that it counts chars, not receives notify like GEANY_DISPLAY_AUTOCOMPLETE)
But
> My understanding is that the plugin will get notified of characters the user
> types by the editor-notify signal, when it has a suitable sequence of
> identifier characters its sends those to the language server to get what
> possible autocompletes are available at that position. When the
> I meant how can Geany know WHEN to notify the plugin?
Then Geany displays built-in autocompletion window. Or I isn't understand
something?
(Topic can be changed to "Autocompletion plugins support"?)
--
You are receiving this because you are subscribed to this thread.
Reply to this email
> I still don't understand, how can Geany notify the plugin of anything for
> autocompletion?
I am isn't know. It is possible to emit notify like SCN_CHARADDED? Something
like GEANY_DISPLAY_AUTOCOMPLETE?
Plugin will be able to listen for this notify and display its own dialog
instead of
This is second option if it is impossible to add notify for start of
completion/tips dialog displaying. Although it would be more correct to have
this notify.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> Its probably going to be easier to just have your own autocomplete dialog
Ok, but at least it is need to add notify for start of dialog displaying.
> the Geany version is provided by Scintilla, but populated by Geany, and is
> strongly linked to Geany's tags and symbols mechanism that you
> thats a good idea, even if initially the user had to manually turn off Geany
> autocompletes in prefs it would allow the plugin to be developed fully
> standalone to show its usability, and then a later improvement could allow
> the plugin to shut down Geany autocompletes.
May be just add an
> It's theoretically possible for a plugin to force and keep off Scintilla's
> (very basic) auto-complete list and replace with a better one using plain
> GTK+ calls.
Currently my plugin listen on_editor_notify and checks if SCN_CHARADDED is
occured. Is there some other mechanism? I'm not very
So, if someone write a suitable patch and no one does discussed about it, it
will be accepted?
--
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/1854#issuecomment-386882025
I saw that a year ago there was a discussion of this in mailing list. It ended
with nothing?
--
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/1854#issuecomment-386869010
It is possible to add it?
--
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/1854
@elextr, @b4n - thanks!
--
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/1708#issuecomment-349093367
It can't be called problem that is totally on the Geany side, because something
is definitely wrong with the file, but still, less and cat can read it and
micro can read and edit it. Geany at first can't open the file at all.
One of the things that are wrong is that the file does not end with a
I want API for plugins!
May be just do it as copy and paste from any other IDE plugin API? And tag it
as experimental.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Oops. Thanks, I'm completely new to this.
--
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/1429#issuecomment-286762758
Then perhaps this issue should be renamed (is it possible?) or a new one
created with a name more directly related to transferring from nested submenus
to a searchable list?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> Ok, makes more sense, but somebody has to do it.
Well, unfortunately I'm not a programmer, so if no one from the Geany team is
willing to handle it, then I suppose I have to close the issue now.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
I'm sorry, but there seems to be a miscommunication.
>> Probably if on pressing "Reload as" or "Set encoding" a flat list
>
>There can be a lot of encodings, a flat list is likely to be too big for small
>screens like laptops.
I wrote
> Probably if on pressing "Reload as" or "Set encoding"
Then I guess it's more of a feature request: selection of the encoding (for
both "Reload as" and "Set encoding") could be improved: right now it requires
wading through submenus: Document -> Set encoding -> $Group (West European,
East European, etc.) -> $ActualEncoding. Or File -> Reload as ->
I noticed this bug when I received a text file that Geany opened as something
unreadable, but I found out that it is easily reproducible.
Let's say I create a file test.txt with some cyrillic content. For example,
just one word "Тест", which is "Test" in Russian. Of course, it's two lines:
the
29 matches
Mail list logo
