Re: [Github-comments] [geany/geany] Geany is changing the group ownership of remote file (stfp) when saved. [Ubuntu 16.04] (#2039)

2019-01-05 Thread elextr
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:
https://github.com/geany/geany/issues/2039#issuecomment-451721634

[Github-comments] [geany/geany] Geany is changing the group ownership of remote file (stfp) when saved. [Ubuntu 16.04] (#2039)

2019-01-05 Thread deanresin
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:
https://github.com/geany/geany/issues/2039

Re: [Github-comments] [geany/geany-plugins] geanypy: Use Python callback return value for keybindings return value (#809)

2019-01-05 Thread Matthew Brush
> 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 think 
he wrote this code, or at least looked at it more recently than me I think.

-- 
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/809#issuecomment-451696882

Re: [Github-comments] [geany/geany-plugins] geanypy: Use Python callback return value for keybindings return value (#809)

2019-01-05 Thread Colomban Wendling
> 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 sound like this is not the normal case.

It's a good question, but it will always be better than the current situation 
that returns a more or less random value -- I'm not sure if it's undefined or 
implementation defined behavior, but GCC seems to return 0.
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.

If you want returning `True` as the default case, I'm not sure what the best 
solution is but maybe simply assuming `None` means *"didn't return a value"* 
might be good enough, as it's the default return value, and not a valid value 
for an explicit return.

> It may be useful in either case to improve [the 
> doctstrings](https://github.com/geany/geany-plugins/pull/809/files#diff-8c19fc53e5ac665274c8ae6877c63a84L145)
>  to clarify this, as a separate change if need be.

Yep, definitely.

-- 
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/809#issuecomment-451696211

Re: [Github-comments] [geany/geany] Ruby wrong syntax highlighting (#2038)

2019-01-05 Thread elextr
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 3.10 not version 
4 when you report, but that should not affect the Ruby lexer).  Geany devs are 
not Ruby experts, better for you to directly communicate with the lexer 
maintainer.  Please post the issue number here for tracking.

-- 
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/2038#issuecomment-451692721

[Github-comments] [geany/geany] Ruby wrong syntax highlighting (#2038)

2019-01-05 Thread Niboucha Redouane
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
string = %= this is a string = ;  # this one is correctly colored
n %= w;  # this is the most important issue, the expression is equivalent to n 
= n % w; but it's recognised like the previous line
print x%r  # %r is also recognised like a beginning of regex, but in this case, 
the %= of the previous line is still not terminated (no equal sign encoutered).
```

Tested on Geany 1.33 on Linux (Debian).

-- 
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/2038

Re: [Github-comments] [geany/geany] Multiple carets, selections, insertion points and paste (#1141)

2019-01-05 Thread Ryan Wiedemann
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:
> 
> Any news in this? I will like to see this feature in Geany
> 
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.


-- 
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/1141#issuecomment-451680217

[Github-comments] [geany/geany-plugins] Tableconvert: Improve template system (#811)

2019-01-05 Thread Frank Lanitz
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 something Jinja-based or similar. 

-- 
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/811

[Github-comments] [geany/geany-plugins] Tableconvert: Move template definitons into configuration files (#810)

2019-01-05 Thread Frank Lanitz
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:
https://github.com/geany/geany-plugins/issues/810