well known module config about gohack HOT 4 OPEN

When you run that gohack config command, where is that setting stored?

Have you considered specifying the directory as part of the regular gohack some-module command? For example, if it were configurable via an environment variable, one could ensure that the variable is exported whenever one enters that directory via one of those cd magic wrappers.

An even crazier idea would be to piggyback off an existing file in a module. I can imagine a comment in go.mod, but that would be a setting for everyone cloning the repository, and not just the one author.

from gohack.

When you run that gohack config command, where is that setting stored?

GOHACK/.config?

Have you considered specifying the directory as part of the regular gohack some-module command?

That's quite a verbose option, yes. Almost akin to setting the environment variable as part of the command itself, e.g. GOHACK=$HOME/mywork gohack $module. It requires me to specify the directory each time.

...via one of those cd magic wrappers.

I use such a magic wrapper, but not everyone does. This sort of thing feels like an additional bar.

An even crazier idea would be to piggyback off an existing file in a module. I can imagine a comment in go.mod, but that would be a setting for everyone cloning the repository, and not just the one author.

Yes, I think this is something that doesn't work... not least because this particular example is something that is global.

from gohack.

I can definitely see the motivation for this idea. I might be tempted to put the config file at $GOHACK/config.txt because I don't see any particular reason for hiding it and it probably wants some kind of file extension.

Another possibility to consider is being able to specify a gohack location for a subtree. For example, I might want all modules under github.com/juju to go into /home/rog/src/work when gohacked.

from gohack.

I also think there is some scope for a module-local config that overrides the global well known "default". In many respects this would be similar to how a git config setting at a branch level has higher precedence that its global equivalent.

from gohack.