-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default location of dump file #222
Comments
Why configured instead of in the directory from which edwood was opened? I
keep being surprised when my dump file winds up global instead of where I
rooted my session from.
…On Mon, May 13, 2019 at 5:04 PM Fazlul Shahriar ***@***.***> wrote:
Currently, we're using $HOME/edwood.dump, which is not very portable. We
can use os.UserHomeDir <https://golang.org/pkg/os/#UserHomeDir> (added in
Go 1.12) but I think it'll be better to eventually use os.UserConfigDir
<https://tip.golang.org/pkg/os/#UserConfigDir>, which will be in Go 1.13.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#222?email_source=notifications&email_token=AAJ6RUGL7LKECCIODXR6VGTPVHJVJA5CNFSM4HMTNOT2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GTQ2DDQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJ6RUBCBGDMBMTDVGL36YLPVHJVJANCNFSM4HMTNOTQ>
.
|
Current directory may not be writable? I recently broke the |
I actually wrap my acme/edwood invocations to manage my dump files per
project I work on. And my dump files always include "Dump dumpfilename" in
the main tag, just to make it easy to save correctly. I could avoid that
dance if the dump file was local to the directory I launched in, or
re-dumped to the same dump file as named in -l
Paul
…On Mon, May 13, 2019 at 5:12 PM Fazlul Shahriar ***@***.***> wrote:
Current directory may not be writable? I recently broke the -l flag, so
you may be experiencing that. I'll send a fix shortly.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#222?email_source=notifications&email_token=AAJ6RUFFT3UCS4TGT4UMYGDPVHKSRA5CNFSM4HMTNOT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVJSNNI#issuecomment-491988661>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJ6RUG43IL3HQOATOAW6J3PVHKSRANCNFSM4HMTNOTQ>
.
|
I'm in favor of this. Most of the time you probably want to dump to the same file you loaded from. The |
fhs
added a commit
to fhs/edwood
that referenced
this issue
Sep 24, 2019
os.UserHomeDir() was introduced in Go 1.12. Update rjkroege#222
Merged
rjkroege
pushed a commit
that referenced
this issue
Sep 26, 2019
os.UserHomeDir() was introduced in Go 1.12. Update #222
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, we're using
$HOME/edwood.dump
, which is not very portable. We can useos.UserHomeDir
(added in Go 1.12) but I think it'll be better to eventually useos.UserConfigDir
, which will be in Go 1.13.The text was updated successfully, but these errors were encountered: