The treebrowser context menu items "Open externally" and "Open Terminal" don't work on Windows 10.
It doesn't lunch any external application.
However, the "Open Externally" function in built-in plugin Filebrowser is working correctly.
--
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/556
When writing LaTeX, symbols in the Symbols list are grouped by type (Environment, Section, Paragraph, Chapter, ...), so it is not immediate to understand the structure of the document.
It would be nice if the Symbols list could have a third sorting mode (besided "by Name" and "by Appearance") that makes the Symbol list like a Table of Contents.
---
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/1082
I love the ability to theme the edit area and I prefer a darker theme.
The problem is that the theme does not apply to the side bar which to my mind is a bit inconsistent. Especially when there is a strong light / dark contrast.
I am sure there are users that would prefer it to stay the way it is but for myself at least I would optionally like the relevant portions of the theme to apply to the side bar.
Thanks
--
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/1344
When editing a document in (soft) Line wrapping mode (the document line that is longer than the screen width is spread over multiple display lines while keeping the same line number), the End key takes you to the end of the document line. This is understandable, but it keeps being unexpected while editing in the middle of a document line...
My proposal is just to change the defaults:
End = "go to the end of the display line", Alt-End = "go to the end of the document line", Home = "go to the beginning of the display line", and Alt-Home = "go to the beginning of the document line"
When not in Line Wrapping mode, it still works the same, but when in Line Wrapping mode, it's more intuitive.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/949
Dear all,
I am very thankful to the debugger plugin team. It is a very good tool to my work.
I would like to ask some "how to" here. Maybe some of them can be considered into wishlist.
1. How to show variables' address?
In F90, we have LOC(x) to show its address in memery. Can I use it in the "watching window" as well?
2.how to access some variables that are located under module?
In intel f90+VS in Windows10, we have "mod::" method in debugger to enable this. Can we have the similar functions in geany?
3. ... (Maybe we can add more "enhancement" under this box?:D)
Thanks.
Shuo
--
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/583
The error I'm getting is
> Geany tried to access the Unix Domain socket of another instance running as another user.
> This is a fatal error and Geany will now quit.
I'm aware of [#294](https://github.com/geany/geany/issues/294), but I'm not running geany as root. This error occurs whenever I start an instance of geany, then either start another instance or open a file with geany (through right click -> open with geany).
While an instance of geany is running, `ls -l .config/geany/ | grep socket` shows
`lrwxrwxrwx. 1 root root 60 Feb 26 14:11 geany_socket_Starlight__0 -> /tmp/geany_socket.fcdcdb1b`
If I understand correctly, the owner of this file should be me, not root.
I suspect that this problem is related to the way I've set up my home directory - it's on an NTFS partition. (More accurately, .config/geany is symlinked to a directory on an NTFS partition.)
--
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/1411
I was using [`git-new-workdir`](http://nuclearsquid.com/writings/git-new-workdir/) and recently switched to using the newer form [`git worktree`](https://github.com/blog/2042-git-2-5-including-multiple-worktree… however found this stops the plugin working.
The reason appears to be that instead of a `.git` directory in the 'worktee directory' there is a `.git` file that contains a reference to the original directory. e.g. `gitdir: /home/ubuntu/origdir.git/.git/worktrees/newdir.git`.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/285
The docs state that if you have a visual diff tool installed, like meld, running VC->*->Diff will use that tool. This appears to work for VC->File->Diff, but not for VC->Directory->Diff, which spits out the default diff output.
Thinking that GeanyVC was using `git diff`, I tried overriding the `git diff` with:
git config --global diff.external meld
but this has no effect, since GeanyVC appears to ignore git's `diff.external` setting, preventing the use of a visual diff tool.
--
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/573
Currently geany updates geany.conf with info about window position and
geometry. These vary across different machines and cause diffs that
are meaningless.
--
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/1392
This is a tracking bug where we are with universal-ctags syncing regarding individual parsers. After https://github.com/geany/geany/pull/1160 gets in, the work on merging the parsers can start.
If someone wants to merge some of the parsers, it would be best to drop a line here so people don't do the same work in parallel.
Below is the state of individual parsers -> shows the general direction of from where to where the changes should be brought. <-> means changes will probably be necessary in both Geany and uctags parsers.
**basically merged**
- [ ] asm
- [ ] cobol
- [ ] css
- [ ] erlang
- [ ] json
- [ ] objc
**waiting for varType in uctags**, see https://github.com/universal-ctags/ctags/issues/862 (simple to merge)
- [ ] go (Geany->uctags)
- [ ] rust (Geany->uctags)
**normal diffs**
- [ ] basic (uctags->Geany)
- [ ] diff (uctags->Geany)
- [ ] fortran (uctags<->Geany)
- [ ] html (Geany->uctags)
- [ ] jscript (uctags<->Geany)
- [ ] lua (uctags->Geany)
- [ ] make (uctags->Geany)
- [ ] pascal (Geany->uctags)
- [ ] perl (uctags->Geany)
- [ ] php (uctags<->Geany)
- [ ] ruby (uctags->Geany)
- [ ] sql (uctags->Geany)
- [ ] tcl (Geany->uctags)
**big diffs**
- [ ] python (uctags->Geany)
- [ ] r (uctags<->Geany)
- [ ] sh (uctags->Geany)
- [ ] verilog (uctags->Geany)
**unmergable diffs**
- [ ] latex (uctags) vs tex (Geany) - different parsers - haven't checked what they do and if they should be treated as a parser of a single language or not
- [ ] matlab (we have regex-based parser, uctags has hand-written one - we should probably grab the uctags one)
- [ ] VHDL (different parsers from different people - uctags parser contains more LOCs so it's probably better :-)
- [ ] c.c (meh)
**extra parsers in Geany**
abaqus, abc, actionscript, asciidoc, conf, docbook, haskell, haxe, markdown, nsis, powershell, rest, txt2tags
**extra parsers in uctags**
ada, ant, asp, awk, beta, clojure, dbusintrospect, dosbatch, dts, eiffel, falcon, flex, glade, jprop, lisp, maven2, myrddin, ocaml, perl6, plist, protobuf, relaxng, rex, rpmspec, rst, scheme, slang, sml, svg, ttcn, vim, windres, xslt, yacc
---
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/1162