From: dkcombs@panix.com (David Combs)
To: help-gnu-emacs@gnu.org
Subject: Re: recover file after crash
Date: Wed, 20 Feb 2013 01:35:43 +0000 (UTC) [thread overview]
Message-ID: <kg199f$nqi$2@reader1.panix.com> (raw)
In-Reply-To: mailman.18392.1359236878.855.help-gnu-emacs@gnu.org
In article <mailman.18392.1359236878.855.help-gnu-emacs@gnu.org>,
Ludwig, Mark <ludwig.mark@siemens.com> wrote:
>> From: Eli Zaretskii
>> Sent: Saturday, January 26, 2013 4:40 AM
>>
>> > From: "Ludwig, Mark" <ludwig.mark@siemens.com>
>> > Date: Fri, 25 Jan 2013 20:56:47 +0000
>> >
>> > I think I thoroughly documented this in Bug # 9589
>> > (http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9589) for the
>> > developers to consider, which see.
>>
>> Assuming the OP has such long lines, yes. But that would be unusual
>> in a file that is being read in any kind of overview mode, because
>> those normally are for human consumption, so long lines are unlikely
>> to appear in them.
>
>Agreed, this is not an every-day occurrence.
>
>In my case, it is because log files I receive from customers sometimes
>have a huge number of NUL bytes preceding the readable content. This
>leading, extremely-long line gets in the way of reasonable
>responsiveness.
>
>I also confess that I have not been keeping up with the current trends
>in Emacs development. Back when I started using EMACS [sic], it was
>an excellent binary editor. Apparently this is not a current
>requirement, because it clearly is no longer useful for same. Side
>question: is there a GNU tool designed for editing binary files?
>
>Cheers,
>Mark
>
About all those nulls that make lines so long, couldn't you run
the file through sed or some super-short c-program or even perl
first, and delete (ie ignore) all those nulls then?
David
next prev parent reply other threads:[~2013-02-20 1:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 20:16 recover file after crash drain
2013-01-24 21:00 ` Drew Adams
2013-01-25 18:23 ` drain
2013-01-25 18:30 ` Valentin Baciu
2013-01-25 19:12 ` drain
2013-01-25 19:29 ` Eli Zaretskii
2013-01-25 20:31 ` drain
2013-01-25 20:44 ` Eli Zaretskii
2013-01-25 21:04 ` drain
2013-01-25 20:56 ` Ludwig, Mark
2013-01-26 10:39 ` Eli Zaretskii
2013-01-26 21:47 ` Ludwig, Mark
2013-01-27 6:19 ` Eli Zaretskii
[not found] ` <mailman.18392.1359236878.855.help-gnu-emacs@gnu.org>
2013-02-20 1:35 ` David Combs [this message]
2013-01-25 19:36 ` Valentin Baciu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='kg199f$nqi$2@reader1.panix.com' \
--to=dkcombs@panix.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.