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
Bash allows more characters besides `[[:alnum:]_]` when declaring
function names using the `function` keyword. It also does not require
having a pair of parentheses after the name. Some shells may actually
implement it differently but we don't have to be that strict since the
user explicitly specifies the `function` keyword anyway.
This update implements the ones described above, and also invalidates
function names that are completely made up of digits.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/662
-- Commit Summary --
* Enhance detection of sh functions
-- File Changes --
M tagmanager/ctags/sh.c (125)
-- Patch Links --
https://github.com/geany/geany/pull/662.patchhttps://github.com/geany/geany/pull/662.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/662
This is an improved version of PR #637.
No more "--" - not needed.
No guard for is_osx_bundle() under Windows - does not belong here.
Split into proper sequential commits.
Fixed the encoding of options and doc_name.
Fixed the OSX bundle executable name.
Created a function to return the reproduced arguments instead of exposing global variables.
Re-tested under Windows and Linux.
There is only one problem left. As described in PR #637, under Windows, mscvrt often breaks unquoted locale strings on 2+ pieces, considering some characters "spaces". So spawn should quote any argv elements containing locale. But that must obviously be a separate PR.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/653
-- Commit Summary --
* Add reverse option parser to main
* Add support for geany executable to utils_resource_dir()
* Improve New Window: pass the proper arguments and save configuration
-- File Changes --
M src/libmain.c (121)
M src/main.h (2)
M src/plugins.c (2)
M src/utils.c (111)
M src/utils.h (17)
-- Patch Links --
https://github.com/geany/geany/pull/653.patchhttps://github.com/geany/geany/pull/653.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/653
'Geany' no longer detects if there is an instance of itself already running, thus multiple instances are starting up, instead of files being opened in the current instance.
I doubt it is a "#ifdef HAVE_SOCKET" not being defined since the mutexs (called mutants in win32) are being created with the name 'Geany'.
I suspect it had to do with recent cleanups and changes in https://github.com/geany/geany/commits/c5b0fc459a1251c824a44edb5dfab4a8feb0…
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/641
For a verilog file, the variables list parses the old (1995) style verilog module declarations. Verilog 2001 enhanced the syntax and seems to confuse Geany....
1995 syntax:
module (foo, bar, buz);
input foo; // foo port
output bar; // bar port
output buz; // buz port
reg buz; // buz variable
2001 syntax:
module (
input wire foo, // foo port is a wire
output wire bar, // bar port is a wire
output reg buz // buz port is a variable
);
// note: the "wire" is optional and the ports could have been declared with or without
Geany variables list seems to get confused by the 2001 style. It seems to parse the wire keyword as the variable name if I keep the optional "wire" keyword:
If I omit the "wire" keyword, Geany still gets confused, but in a different way. It seems to parse every other variable and then parse the "input" or "output" keywords as variables in some cases:
If someone who knows the code base can even point me to the module(s) doing the parsing for the variables, I may be able to help create the fix/enhancement for this. I'd be happy to try anyway. I am not familiar with the Geany code base so just getting started seems like an insurmountable task.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/670
When new file is opened (previous file which hasn't been opened before), it doesn't open maximized, window is not fully across the screen. This is clean installation of 2.24 version on Windows 7. You should also have previous files already opened in geany showing in tabs to replicate this problem
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/671
This one is hard to reproduce (sorry), and I have no idea what causes this or what is happening.
Steps to reproduce *sometimes*:
0. Install and enable GeanyLaTeX (in case it is relevant: I have only the "auto-completion" activated)
1. Create and open: A latex file and a Makefile, in the same directory (I use the makefile to compile the latex document)
2. Edit the latex file over a long time, intermittently calling "make" via the shortcut "Shift+F9" (as found in the menu)
Actual behaviour: Sometimes the "Make" menu item becomes and stays disabled. This also disables the keyboard shortcut, so Shift+F9 does not do anything anymore. Switching between geany-tabs or re-opening the file does not help. The only way to work around this is to restart Geany.
Expected behaviour: Shift+F9 and the "Make" menu item stay enabled for the whole time.
Versions: Geany 1.25 "Veed" // "(compiled on 2015-07-12 or later)"
Sorry that I can't provide a more reliable way of reproducing the bug. I have already played with different things, and have, so far, only come to the conclusion that disabling the GeanyLaTeX pluging avoids this bug. However, this is not a guarantee, since I "only" tried that for a week. Otherwise I run into that bug roughly once every two weeks, so this experiment isn't conclusive.
I continue using Geany, so if anyone can give me a better "test", or instructions on what to look for via gdb while this is happening, I'd gladly do that.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/282
Geany is still using GTK2 according to the official Geany.org homepage. Should Geany update to GTK3? I suggest this because occasionally I get odd (and non-reproducible) GUI-glitches in Geany.
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/644
Closes #622.
---
While a very common keybinding for this would be `Alt+Return`, I didn't set any default because:
1. `Alt+Return` might be in use by a plugin already, and Geany would steal it;
2. Properties don't seem to be important enough to me to really need a default keybinding.
You can view, comment on, or merge this pull request online at:
https://github.com/geany/geany/pull/652
-- Commit Summary --
* Allow to set a keybinding for File->Properties
-- File Changes --
M data/geany.glade (2)
M src/callbacks.c (2)
M src/callbacks.h (2)
M src/keybindings.c (5)
M src/keybindings.h (1)
M src/ui_utils.c (2)
-- Patch Links --
https://github.com/geany/geany/pull/652.patchhttps://github.com/geany/geany/pull/652.diff
---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/pull/652