Date: Mon, 26 Jan 2004 18:12:23 -0600 From: mcabanatuan@wi.rr.com To: rob_spellberg <emailrob@emailrob.com> Cc: questions@freebsd.org Subject: Re: [kinda ot] writing the date into a file when saving it Message-ID: <3bbe1d3bf6bc.3bf6bc3bbe1d@rdc-kc.rr.com>
next in thread | raw e-mail | index | archive | help
as far as I know there is a check-in/check-out system in FreeBSD and other UNIX systems(rcs or revision control system) that allow you to add a $Tag to a file and it will be processed as such. iirc, you use co/ci file. then edit then check it back in. Taken from _Absolute BSD_ by; Michael Lucas - "Begin the revision-control process by checking in a file with ci(1), which is much like giving a book to the library. For example, a good file to protect with RCS is /etc/rc.conf. To start the RCS process, enter ci <path/filename>" - There is an excellent description on usage of this system in that book, but it's a bit drafted to post to the list. But there is a tag you can use in the file, $Id$, that shows time of last save/edit, who did it, and what version it's at. Hope that helps you any. Cheers, marc ----- Original Message ----- From: rob_spellberg <emailrob@emailrob.com> Date: Monday, January 26, 2004 3:59 pm Subject: [kinda ot] writing the date into a file when saving it > dear sir or madam --- > > this may be a vi question, but i'd like to be editor-independent, > if possible. > > i want to self-document source code files when i write them to disk. > > this would include such things as path and modification time. > > ideally, within vi, i would like to have :w run a script [ that i > would write ] > that does exactly what i want. > > for years, i've been doing this more or less haphazardly during > development, until i was satisfied that the file was in its > final form. > then i would manually get it right and leave it alone. > but i'm writing too much right now to keep doing this manually and > i'm something of a nut for documentation. > > its easy enough to write a sed script to find a unique string and > do a replacement. > its only slightly more involved to write a glorified version of touch > [ which is kinda what i want, actually ]. > > maybe what i want is to go into vi [ or ex, or wherever ], > find where :w is processed and cause it to look for a script to > run. > i know about :so. > i know about !command. > neither are really "it". > > i've been googling for about an hour and coming up almost > completely empty. > maybe there's a jargon word for what i want that i don't know. > > so to get to the question: what do you folks do? > > rob spellberg > woodstock, illinois > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions- > unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3bbe1d3bf6bc.3bf6bc3bbe1d>