`async` and `await` are Python keywords since Python 3.5, however, they are not highlighted as such in 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/geany/issues/1351
It would be useful to be able to place the message window on the left as currently Geany only allows placing it on the right or bottom of the screen. Whereas the sidebar can be placed on either side of the screen.
--
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/1719
Hello,
While trying operator overloading in Rust, I see some unexepected behaviour of Geany. For a structure called ComplexNumber, the implementation of Add and Mul require separate implementation blocks. I expected that Add and Mul would be listed together with print and magnitude. If I try operator overloading in a similar way in C++, the member functions get nicely grouped below the name of the structure, even if they are defined in separate blocks. See the picture and the attached Rust example.
use std::ops::{Add,Mul};
#[derive(Debug,Copy,Clone)]
pub struct ComplexNumber {
r : f64,
j : f64
}
impl Add for ComplexNumber{
type Output = ComplexNumber;
fn add(self, rhs: ComplexNumber) -> ComplexNumber {
ComplexNumber {r: self.r+rhs.r, j: self.j+rhs.j}
}
}
impl Mul for ComplexNumber{
type Output = ComplexNumber;
fn mul(self, rhs: ComplexNumber) -> ComplexNumber {
ComplexNumber {r: self.r*rhs.r-self.j*rhs.j, j: self.r*rhs.j+self.j*rhs.r}
}
}
impl ComplexNumber {
fn print(& self) {
print!("{}+{}i ",self.r,self.j);
}
fn magnitude(& self) -> f64 {
(self.r.powi(2)+self.j.powi(2)).sqrt()
}
}
fn main()
{
let a = ComplexNumber {r: 1.0, j: 0.0};
let b = ComplexNumber {r: 0.0, j: 1.0};
let c = a + b;
let d = a * b;
let e = c + d;
c.print();
d.print();
e.print();
print!("{} ", e.magnitude());
}
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/728
This is a sister implementation for "k" in order to behave like "j" when wrapping is on (see #748). The problem with the current implementation is that "k" moves caret to the last line of a wrapped line instead of the first one like "j".
@pcworld Can you check if it looks good to you? This one is a bit more complex because one has to either "iterate" over the wraps when going up (for the first line only) or go to the previous line and go down.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/754
-- Commit Summary --
* vimode: When wrapping is on, "k" should go to the first line of wrapping
-- File Changes --
M vimode/src/cmds/motion.c (48)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/754.patchhttps://github.com/geany/geany-plugins/pull/754.diff
--
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/754
SCI_LINEDOWN goes down only one display line, hence when line wrapping
was enabled and a line wrapped over more than two lines, it was
impossible to go to the next actual line when pressing j.
Note that this still doesn't emulate vim behavior correctly where
caret-x position is saved for actual lines and not display lines. But
this change at least makes j go the next line when wrapping is enabled.
Note that I'm not completely sure whether this change retains all workarounds [mentioned in `cmd_goto_up`](https://github.com/geany/geany-plugins/blob/341cab4e13c122b2b74e6f31a43be9adc653f8af/vimode/src/cmds/motion.c#L51-L54).
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/748
-- Commit Summary --
* vimode: Fix goto_down with line wrapping
-- File Changes --
M vimode/src/cmds/motion.c (2)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/748.patchhttps://github.com/geany/geany-plugins/pull/748.diff
--
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/748
I installed the latest geany on my windows 7 machine a couple days ago. When I type anywhere on the program that text can be typed, it appears in one the the Japanese alphabets (katakana). The encoding in the program is set to UTF-8. No matter what I change the encoding to, it is still typing in katakana.
My windows 7 is set to English US. I have no idea how to get it to type in english using roman character.
I do have a Japanese keyboard set so I can type in Japanese when need be, but it has never been an issue.
99% of the time I'm not typing in Japanese anyways.
When you type in japanese, it is phoenetic. To make a syllable you need to type "t" + "a" to get "ta"->た. and that is hiragana.
When I try typing in geany, i get katakana characters showing up even if I press one key. My Japanese keyboard is not set to do that anyways.
Any ideas how I could fix this?
Thank you.
--
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/1785
On my computer:
Windows 8.1 x64. there version do not work but version 1.29.9 work.
(include changing of compatibility)
--
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/1454
When I push the text size up to the limit using <b>control+mouse wheel</b> and then do a word completion, the choice seem to be truncated.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/702