The current highlighting of dark blue (as opposed to black when not selected) is very difficult for me to see I imagine there's something I can edit, but there's nothing in the documentation and playing with brace_good in filetypescommon didn't appear to achieve much
Using geany 1241
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/885
1- Enable Tools -> Split Window -> Side by side
2- Open one file in both left and right sides
3- Change cursor position in one side so that cursor and scroll position in 2 sides are different
4- Type something in the right side, then press Control + Z
5- The cursor and scroll position in left side changes (unexpectedly) to the position of right side, so that you loose where you were (writing something in a different part of the same file)
---
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/988
Hi.
OS: Windows 7 64bits
Geany version: 1.26
In "Edit>Preferences>Files>Default encoding" I selected IBM850 as default encoding in all options, new files and open files, but all files are opened with 1252 encoding. With new files there is no problem.
Thank you.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/900
Please consider adding an <b>Unflow paragraph</b> command - the opposite of
<b>Reflow Lines/Block</b> The use case for this is to make it easy to type in
<b>Geany</b> and then paste the results into the Gmail or Github editor
Incidentally, <b>Reflow Lines/Block</b> indicates that the conception of a
block of line is already endogenous to <b>Geany</b> and thus I believe that the
concept of extending the highlighting of lines to the line numbers columns
should be considered an extension of an existing capability
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/802
In the Build Commands dialog there are additional commands under `Conf commands`, `Independent commands` and `Execute commands` that are not available to setup in Preferences|Keybindings. It would be very useful to be able to set keybindings for these. Further to this the command names in Build commands can be modified but this is not reflected in Keybindings preferences.
Just a quick thought too; a button linking to the keybindings prefecences would be a helpful addition to the Build commands dialog.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/705
I switched today from Geany 125 to 126 With the new version (running on Windows 7 64bit), I have (reproducibly) a strange problem with one file (its name is `irbrc`) which I had created with 125: When I want to save the file, an error popup occurs (see screenshot) which gives a "permission denied" message Moreover, this popup can not be clicked away (more precisely, when I click on OK, the popup seems to disappear for a fraction of a second, only to reappear again) I think, this behaviour of the popup window is clearly an error, because it is a modal dialogue, and I have to kill Geany with the task manager in order to continue my work It could be that Geany, after I clicked OK, tries again to fulfil the *Save* request, and finds - for whatever reason - the file still write-protected and brings up the same dialogue again
BTW, I don't think that this is *really* a permission issue, even though the message says so, because I can happily edit this file with other text editors I don't know why this file is special It is neither the name nor the content - I can use "save as" to save the file into a different directory
![capture_20151214_170717](https://cloudgithubusercontentcom/assets/6795665/11786323/301e8616-a286-11e5-8c48-98772ff2ad57jpg)
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/815
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
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
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
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