The menu options
View -> Show Markers Margin
View -> Show Line Numbers
don't control the respective items on the right side split.
You can "unsplit," set the options, and then split again and the new window has the proper appearance.
--
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/600
The regex engine used by Geany does not match the one used by upstream ctags, so incorporating the regex parsers would need two regex engines.
Either this should be accepted (IMHO preferred as it allows to keep in sync with upstream) or an alternative implementation for those languages should be provided.
--
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/2119
I use `cargo check` frequently.
https://doc.rust-lang.org/cargo/commands/cargo-check.html
```Check a local package and all of its dependencies for errors. This will essentially compile the packages without performing the final step of code generation, which is faster than running cargo build. The compiler will save metadata files to disk so that future runs will reuse them if the source has not been modified.```
One problem with this patch though. As I moved the 3 items down, putting `Cargo Check` at the top. When I test my patch, I get the dialog to enter custom text when selecting `cargo build`, but before it was when selecting `cargo test`. I couldn't figure out where geany was getting the instruction to pop up a dialog, as all those fields are the same, both in the filetypes.rs file, and when looking at them from the Geany build menu.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2573
-- Commit Summary --
* Add "cargo check" to build commands
-- File Changes --
M data/filedefs/filetypes.rust (15)
-- Patch Links --
https://github.com/geany/geany/pull/2573.patchhttps://github.com/geany/geany/pull/2573.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/2573
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2149
-- Commit Summary --
* .travis.yml:add tests for gcc 7 and 8
* use build matrix #2139
* for gcc 8, specify xenial and the correct version
* try globalizing the GTK3 env directives
* try indenting the matrix to get global to work
* revert a little
* fix indentation
* add clang 5 test (closes #2139)
* only run `make distcheck` for a single job
* specify dist and compiler explicity
* remove unneeded hyphenated lines
* add DISTCHECK_ONLY, don't hide it under gcc-5
* use xenial instead of trusty
* reduce clang to 3.5
* try default clang on xenial
* try default clang on trusty
* clang:revert to using 5.0 on trusty
* allow clang to fail
* remove cache directive, try clang 3.5 again; also...
* specifying 3.5 on trusty
* install libc++
* clang:explicity enable C++11 support
* make:temporarily add -n and VERBOSE=1
* use clang 3.8
-- File Changes --
M .travis.yml (77)
-- Patch Links --
https://github.com/geany/geany/pull/2149.patchhttps://github.com/geany/geany/pull/2149.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/2149
This includes patches by @b4n in #2149
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/2574
-- Commit Summary --
* .travis.yml:add tests for gcc 7 and 8
* use build matrix #2139
* for gcc 8, specify xenial and the correct version
* try globalizing the GTK3 env directives
* try indenting the matrix to get global to work
* revert a little
* fix indentation
* add clang 5 test (closes #2139)
* only run `make distcheck` for a single job
* specify dist and compiler explicity
* remove unneeded hyphenated lines
* add DISTCHECK_ONLY, don't hide it under gcc-5
* use xenial instead of trusty
* reduce clang to 3.5
* try default clang on xenial
* try default clang on trusty
* clang:revert to using 5.0 on trusty
* allow clang to fail
* remove cache directive, try clang 3.5 again; also...
* specifying 3.5 on trusty
* install libc++
* clang:explicity enable C++11 support
* make:temporarily add -n and VERBOSE=1
* use clang 3.8
* use clang 3.5, add missing "compiler" line
* Major Travis update
-- File Changes --
M .travis.yml (105)
-- Patch Links --
https://github.com/geany/geany/pull/2574.patchhttps://github.com/geany/geany/pull/2574.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/2574
Geany version: 1.33
If the compilation of file A modifies file B, the scrollbar in file B doesn't move after the compilation.
How to reproduce:
1. Start compilation of some file. It has to modify another opened file.
2. Switch to the other file that has been modified by the compilation.
3. In appearing message window, "The file _\<filename\>_ on the disk is more recent than the current buffer.", reload the file.
4. Finished. Now the scrollbar of the modified file won't move
[Here is a video of the bug reproduction (zipped)](https://github.com/geany/geany/files/2169464/geany-bug-demonstrati…).
--
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/1893
The [HACKING](https://github.com/geany/geany/blob/master/HACKING) file has this:
> Before the 1.0 release series, the ABI can change when necessary, and
even the API can change.
Obviously Geany has long switched to 1.x versions. Does this text still apply?
--
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/1475
Hi, I'm coming from TextMate 2 on Mac, and TextMate does a great job with projects - by essentially making it invisible (frictionless).
You just open a folder, and that folder automatically becomes a project.
Geany could easily do something similar in my opinion. I don't know if the GNOME file picker allows you to pick either a directory or file, but if so, just do that and automatically create a new project file with the same name as the directory you 'Open'. If not, just have a separate "Project -> New from folder" menu option that is for choosing a directory.
If you implement this it will really make using Geany a lot nicer. Imagine being able to open up any random git clone you did and having everything 'just work'. Especially if you have the .editorconfig plugin installed.
Failing that, you could at least remove a little friction from the New Project form. I think if the path in the 'Filename' option is changed, it should automatically adjust the 'Base path' to match it.
--
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/2245