Feature request
Beartooth <[email protected]>
| Newsgroups | gmane.mail.pine.general |
|---|---|
| Message-ID | <[email protected]> |
There are several places in pine where, when I want to add something, a fully qualified folder specification is either required or advised (in a FAQ, for instance). In some but not others of these places, ^T will get either what I want, or something from which, with care, I can clone what I want. It works at several places while constructing a role or a filter, and is a great help. In MSC > --- [ Normally hidden configuration options ] ---, for instance, if I want to add or rename a collection, ^T does not work. Nor does it at the top of MSC if I want to add, say, an archiving pair. For those of us who can just about manage to understand what a fully qualified folder specification is, or at most recognize one, this would be a great help. Understanding a fully qualified folder specification is not enough even for proofreading, let alone constructing one. But I suspect for various reasons that the number of us beginning to need such advanced devices is on the rise, particularly as we begin using more than one ISP. -- Beartooth Staffwright, PhD, Neo-Redneck Linux Convert What do they know of country, who only country know? _______________________________________________ Pine-info mailing list [email protected] http://mailman1.u.washington.edu/mailman/listinfo/pine-info