From: Werner LEMBERG <wl@gnu.org>
To: drew.adams@oracle.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: reading/writing binary data in structured form
Date: Sun, 27 Apr 2008 00:29:04 +0200 (CEST) [thread overview]
Message-ID: <20080427.002904.30968782.wl@gnu.org> (raw)
In-Reply-To: <001301c8a7bc$a5dc5630$0200a8c0@us.oracle.com>
> No, I wasn't joking; I was trying to help.
OK, thanks.
> It wasn't clear to me from your "in a structured way" that you meant
> anything like what you describe now. You did not mention that you
> were familiar with hexl-mode or explain anything about what you
> wanted that was different.
This is probably caused by the fact that English is not my mother
tongue...
Werner
next prev parent reply other threads:[~2008-04-26 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080426.160513.247304034.wl@gnu.org>
2008-04-26 14:22 ` reading/writing binary data in structured form Drew Adams
2008-04-26 15:18 ` Werner LEMBERG
2008-04-26 16:43 ` Drew Adams
2008-04-26 22:29 ` Werner LEMBERG [this message]
[not found] ` <mailman.10841.1209223213.18990.help-gnu-emacs@gnu.org>
2008-04-27 1:47 ` Dan Espen
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=20080427.002904.30968782.wl@gnu.org \
--to=wl@gnu.org \
--cc=drew.adams@oracle.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.
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).