pidgin – Instantaneous Messaging shopper


pidgin [options]


pidgin(1)                   Normal Instructions Guide                  pidgin(1)


       pidgin - Instantaneous Messaging shopper

       pidgin [options]

       pidgin is a graphical modular messaging shopper primarily based on libpurple which
       is able to connecting to AIM, XMPP, ICQ, IRC,  SILC,  Novell  Group-
       Sensible,  Lotus  Sametime,  Zephyr,  Gadu-Gadu, and QQ . It has
       many frequent options present in different purchasers, as  effectively  as  many  distinctive
       options.  Pidgin is just not endorsed by or affiliated with America On-line,
       ICQ, or Microsoft.

       Pidgin may be prolonged by plugins written in a number of programming  lan-
       guages and managed by DBus or purple-remote.

       The  following  choices  are  offered by Pidgin utilizing the usual GNU
       command line syntax:

       -c, --config=DIR
              Use DIR because the listing for config information as a substitute of ~/.purple.

       -d, --debug
              Print debugging messages to stdout.  These are the  similar  debug-
              ging messages which can be displayed within the Debug Window.

       -f, --force-online
              Attempt to be on-line even when the community is reported (by Home windows, or
              NetworkManager on Linux) to be unavailable.

       -h, --help
              Print a abstract of command line choices and exit.

       -m, --multiple
              Permit a number of cases of Pidgin to run.

       -n, --nologin
              Do not routinely login when Pidgin begins.  Units  the  international
              standing to Offline.

       -l, --login[=NAME,NAME,...]
              Allow  the comma-separated record of accounts offered, disabling
              all different accounts.  If the consumer doesn't specify such a  comma-
              separated  record,  the  first  account  in  accounts.xml  might be

       -v, --version
              Print the present model and exit.

       Pidgin makes use of a number of phrases otherwise from different purposes.  For  con-
       venience they're outlined right here:

       Buddy Checklist
              The  record of different customers who the consumer needs to see standing infor-
              mation for and have fast entry to for messaging.

       Buddy  A consumer who has been added to the Buddy Checklist.

              A grouping of a couple of buddy who're all of the  similar  particular person.
              A  contact could include buddies from any protocol and will include
              as many buddies because the consumer wishes.  Contact  preparations  are
              saved domestically solely.

       Alias  A  personal  "nickname"  that  could also be set for Buddies or the consumer
              himself.  On some protocols, aliases are saved on the server however
              not  seen  to  different  customers.  On different protocols, aliases are
              saved solely domestically.

              A messaging service.  AIM, XMPP,  Zephyr,  and many others.  are  protocols.
              Others  could  name  these "service types," "account types," "ser-
              vices," and so forth.

       The Buddy Checklist window is Pidgin's important interface  window.   Utilizing  this
       window  a  consumer can see which of his/her buddies is on-line, away, idle,
       and many others.  The consumer can even add buddies to  and  take away  buddies  from  the
       buddy record.

       The  Buddy  Checklist  window  incorporates a listing of the consumer's buddies who're
       on-line and have allowed the consumer to be notified of their presence.  The
       icon  to  the  left of every buddy signifies the buddy's present standing.
       Double clicking a buddy will open a  new  Dialog  window.   Proper
       clicking will pop up a menu:

       Get Information
              Retrieves and shows details about the buddy.  This infor-
              mation is also referred to as a Profile.

       IM     Opens a brand new Dialog window to the chosen buddy.

       Ship File
              Sends a file to the chosen buddy (solely accessible on  protocols
              that help file switch).

       Add Buddy Pounce
              A  Buddy  Pounce  is  a configurable automated motion to be per-
              shaped when the buddy's state modifications.  It will open the Buddy
              Pounce dialog, which might be mentioned later.

       View Log
              Pidgin is able to routinely logging messages.  These logs
              are both plain textual content information (with  a  .txt  extension)  or  html
              information  (with a .html extension) situated below the ~/.purple/logs
              listing.  This menu command will show Pidgin's  log  viewer
              with logs loaded for that buddy or chat.

       Alias  Create an alias for this buddy.  It will present an editable textual content
              discipline the place the buddy's title was displayed.  On this  discipline  one
              can  give  this buddy an alternate, extra pleasant title to seem
              on the buddy record and in conversations.

              For instance, if a buddy's title was  jsmith1281xx  and  his  actual
              title  was 'John Q. Smith,' one might create an alias as to iden-
              tify the buddy by his frequent title.

       The rest of the menu will include protocol  particular  instructions.
       These instructions range relying on the protocol.

       Standing Selector
              At  the  backside  of  the  Buddy  Checklist is a standing selector which
              permits one to vary his/her standing.   This  will  be  mentioned
              additional within the STATUS MESSAGES part under.

       The account editor consists of a listing of accounts and details about
       them.  It may be accessed by choosing Handle from the  Accounts  menu.
       Clicking  Delete  will delete the presently chosen account.  Clicking
       Add or Modify will invoke a Modify Account window.  Right here, the consumer  can
       add  or  alter  account  data.  When creating a brand new account, the
       consumer will submit a username and password.  The consumer  will  additionally  select
       the protocol for the account.

       If  Bear in mind Password is chosen, the password might be saved in Pidgin's
       ~/.purple/accounts.xml configuration file.

       If Enabled is checked within the accounts dialog, this account will  observe
       the  standing  presently  chosen  within the standing selector.  If it's not
       checked, the account will all the time be offline.

       Every protocol has its personal particular choices that may  be  discovered  in  the
       modify display.

       All choices take impact instantly.

       Present system tray icon
              Specifies when to point out a Pidgin icon within the notification space of
              the consumer's panel (generally known as the System Tray).

       Disguise new IM conversations
              Specifies when to cover new IM  messages.   Messages  will  queue
              below  the required situation till proven.  Clicking the Pidgin
              icon within the notification space or system tray  will  show  the
              queued  messages.  An icon additionally seems within the buddy record's menu
              bar; this icon may additionally be used to show queued messages.

       Present IMs and chats in tabbed home windows
              When checked, this feature will trigger IM  and  chat  classes  to
              seem  in  home windows  with a number of tabs.  One tab will signify
              one dialog or chat.  The place tabs are positioned  will  be  dic-
              tated by the preferences under.

       Present shut buttons on tabs
              When  checked, this feature will trigger a clickable "U+2715 MULTI-
              PLICATION X" unicode character to seem on the  proper  edge  of
              every tab.  Clicking it will trigger the tab to be closed.

              Specifies  the place to put tabs within the window.  Some tab orienta-
              tions could enable some customers to suit extra tabs right into a single window

       New conversations
              Specifies  below  which situations tabs are positioned into current
              home windows or into new home windows.  For a single window,  choose  Final
              created window right here.

       Allow buddy icon animation
              If  a  buddy's  icon  occurs  to  be animated, this feature will
              allow the animation, in any other case solely the  first  body  will  be

       Notify buddies that you're typing to them
              Some protocols enable purchasers to inform their buddies when they're
              typing.  This selection allows this  function  for  protocols  that
              helps it.

       Default Formatting
              Permits  specifying the default formatting to use to all outgo-
              ing messages (solely relevant to protocols that help  format-
              ting in messages).

