From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.help Subject: Re: md5 checksum of a img file, or get the value of 100th byte Date: Mon, 09 Jun 2008 10:04:45 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <863anmwsxe.fsf@lifelogs.com> References: <196be374-4aa5-4c2f-ac8d-9555502d386c@s21g2000prm.googlegroups.com> <861w3azkpi.fsf@lifelogs.com> <868wxixujt.fsf@lifelogs.com> <86lk1iw5bc.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1213026067 21507 80.91.229.12 (9 Jun 2008 15:41:07 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 9 Jun 2008 15:41:07 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Jun 09 17:41:47 2008 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K5jVA-0001Hw-25 for geh-help-gnu-emacs@m.gmane.org; Mon, 09 Jun 2008 17:41:44 +0200 Original-Received: from localhost ([127.0.0.1]:54133 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K5jUM-0004QB-Pr for geh-help-gnu-emacs@m.gmane.org; Mon, 09 Jun 2008 11:40:54 -0400 Original-Path: news.stanford.edu!headwall.stanford.edu!newshub.sdsu.edu!news.albasani.net!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 42 Original-X-Trace: news.albasani.net WWX5tRTBi18vWy3uHnYya8dlLD+Zsn2NX2iBcXu62kEz+QubMHJyQqzWI6cDklKY7JX7pUuvgbOmXGAQGqSXGo2Z3cY9lcgRTT4PBDvhkz3fxKZT+jp8VaKQsQl1PAg4 Original-X-Complaints-To: abuse@albasani.net Original-NNTP-Posting-Date: Mon, 9 Jun 2008 15:00:57 +0000 (UTC) X-User-ID: gMLksuCb5bCNyYYLqrNt5CqNdueFXLTdKTyWG/O1NJM= X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Cancel-Lock: sha1:AzEfd8rSpF+VblNXs7vyPKq72/c= sha1:qcLG+UeN28LxVXvYz3jTv5MGMd4= User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) X-NNTP-Posting-Host: 1ELPUeWCifrLElhVmdbxxYv5Xy4TBlJn12YUsBl2P10= Original-Xref: news.stanford.edu gnu.emacs.help:159280 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:54640 Archived-At: On Sat, 07 Jun 2008 09:34:01 +0300 Eli Zaretskii wrote: >> From: Ted Zlatanov >> Date: Fri, 06 Jun 2008 17:45:43 -0500 >> EZ> For editing, I submit that there should be no reason to edit such EZ> large files. >> >> Maybe 10 years ago that was true. Today I see huge (over 300 MB) files >> very often (as a programmer and as a sysadmin). Logs of all sorts, for >> instance, and database dumps. EZ> Why would you want to _edit_ (as opposed to _view_) these files? As an example, at a previous job all server log time stamps were in Unix epoch offsets. That was hard to interpret, so I often had to filter the whole file to rewrite those time stamps to UTC ISO format. I then needed to do further modifications, e.g. look at only fields 3-9 and 12. I wrote many custom tools to make this easier, but in Emacs it would have been trivial. Sure, I can write a custom mode or pipe the file through a filter, but I *knew* I'd never need the original time stamps, so saving the ISO dates the first time was productive, and editing on the fly in general would have made my life easier. As another example, I often have to peek inside a large database dump or import CSV/TSV/etc. file and understand what went wrong. Once understood, it's more efficient to fix and save inside Emacs than split, modify, recombine outside Emacs. Expected memory sizes today are 2-8 GB. Disk speed is really the major issue with editing a 300MB file, and that's improving swiftly lately. I think it's feasible and not too painful to allow this kind of editing. How hard would it be to customize the Emacs defaults for that to happen? EZ> Please note that I agreed that viewing such large files chunk-wise EZ> would be useful, indeed. Do you or anyone know of an existing less-like mode for Emacs? If not, I'll put it on my TODO list. Thanks Ted