978 lines
32 KiB
HTML
978 lines
32 KiB
HTML
|
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
|
<HTML><HEAD><TITLE>Man page of pidgin</TITLE>
|
|
</HEAD><BODY>
|
|
<H1>pidgin</H1>
|
|
Section: User Commands (1)<BR>Updated: <BR><A HREF="#index">Index</A>
|
|
<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
|
|
|
<A NAME="lbAB"> </A>
|
|
<H2>NAME</H2>
|
|
|
|
pidgin - Instant Messaging client
|
|
<A NAME="lbAC"> </A>
|
|
<H2>SYNOPSIS</H2>
|
|
|
|
<DL COMPACT>
|
|
<DT id="1"><B>pidgin </B><I>[options]</I><DD>
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAD"> </A>
|
|
<H2>DESCRIPTION</H2>
|
|
|
|
<P>
|
|
|
|
<B>pidgin</B> is a graphical modular messaging client based on libpurple
|
|
which is capable of connecting to AIM, XMPP, ICQ, IRC, SILC,
|
|
Novell GroupWise, Lotus Sametime, Zephyr, Gadu-Gadu, and QQ all at once. It has
|
|
many common features found in other clients, as well as many unique features.
|
|
Pidgin is not endorsed by or affiliated with America Online, ICQ, or Microsoft.
|
|
<P>
|
|
|
|
Pidgin can be extended by plugins written in multiple programming languages and
|
|
controlled through DBus or <B>purple-remote</B>.
|
|
<P>
|
|
<A NAME="lbAE"> </A>
|
|
<H2>OPTIONS</H2>
|
|
|
|
The following options are provided by Pidgin using the standard GNU
|
|
command line syntax:
|
|
<DL COMPACT>
|
|
<DT id="2"><B>-c, --config=</B><I>DIR</I><B></B>
|
|
|
|
<DD>
|
|
Use <I>DIR</I> as the directory for config files instead of <I>~/.purple</I>.
|
|
<DT id="3"><B>-d, --debug</B>
|
|
|
|
<DD>
|
|
Print debugging messages to stdout. These are the same debugging messages
|
|
that are displayed in the <B>Debug Window</B>.
|
|
<DT id="4"><B>-f, --force-online</B>
|
|
|
|
<DD>
|
|
Try to be online even if the network is reported (by Windows, or NetworkManager
|
|
on Linux) to be unavailable.
|
|
<DT id="5"><B>-h, --help</B>
|
|
|
|
<DD>
|
|
Print a summary of command line options and exit.
|
|
<DT id="6"><B>-m, --multiple</B>
|
|
|
|
<DD>
|
|
Allow multiple instances of Pidgin to run.
|
|
<DT id="7"><B>-n, --nologin</B>
|
|
|
|
<DD>
|
|
Don't automatically login when Pidgin starts. Sets the global status to
|
|
<B>Offline</B>.
|
|
<DT id="8"><B>-l, --login[=</B><I>NAME</I>,<I>NAME</I>,...]
|
|
|
|
<DD>
|
|
Enable the comma-separated list of accounts provided, disabling all other
|
|
accounts. If the user does not specify such a comma-separated list, the
|
|
first account in accounts.xml will be enabled.
|
|
<DT id="9"><B>-v, --version</B>
|
|
|
|
<DD>
|
|
Print the current version and exit.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAF"> </A>
|
|
<H2>TERMS</H2>
|
|
|
|
Pidgin uses a few terms differently from other applications. For convenience
|
|
they are defined here:
|
|
<DL COMPACT>
|
|
<DT id="10"><B>Buddy List</B>
|
|
|
|
<DD>
|
|
The list of other users who the user wants to see status information for
|
|
and have quick access to for messaging.
|
|
<DT id="11"><B>Buddy</B>
|
|
|
|
<DD>
|
|
A user who has been added to the Buddy List.
|
|
<DT id="12"><B>Contact</B>
|
|
|
|
<DD>
|
|
A grouping of more than one buddy who are all the same person. A contact may
|
|
contain buddies from any protocol and may contain as many buddies as the user
|
|
desires. Contact arrangements are stored locally only.
|
|
<DT id="13"><B>Alias</B>
|
|
|
|
<DD>
|
|
A private "nickname" that may be set for Buddies or the user himself. On some
|
|
protocols, aliases are saved on the server but not visible to other users. On
|
|
other protocols, aliases are saved only locally.
|
|
<DT id="14"><B>Protocol</B>
|
|
|
|
<DD>
|
|
A messaging service. AIM, XMPP, Zephyr, etc. are protocols. Others may
|
|
call these "service types," "account types," "services," and so on.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAG"> </A>
|
|
<H2>BUDDY LIST</H2>
|
|
|
|
The <B>Buddy List</B> window is Pidgin's main interface window. Using
|
|
this window a user can see which of his/her buddies is online, away, idle,
|
|
etc. The user can also add buddies to and remove buddies from the buddy list.
|
|
<P>
|
|
The <B>Buddy List</B> window contains a list of the user's buddies who are
|
|
online and have allowed the user to be notified of their presence. The icon
|
|
to the left of each buddy indicates the buddy's current status. Double
|
|
clicking a buddy will open a new <B>Conversation</B> window. Right clicking
|
|
will pop up a menu:
|
|
<DL COMPACT>
|
|
<DT id="15"><B>Get Info</B>
|
|
|
|
<DD>
|
|
Retrieves and displays information about the buddy. This information is
|
|
also known as a Profile.
|
|
<DT id="16"><B>IM</B>
|
|
|
|
<DD>
|
|
Opens a new <B>Conversation</B> window to the selected buddy.
|
|
<DT id="17"><B>Send File</B>
|
|
|
|
<DD>
|
|
Sends a file to the selected buddy (only available on protocols that support
|
|
file transfer).
|
|
<DT id="18"><B>Add Buddy Pounce</B>
|
|
|
|
<DD>
|
|
A Buddy Pounce is a configurable automated action to be performed when the
|
|
buddy's state changes. This will open the <B>Buddy Pounce</B> dialog, which
|
|
will be discussed later.
|
|
<DT id="19"><B>View Log</B>
|
|
|
|
<DD>
|
|
Pidgin is capable of automatically logging messages. These logs are
|
|
either plain text files (with a .txt extension) or html files (with a
|
|
.html extension) located under the <I>~/.purple/logs</I> directory. This
|
|
menu command will display Pidgin's log viewer with logs loaded for that
|
|
buddy or chat.
|
|
<DT id="20"><B>Alias</B>
|
|
|
|
<DD>
|
|
Create an alias for this buddy. This will show an editable text field where
|
|
the buddy's name was displayed. In this field one can give this
|
|
buddy an alternate, more friendly name to appear on the buddy list and in
|
|
conversations.
|
|
<P>
|
|
For example, if a buddy's name was jsmith1281xx and his real
|
|
name was 'John Q. Smith,' one could create an alias as to identify the
|
|
buddy by his common name.
|
|
</DL>
|
|
<P>
|
|
|
|
The remainder of the menu will consist of protocol specific commands.
|
|
These commands vary depending on the protocol.
|
|
<DL COMPACT>
|
|
<DT id="21"><B>Status Selector</B>
|
|
|
|
<DD>
|
|
At the bottom of the <B>Buddy List</B> is a status selector which allows one to
|
|
change his/her status. This will be discussed further in the <B>STATUS
|
|
MESSAGES</B> section below.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAH"> </A>
|
|
<H2>ACCOUNT EDITOR</H2>
|
|
|
|
The account editor consists of a list of accounts and information about
|
|
them. It can be accessed by selecting <B>Manage</B> from the Accounts menu.
|
|
Clicking <I>Delete</I> will delete the currently selected account.
|
|
Clicking <I>Add</I> or <I>Modify</I> will invoke a <B>Modify Account</B>
|
|
window. Here, the user can add or alter account information. When creating
|
|
a new account, the user will submit a username and password. The user will
|
|
also choose the protocol for the account.
|
|
<P>
|
|
If <I>Remember Password</I> is chosen, the password will be saved in
|
|
Pidgin's <I>~/.purple/accounts.xml</I> configuration file.
|
|
<P>
|
|
If <I>Enabled</I> is checked in the accounts dialog, this account will
|
|
follow the status currently selected in the status selector. If it is
|
|
not checked, the account will always be offline.
|
|
<P>
|
|
Each protocol has its own specific options that can be found in the
|
|
modify screen.
|
|
<P>
|
|
<A NAME="lbAI"> </A>
|
|
<H2>PREFERENCES</H2>
|
|
|
|
<P>
|
|
All options take effect immediately.
|
|
<P>
|
|
<A NAME="lbAJ"> </A>
|
|
<H2>Interface</H2>
|
|
|
|
<P>
|
|
<DL COMPACT>
|
|
<DT id="22"><B>Show system tray icon</B>
|
|
|
|
<DD>
|
|
Specifies when to show a Pidgin icon in the notification area of the user's
|
|
panel (commonly referred to as the System Tray).
|
|
<P>
|
|
<DT id="23"><B>Hide new IM conversations</B>
|
|
|
|
<DD>
|
|
Specifies when to hide new IM messages. Messages will queue under the
|
|
specified condition until shown. Clicking the Pidgin icon in the
|
|
notification area or system tray will display the queued messages. An
|
|
icon also appears in the buddy list's menu bar; this icon may also be
|
|
used to display queued messages.
|
|
<P>
|
|
<DT id="24"><B>Show IMs and chats in tabbed windows</B>
|
|
|
|
<DD>
|
|
When checked, this option will cause IM and chat sessions to appear in
|
|
windows with multiple tabs. One tab will represent one conversation or
|
|
chat. Where tabs are placed will be dictated by the preferences below.
|
|
<P>
|
|
<DT id="25"><B>Show close buttons on tabs</B>
|
|
|
|
<DD>
|
|
When checked, this option will cause a clickable "U+2715 MULTIPLICATION X"
|
|
unicode character to appear at the right edge of each tab. Clicking this
|
|
will cause the tab to be closed.
|
|
<P>
|
|
<DT id="26"><B>Placement</B>
|
|
|
|
<DD>
|
|
Specifies where to place tabs in the window. Some tab orientations may
|
|
allow some users to fit more tabs into a single window comfortably.
|
|
<P>
|
|
<DT id="27"><B>New conversations</B>
|
|
|
|
<DD>
|
|
Specifies under which conditions tabs are placed into existing windows or
|
|
into new windows. For a single window, select <I>Last created window</I> here.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAK"> </A>
|
|
<H2>Conversations</H2>
|
|
|
|
<P>
|
|
<DL COMPACT>
|
|
<DT id="28"><B>Enable buddy icon animation</B>
|
|
|
|
<DD>
|
|
If a buddy's icon happens to be animated, this option will enable the
|
|
animation, otherwise only the first frame will be displayed.
|
|
<P>
|
|
<DT id="29"><B>Notify buddies that you are typing to them</B>
|
|
|
|
<DD>
|
|
Some protocols allow clients to tell their buddies when they are typing.
|
|
This option enables this feature for protocols that supports it.
|
|
<P>
|
|
<DT id="30"><B>Default Formatting</B>
|
|
|
|
<DD>
|
|
Allows specifying the default formatting to apply to all outgoing messages
|
|
(only applicable to protocols that support formatting in messages).
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAL"> </A>
|
|
<H2>Smiley Themes</H2>
|
|
|
|
Allows the user to choose between different smiley themes. The "none" theme
|
|
will disable graphical emoticons - they will be displayed as text instead.
|
|
The <B>Add</B> and <B>Remove</B> buttons may be used to install or uninstall
|
|
smiley themes. Themes may also be installed by dragging and dropping them
|
|
onto the list of themes.
|
|
<P>
|
|
<A NAME="lbAM"> </A>
|
|
<H2>Sounds</H2>
|
|
|
|
<P>
|
|
<DL COMPACT>
|
|
<DT id="31"><B>Method</B>
|
|
|
|
<DD>
|
|
Lets the user choose between different playback methods. The user can also
|
|
manually enter a command to be executed when a sound is to be played(<I>%s</I> expands to the full path to the file name).
|
|
<P>
|
|
<DT id="32"><B>Sounds when conversation has focus</B>
|
|
|
|
<DD>
|
|
When checked, sounds will play for events in the active conversation if
|
|
the window is focused. When unchecked, sounds will not play for the
|
|
active conversation when the window is focused.
|
|
<P>
|
|
<DT id="33"><B>Enable Sounds</B>
|
|
|
|
<DD>
|
|
Determines when to play sounds.
|
|
<P>
|
|
<DT id="34"><B>Sound Events</B>
|
|
|
|
<DD>
|
|
Lets the user choose when and what sounds are to be played.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAN"> </A>
|
|
<H2>Network</H2>
|
|
|
|
<P>
|
|
<DL COMPACT>
|
|
<DT id="35"><B>STUN server</B>
|
|
|
|
<DD>
|
|
This allows specifying a server which uses the STUN protocol to determine
|
|
a host's public IP address. This can be particularly useful for some
|
|
protocols.
|
|
<P>
|
|
<DT id="36"><B>Autodetect IP address</B>
|
|
|
|
<DD>
|
|
When checked, causes Pidign to attempt to determine the public IP address
|
|
of the host on which Pidgin is running and disables the <B>Public IP</B>
|
|
text field listed below.
|
|
<P>
|
|
<DT id="37"><B>Public IP</B>
|
|
|
|
<DD>
|
|
If <B>Autodetect IP address</B> is disabled, this field allows manually
|
|
specifying the public IP address for the host on which Pidgin is running.
|
|
This is mainly useful for users with multiple network interfaces or behind
|
|
NATs.
|
|
<P>
|
|
<DT id="38"><B>Manually specify range of ports to listen on</B>
|
|
|
|
<DD>
|
|
Specify a range ports to listen on, overriding any defaults. This is
|
|
sometimes useful for file transfers and Direct IM.
|
|
<P>
|
|
<DT id="39"><B>Proxy Server</B>
|
|
|
|
<DD>
|
|
The configuration section to enable Pidgin to operate through a proxy
|
|
server. Pidgin currently supports SOCKS 4/5 and HTTP proxies.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAO"> </A>
|
|
<H2>Browser</H2>
|
|
|
|
<P>
|
|
<DL COMPACT>
|
|
<DT id="40"><B>Browser</B>
|
|
|
|
<DD>
|
|
Allows the user to select Pidgin's default web browser. Firefox, Galeon,
|
|
Konqueror, Mozilla, Netscape and Opera are supported natively. The user
|
|
can also manually enter a command to be executed when a link is clicked
|
|
(<I>%s</I> expands to the URL). For example, <I>xterm -e lynx "%s"</I> will
|
|
open the link with lynx.
|
|
<P>
|
|
<DT id="41"><B>Open link in</B>
|
|
|
|
<DD>
|
|
Allows the user to specify whether to use an existing window, a new tab, a
|
|
new window, or to let the browser to decide what to do when calling the
|
|
browser to open a link. Which options are available will depend on which
|
|
browser is selected.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAP"> </A>
|
|
<H2>Logging</H2>
|
|
|
|
<P>
|
|
<DL COMPACT>
|
|
<DT id="42"><B>Log format</B>
|
|
|
|
<DD>
|
|
Specifies how to log. Pidgin supports HTML and plain text, but plugins can
|
|
provide other logging methods.
|
|
<P>
|
|
<DT id="43"><B>Log all instant messages</B>
|
|
|
|
<DD>
|
|
When enabled, all IM conversations are logged. This can be overridden on a
|
|
per-conversation basis in the conversation window.
|
|
<P>
|
|
<DT id="44"><B>Log all chats</B>
|
|
|
|
<DD>
|
|
When enabled, all chat conversations are logged. This can be overridden on a
|
|
per-conversation basis in the conversation window.
|
|
<P>
|
|
<DT id="45"><B>Log all status changes to system log</B>
|
|
|
|
<DD>
|
|
When enabled, status changes are logged.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAQ"> </A>
|
|
<H2>Status / Idle</H2>
|
|
|
|
<P>
|
|
<DL COMPACT>
|
|
<DT id="46"><B>Report idle time</B>
|
|
|
|
<DD>
|
|
Determines under which conditions to report idle time. <B>Based on keyboard
|
|
and mouse use</B> uses keyboard and mouse activity to determine idle time.
|
|
<B>From last sent message</B> uses the time at which the user last sent a
|
|
message in Pidgin to determine idle. <B>Never</B> disables idle reporting.
|
|
<P>
|
|
<DT id="47"><B>Auto-reply</B>
|
|
|
|
<DD>
|
|
Determines when to send an auto-reply on protocols which support it
|
|
(currently only AIM).
|
|
<P>
|
|
<DT id="48"><B>Change status when idle</B>
|
|
|
|
<DD>
|
|
When enabled, this uses the <B>Minutes before becoming idle</B> and <B>Change
|
|
status to</B> preferences described below to set status on idle.
|
|
<P>
|
|
<DT id="49"><B>Minutes before becoming idle</B>
|
|
|
|
<DD>
|
|
Specifies how many minutes of inactivity are required before considering the
|
|
user to be idle.
|
|
<P>
|
|
<DT id="50"><B>Change status to</B>
|
|
|
|
<DD>
|
|
Specifies which "primitive" or "saved" status to use when setting status on
|
|
idle.
|
|
<P>
|
|
<DT id="51"><B>Use status from last exit at startup</B>
|
|
|
|
<DD>
|
|
If this is checked, Pidgin will remember what status was active when the
|
|
user closed Pidgin and restore it at the next run. When disabled, Pidgin
|
|
will always set the status selected in <B>Status to apply at startup</B>
|
|
at startup.
|
|
<P>
|
|
<DT id="52"><B>Status to apply at startup</B>
|
|
|
|
<DD>
|
|
When <B>Use status from last exit at startup</B> is disabled, this specifies
|
|
which "primitive" or "saved" status to use at startup.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAR"> </A>
|
|
<H2>CONVERSATIONS</H2>
|
|
|
|
When starting a new conversation, the user is presented with the
|
|
<B>Conversation</B> window. The conversation appears in the upper text box
|
|
and the user types his/her message in the lower text box. Between the two
|
|
is a row of options, represented by icons. Some or all buttons may not be
|
|
active if the protocol does not support the specific formatting. From left
|
|
to right:
|
|
<DL COMPACT>
|
|
<DT id="53"><B>Font</B>
|
|
|
|
<DD>
|
|
This menu provides font control options for the current conversation. Size,
|
|
style, and face may be configured here.
|
|
<DT id="54"><B>Insert</B>
|
|
|
|
<DD>
|
|
This menu provides the ability to insert images, horizontal rules, and links
|
|
where the protocol supports each of these features.
|
|
<DT id="55"><B>Smile!</B>
|
|
|
|
<DD>
|
|
Allows the insertion of graphical smileys via the mouse. This button shows
|
|
the user a dialog with the available smileys for the current conversation.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAS"> </A>
|
|
<H2>CHATS</H2>
|
|
|
|
For protocols that allow it, <B>Chats</B> can be entered through the
|
|
<I>Buddies</I> menu.
|
|
<P>
|
|
Additional features available in chat, depending on the protocol are:
|
|
<DL COMPACT>
|
|
<DT id="56"><B>Whisper</B>
|
|
|
|
<DD>
|
|
The text will appear in the chat conversation, but it will only be visible
|
|
to the sender and the receiver.
|
|
<DT id="57"><B>Invite</B>
|
|
|
|
<DD>
|
|
Invite other people to join the chat room.
|
|
<DT id="58"><B>Ignore</B>
|
|
|
|
<DD>
|
|
Ignore anything said by the chosen person
|
|
<DT id="59"><B>Set Topic</B>
|
|
|
|
<DD>
|
|
Set the topic of the chat room. This is usually a brief sentence
|
|
describing the nature of the chat--an explanation of the chat room's name.
|
|
<DT id="60"><B>Private Message (IM)</B>
|
|
|
|
<DD>
|
|
Send a message to a specific person in the chat. Messages sent this way will
|
|
not appear in the chat window, but instead open a new IM conversation.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAT"> </A>
|
|
<H2>STATUS MESSAGES</H2>
|
|
|
|
Most protocols allow for status messages. By using status messages, a user
|
|
can leave an informative message for others to see. Status and status
|
|
messages are configured via the status selector at the bottom of the Buddy
|
|
List window. By default the menu shown here is divided into sections for
|
|
"primitive" status types, such as <I>Available</I>, <I>Away</I>, etc.; a few
|
|
"popular" statuses (including "transient" statuses) which have been
|
|
recently used, and a section which shows <B>New Status...</B> and <B>Saved
|
|
Statuses...</B> options for more advanced status manipulation.
|
|
<P>
|
|
<DL COMPACT>
|
|
<DT id="61"><B>Primitive Statuses</B>
|
|
|
|
<DD>
|
|
A primitive status is a basic status supported by the protocol. Examples of
|
|
primitive statuses would be Available, Away, Invisible, etc. A primitive
|
|
status can be used to create a <B>Transient Status or a Saved Status</B>,
|
|
both explained below. Essentially, primitive statuses are building blocks
|
|
of more complicated statuses.
|
|
<P>
|
|
<DT id="62"><B>Transient Statuses</B>
|
|
|
|
<DD>
|
|
When one of the statuses from the topmost section of the status selector's
|
|
menu is selected, this creates a transient, or temporary, status. The status
|
|
will show in the "popular statuses" section in the menu until it has not been
|
|
used for a sufficiently long time. A transient status may also be created by
|
|
selecting <I>New Status...</I> from the status selector's menu, then clicking
|
|
<I>Use</I> once the user has entered the message.
|
|
<P>
|
|
<DT id="63"><B>Saved Statuses</B>
|
|
|
|
<DD>
|
|
Saved statuses are permanent--once created, they will exist until deleted.
|
|
Saved statuses are useful for statuses and status messages that will be used
|
|
on a regular basis. They are also useful for creating complex statuses in
|
|
which some accounts should always have a different status from others. For
|
|
example, one might wish to create a status called "Sleeping" that has all
|
|
accounts set to "Away", then create another status called "Working" that
|
|
has three accounts set to "Away" and another account set to "Available."
|
|
<P>
|
|
<DT id="64"><B>New Status Window</B>
|
|
|
|
<DD>
|
|
When the user selects <I>New Status...</I> from the status selector menu,
|
|
Pidgin presents the user with a dialog asking for status-related information.
|
|
That information is discussed below:
|
|
<P>
|
|
<I>Title</I> - The name of the status that will appear in the status selctor's
|
|
menu. If the user clicks the <I>Save</I> or <I>Save & Use</I> button, this
|
|
name will also be shown in the <B>Saved Status Window</B>. The title should
|
|
be a short description of the status.
|
|
<P>
|
|
<I>Status</I> - The type of status being created, such as Available, Away, etc.
|
|
<P>
|
|
<I>Message</I> - The content of the status message. This is what is visible
|
|
to other users. Some protocols will allow formatting in some status messages;
|
|
where formatting is not supported it will be stripped to the bare text entered.
|
|
<P>
|
|
<I>Use a different status for some accounts</I> - This allows the creation of
|
|
complex statuses in which some accounts' status differs from that of other
|
|
accounts. To use this, the user will click the expander to the left of the
|
|
text, then select individual accounts which will have a different status
|
|
and/or status message. When the user selects an account, Pidgin will present
|
|
another status dialog asking for a status and a message just for the selected
|
|
account.
|
|
<P>
|
|
<DT id="65"><B>Saved Status Window</B>
|
|
|
|
<DD>
|
|
When the user selects <I>Saved Statuses...</I> from the status selector's menu,
|
|
Pidgin presents a dialog that lists all saved statuses. "Transient" statuses,
|
|
discussed above, are <B></B><I>NOT</I> shown here. This window provides the
|
|
ability to manage saved statuses by allowing the creation, modification, and
|
|
deletion of saved statuses. The <I>Use</I>, <I>Modify</I>, and <I>Delete</I>
|
|
buttons here allow operation on the status selected from the list; the dd
|
|
button allows creation of a new saved status, and the <I>Close</I> button closes
|
|
the window.
|
|
<P>
|
|
</DL>
|
|
<A NAME="lbAU"> </A>
|
|
<H2>BUDDY POUNCE</H2>
|
|
|
|
A Buddy Pounce is an automated trigger that occurs when a buddy returns to
|
|
a normal state from an away state. The <B>Buddy Pounce</B> dialog box
|
|
can be activated by selecting the <I>Buddy Pounce</I> option from the
|
|
<B>Tools</B> menu. From this dialog, new pounces can be created with the
|
|
<B>Add</B> button and existing pounces can be removed with the <B>Delete</B>
|
|
button. A pounce can be set to occur on any combination of the
|
|
events listed, and any combination of actions can result. If <I>Pounce
|
|
only when my status is not Available</I> is checked, the pounce will occur
|
|
only if the user is set to a non-available status, such as invisible, do not
|
|
disturb, away, etc. If <I>Recurring</I> is checked, the pounce will remain
|
|
until removed by the <B>Delete</B> button.
|
|
<P>
|
|
<A NAME="lbAV"> </A>
|
|
<H2>CUSTOM SMILIES</H2>
|
|
|
|
Pidgin 2.5.0 introduced support for custom smilies on those protocols for which
|
|
interested contributors have developed support. The custom smiley manager can
|
|
be accessed by selecting <I>Smiley</I> from the <I>Tools</I> menu. From here,
|
|
custom smilies may be added, edited, or deleted by clicking the <I>Add</I>,
|
|
<I>Edit</I>, or <I>Delete</I> buttons, respectively.
|
|
<P>
|
|
During a conversation with another user, that user's custom smileys may be
|
|
added to the user's own custom smiley list directly from the conversation
|
|
window by right-clicking the new custom smiley and selecting <I>Add Custom
|
|
Smiley...</I>
|
|
<P>
|
|
<A NAME="lbAW"> </A>
|
|
<H2>PLUGINS</H2>
|
|
|
|
Pidgin allows for dynamic loading of plugins to add extra functionality
|
|
to Pidgin. See <I>plugins/HOWTO</I> or
|
|
<I><A HREF="http://developer.pidgin.im/wiki/CHowTo">http://developer.pidgin.im/wiki/CHowTo</A></I> for information on writing
|
|
plugins.
|
|
<P>
|
|
The plugins dialog can be accessed by selecting <I>Plugins</I> from the
|
|
<I>Tools</I> menu. Each plugin available appears in this dialog with its name,
|
|
version, and a short summary of its functionality. Plugins can be enabled
|
|
with the checkbox beside the name and short description. More information on
|
|
the currently selected plugin is available by clicking the expander beside the
|
|
text <I>Plugin Details</I>. If the selected plugin has preferences or
|
|
configuration options, the <I>Configure Plugin</I> button will present the
|
|
plugin's preferences dialog.
|
|
<P>
|
|
<A NAME="lbAX"> </A>
|
|
<H2>PERL</H2>
|
|
|
|
Pidgin allows for plugins to be written in the perl scripting language. See
|
|
<I>Perl Scripting HOWTO</I> in the Pidgin documentation for more information
|
|
about perl scripting.
|
|
<P>
|
|
<A NAME="lbAY"> </A>
|
|
<H2>TCL</H2>
|
|
|
|
Pidgin allows for plugins to be written in the Tcl scripting language. See
|
|
<I>plugins/tcl/TCL-HOWTO</I> for more information about Tcl scripting.
|
|
<P>
|
|
<A NAME="lbAZ"> </A>
|
|
<H2>D-Bus</H2>
|
|
|
|
Pidgin allows for interaction via D-Bus. Currently very little documentation
|
|
about this interaction exists.
|
|
<P>
|
|
<A NAME="lbBA"> </A>
|
|
<H2>FILES</H2>
|
|
|
|
<BR> <I>/usr/bin/pidgin</I>: Pidgin's location.
|
|
<BR>
|
|
|
|
<BR> <I>~/.purple/blist.xml</I>: the buddy list.
|
|
<BR>
|
|
|
|
<BR> <I>~/.purple/accounts.xml</I>: information about the user's accounts.
|
|
<BR>
|
|
|
|
<BR> <I>~/.purple/pounces.xml</I>: stores the user's buddy pounces.
|
|
<BR>
|
|
|
|
<BR> <I>~/.purple/prefs.xml</I>: Pidgin's configuration file.
|
|
<BR>
|
|
|
|
<BR> <I>~/.purple/status.xml</I>: stores the user's away messages.
|
|
<BR>
|
|
|
|
<BR> <I>~/.purple/logs/PROTOCOL/ACCOUNT/BUDDYNAME/DATE.{html,txt}</I>: conversation logs.
|
|
<P>
|
|
<A NAME="lbBB"> </A>
|
|
<H2>DIRECTORIES</H2>
|
|
|
|
<BR> <I>/usr/lib/pidgin/</I>: Pidgin's plugins directory.
|
|
<BR>
|
|
|
|
<BR> <I>/usr/lib/purple-2/</I>: libpurple's plugins directory.
|
|
<BR>
|
|
|
|
<BR> <I>~/.purple</I>: users' local settings
|
|
<BR>
|
|
|
|
<BR> <I>~/.purple/plugins/</I>: users' local plugins
|
|
<P>
|
|
<A NAME="lbBC"> </A>
|
|
<H2>BUGS</H2>
|
|
|
|
The bug tracker can be reached by visiting <I><A HREF="http://developer.pidgin.im/query">http://developer.pidgin.im/query</A></I>
|
|
<P>
|
|
Before sending a bug report, please verify that you have the latest
|
|
version of Pidgin. Many bugs (major and minor) are fixed
|
|
at each release, and if yours is out of date, the problem may already
|
|
have been solved.
|
|
<P>
|
|
<A NAME="lbBD"> </A>
|
|
<H2>PATCHES</H2>
|
|
|
|
If you fix a bug in Pidgin (or otherwise enhance it), please submit a
|
|
patch (using <B>mtn diff > my.diff</B> against the latest version from the
|
|
Monotone repository) at <I><A HREF="http://developer.pidgin.im/simpleticket">http://developer.pidgin.im/simpleticket</A></I>
|
|
<P>
|
|
You are also encouraged to drop by at <B>#pidgin</B> on <I>irc.freenode.net</I>
|
|
to discuss development.
|
|
<P>
|
|
<P>
|
|
<A NAME="lbBE"> </A>
|
|
<H2>SEE ALSO</H2>
|
|
|
|
<I><A HREF="http://pidgin.im/">http://pidgin.im/</A></I>
|
|
<BR>
|
|
|
|
<I><A HREF="http://developer.pidgin.im/">http://developer.pidgin.im/</A></I>
|
|
<BR>
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+purple-remote">purple-remote</A></B>(1)
|
|
<BR>
|
|
|
|
<B><A HREF="/cgi-bin/man/man2html?1+finch">finch</A></B>(1)
|
|
<P>
|
|
<A NAME="lbBF"> </A>
|
|
<H2>LICENSE</H2>
|
|
|
|
This program is free software; you can redistribute it and/or modify
|
|
it under the terms of the GNU General Public License as published by
|
|
the Free Software Foundation; either version 2 of the License, or
|
|
(at your option) any later version.
|
|
<P>
|
|
This program is distributed in the hope that it will be useful, but
|
|
<B>WITHOUT ANY WARRANTY</B>; without even the implied warranty of
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
General Public License for more details.
|
|
<P>
|
|
You should have received a copy of the GNU General Public License
|
|
along with this program; if not, write to the Free Software
|
|
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02111-1301 USA
|
|
<P>
|
|
<A NAME="lbBG"> </A>
|
|
<H2>AUTHORS</H2>
|
|
|
|
Pidgin's active developers are:
|
|
<BR>
|
|
|
|
<BR> Daniel 'datallah' Atallah (developer)
|
|
<BR>
|
|
|
|
<BR> Paul 'darkrain42' Aurich (developer)
|
|
<BR>
|
|
|
|
<BR> John 'rekkanoryo' Bailey (developer and bugmaster)
|
|
<BR>
|
|
|
|
<BR> Ethan 'Paco-Paco' Blanton (developer)
|
|
<BR>
|
|
|
|
<BR> Thomas Butter (developer)
|
|
<BR>
|
|
|
|
<BR> Ka-Hing Cheung (developer)
|
|
<BR>
|
|
|
|
<BR> Sadrul Habib Chowdhury (developer)
|
|
<BR>
|
|
|
|
<BR> Mark 'KingAnt' Doliner (developer) <<I><A HREF="mailto:thekingant@users.sourceforge.net">thekingant@users.sourceforge.net</A></I>>
|
|
<BR>
|
|
|
|
<BR> Sean Egan (developer) <<I><A HREF="mailto:seanegan@gmail.com">seanegan@gmail.com</A></I>>
|
|
<BR>
|
|
|
|
<BR> Casey Harkins (developer)
|
|
<BR>
|
|
|
|
<BR> Ivan Komarov
|
|
<BR>
|
|
|
|
<BR> Gary 'grim' Kramlich (developer)
|
|
<BR>
|
|
|
|
<BR> Richard 'rlaager' Laager (developer) <<I><A HREF="mailto:rlaager@pidgin.im">rlaager@pidgin.im</A></I>>
|
|
<BR>
|
|
|
|
<BR> Sulabh 'sulabh_m' Mahajan (developer)
|
|
<BR>
|
|
|
|
<BR> Richard 'wabz' Nelson (developer)
|
|
<BR>
|
|
|
|
<BR> Christopher 'siege' O'Brien (developer)
|
|
<BR>
|
|
|
|
<BR> Bartosz Oler (developer)
|
|
<BR>
|
|
|
|
<BR> Etan 'deryni' Reisner (developer)
|
|
<BR>
|
|
|
|
<BR> Tim 'marv' Ringenbach (developer) <<I><A HREF="mailto:marv_sf@users.sf.net">marv_sf@users.sf.net</A></I>>
|
|
<BR>
|
|
|
|
<BR> Michael 'Maiku' Ruprecht (developer, voice and video)
|
|
<BR>
|
|
|
|
<BR> Elliott 'QuLogic' Sales de Andrade (developer)
|
|
<BR>
|
|
|
|
<BR> Luke 'LSchiere' Schierer (support)
|
|
<BR>
|
|
|
|
<BR> Megan 'Cae' Schneider (support/QA)
|
|
<BR>
|
|
|
|
<BR> Evan Schoenberg (developer)
|
|
<BR>
|
|
|
|
<BR> Kevin 'SimGuy' Stange (developer and webmaster)
|
|
<BR>
|
|
|
|
<BR> Will 'resiak' Thompson (developer)
|
|
<BR>
|
|
|
|
<BR> Stu 'nosnilmot' Tomlinson (developer)
|
|
<BR>
|
|
|
|
<BR> Nathan 'faceprint' Walp (developer)
|
|
<BR>
|
|
|
|
<P>
|
|
<P>
|
|
Our crazy patch writers include:
|
|
<BR>
|
|
|
|
<BR> Marcus 'malu' Lundblad
|
|
<BR>
|
|
|
|
<BR> Dennis 'EvilDennisR' Ristuccia
|
|
<BR>
|
|
|
|
<BR> Peter 'fmoo' Ruibal
|
|
<BR>
|
|
|
|
<BR> Gabriel 'Nix' Schulhof
|
|
<BR>
|
|
|
|
<BR> Jorge 'Masca' Villaseñor
|
|
<BR>
|
|
|
|
<P>
|
|
<P>
|
|
Our artists are:
|
|
<BR>
|
|
|
|
<BR> Hylke Bons <<I><A HREF="mailto:h.bons@student.rug.nl">h.bons@student.rug.nl</A></I>>
|
|
<BR>
|
|
|
|
<P>
|
|
<P>
|
|
Our retired developers are:
|
|
<BR>
|
|
|
|
<BR> Herman Bloggs (win32 port) <<I><A HREF="mailto:herman@bluedigits.com">herman@bluedigits.com</A></I>>
|
|
<BR>
|
|
|
|
<BR> Jim Duchek <<I><A HREF="mailto:jim@linuxpimps.com">jim@linuxpimps.com</A></I>> (maintainer)
|
|
<BR>
|
|
|
|
<BR> Rob Flynn <<I><A HREF="mailto:gaim@robflynn.com">gaim@robflynn.com</A></I>> (maintainer)
|
|
<BR>
|
|
|
|
<BR> Adam Fritzler (libfaim maintainer)
|
|
<BR>
|
|
|
|
<BR> Christian 'ChipX86' Hammond (developer & webmaster) <<I><A HREF="mailto:chipx86@chipx86.com">chipx86@chipx86.com</A></I>>
|
|
<BR>
|
|
|
|
<BR> Syd Logan (hacker and designated driver [lazy bum])
|
|
<BR>
|
|
|
|
<BR> Jim Seymour (XMPP developer)
|
|
<BR>
|
|
|
|
<BR> Mark Spencer (original author) <<I><A HREF="mailto:markster@marko.net">markster@marko.net</A></I>>
|
|
<BR>
|
|
|
|
<BR> Eric Warmenhoven (former lead developer) <<I><A HREF="mailto:eric@warmenhoven.org">eric@warmenhoven.org</A></I>>
|
|
<BR>
|
|
|
|
<P>
|
|
<P>
|
|
Our retired crazy patch writers include:
|
|
<BR>
|
|
|
|
<BR> Felipe 'shx' Contreras
|
|
<BR>
|
|
|
|
<BR> Decklin Foster
|
|
<BR>
|
|
|
|
<BR> Peter 'Bleeter' Lawler
|
|
<BR>
|
|
|
|
<BR> Robert 'Robot101' McQueen
|
|
<BR>
|
|
|
|
<BR> Benjamin Miller
|
|
<BR>
|
|
|
|
<P>
|
|
<P>
|
|
This manpage was originally written by Dennis Ristuccia
|
|
<<I><A HREF="mailto:dennis@dennisr.net">dennis@dennisr.net</A></I>>. It has been updated and largely rewritten by
|
|
Sean Egan <<I><A HREF="mailto:seanegan@gmail.com">seanegan@gmail.com</A></I>>,
|
|
Ben Tegarden <<I><A HREF="mailto:tegarden@uclink.berkeley.edu">tegarden@uclink.berkeley.edu</A></I>>,
|
|
and John Bailey <<I><A HREF="mailto:rekkanoryo@pidgin.im">rekkanoryo@pidgin.im</A></I>>.
|
|
<P>
|
|
|
|
<HR>
|
|
<A NAME="index"> </A><H2>Index</H2>
|
|
<DL>
|
|
<DT id="66"><A HREF="#lbAB">NAME</A><DD>
|
|
<DT id="67"><A HREF="#lbAC">SYNOPSIS</A><DD>
|
|
<DT id="68"><A HREF="#lbAD">DESCRIPTION</A><DD>
|
|
<DT id="69"><A HREF="#lbAE">OPTIONS</A><DD>
|
|
<DT id="70"><A HREF="#lbAF">TERMS</A><DD>
|
|
<DT id="71"><A HREF="#lbAG">BUDDY LIST</A><DD>
|
|
<DT id="72"><A HREF="#lbAH">ACCOUNT EDITOR</A><DD>
|
|
<DT id="73"><A HREF="#lbAI">PREFERENCES</A><DD>
|
|
<DT id="74"><A HREF="#lbAJ">Interface</A><DD>
|
|
<DT id="75"><A HREF="#lbAK">Conversations</A><DD>
|
|
<DT id="76"><A HREF="#lbAL">Smiley Themes</A><DD>
|
|
<DT id="77"><A HREF="#lbAM">Sounds</A><DD>
|
|
<DT id="78"><A HREF="#lbAN">Network</A><DD>
|
|
<DT id="79"><A HREF="#lbAO">Browser</A><DD>
|
|
<DT id="80"><A HREF="#lbAP">Logging</A><DD>
|
|
<DT id="81"><A HREF="#lbAQ">Status / Idle</A><DD>
|
|
<DT id="82"><A HREF="#lbAR">CONVERSATIONS</A><DD>
|
|
<DT id="83"><A HREF="#lbAS">CHATS</A><DD>
|
|
<DT id="84"><A HREF="#lbAT">STATUS MESSAGES</A><DD>
|
|
<DT id="85"><A HREF="#lbAU">BUDDY POUNCE</A><DD>
|
|
<DT id="86"><A HREF="#lbAV">CUSTOM SMILIES</A><DD>
|
|
<DT id="87"><A HREF="#lbAW">PLUGINS</A><DD>
|
|
<DT id="88"><A HREF="#lbAX">PERL</A><DD>
|
|
<DT id="89"><A HREF="#lbAY">TCL</A><DD>
|
|
<DT id="90"><A HREF="#lbAZ">D-Bus</A><DD>
|
|
<DT id="91"><A HREF="#lbBA">FILES</A><DD>
|
|
<DT id="92"><A HREF="#lbBB">DIRECTORIES</A><DD>
|
|
<DT id="93"><A HREF="#lbBC">BUGS</A><DD>
|
|
<DT id="94"><A HREF="#lbBD">PATCHES</A><DD>
|
|
<DT id="95"><A HREF="#lbBE">SEE ALSO</A><DD>
|
|
<DT id="96"><A HREF="#lbBF">LICENSE</A><DD>
|
|
<DT id="97"><A HREF="#lbBG">AUTHORS</A><DD>
|
|
</DL>
|
|
<HR>
|
|
This document was created by
|
|
<A HREF="/cgi-bin/man/man2html">man2html</A>,
|
|
using the manual pages.<BR>
|
|
Time: 00:05:23 GMT, March 31, 2021
|
|
</BODY>
|
|
</HTML>
|