Try different file saving settings, see
[this](https://wiki.geany.org/config/all_you_never_wanted_to_know_about_file_saving)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Geany is changing the group ownership of my file to the user owner when saved.
This is only happening in Ubuntu 16.04 with a file over sftp.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> In practice, this seems to lead to no change if the Python function doesn't
> return, but allows it to return a value that will be passed along.
Yeah, I don't mind if this gets merged as is (once tested), and improve the
other stuff later. I'd be interested to hear @kugel-'s thoughts since I
> The only question is whether the semantics make any sense, as in whether
> returning nothing in the Python function should default to returning `FALSE`
> to Geany. The [API
> Reference](https://www.geany.org/manual/reference/keybindings_8h.html#afb2861d240a298186fe4d84430e5066f)
> makes it
The highlighting is done by lexers that are part of the Scintilla editing
component Geany uses, which is a separate [project](https://www.scintilla.org).
Test highlighting problems in the Scite reference editor for Scintilla if you
can, report them directly to Scintilla (NB Geany uses version
Geany wrongly colors sequences starting with a percentage sign (%).
Program that illustrates some issues:
```
n = 1337;
w = r = 5
x = n%w + 1; # "%w " is recognised as the beginning of an array of words, like
%w[ ... ]
y = n%r ; # "%r " is recognised as the beginning of a regular expression
Sorry, I have stopped working on this, and I probably should have said
something. If someone else wants to go forward with this, hopefully the gist I
linked to above which shows how to enable the scintilla feature would be
helpful.
> On Jan 4, 2019, at 10:41 AM, João Paulo Pulga
> wrote:
>
This is somehow related to #810
Currently the templating works via a huge struct defining variables to handle
different situations inside processing the input. It would be awesome to have
more template-like way of defining it to better split between templates and
processing code -- maybe
Right now the template definitions are hard coded inside C-code. Would be a
good point to have this in some kind of configuration file for easy
access/change/extension
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
