Isn't there something on this list about "profile not speculate"?
(defun convert-tai64nlocal (arg)
"generate a local, human timestamped buffer from a tai64 timestamped buffer"
(interactive "p")
(mark-whole-buffer)
(shell-command-on-region
(region-beginning) (region-end) "tai64nlocal" nil nil)
)
works pretty fast, only issue it opens an output buffer, but OTOH, you
don't have to go to any effort.... ;^)
You could also just take out the 't' in your "...log/run" files, no time
stamp, no problem.
Regards,
Tony
On Mon, 31 Jul 2000, David Dyer-Bennet wrote:
> Charles Cazabon <[EMAIL PROTECTED]> writes on 31 July 2000 at 11:20:48 -0600
> > David Dyer-Bennet <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Really? If I want to tail a log file, eg, I go like this:
> > > >
> > > > tail ../someservice/current | tai64nlocal
> > > >
> > > > and it all looks fine for humans.
> >
> > > Yeah, it works fine for people who check log files by tailing them. I
> > > check them by bringing them into an emacs buffer, so the funny
> > > timestamps make them darned near useless.
> >
> > So why not tail them to a temp file and use emacs to view the temp file?
> > Or write an emacs-lisp function to convert the timestamps.
>
> If I'm going to go to effort to make it work the way I want, I think
> I'll just change multilog to use a sensible format. It's silly having
> archival log files sitting there that don't mean anything without a
> conversion program; straight text is the appropriate format for log
> files.
>
> I had thought about writing a mode for TAI stamped log files that
> converts the timestamps, but that will be pretty slow since it'll have
> to change every line of the file.
>
--
Tony Hansmann ([EMAIL PROTECTED])
Director of Technical Services
Quepasa.com, INC.
602-716-0100
