open all threds command bug?

2004-06-25 Thread Jan Rifkinson
On my system, shortcut ctlshft* no longer opens all msgs in folder. Can anyone confirm? Thanks, -- Jan Rifkinson Ridgefield, CT USA TB! V2.12 Beta/1/W2K_SP3 ICQ 41116329 Current version is 2.11.02 | 'Using TBUDL' information:

Re: open all threds command bug?

2004-06-25 Thread Roelof Otten
Hallo Jan, On Fri, 25 Jun 2004 08:01:44 -0400GMT (25-6-2004, 14:01 +0200, where I live), you wrote: JR On my system, shortcut ctlshft* no longer opens all msgs in JR folder. JR Can anyone confirm? Yep. CtrlShift* closes all threads on my system. CtrlAlt* opens them. Though I continuously mix

Re[2]: open all threds command bug?

2004-06-25 Thread Maggie
Hello Roelof and Jan, Friday, June 25, 2004, 8:32:19 AM, you wrote: JR On my system, shortcut ctlshft* no longer opens all msgs in JR folder. JR Can anyone confirm? R Yep. CtrlShift* closes all threads on my system. CtrlAlt* R opens them. Though I continuously mix up those two, I wouldn't be R

Re: open all threds command bug?

2004-06-25 Thread Roelof Otten
Hallo Maggie, On Fri, 25 Jun 2004 09:05:29 -0400GMT (25-6-2004, 15:05 +0200, where I live), you wrote: R Yep. CtrlShift* closes all threads on my system. CtrlAlt* R opens them. Though I continuously mix up those two, I wouldn't be R surprised that this is as it always has been. M On my laptop,

Re[2]: open all threds command bug?

2004-06-25 Thread Maggie
Hello Roelof, M On my laptop, neither of the commands works. They do nothing it seems. M I am sorting by References. R That's a known issue, since you're supposed to use the * on the R numerical keypad and that's lacking on (most) laptops. Aha! OK. Just for the heck of it, I tried Fn+0 (zero)

Re: open all threds command bug?

2004-06-25 Thread Thomas Fernandez
Hello Jan, On Fri, 25 Jun 2004 08:01:44 -0400 GMT (25/06/2004, 19:01 +0700 GMT), Jan Rifkinson wrote: JR On my system, shortcut ctlshft* no longer opens all msgs in JR folder. It's crtl-* (no shift) over here that works fine, as it always has. -- Cheers, Thomas. Moderator der deutschen The

Re[3]: open all threds command bug?

2004-06-25 Thread Richard H. Stoddard
Maggie, Friday, June 25, 2004, 6:18:08 PM, you wrote: M Aha! OK. Just for the heck of it, I tried Fn+0 (zero) where the M asterisk is on the numeric keypad and none of the combinations worked M with that. But thank you for your explanation. :) Surprise, surprise - I tried Fn+0 with CtrlAlt

Re[4]: open all threds command bug?

2004-06-25 Thread Maggie
Hello Richard, Friday, June 25, 2004, 10:20:17 AM, you wrote: M Aha! OK. Just for the heck of it, I tried Fn+0 (zero) where the M asterisk is on the numeric keypad and none of the combinations worked M with that. But thank you for your explanation. :) R Surprise, surprise - I tried Fn+0 with

Re: open all threds command bug?

2004-06-25 Thread Cyrille
Hello Roelof, Friday, June 25, 2004, 3:11:34 PM, you wrote: R CtrlShift* closes all threads on my system. CtrlAlt* R opens them. M On my laptop, neither of the commands works. They do nothing it seems. M I am sorting by References. R That's a known issue, since you're supposed to use the * on

Re[5]: open all threds command bug?

2004-06-25 Thread Richard H. Stoddard
Maggie, Friday, June 25, 2004, 7:42:51 PM, you wrote: M OK. I hadn't tried doing Ctrl+Shift+Fn+0 - Ctrl+Alt+Fn+0, not Shift, at least not on mine.. M If I hold Ctrl+Shift+Fn then tap the 0, it rather seems to work like a M toggle here on the Toshiba. But trying to get all the fingers in M

Re: open all threds command bug?

2004-06-25 Thread Adam
Hello Jan, Friday, June 25, 2004, 9:31:44 AM, you wrote: On my system, shortcut ctlshft* no longer opens all msgs in folder. Can anyone confirm? I can kind of confirm. I certainly notice occasionally I ^* to open all threads, and TB fails to respond to that. And it stays that way till I

Re: open all threds command bug?

2004-06-25 Thread Adam
Hello Roelof, Friday, June 25, 2004, 10:41:34 AM, you wrote: M On my laptop, neither of the commands works. They do nothing it seems. M I am sorting by References. That's a known issue, since you're supposed to use the * on the numerical keypad and that's lacking on (most) laptops. With a