23 Aug 2006 09:38
Re: Understanding Pine incoming ....
>> Unfortunately, you're right that ^T doesn't work here -- I'll >> add this to my Pine wish list. Maybe you could post this wish >> in one of the Pine discussion groups? > > I sent it to the one on gmane, and got an acknowledgement; I > may not be subscribed to that one ... Thank you, let's hope that ^T will work for incoming-folder specifications in the upcoming Alpine (Apache-Licensed Pine)! >> You can, however, use ^X if the fully qualified folder >> specification is the same as your inbox-path folder. >> >> Let me know if ^X works for you! > > It worked just now when I added an incoming folder -- took > the full form from Lserv -- and, I think, would have let me > edit it into one for another ISP. Excellent. Another trick is to temporarily change your inbox-path while you add nicknames for folders on that (the temporary) inbox-path's server. When you're done setting up those nicknames, switch the inbox-path back to what you really want for your inbox-path. It's a hack, but it works! Nancy
RSS Feed