Re: [Enigmail] keymanager - column display

2014-02-03 Thread Anne Wilson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2014 17:40, Philip Jackson wrote: When I add 'fingerprint', 'name' shoves off the left hand side. You are quite right that by dragging the border on the left-hand side of the rightmost wide fingerprint column, I can reduce its width. But

Re: [Enigmail] keymanager - column display

2014-02-02 Thread Philip Jackson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2014 20:31, David wrote: On 2/2/2014 12:40 PM, Philip Jackson wrote: Hi : I have now managed by pulling and pushing borders to get a display of key manager with 5 columns : Name, KeyID, Type, Key validity, Expiry. This is quite

Re: [Enigmail] keymanager - column display

2014-02-02 Thread Ludwig Hügelschäfer
On 02.02.14 18:40, Philip Jackson wrote: (...) My conclusion is that there must be some difference in the implementation of the key manager display and the Thunderbird display. No, there isn't. (...) But since this does not seem to affect anyone else I just managed to make the name column

Re: [Enigmail] keymanager - column display

2014-02-02 Thread David
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/2/2014 3:12 PM, Philip Jackson wrote: On 02/02/2014 20:31, David wrote: On 2/2/2014 12:40 PM, Philip Jackson wrote: Hi : I have now managed by pulling and pushing borders to get a display of key manager with 5 columns : Name, KeyID, Type,

Re: [Enigmail] keymanager - column display

2014-02-02 Thread Philip Jackson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/02/2014 22:01, Ludwig Hügelschäfer wrote: On 02.02.14 18:40, Philip Jackson wrote: (...) My conclusion is that there must be some difference in the implementation of the key manager display and the Thunderbird display. No, there isn't.

Re: [Enigmail] keymanager - column display

2014-02-02 Thread Ludwig Hügelschäfer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 02.02.14 22:54, Philip Jackson wrote: Good news !! (...) I'm sorry for all the time you've wasted on my problem. Your strange experience maybe was the result of a corrupted localstore.rdf file (located in the profile directory). I once had