Bug 621971 - Add name highlight to finch in IRC
Summary: Add name highlight to finch in IRC
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin   
(Show other bugs)
Version: 12
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Stu Tomlinson
QA Contact: Fedora Extras Quality Assurance
Depends On: 621960
TreeView+ depends on / blocked
Reported: 2010-08-06 16:32 UTC by Veaceslav Falico
Modified: 2014-09-30 23:44 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-03 12:55:43 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
RHEL6 patch, should apply with some shifts (4.40 KB, patch)
2010-08-06 16:34 UTC, Veaceslav Falico
no flags Details | Diff

Description Veaceslav Falico 2010-08-06 16:32:36 UTC
+++ This bug was initially created as a clone of Bug #621960 +++

Created an attachment (id=437191)
proposed patch

Description of problem:
When using finch as an IRC client, the tabs of chats are updated the same way if you are addressed in chat or not.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. start finch, join a chat-room in irc, make the window unfocused
2. write from another account to the first account
3. the chat-room tab is highlighted the same way as if you were not addressed

Additional info:

It is very uncomfortable to always either check the chat-rooms or use irssi/another irc proxy to see if you were addressed.

Patch attached.

--- Additional comment from vfalico@redhat.com on 2010-08-06 11:55:22 EDT ---

Filed the patch to upstream also:


Comment 1 Veaceslav Falico 2010-08-06 16:34:01 UTC
Created attachment 437201 [details]
RHEL6 patch, should apply with some shifts

Comment 2 Fedora Admin XMLRPC Client 2010-09-22 19:37:03 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora Admin XMLRPC Client 2010-09-22 19:38:10 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Bug Zapper 2010-11-03 11:12:04 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 5 Bug Zapper 2010-12-03 12:55:43 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.