Bug 142799 - Usage time logging functionality is needed
Summary: Usage time logging functionality is needed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-14 08:05 UTC by Bill
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-12-14 11:42:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Bill 2004-12-14 08:05:21 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; MSNIA; 
T312461)

Description of problem:
I have to report my time spent on maintenance projects.  Most of that 
time is spent editing programs.  I would love to have all the editors 
log: file name, start edit time, end edit time

I would prefer the data logged onto my PC.

I could then take the log and plug it into my time accounting 
system.  It would save me hours every week and it would likely 
increase my pay.  I currently use a paper system and I've got a labor 
intensive web page I could use.  But in either case it's a manual 
process.  I think the computer should be able to handle this task 
without too much human intervention.


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


How reproducible:
Always

Steps to Reproduce:
1. no editor I know of offers this logging feature 
2. many people have to report their time
3.
    

Additional info:

Comment 1 Karsten Hopp 2004-12-14 11:42:55 UTC
Why don't you write a small wrapper around vim, rename vim to vim_orig
and name the new script vim ? Time logging isn't something an editor
should do, a wrapper around it is much simpler to customize.

Something like this:

#!/bin/bash
echo -n "Start edit of $1 at " >> LOGFILE
date >> LOGFILE
vim_orig $1
echo -n "End edit of $1 at " >> LOGFILE
date >> LOGFILE


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