Why does Harpoon die at startup?
Answer At startup, Harpoon tries to open a harp.cfg file for writing. If this fails, then Harpoon will fail to start. On Linux/Unix, if the directory where you start Harpoon doesn’t have read/write permissions, or the existing harp.cfg file doesn’t have read/write permissions, harpoon will fail to start. You will get a message, “Could not open config file – check write permissions”. You will need to start Harpoon from a different directory, or change the write permissions of the directory and/or the existing harp.cfg file. On Windows, if you don’t have read/write permission to the directory pointed to by the HOME environmental variable, then Harpoon will fail to start. If you don’t have read/write permission to an existing harp.cfg file, then harpoon will fail to start. If you start by double-clicking an alias pointing to the executable, you may not see an error message, but harpoon will fail to start. To fix this problem, change your HOME environmental variable and/or your permissions
