On Monday 22 February 2016 12:03:40 Gene Heskett wrote: > On Monday 22 February 2016 04:15:02 Lisi Reisz wrote: > > On Monday 22 February 2016 00:05:41 Gene Heskett wrote: > > > On Sunday 21 February 2016 15:39:57 Thierry de Coulon wrote: > > > > On Sunday 21 February 2016 01.41:18 Glen Cunningham wrote: > > > > > Reply to my own post for the archives. > > > > > > > > > > On Sunday 21 February 2016 09:38:25 Glen Cunningham wrote: > > > > > > Thanks for the try, Nik, > > > > > > > > > > > > On Sunday 21 February 2016 03:39:15 Dr. Nikolaus Klepp wrote: > > > > > > > Hi! > > > > > > > > > > > > > > It's that simple :-) > > > > > > > > > > > > NO! It is not that simple. > > > > > > > > (...) > > > > > > > > > Laboriously copied the above 6 files/directories from .kde3 on > > > > > the old box to .trinity on the new one. > > > > > That did not work! Kmail failed to start. > > > > > Deleted the 5 config files, restarted kmail, at least kmail > > > > > started this time and my old mailboxes seem to have survived. > > > > > > > > > > There has gotta be a better way! > > > > > Cheers, > > > > > Glen > > > > > > > > It should - almost - work the way Nik indicated. > > > > > > > > There are possibly a few things to edit when you move to .trinity > > > > (but that will be only once). Mainly, did you edit > > > > /.trinity/share/config/kmailrc ? In the last part of the file > > > > (after the mailboxes), you have the path to your mail directory. > > > > > > > > In (very) old time this would have been ~/mail , but somwhere in > > > > KDE history it was relocated to a ./kde3 subdirectory, usually > > > > $HOME/.kde3/share/apps/kmail/mail. You must change that to > > > > $HOME/.trinity/share/apps/kmail/mail > > > > > > > > As far as I remember that's all I had to do (apart from copyinf > > > > the directory). > > > > > > > > Thierry > > > > > > That might not be 100% good info, here on a wheezy system, its > > > ~/Mail, and I can't remember when it was different. > > > > Sorry, Gene - this is the not 100% correct information. You have not > > got a standard Wheezy system by any manner of means. It was possible > > to keep mail in ~/Mail. which is where it was before, but only by > > deliberately hacking one's system. It is NOT where it is on a standard > > Wheezy/TDE system. E.g., it is not on mine. I migrated my mails, > > with help from the community, I did not hack and set up links or > > whatever in order to keep ~/Mail, although that was a possibility. > > ISTR that I tried and made a mess of it. > > > > Lisi > > I didn't "hack" anything to put it there, Lisi. Thats where my first > EMC2 install put it, from one of Paul Conners Brain Dead Installers 15 > years ago put it, that is where the Lucid 8.04 LTS install put it, thats > where the Hardy 10.04 LTS install put it and thats where the install > iso based on Wheezy put it. It is TDE not Wheezy that decides that. I know that it was what used to be the case. But when .kde changed to .trinity things changed and Mail moved. What you have got is now non-standard. > All I had to do was copy the email corpus > from the old drive to the new one each time I made a new install on a > new drive. > > Sure I write scripts to take care of stuff the installer should have > taken care of but didn't, and cannot because the choices would exceed > the size of the dvd. All I am doing is scrattching an itch. > > To me its not hacking, its polishing the apple. Use whatever word you choose. Hacking is the correct term, but I don't insist on it. > I don't build/buy these > machines to be told how I have to conform to them, Of course. But home/$USER/Mail is no longer, now (in this case 3.5.13.2) the standard place for mail to be, and when one changes from TDE 3.5.?11 (I forget exactly when the change came) one has to go with the flow and migrate as required or hack around not to migrate. Your system is by no means standard. It is not standard Wheezy, and it sounds as though it is not standard TDE either. There is nothing wrong with being non-standard. It just isn't standard. [tl:dnr] > > To you, even changing a password is hacking I guess. Of course not. Don't be ridiculous. > But to make a > machine do something it is fully capable of doing, even if its not on > the menu at your favorite "greasy spoon"/"distribution" is not hacking, > its making the machine do what I need it to do AND bought it or built it > to do. That is what hacking means, for goodness sake. > I think you need to find a better word than "hacking". Its usually > called programming. Gene, you are very knowledgeable in electronics. I am highly qualified in language. I know what programming is. For what I meant, hacking is fine. It is a word with a lot of meanings. I meant, and I quote from www.oxforddictionaries.com: "2.1Program quickly and roughly." Merriam-Webster gives: "4 a : to write computer programs for enjoyment" I did not mean programming. I meant, and advisedly said, hacking. Quick is the operative word there. Creating the odd link, moving and/or renaming the odd file is NOT programming in my book. Lisi