Re: gmc: atime == ctime ?!



>>>> In message <199906041555.LAA04059@rwf.lms.mit.edu>
>>>> On the subject of "Re: gmc: atime == ctime ?!"
>>>> Sent on Fri, 4 Jun 1999 11:55:32 -0400 (EDT)
>>>> Honorable "Sergey I. Panov" <sipan@mit.edu> writes:
 >> Sam Steingold wrote:
 >> >
 >> > put both atime & ctime in the custom view of gmc and observe that they
 >> > are reported to be identical for all files.
 >> > is this a bug?
 >> 
 >> Check your files with
 >> 
 >> ===============8<----------------------------------------------------
 >> #include <stdio.h>
 >> #include <time.h>
 >> #include <sys/types.h>
 >> #include <sys/stat.h>
 >> 
 >> int main (argc, argv)
 >> int     argc;
 >> char    *argv[];
 >> {
 >>     struct stat buf;
 >> 
 >>     while (--argc > 0)
 >>        {
 >>         stat(argv[argc], &buf);
 >>         printf("\"%s\": atime - %s", argv[argc], ctime(&buf.st_atime));
 >>         printf("\"%s\": mtime - %s", argv[argc], ctime(&buf.st_mtime));
 >>         printf("\"%s\": ctime - %s", argv[argc], ctime(&buf.st_ctime));
 >>         }
 >>    return 0;
 >> }
 >> ===============8<----------------------------------------------------
 >> 
 >> to see what your real m and c times are.

$ find -printf "%p - %s\n   atime: %a\n   mtime: %t\n   ctime: %c\n"

gives the same information and is somewhat shorter.

yes, it IS a gmc bug.

 >> Emacs creates new file everytime you save file but vi should not.

not always.  see `make-backup-files' and `backup-by-copying-when-linked'.


-- 
Sam Steingold (http://www.goems.com/~sds) running RedHat6.0 GNU/Linux
Micros**t is not the answer.  Micros**t is a question, and the answer is Linux,
(http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation.
You think Oedipus had a problem -- Adam was Eve's mother.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]