From: John McCabe <john@nospam.assen.demon.co.uk>
To: help-gnu-emacs@gnu.org
Subject: Re: Reading file in emacs
Date: Wed, 23 Jun 2010 10:05:54 +0100 [thread overview]
Message-ID: <kij326ptj5bfmupqg69eqf5qemdn2m368o@4ax.com> (raw)
In-Reply-To: mailman.0.1277266011.21451.help-gnu-emacs@gnu.org
On Tue, 22 Jun 2010 22:05:18 -0600, Qiang Guo <mcknight0219@gmail.com>
wrote:
>Here comes my second question, how to process file
>in a byte-by-byte fashion, for instance, instead of editing
>a line of text, I'd like to edit directly their binary
>representations ?
M-x hexl-mode
Does that help?
next parent reply other threads:[~2010-06-23 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1277266011.21451.help-gnu-emacs@gnu.org>
2010-06-23 9:05 ` John McCabe [this message]
2010-06-23 4:05 Reading file in emacs Qiang Guo
2010-06-23 5:11 ` Dirk-Jan C. Binnema
2010-06-23 5:13 ` Dirk-Jan C. Binnema
2010-06-23 6:38 ` Kevin Rodgers
2010-06-23 11:28 ` Deniz Dogan
2010-06-23 14:38 ` Gary
[not found] ` <mailman.4.1277292530.15366.help-gnu-emacs@gnu.org>
2010-06-24 10:26 ` Pascal J. Bourguignon
2010-06-24 11:20 ` Andreas Politz
2010-06-24 11:50 ` Pascal J. Bourguignon
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kij326ptj5bfmupqg69eqf5qemdn2m368o@4ax.com \
--to=john@nospam.assen.demon.co.uk \
--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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).