| 339 |
339 |
| 340 Some plugins can be configured. If you load such a plugin, its |
340 Some plugins can be configured. If you load such a plugin, its |
| 341 configuration preferences will appear as a submenu to \fBPlugins\fR, with |
341 configuration preferences will appear as a submenu to \fBPlugins\fR, with |
| 342 the submenu title determined by the plugin's name. |
342 the submenu title determined by the plugin's name. |
| 343 |
343 |
| 344 .SH Protocols |
|
| 345 |
|
| 346 Protocols provide protocol specific preferences here. |
|
| 347 |
|
| 348 .SH CONVERSATIONS |
344 .SH CONVERSATIONS |
| 349 When starting a new conversation, the user is presented with the |
345 When starting a new conversation, the user is presented with the |
| 350 \fBConversation\fR window. The conversation appears in the upper text box |
346 \fBConversation\fR window. The conversation appears in the upper text box |
| 351 and the user types his/her message in the lower text box. Between the two |
347 and the user types his/her message in the lower text box. Between the two |
| 352 is a row of settings, represented by icons. Some or all buttons may not be |
348 is a row of options, represented by icons. Some or all buttons may not be |
| 353 active if the protocol does not support the specific formatting. From left |
349 active if the protocol does not support the specific formatting. From left |
| 354 to right: |
350 to right: |
| 355 .TP |
351 .TP |
| 356 .B Bold |
352 .B Font |
| 357 Turns on/off bold. |
353 This menu provides font control options for the current conversation. Size, |
| 358 .TP |
354 style, and face may be configured here. |
| 359 .B Italics |
355 .TP |
| 360 Turns on/off italics. |
356 .B Insert |
| 361 .TP |
357 This menu provides the ability to insert images, horizontal rules, and links |
| 362 .B Underline |
358 where the protocol supports each of these features. |
| 363 Turns on/off underline. |
359 .TP |
| 364 .TP |
360 .B Smile! |
| 365 .B Decrease font size |
361 Allows the insertion of graphical smileys via the mouse. This button shows |
| 366 Increases the size of the message text. |
362 the user a dialog with the available smileys for the current conversation. |
| 367 .TP |
363 |
| 368 .B Increase font size |
364 .SH CHATS |
| 369 Decreases the size of the message text. |
365 For protocols that allow it, \fBChats\fR can be entered through the |
| 370 .TP |
366 \fIBuddies\fR menu. |
| 371 .B Select a foreground color |
367 |
| 372 Changes the foreground color of the message text. |
|
| 373 .TP |
|
| 374 .B Select a background color |
|
| 375 Changes the background color of the message text. |
|
| 376 .TP |
|
| 377 .B Add image |
|
| 378 Inserts an in-line image in the message. |
|
| 379 .TP |
|
| 380 .B Add hyperlink |
|
| 381 Adds a clickable link to the message. |
|
| 382 .TP |
|
| 383 .B Add smiley |
|
| 384 Adds an emoticon (smiley) to your message. |
|
| 385 |
|
| 386 Beneath the lower text box is a row of buttons that execute commands: |
|
| 387 .TP |
|
| 388 .B Warn |
|
| 389 This issues a warning to the other person in the conversation (not |
|
| 390 available in all protocols). |
|
| 391 .TP |
|
| 392 .B Block |
|
| 393 This adds the other person to your deny list (not available in all |
|
| 394 protocols). |
|
| 395 .TP |
|
| 396 .B Send File |
|
| 397 Send a file to this user. This option is only available on protocols where |
|
| 398 Pidgin supports file transfer. |
|
| 399 .TP |
|
| 400 .B Add |
|
| 401 This adds this user to your buddy list. This option is not available if |
|
| 402 the user is already on your list. |
|
| 403 .TP |
|
| 404 .B Remove |
|
| 405 This removes this user from your buddy list. This option is not available |
|
| 406 if the user is not on your list. |
|
| 407 .TP |
|
| 408 .B Info |
|
| 409 This gets information (a profile) about the other person in the |
|
| 410 conversation (not available in all protocols). |
|
| 411 .TP |
|
| 412 .B Send |
|
| 413 This sends what's currently in the lower text box |
|
| 414 |
|
| 415 .SH BUDDY CHATS |
|
| 416 For protocols that allow it, \fBBuddy Chats\fR can be entered through the |
|
| 417 \fIFile\fR menu or the \fIChat\fR button at the bottom of the \fBBuddy |
|
| 418 List\fR's \fBOnline\fR tab. |
|
| 419 |
368 |
| 420 Additional commands available in chat, depending on the protocol are: |
369 Additional commands available in chat, depending on the protocol are: |
| 421 .TP |
370 .TP |
| 422 .B Whisper |
371 .B Whisper |
| 423 The text will appear in the chat conversation, but it will only be visible |
372 The text will appear in the chat conversation, but it will only be visible |
| 431 .TP |
380 .TP |
| 432 .B Set Topic |
381 .B Set Topic |
| 433 Set the topic of the chat room. This is usually a brief sentence |
382 Set the topic of the chat room. This is usually a brief sentence |
| 434 describing the nature of the chat--an explanation of the chat room's name. |
383 describing the nature of the chat--an explanation of the chat room's name. |
| 435 |
384 |
| 436 .SH AWAY MESSAGES |
385 .SH STATUS MESSAGES |
| 437 Most protocols allow for away messages. When a user is \fIAway\fR, he can |
386 Most protocols allow for status messages. By using status messages, a user |
| 438 leave an informative message for others to see. The \fBAway\fR submenu of |
387 can leave an informative message for others to see. Status and status |
| 439 the \fBTools\fR menu is used to add and remove away messages. |
388 messages are configured via the status selector at the bottom of the Buddy |
| 440 |
389 List window. By default the menu shown here is divided into sections for |
| 441 \fINew Away Message\fR provides space for one to enter an away message and |
390 "primitive" status types, such as \fIAvailable\fR, \fIAway\fR, etc.; a few |
| 442 a title for that message. If \fISave\fR or \fISave & Use\fR are chosen, |
391 "popular" statuses which have been recently used, and a section which shows |
| 443 this message will be saved. It can later be referred to by the title given |
392 \fBNew...\fR and \fBSaved...\fR options for more advanced status manipulation. |
| 444 to it. |
|
| 445 |
|
| 446 \fIRemove Away Message\fR is a submenu containing the titles of saved away |
|
| 447 messages. Clicking on one of these titles will remove the away message |
|
| 448 associated with it. |
|
| 449 |
|
| 450 The rest of the \fIaway\fR menu provides the user with a way to assign |
|
| 451 different away messages to different connections. Choosing \fISet All |
|
| 452 Away\fR will set away all the connections capable of the away state. |
|
| 453 |
393 |
| 454 .SH BUDDY POUNCE |
394 .SH BUDDY POUNCE |
| 455 A Buddy Pounce is an automated trigger that occurs when a buddy returns to |
395 A Buddy Pounce is an automated trigger that occurs when a buddy returns to |
| 456 a normal state from an away state. The \fBNew Buddy Pounce\fR dialog box |
396 a normal state from an away state. The \fBBuddy Pounce\fR dialog box |
| 457 can be activated by selecting the \fIBuddy Pounce\fR submenu from the |
397 can be activated by selecting the \fIBuddy Pounce\fR option from the |
| 458 \fBTools\fR menu. A pounce can be set to occur on any combination of the |
398 \fBTools\fR menu. From this dialog, new pounces can be created with the |
| 459 events listed, and any combination of actions can result. If \fISave this |
399 \fBAdd\fR button and existing pounces can be removed with the \fBDelete\fR |
| 460 pounce after activation\fR is checked, the trigger will remain until it is |
400 button. A pounce can be set to occur on any combination of the |
| 461 removed from the \fIRemove Buddy Pounce\fR menu. |
401 events listed, and any combination of actions can result. If \fIPounce |
| |
402 only when my status is not Available\fR is checked, the pounce will occur |
| |
403 only if you are set to a non-available status, such as invisible, do not |
| |
404 disturb, away, etc. If \fIRecurring\fR is checked, the pounce will remain |
| |
405 until removed by the \fBDelete\fR button. |
| 462 |
406 |
| 463 .SH PLUGINS |
407 .SH PLUGINS |
| 464 Pidgin allows for dynamic loading of plugins to add extra functionality |
408 Pidgin allows for dynamic loading of plugins to add extra functionality |
| 465 to Pidgin. Plugins can be enabled and configured from the |
409 to Pidgin. Plugins can be enabled and configured from the |
| 466 \fBPreferences\fR window. See \fIplugins/HOWTO\fR for more information on |
410 \fBPreferences\fR window. See \fIplugins/HOWTO\fR or |
| |
411 \fIhttp://developer.pidgin.im/wiki/CHowTo\fR for more information on |
| 467 writing plugins. |
412 writing plugins. |
| 468 |
413 |
| 469 .SH PERL |
414 .SH PERL |
| 470 Pidgin allows for perl scripting. See \fIPerl Scripting HOWTO\fR in |
415 Pidgin allows for perl scripting. See \fIPerl Scripting HOWTO\fR in |
| 471 the Pidgin documentation for more information about perl scripting. |
416 the Pidgin documentation for more information about perl scripting. |
| 489 .br |
434 .br |
| 490 \fI~/.purple/logs/PROTOCOL/ACCOUNT/SCREENNAME/DATE.{html,txt}\fR: conversation logs. |
435 \fI~/.purple/logs/PROTOCOL/ACCOUNT/SCREENNAME/DATE.{html,txt}\fR: conversation logs. |
| 491 .br |
436 .br |
| 492 \fI~/.purple/blist.xml\fR: the buddy list. |
437 \fI~/.purple/blist.xml\fR: the buddy list. |
| 493 .br |
438 .br |
| 494 \fI~/.purple/plugins/\fR: users local plugins |
439 \fI~/.purple/plugins/\fR: users' local plugins |
| 495 |
440 |
| 496 .SH BUGS |
441 .SH BUGS |
| 497 The bug tracker can be reached by visiting: |
442 The bug tracker can be reached by visiting \fIhttp://developer.pidgin.im/query\fR |
| 498 .br |
|
| 499 \fIhttp://developer.pidgin.im/report\fR |
|
| 500 |
443 |
| 501 .SH PATCHES |
444 .SH PATCHES |
| 502 If you fix a bug in Pidgin (or otherwise enhance it), please submit a |
445 If you fix a bug in Pidgin (or otherwise enhance it), please submit a |
| 503 patch (using \fImtn diff > my.diff\fR against the latest version from the |
446 patch (using \fImtn diff > my.diff\fR against the latest version from the |
| 504 Monotone repository) at |
447 Monotone repository) at \fIhttp://developer.pidgin.im/simpleticket\fR |
| 505 .br |
|
| 506 \fIhttp://developer.pidgin.im/newticket\fR |
|
| 507 |
448 |
| 508 Before sending a bug report, please verify that you have the latest |
449 Before sending a bug report, please verify that you have the latest |
| 509 version of Pidgin. Many bugs (major and minor) are fixed |
450 version of Pidgin. Many bugs (major and minor) are fixed |
| 510 at each release, and if yours is out of date, the problem may already |
451 at each release, and if yours is out of date, the problem may already |
| 511 have been solved. |
452 have been solved. |
| 528 along with this program; if not, write to the Free Software |
469 along with this program; if not, write to the Free Software |
| 529 Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02111-1301 USA |
470 Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02111-1301 USA |
| 530 |
471 |
| 531 .SH AUTHORS |
472 .SH AUTHORS |
| 532 Pidgin's active developers are: |
473 Pidgin's active developers are: |
| 533 |
474 .br |
| 534 Sean Egan (lead developer) <\fIseanegan@gmail.com\fR> |
475 Sean Egan (lead developer) <\fIseanegan@gmail.com\fR> |
| 535 .br |
476 .br |
| 536 Daniel 'datallah' Atallah (developer) |
477 Daniel 'datallah' Atallah (developer) |
| 537 .br |
478 .br |
| 538 Ethan 'Paco-Paco' Blanton (developer) |
479 John 'rekkanoryo' Bailey (developer) |
| 539 .br |
480 .br |
| 540 Thomas Butter (developer) |
481 Ethan 'Paco-Paco' Blanton (developer) |
| 541 .br |
482 .br |
| 542 Ka-Hing Cheung (developer) |
483 Thomas Butter (developer) |
| 543 .br |
484 .br |
| 544 Sadrul Habib Chowdhury (developer) |
485 Ka-Hing Cheung (developer) |
| 545 .br |
486 .br |
| 546 Mark 'KingAnt' Doliner (developer) <\fIthekingant@users.sourceforge.net\fR> |
487 Sadrul Habib Chowdhury (developer) |
| 547 .br |
488 .br |
| 548 Christian 'ChipX86' Hammond (developer & webmaster) <\fIchipx86@chipx86.com\fR> |
489 Mark 'KingAnt' Doliner (developer) <\fIthekingant@users.sourceforge.net\fR> |
| 549 .br |
490 .br |
| 550 Gary 'grim' Kramlich (developer) |
491 Casey Harkins (developer) |
| 551 .br |
492 .br |
| 552 Richard 'rlaager' Laager (developer) <\fIrlaager@pidgin.im\fR> |
493 Gary 'grim' Kramlich (developer) |
| 553 .br |
494 .br |
| 554 Richard 'wabz' Nelson (developer) |
495 Richard 'rlaager' Laager (developer) <\fIrlaager@pidgin.im\fR> |
| 555 .br |
496 .br |
| 556 Christopher 'siege' O'Brien (developer) |
497 Richard 'wabz' Nelson (developer) |
| 557 .br |
498 .br |
| 558 Bartosz Oler (developer) |
499 Christopher 'siege' O'Brien (developer) |
| 559 .br |
500 .br |
| 560 Etan 'deryni' Reisner (developer) |
501 Bartosz Oler (developer) |
| 561 .br |
502 .br |
| 562 Tim 'marv' Ringenbach (developer) <\fImarv_sf@users.sf.net\fR> |
503 Etan 'deryni' Reisner (developer) |
| 563 .br |
504 .br |
| 564 Luke 'LSchiere' Schierer (support) |
505 Tim 'marv' Ringenbach (developer) <\fImarv_sf@users.sf.net\fR> |
| 565 .br |
506 .br |
| 566 Megan 'Cae' Schneider (support/QA) |
507 Luke 'LSchiere' Schierer (support) |
| 567 .br |
508 .br |
| 568 Evan Schoenberg (developer) |
509 Megan 'Cae' Schneider (support/QA) |
| 569 .br |
510 .br |
| 570 Stu 'nosnilmot' Tomlinson (developer) |
511 Evan Schoenberg (developer) |
| 571 .br |
512 .br |
| 572 Nathan 'faceprint' Walp (developer) |
513 Kevin 'SimGuy' Stange (developer and webmaster) |
| |
514 .br |
| |
515 Stu 'nosnilmot' Tomlinson (developer) |
| |
516 .br |
| |
517 Nathan 'faceprint' Walp (developer) |
| 573 .br |
518 .br |
| 574 |
519 |
| 575 |
520 |
| 576 Our crazy patch writers include: |
521 Our crazy patch writers include: |
| 577 |
522 .br |
| 578 John 'rekkanoryo' Bailey |
523 Dennis 'EvilDennisR' Ristuccia |
| 579 .br |
524 .br |
| 580 Felipe 'shx' Contreras |
525 Peter 'fmoo' Ruibal |
| 581 .br |
526 .br |
| 582 Decklin Foster |
527 Gabriel 'Nix' Schulhof |
| 583 .br |
528 .br |
| 584 Casey Harkins |
529 Will 'resiak' Thompson |
| 585 .br |
530 .br |
| 586 Peter 'Bleeter' Lawler |
531 |
| 587 .br |
532 |
| 588 Robert 'Robot101' McQueen |
533 Our artists are: |
| 589 .br |
534 .br |
| 590 Benjamin Miller |
535 Hylke Bons <\fIh.bons@student.rug.nl\fR> |
| 591 .br |
536 .br |
| 592 Kevin 'SimGuy' Stange |
537 |
| 593 .br |
538 |
| 594 |
539 Our retired developers are: |
| 595 |
540 .br |
| 596 The retired developers of \fBgaim\fR are: |
541 Herman Bloggs (win32 port) <\fIherman@bluedigits.com\fR> |
| 597 |
542 .br |
| 598 Herman Bloggs (win32 port) <\fIherman@bluedigits.com\fR> |
543 Jim Duchek <\fIjim@linuxpimps.com\fR> (maintainer) |
| 599 .br |
544 .br |
| 600 Jim Duchek <\fIjim@linuxpimps.com\fR> (maintainer) |
545 Rob Flynn <\fIgaim@robflynn.com\fR> (maintainer) |
| 601 .br |
546 .br |
| 602 Rob Flynn <\fIgaim@robflynn.com\fR> (maintainer) |
547 Adam Fritzler (libfaim maintainer) |
| 603 .br |
548 .br |
| 604 Adam Fritzler (libfaim maintainer) |
549 Christian 'ChipX86' Hammond (developer & webmaster) <\fIchipx86@chipx86.com\fR> |
| 605 .br |
550 .br |
| 606 Syd Logan (hacker and designated driver [lazy bum]) |
551 Syd Logan (hacker and designated driver [lazy bum]) |
| 607 .br |
552 .br |
| 608 Jim Seymour (Jabber developer) |
553 Jim Seymour (XMPP developer) |
| 609 .br |
554 .br |
| 610 Mark Spencer (original author) <\fImarkster@marko.net\fR> |
555 Mark Spencer (original author) <\fImarkster@marko.net\fR> |
| 611 .br |
556 .br |
| 612 Eric Warmenhoven (former lead developer) <\fIeric@warmenhoven.org\fR> |
557 Eric Warmenhoven (former lead developer) <\fIeric@warmenhoven.org\fR> |
| 613 .br |
558 .br |
| |
559 |
| |
560 |
| |
561 Our retired crazy patch writers include: |
| |
562 .br |
| |
563 Felipe 'shx' Contreras |
| |
564 .br |
| |
565 Decklin Foster |
| |
566 .br |
| |
567 Peter 'Bleeter' Lawler |
| |
568 .br |
| |
569 Robert 'Robot101' McQueen |
| |
570 .br |
| |
571 Benjamin Miller |
| |
572 .br |
| |
573 |
| 614 |
574 |
| 615 This manpage was originally written by Dennis Ristuccia <\fIdennis@dennisr.net\fR>. It has been updated and largely rewritten by Sean Egan <\fIseanegan@gmail.com\fR> and Ben Tegarden <\fItegarden@uclink.berkeley.edu\fR>. |
575 This manpage was originally written by Dennis Ristuccia <\fIdennis@dennisr.net\fR>. It has been updated and largely rewritten by Sean Egan <\fIseanegan@gmail.com\fR> and Ben Tegarden <\fItegarden@uclink.berkeley.edu\fR>. |