Is `~/.npm-rfc/` a better temp folder than `/tmp/ietf-rfc`?
leesei opened this issue · comments
I'm also thinking of allowing the user to export and bookmark rfcs, it would be better if there is a user's folder for this app.
or ~/.rfc? I like the idea of moving away from using $TMPDIR
I'm afraid the ~/.rfc namespace is too generic and might cause a conflict.
Also, some programs use .d suffix to denote a directory, I also recommend that.
Here are my updated suggestions:
~/.npm-rfc.d/
~/.node-rfc.d/
~/.rfc.d/
I think leaving npm and node out of the name is a good idea. These aren't RFCs for node or npm... ~/.rfc.d could work
K, are you free to implement this?
I can help within week's time.
On Fri, May 8, 2015 at 1:30 AM, Joseph Werle notifications@github.com
wrote:
I think leaving npm and node out of the name is a good idea. These aren't
RFCs for node or npm... ~/.rfc.d could work—
Reply to this email directly or view it on GitHub
#4 (comment).
I'm very busy for the next week. I will happily accept a PR!
K.
I'll do this first and then my other improvements.
Thank you, I would have to write a similar tool from scratch otherwise.
On Fri, May 8, 2015 at 1:38 AM, Joseph Werle notifications@github.com
wrote:
I'm very busy for the next week. I will happily accept a PR!
—
Reply to this email directly or view it on GitHub
#4 (comment).
No problem !