If some control characters don't work in Pine (or Pico), it is probably because the communication or operating system software you are using is intercepting those characters before they get to Pine. Some that are more likely to be intercepted include ^C, ^J, ^O, ^^, and ^_. If you are unable to reconfigure your communication software to correct this, a work-around is to press the ESCAPE key twice followed by the desired control key. For example, ^C would be simulated by pressing "ESC ESC C" and "^^" would be "ESC ESC ^".
Some of the Pine commands you may read or hear about have to be explicitly enabled in the [S]ETUP CONFIGURATION screen, which is accessed from Pine's [M]AIN MENU, to be functional. For example, to be able to use the "B Bounce" command, the following feature has to be checked:
[X] enable-bounce-cmd
and to be able to use the "Select"/"Apply" operations, you must first check:
[X] enable-aggregate-command-set
Also note: The key menu at the bottom of the message composer does not show all of the available commands. Use "^G Get Help" for a complete list.
Go into SETUP CONFIGURATION, pressing M for Main Menu, S for Setup and then C for Config, and check the setting of compose-maps-delete-key-to-ctrl-d.
If you are running pine from a terminal emulator/telnet, make sure the client is configured correctly for the delete/backspace key.
By pressing ESC ESC 'n', where n is the decimal ASCII (American Standard Code for Information Interchange) code for the character.
That's true! but there is solution within pine, which is kind of awkward to say the least. First you need to make sure that pine accepts that input. You have to set your charater-set to be "ISO-8859-1", instead of US-ASCII (the default). Now whenever you want to insert a character with an accent you have to press ESC ESC n, where "n" is the ascii code of the character, here there is a small dictionary for you: http://www.w3.org/MarkUp/Wilbur/latin1.gifQ&A submitted by: Timothy J. Luoma <luomat+pine@luomat.peak.org>
(From the PINE source code:)
The files are useful for figuring out what a user did when he complains that something went wrong. It's important to keep a bunch around, usually 4, so that the debug file in question will still be around when the problem gets investigated. Users tend to go in and out of Pine a few times and there is one file for each pine invocation.
Yes, but there's really no need to do so. PINE will only keep a certain amount of them around, usually 4. The files are rather small and do no harm.
You can prevent the files from being created by using the -d flag as follows:
-d n
If n=0, no debug files will be created.
You can change the level of debugging done with numbers 1-9:
1 - logs only highest level events and errors 2 - logs events like file writes 3 - 4 - logs each command 5 - 6 - 7 - logs details of command execution (7 is highest to run any production) 8 - 9 - logs gross details of command execution
For systems administrators and advanced users, see also 12.13 Where is the .pine-debug setting set at compile-time?.
Q&A by Scott Liebrand <leibrand@u.washington.edu>
Probably because it is confused about who to log in as. This occurs when Pine is configured to access remote folders or mailboxes at remote or multiple servers. By default Pine uses the login used when Pine first begins.
To clear up the confusion, edit your pinerc and add /user=yourusername to every instance of your mail server address.
For example,
{mail.server.edu}INBOX
would become,
{mail.server.com/user=yourusername}INBOX
Any other attempts made to have Pine remember your password will be futile unless this problem is fixed first.
Pine is capable of accessing POP3 Mailboxes, but only in a quasi-online mode, unable to preserve message flags (New, Read, Deleted). Furthermore, due to the nature of the POP3 Protocol, Pine will not see new messages arriving on the POP3 server unless the connection to the server is closed and reopened. This occurs by quitting and restarting Pine, or by opening another folder and and then returning to the POP3 inbox. POP3, unlike IMAP, has no way of announcing the arrival of new messages.
One possible explaination is Pine trying to open a UNIX remote shell connection, which is not possible on certain server types. Therefore, setting rsh-open-timout equal to 0 (zero) could possibly remedy the large amount of time it takes Pine to open an inbox located on such a server.