Bug 919452 - tcsh does not save history
Summary: tcsh does not save history
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: tcsh
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ondrej Vasik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-08 14:09 UTC by Daniel Qarras
Modified: 2013-07-09 07:33 UTC (History)
3 users (show)

Fixed In Version: tcsh-6.18.00-7.fc20.rpm
Clone Of:
Environment:
Last Closed: 2013-07-09 07:33:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Daniel Qarras 2013-03-08 14:09:05 UTC
Description of problem:
This is probably related to bug 653054. With 

set history  = 2
set savehist = (5 merge)

in my ~/.tcshrc any session remembers two previous commands as expected or two commands initially loaded from ~/.history. And when starting with no ~/.history in place the two commands are saved as expected. But on subsequent sessions ~/.history is never updated. This happens with and without merge, seems like if sizes of history and savehist are different then there are issue.

After reading the manual page I was expecting the above to 1) keep two previous commands in memory and 2) saving those two commands to the history file which would contain five entries.

Version-Release number of selected component (if applicable):
tcsh-6.18.00-3.fc18.i686

How reproducible:
Always

Steps to Reproduce:
1. See above
2.
3.
  
Actual results:
History file ~/.history never updated after initial creation.

Expected results:
History file ~/.history updated after each shell session exits.

Additional info:
Putting history -S into ~/.logout makes no difference.

Comment 1 Fedora Admin XMLRPC Client 2013-03-26 16:50:45 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora Admin XMLRPC Client 2013-03-27 08:19:46 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fridolín Pokorný 2013-03-28 13:16:09 UTC
Fixed in rawhide by scm-commit (http://lists.fedoraproject.org/pipermail/scm-commits/Week-of-Mon-20130325/989711.html). I do plan to fix it in f18 in next cumulative update.

Comment 4 Fedora Update System 2013-04-05 09:32:36 UTC
tcsh-6.18.01-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/tcsh-6.18.01-1.fc18

Comment 5 Daniel Qarras 2013-04-05 18:44:48 UTC
(In reply to comment #4)
> tcsh-6.18.01-1.fc18 has been submitted as an update for Fedora 18.
> https://admin.fedoraproject.org/updates/tcsh-6.18.01-1.fc18

Otherwise works ok but this BZ is not fixed due to

http://mx.gw.com/pipermail/tcsh-bugs/2013-March/000824.html

so I think this BZ should be marked as NOTABUG then?

Thanks!

Comment 6 Fedora Update System 2013-04-07 00:22:06 UTC
Package tcsh-6.18.01-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tcsh-6.18.01-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-5056/tcsh-6.18.01-1.fc18
then log in and leave karma (feedback).

Comment 7 Fridolín Pokorný 2013-05-09 06:34:03 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > tcsh-6.18.01-1.fc18 has been submitted as an update for Fedora 18.
> > https://admin.fedoraproject.org/updates/tcsh-6.18.01-1.fc18
> 
> Otherwise works ok but this BZ is not fixed due to
> 
> http://mx.gw.com/pipermail/tcsh-bugs/2013-March/000824.html
> 
> so I think this BZ should be marked as NOTABUG then?

Well, this is not one issue, but there were noted two issues:
1. ~/.history was never updated - fixed BUG
2. commands in history reflect "history" count if "savehist > history" - NOTABUG

Comment 9 Ondrej Vasik 2013-07-09 07:33:43 UTC
Closing NEXTRELEASE as only maintainer can push update to stable and Frido is no longer around.


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