Rust language provides many tools to make programming easy and finding bugs faster. Some of the tools I personally use are rustfmt, clippy and miri. Right now when I have to run these tools, I have to execute these from command line. Take `rustfmt` for example after formatting the code using `rustfmt main.rs` we have to reload our code every time in geany. It would be very helpful if we have a way to integrate such tools in geany. It will be also useful if we have a dedicated one click buttons for such tools in our tool bar itself similar to run, build buttons.
--
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/2587
every time i close a tab, the following error is thrown onto the command line and a similar one in the debug message list:
`(geany:24402): Gtk CRITICAL **: <timestamp>: gtk_notebook_get_tab_label: assertion 'list != NULL' failed`.
it doesn't seem to have much effect, but it's just a bit annoying to have it show up so often in the terminal
--
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/2588
Hi,
Geany doesn't create the path specified for "Filename", only for "Base path".
So if we specify a path for "Filename" different from "Base path", we get the error:<br>
*`Project file could not be written (No such file or directory).`*
So the workaround is to create the path by hand ..., eg:<br>
```shell
mkdir -p /home/someone/projects/
```
So I think it is better for usability to ask users if they want the filename's
path to also be created.
I'm not a C developer, but thanks to the Geany guides I was able to come
up with a solution.
If you also think this change is important, then please review this PR
and guide me on how to make it better.
I only tested on Ubuntu and it worked.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2586
-- Commit Summary --
* Create project's filename path
-- File Changes --
M src/project.c (47)
-- Patch Links --
https://github.com/geany/geany/pull/2586.patchhttps://github.com/geany/geany/pull/2586.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/2586
@getzze the ctags parser is used for the symbol pane and passing typenames to the lexer, as well as completions.
But yes the Julia syntax is not context sensitive (unlike say C) and you can recognise and highlight :: and other type operators in the lexer (along with all the myriad of operators Julia allows as your point 5 says). Also of course you can also highlight all the keywords like "primitive type abstract struct" etc and do folding on them.
Whilst you _could_ highlight identifiers that are recognised as typenames in a file, I wouldn't recommend it since the lexer has no way to know about typenames from outside the file (from modules etc) so only local typenames would be highlighted and that would not be very helpful (IMHO, Julia editor without `Array` highlighted would be sacrilege :grin:).
What most of the lexers do is accept lists of identifiers to highlight differently to the default identifiers, a feature that was meant to allow for additional keywords, but which Geany (ab)uses to identify types that the ctags parsers recognise, and in some languages to highlight differently the "built-in" types.
You could use a static list of builtins and standard library in `filetypes.Julia` until your parser is working and you can make a tags file for standard library stuff to be loaded when the first Julia file is loaded (as is done for Python and C and others).
--
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/434#issuecomment-691365199
I think it can be done in the lexer, by parsing the `:` character.
If I understood correctly, the ctags parser is used for completion, it would be great to implement it also.
--
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/434#issuecomment-691330215
@getzze that's amazing! As for the last 2 bullets of your list, is a parser needed to address them?
--
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/434#issuecomment-691320781
I made a pull-request with a lexer I just made using Matlab, Python and other existing lexers.
So far:
- [X] using splatting `...` and `%` make the end of the line being recognized as comment
- [X] parse `begin` and `end` as numbers inside indexing brackets, so code folding works.
- [X] complex strings with interpolation are not correctly parsed.
- [X] macros are not colored
- [ ] symbols are not recognized as special type (like strings).
- [ ] type annotations with ::, <: are not emphasized
--
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/434#issuecomment-691247566