r2evans

I'd be interested in working on both this issue and (perhaps separately) #27. I'll look into it.

(and I apologize for being completely unavailable since making that recommendation and offer, sorry @dspinellis )

Two things that appear to work: 1. *Infer*: if the dirname of the executable has as its second character a colon, then transform to GfW's fancy c-drive-mounting (e.g., `c:/Users/r2` -->...

Do you mean using `LIBPREFIX` (currently set in the `Makefile`) within `git-issue.sh`? To make sure I don't go in the wrong direction, I think this means: 1. change `git-issue.sh` so...

I tested with this `Makefile` and it worked! ```diff diff --git a/Makefile b/Makefile index 8b4aaae..67d48ee 100644 --- a/Makefile +++ b/Makefile @@ -10,7 +10,8 @@ install: @mkdir -p $(DESTDIR)$(MANPREFIX) @mkdir -p...

... just a thought, though ... if a user sets `make PREFIX=... install`, then all is fine. If a user sets `make PREFIX=... LIBPREFIX=... install`, then things will not be...

Is it important to you to support these extra `*PREFIX` variables in `gfw-install.sh`? For instance, do you want GfW users to be able to do the following? ```bash PREFIX=/quux LIBPREFIX=/quux/other/lib...

Do you mean starting `Makefile` with this? ```make prefix := /usr/local bindir := $(prefix)/bin libexecdir := $(prefix)/libexec/git-issue sysconfdir := $(prefix)/etc/bash_completion.d mandir := $(prefix)/share/man man1dir := $(mandir)/man1 ``` and the `gfw-install.sh`...

GfW is really just meant to do one thing: provide `git.exe` and all of the tools **required** to support it. That means `unzip` (but not `zip` ...), `tar`, etc, and...

That's a very relevant point: GfW has no package management, perhaps that gives you some perspective to understand why it is both "good" (simple) and not extensible. (I apologize if...