Bug 443717 - Populating INPUTRC with /etc/inputrc by /etc/profile prevents using ~/.inputrc
Summary: Populating INPUTRC with /etc/inputrc by /etc/profile prevents using ~/.inputrc
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: setup
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-22 23:31 UTC by HK Kim
Modified: 2009-02-06 12:08 UTC (History)
0 users

Fixed In Version: setup-2.6.18-2.fc9
Clone Of:
Environment:
Last Closed: 2009-02-06 12:08:14 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description HK Kim 2008-04-22 23:31:35 UTC 
Description of problem:

Populating INPUTRC with /etc/inputrc by /etc/profile prevents using ~/.inputrc

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

How reproducible:
Always

Steps to Reproduce:
1. install rawhide
2. login
3. create .inputrc
4. call the program uses readline facility
  
Actual results:
4. .inputrc is not used.

Expected results:
4. .inputrc is respected.

Additional info:
It seems that it's unnecessary since readline library is supposed to do that.
Comment 1 Bug Zapper 2008-05-14 09:59:12 UTC 
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 2 Tom Lane 2008-06-19 18:11:40 UTC 
I've just gotten burnt by this too.  The code in /etc/profile to set INPUTRC is useless since readline started 
to support /etc/inputrc by itself, and it screws up the corner case where ~/.inputrc was just created in the 
current session.  Please remove it.
Comment 3 Ondrej Vasik 2008-12-10 16:22:08 UTC 
Fixed in rawhide and built as setup-2.7.5-2.fc11, will wait for a while with F-9/F-10 update to see if it is harmless change.
Comment 4 Ondrej Vasik 2009-02-06 12:08:14 UTC 
Fixed in setup-2.6.18-2.fc9 and setup-2.7.4-3.fc10, closing NEXTRELEASE.
Note You need to log in before you can comment on or make changes to this bug.