The most idiomatic way would be to just use an existing crate, in this case shellexpand (github, crates.io) seems to do what you want: extern crate shellexpand; // 1.0.0 #[test] fn test_shellexpand() { let home = std::env::var(“HOME”).unwrap(); assert_eq!(shellexpand::tilde(“~/foo”), format!(“{}/foo”, home)); } Alternatively, you could try it with dirs (crates.io). Here is a sketch: extern crate … Read more
I don’t think it’s possible to completely hide the Windows/Unix divide with this one (unless, maybe, Boost has something). The most portable way would have to be getenv(“HOME”) on Unix and concatenating the results of getenv(“HOMEDRIVE”) and getenv(“HOMEPATH”) on Windows.
Tilde expansion doesn’t work in some situations, like in the middle of strings like /foo/bar:~/baz
~ is a bash-ism rather than a perl-ism, which is why it’s not working. Given that you seem to be on a UNIX-type system, probably the easiest solution is to use the $HOME environment variable, such as: if ( -e $ENV{“HOME”} . “/foo.txt” ) { print “yes ,it exists!” ; } And yes, I know … Read more
Of course, never fails. Found the solution about a minute after posting the above question… solution for those that may have had the same issue: ContextWrapper.getFilesDir() Found here.
I think os.path.expanduser(path) could be helpful. On Unix and Windows, return the argument with an initial component of ~ or ~user replaced by that user‘s home directory. On Unix, an initial ~ is replaced by the environment variable HOME if it is set; otherwise the current user’s home directory is looked up in the password … Read more
It’s a Bash feature called “tilde expansion”. It’s a function of the shell, not the OS. You’ll get different behavior with csh, for example. To answer your question about where the information comes from: your home directory comes from the variable $HOME (no matter what you store there), while other user’s homes are retrieved real-time … Read more
Since go 1.12 the recommended way is: package main import ( “os” “fmt” “log” ) func main() { dirname, err := os.UserHomeDir() if err != nil { log.Fatal( err ) } fmt.Println( dirname ) } Old recommendation: In go 1.0.3 ( probably earlier, too ) the following works: package main import ( “os/user” “fmt” “log” … Read more
Is there something special with that directory or are you really just asking how to copy directories? Copy recursively via CLI: cp -R <sourcedir> <destdir> If you’re only seeing the files under the sourcedir being copied (instead of sourcedir as well), that’s happening because you kept the trailing slash for sourcedir: cp -R <sourcedir>/ <destdir> … Read more
As mentioned in a more recent answer, the preferred way is now simply: const homedir = require(‘os’).homedir(); [Original Answer] Why not use the USERPROFILE environment variable on win32? function getUserHome() { return process.env[(process.platform == ‘win32’) ? ‘USERPROFILE’ : ‘HOME’]; }