Finally off work and get a chance to play with this too.
Used Mint's git
to download, all okay with that.
Running sudo ./install.sh
gave this error:
cp: target '/usr/local/share/man/man1' is not a directory
I modified install.sh
to make MANDIR="/usr/share/man"
and then it installed without error.
Goddamn it Mint - why do you not behave like other distros?!
OK, that's really odd.....
Traditionally programs installed to /usr/local/bin/ get their man pages installed to /usr/local/share/man/
And programs installed to /usr/bin get their man pages installed to /usr/share/man
So I try to respect that. I don't know why this isn't working for mint.....
We know that /usr/local/share/man exists and is on the manpath. The 'mkdir -p' I used in the script should
create the man1 directory inside /usr/local/share/man/.. I don't understand why the copy operation is failing....
What is the result of the command:
This is REALLY odd!
I wonder if perhaps Mint are using a symbolic link for the /man or /man1 part of the path or something?!
If file says they are directories - I really don't understand why cp is failing.
The script was ran as root via sudo - so there was enough privilege..... Hmmmm.....
I am not able to create a new note with the command (with or without sudo
The error I get for that is:
/usr/local/bin/note: line 144: : command not found
Yes - I believe this bug can be filed under ass/u/me - in other words I've been bitten on the arse by another of my naive assumptions. heh heh!
Line 144 is the line that attempts to create/open a note in the editor.
I have a sneaky suspicion that the environment variable $EDITOR is not set on your system.
So when notesettings attempted to set itself up - the $ED variable in settings.cfg will be empty.
After having a dig through my configs - It looks like I'm explicitly exporting it in my .bashrc.
I just ass/u/med that the version in my .bashrc was over-riding an existing environment variable. I hadn't considered that it might not exist at all.
If you run notesettings without any parameters - I have a feeling that you will probably see something like this:
I'll have to update the settings script to ask the user which text editor note should use if $EDITOR is empty.
In the meantime, you can fix the editor related problem using notesettings:
notesettings -e $(which vim)
NOTE: substitute vim for whichever terminal based editor you'd prefer to use - nano, ed, emacs etc.
Then you will see something like:
Obviously, your output for $ED should reflect the path to your chosen editor.
So it looks like I still have a lot of work to do on this! XD
I haven't got any spare USB drives ATM - I need to get hold of one and try booting into Mint and try some messing from a fresh install.....
Thanks for all of the testing you guys are doing for me!