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
I'm using Geany 1.30.1 on (German) Windows 7.
What puzzles me is, that the Geany user interface shows a mixture of English and German. The Menu (File, Edit, Search, ...) is completely in English, but the toolbar below is mostly in German, but with English interspersed (Saying "Neu", "öffnen", "Speichern", "Save All", "Zurücksetzen" (whatever this means), "Schließen", "Zurück", "Vor", "Compile", "Build", "Ausführen").
I understand that Geany uses GTK+ to present itself, and that it is a bit difficult to persuade a GTK+ Application to use a certain language. I do not understand, how I can get such a mixture of languages though.
--
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/1919
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
Add file and directory creation, renaming and removal operations to the Project Organizer sidebar.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/766
-- Commit Summary --
* Add file operations to Project Organizer.
-- File Changes --
M projectorganizer/src/prjorg-project.c (1)
M projectorganizer/src/prjorg-project.h (2)
M projectorganizer/src/prjorg-sidebar.c (246)
M projectorganizer/src/prjorg-utils.c (78)
M projectorganizer/src/prjorg-utils.h (7)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/766.patchhttps://github.com/geany/geany-plugins/pull/766.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/766
Add operations to quickly add, delete and rename files and directories from the project. These operations appear as operations in the side bar context menu.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany-plugins/pull/765
-- Commit Summary --
* Squashed commit of the following:
-- File Changes --
M projectorganizer/src/prjorg-project.c (1)
M projectorganizer/src/prjorg-project.h (2)
M projectorganizer/src/prjorg-sidebar.c (247)
M projectorganizer/src/prjorg-utils.c (41)
M projectorganizer/src/prjorg-utils.h (3)
-- Patch Links --
https://github.com/geany/geany-plugins/pull/765.patchhttps://github.com/geany/geany-plugins/pull/765.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/765
**Rationale:**
Currently geany functionality for Lisp dialects is limited to syntax highlighting and only covers [Common] Lisp and Clojure (currently not full built-in file type). The following change not only expands functionality to existing Lisps dialects but adds support for two major Lisp dialects, Scheme and Racket.
**Changes:**
* Add and integrate universal-ctags parsers for Lisp, Clojure, Scheme and Racket (based on Scheme parser)
* Add built-in filetypes for Clojure, Scheme and Racket (following HACKING instructions)
* Modify calltip functionality to work with current document file type defined wordchars
**Existing problems:**
* Parser capability to identify symbols is limited to functions (Lisp, Clojure, Scheme, Racket), variables (Scheme, Racket) and namespaces (Clojure)
* Calltip only works by typing a open paren after function name which is not suitable for Lisp dialects
* Racket filetype keywords are not being consistently highlighted
* Racket parser is minimal adaptation of Scheme parser
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1922
-- Commit Summary --
* Add TagManager parser for Clojure, Lisp and Scheme
* Add Racket parser and lisp-based builtin filetypes
* Minor fixes relating to the filetypes
* Remove reference to scheme tag file
* Make use of current editor wordchars for calltip
* Add generated keywords to filetype.rkt
-- File Changes --
M ctags/Makefile.am (5)
M ctags/main/parsers.h (6)
A ctags/parsers/clojure.c (175)
A ctags/parsers/lisp.c (134)
A ctags/parsers/racket.c (120)
A ctags/parsers/scheme.c (122)
M data/Makefile.am (5)
R data/filedefs/filetypes.clj (20)
M data/filedefs/filetypes.lisp (3)
A data/filedefs/filetypes.rkt (62)
A data/filedefs/filetypes.scheme (60)
M data/filetype_extensions.conf (4)
M src/editor.c (2)
M src/filetypes.c (5)
M src/filetypes.h (3)
M src/highlighting.c (6)
M src/highlightingmappings.h (16)
M src/symbols.c (31)
M src/tagmanager/tm_parser.c (26)
M src/tagmanager/tm_parser.h (4)
-- Patch Links --
https://github.com/geany/geany/pull/1922.patchhttps://github.com/geany/geany/pull/1922.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/pull/1922
How to reproduce:
open a .vala file
try to comment a line of the code.
Expected behaviour:
comment start at the same indentation level of the code
Actual behaviour:
comments start from the first line and add an extra tab indentation to the code
Example:
python
button = Gtk.Button()
# ~ button = Gtk.Button()
c
enum giorni settimana;
//~ enum giorni settimana;
vala
var label = new Gtk.Label (null);
//~ var label = new Gtk.Label (null);
--
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/1920
This adds the `.ino` extension to the file extension list for c++ code. Arduino sketch files are 99% c++ code. This makes them easier to edit in Geany :).
If unsure, take a read at <https://www.visualmicro.com/page/User-Guide.aspx?doc=INOs-and-CPPs.html>:
>Even though the Arduino web site does not mention it, the programming language Arduino uses is nothing but C++, with some limitations due to the tight memory constraints of the processors used.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/1918
-- Commit Summary --
* Add *.ino (Arduino sketch files) to c++ fileextension list
-- File Changes --
M ctags/parsers/c.c (2)
M data/filetype_extensions.conf (2)
-- Patch Links --
https://github.com/geany/geany/pull/1918.patchhttps://github.com/geany/geany/pull/1918.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/pull/1918
){kind=link}