Smiley Themes
       Permits  the  consumer to decide on between completely different smiley themes. The "none"
       theme will disable graphical emoticons - they are going to be displayed as textual content
       as a substitute.   The  Add  and Take away buttons could also be used to put in or unin-
       stall smiley themes.  Themes may additionally  be  put in  by  dragging  and
       dropping them onto the record of themes.

       Methodology Lets  the  consumer  select  between completely different playback strategies. The
              consumer can even manually enter a command to  be  executed  when  a
              sound  is  to  be performed(%s expands to the complete path to the file

       Sounds when dialog has focus
              When checked, sounds will play for occasions within the lively  conver-
              sation  if  the  window is concentrated.  When unchecked, sounds will
              not play for the lively dialog when the window is concentrated.

       Allow Sounds
              Determines when to play sounds.

       Sound Occasions
              Lets the consumer select when and what sounds are to be performed.

       STUN server
              This permits specifying a server which makes use of the STUN protocol  to
              decide  a bunch's public IP tackle.  This may be significantly
              helpful for some protocols.

       Autodetect IP tackle
              When checked, causes Pidign to aim to find out  the  public
              IP  tackle  of the host on which Pidgin is operating and disables
              the Public IP textual content discipline listed under.

       Public IP
              If Autodetect IP tackle is disabled, this discipline permits manually
              specifying the general public IP tackle for the host on which Pidgin is
              operating.  That is primarily helpful for customers with a number of  community
              interfaces or behind NATs.

       Manually specify vary of ports to hear on
              Specify  a  vary  ports  to hear on, overriding any defaults.
              That is generally helpful for file transfers and Direct IM.

       Proxy Server
              The configuration part to allow Pidgin to function by  a
              proxy  server.   Pidgin  presently  helps  SOCKS 4/5 and HTTP

              Permits the consumer to pick Pidgin's default internet  browser.   Fireplace-
              fox,  Galeon,  Konqueror,  Mozilla,  Netscape and Opera are sup-
              ported natively.  The consumer can even manually enter a command  to
              be executed when a hyperlink is clicked (%s expands to the URL).  For
              instance, xterm -e lynx "%s" will open the hyperlink with lynx.

       Open hyperlink in
              Permits the consumer to specify whether or not to make use of an current window,  a
              new  tab,  a brand new window, or to let the browser to resolve what to
              do when calling the browser to open a hyperlink.  Which  choices  are
              accessible will depend upon which browser is chosen.

       Log format
              Specifies  the best way to log.  Pidgin helps HTML and plain textual content, however
              plugins can present different logging strategies.

       Log all immediate messages
              When enabled, all IM conversations  are  logged.   This  can  be
              overridden  on a per-conversation foundation within the dialog win-

       Log all chats
              When enabled, all chat conversations are logged.   This  can  be
              overridden  on a per-conversation foundation within the dialog win-

       Log all standing modifications to system log
              When enabled, standing modifications are logged.

Standing / Idle
       Report idle time
              Determines below which situations to report idle time.  Based mostly on
              keyboard  and  mouse  use  makes use of  keyboard  and mouse exercise to
              decide idle time.  From final despatched message makes use of  the  time  at
              which  the consumer final despatched a message in Pidgin to find out idle.
              By no means disables idle reporting.

              Determines when to ship an auto-reply on protocols which help
              it (presently solely AIM).

       Change standing when idle
              When  enabled,  this  makes use of  the Minutes earlier than changing into idle and
              Change standing to preferences described under to  set  standing  on

       Minutes earlier than changing into idle
              Specifies  how  many  minutes  of inactivity are required earlier than
              contemplating the consumer to be idle.

       Change standing to
              Specifies which "primitive" or "saved" standing to make use of  when  set-
              ting standing on idle.

       Use standing from final exit at startup
              If  that is checked, Pidgin will keep in mind what standing was lively
              when the consumer closed Pidgin and restore  it  at  the  subsequent  run.
              When  disabled,  Pidgin  will  all the time set the standing chosen in
              Standing to use at startup at startup.

       Standing to use at startup
              When Use standing from final exit  at  startup  is  disabled,  this
              specifies which "primitive" or "saved" standing to make use of at startup.

       When  beginning  a brand new dialog, the consumer is introduced with the Con-
       versation window.  The dialog seems within the higher textual content  field  and
       the  consumer varieties his/her message within the decrease textual content field.  Between the 2
       is a row of choices, represented by icons.  Some or all buttons could not
       be  lively  if  the  protocol doesn't help the particular formatting.
       From left to proper:

       Font   This menu gives font management choices for the present  conver-
              sation.  Dimension, model, and face could also be configured right here.

       Insert This  menu  gives  the  skill  to insert pictures, horizontal
              guidelines, and hyperlinks the place the protocol helps every of those  fea-

       Smile! Permits  the  insertion of graphical smileys through the mouse.  This
              button reveals the consumer a dialog with the  accessible  smileys  for
              the present dialog.

       For  protocols  that enable it, Chats may be entered by the Buddies

       Further options accessible in chat, relying on the protocol are:

              The textual content will seem within the chat dialog, however it's going to  solely
              be seen to the sender and the receiver.

       Invite Invite different folks to hitch the chat room.

       Ignore Ignore something mentioned by the chosen particular person

       Set Subject
              Set  the  subject  of the chat room.  That is normally a quick sen-
              tence describing the character of the chat--an clarification  of  the
              chat room's title.

       Personal Message (IM)
              Ship  a message to a selected particular person within the chat.  Messages despatched
              this fashion is not going to seem within the chat window, however as a substitute open  a
              new IM dialog.

       Most  protocols enable for standing messages.  By utilizing standing messages, a
       consumer can go away an informative message for others to  see.   Standing  and
       standing messages are configured through the standing selector on the backside of
       the Buddy Checklist window.  By default the menu proven right here is split  into
       sections for "primitive" standing varieties, resembling Out there, Away, and many others.; a
       few "popular" statuses (together with  "transient"  statuses)   which  have
       been  lately  used, and a piece which reveals New Standing... and Saved
       Statuses... choices for extra superior standing manipulation.

       Primitive Statuses
              A primitive standing is a primary standing supported by the  protocol.
              Examples of primitive statuses could be Out there, Away, Invisi-
              ble, and many others.  A primitive standing can be utilized to create a  Transient
              Standing  or  a  Saved Standing, each defined under.  Primarily,
              primitive statuses are constructing blocks of extra sophisticated  sta-

       Transient Statuses
              When  one of many statuses from the topmost part of the standing
              selector's menu is chosen, this creates a transient, or tempo-
              rary,  standing.   The  standing will present within the "popular statuses"
              part within the menu till it has not  been  used  for  a  suffi-
              ciently  lengthy  time.   A transient standing may additionally be created by
              choosing New Standing... from the standing  selector's  menu,  then
              clicking Use as soon as the consumer has entered the message.

       Saved Statuses
              Saved  statuses  are  permanent--once  created,  they'll exist
              till deleted.  Saved statuses are helpful for statuses and  sta-
              tus  messages  that  will  be used frequently.  They're
              additionally helpful for creating complicated statuses during which some accounts
              ought to all the time have a special standing from others.  For instance,
              one would possibly want to create a standing referred to as "Sleeping" that has all
              accounts set to "Away", then create one other standing referred to as "Work-
              ing" that has three accounts set to "Away" and  one other  account
              set to "Available."

       New Standing Window
              When  the  consumer  selects  New Standing... from the standing selector
              menu, Pidgin presents the consumer with a dialog asking for  status-
              associated data.  That data is mentioned under:

              Title  -  The  title of the standing that may seem within the standing
              selctor's menu.  If the consumer clicks the Save or Save & Use  but-
              ton,  this  title  may also be proven within the Saved Standing Window.
              The title ought to be a brief description of the standing.

              Standing - The kind of standing being created,  such  as  Out there,
              Away, and many others.

              Message  -  The  content material of the standing message.  That is what's
              seen to different customers.  Some protocols will enable formatting in
              some  standing messages; the place formatting is just not supported it's going to
              be stripped to the naked textual content entered.

              Use a special standing for some accounts - This permits the  cre-
              ation of complicated statuses during which some accounts' standing differs
              from that of different accounts.  To make use of this, the consumer  will  click on
              the  expander  to  the  left of the textual content, then choose particular person
              accounts which may have a special standing and/or  standing  mes-
              sage.   When  the  consumer  selects an account, Pidgin will current
              one other standing dialog asking for a standing and a message only for
              the chosen account.

       Saved Standing Window
              When  the  consumer selects Saved Statuses... from the standing selec-
              tor's menu, Pidgin presents a dialog that lists all  saved  sta-
              tuses.   "Transient"  statuses,  mentioned  above, are NOT proven
              right here.  This window gives the flexibility to handle saved statuses
              by  permitting  the  creation, modification, and deletion of saved
              statuses.  The Use, Modify, and Delete buttons right here enable opera-
              tion  on the standing chosen from the record; the dd button permits
              creation of a brand new saved standing, and the Shut button closes  the

       A Buddy Pounce is an automatic set off that happens when a buddy returns
       to a standard state from an away state.  The Buddy Pounce dialog field  can
       be  activated by choosing the Buddy Pounce choice from the Instruments menu.
       From this dialog, new pounces may be created with the  Add  button  and
       current  pounces  may be eliminated with the Delete button.  A pounce can
       be set to happen on any mixture of the occasions listed, and any combi-
       nation  of  actions  can  outcome.  If Pounce solely when my standing is just not
       Out there is checked, the pounce will happen provided that the consumer is ready  to
       a  non-available  standing, resembling invisible, don't disturb, away, and many others.
       If Recurring is checked, the pounce will stay till  eliminated  by  the
       Delete button.

       Pidgin  2.5.0  launched help for customized smilies on these protocols
       for which  contributors have developed help.   The  customized
       smiley supervisor may be accessed by choosing Smiley from the Instruments menu.
       From right here, customized smilies could also be added, edited, or deleted by  clicking
       the Add, Edit, or Delete buttons, respectively.

       Throughout a dialog with one other consumer, that consumer's customized smileys could
       be added to the consumer's personal customized smiley record straight from the conver-
       sation window by right-clicking the brand new customized smiley and choosing Add
       Customized Smiley...

       Pidgin permits for dynamic loading of plugins so as to add further performance
       to Pidgin.  See plugins/HOWTO or
       for data on writing plugins.

       The plugins dialog may be accessed by choosing Plugins from the  Instruments
       menu.  Every plugin accessible seems on this dialog with its title, ver-
       sion, and a brief abstract of its performance. Plugins may be  enabled
       with the checkbox beside the title and quick description.  Extra informa-
       tion on the presently chosen plugin  is  accessible  by  clicking  the
       expander  beside  the  textual content Plugin Particulars.  If the chosen plugin has
       preferences or configuration choices, the Configure Plugin button  will
       current the plugin's preferences dialog.

       Pidgin permits for plugins to be written within the perl scripting language.
       See Perl Scripting HOWTO within the Pidgin documentation for extra  informa-
       tion about perl scripting.

       Pidgin  permits for plugins to be written within the Tcl scripting language.
       See plugins/tcl/TCL-HOWTO for extra details about Tcl scripting.

       Pidgin permits for interplay through D-Bus.  At the moment very  little  docu-
       mentation about this interplay exists.

         /usr/bin/pidgin: Pidgin's location.
         ~/.purple/blist.xml: the buddy record.
         ~/.purple/accounts.xml: details about the consumer's accounts.
         ~/.purple/pounces.xml: shops the consumer's buddy pounces.
         ~/.purple/prefs.xml: Pidgin's configuration file.
         ~/.purple/standing.xml: shops the consumer's away messages.
         ~/.purple/logs/PROTOCOL/ACCOUNT/BUDDYNAME/DATE.{html,txt}:  conversa-
       tion logs.

         /usr/lib/pidgin/: Pidgin's plugins listing.
         /usr/lib/purple-2/: libpurple's plugins listing.
         ~/.purple: customers' native settings
         ~/.purple/plugins/: customers' native plugins

       The bug  tracker  can  be  reached  by  visiting

       Earlier than  sending  a  bug  report, please confirm that you've got the newest
       model of Pidgin.  Many bugs (main  and  minor)  are  fastened  at  every
       launch, and if yours is outdated, the issue could have already got been

       In the event you repair a bug in Pidgin (or in any other case improve it), please  submit  a
       patch  (utilizing  mtn  diff  > my.diff in opposition to the newest model from the
       Monotone repository) at

       You might be additionally inspired to drop by at #pidgin  on  irc.freenode.internet  to
       talk about improvement.

       See attributes(7) for descriptions of the next attributes:

       |Availability   | communication/im/pidgin |
       |Stability      | Uncommitted             |

       This program is free software program; you possibly can redistribute it and/or modify it
       below the phrases of the GNU Normal Public License as revealed  by  the
       Free  Software program Basis; both model 2 of the License, or (at your
       choice) any later model.

       This program is distributed within the hope that it  will  be  helpful,  however
       WITHOUT  ANY  WARRANTY;  with out  even  the  implied  guarantee  of MER-
       Public License for extra particulars.

       It is best to have obtained a duplicate of the GNU Normal Public License alongside
       with this program; if not, write to the Free Software program Basis, Inc.,
       51 Franklin Road, Fifth Ground, Boston, MA  02111-1301  USA

       Pidgin's lively builders are:
         Daniel 'datallah' Atallah (developer)
         Paul 'darkrain42' Aurich (developer)
         John 'rekkanoryo' Bailey (developer and bugmaster)
         Ethan 'Paco-Paco' Blanton (developer)
         Thomas Butter (developer)
         Ka-Hing Cheung (developer)
         Sadrul Habib Chowdhury (developer)
         Mark 'KingAnt' Doliner (developer) <thekingant@customers.sourceforge.internet>
         Sean Egan (developer) <>
         Casey Harkins (developer)
         Ivan Komarov
         Gary 'grim' Kramlich (developer)
         Richard 'rlaager' Laager (developer) <>
         Sulabh 'sulabh_m' Mahajan (developer)
         Richard 'wabz' Nelson (developer)
         Christopher 'siege' O'Brien (developer)
         Bartosz Oler (developer)
         Etan 'deryni' Reisner (developer)
         Tim 'marv' Ringenbach (developer) <marv_sf@customers.sf.internet>
         Michael 'Maiku' Ruprecht (developer, voice and video)
         Elliott 'QuLogic' Gross sales de Andrade (developer)
         Luke 'LSchiere' Schierer (help)
         Megan 'Cae' Schneider (help/QA)
         Evan Schoenberg (developer)
         Kevin 'SimGuy' Stange (developer and webmaster)
         Will 'resiak' Thompson (developer)
         Stu 'nosnilmot' Tomlinson (developer)
         Nathan 'faceprint' Walp (developer)

       Our loopy patch writers embrace:
         Marcus 'malu' Lundblad
         Dennis 'EvilDennisR' Ristuccia
         Peter 'fmoo' Ruibal
         Gabriel 'Nix' Schulhof
         Jorge 'Masca' Villaseor

       Our artists are:
         Hylke Bons <>

       Our retired builders are:
         Herman Bloggs (win32 port) <>
         Jim Duchek <> (maintainer)
         Rob Flynn <> (maintainer)
         Adam Fritzler (libfaim maintainer)
         Christian     'ChipX86'     Hammond     (developer    &    webmaster)
         Syd Logan (hacker and designated driver [lazy bum])
         Jim Seymour (XMPP developer)
         Mark Spencer (authentic creator) <markster@marko.internet>
         Eric Warmenhoven (former lead developer) <>

       Our retired loopy patch writers embrace:
         Felipe 'shx' Contreras
         Decklin Foster
         Peter 'Bleeter' Lawler
         Robert 'Robot101' McQueen
         Benjamin Miller

       This manpage was initially written by  Dennis  Ristuccia  <dennis@den-
       nisr.internet>.   It  has  been  up to date  and largely rewritten by Sean Egan
       <>, Ben Tegarden <>,  and
       John Bailey <>.

       This     software program     was    constructed    from    supply    accessible    at   The  authentic   group
       supply   was  downloaded  from

       Additional details about this software program may be discovered on the open supply
       group web site at

Pidgin v2.12.0                                                       pidgin(1)
See also  Shovel Knight Download Free (2020)

Leave a Reply

Your email address will not be published.