From: Manuel Giraud <manuel@ledu-giraud.fr>
To: Hongyi Zhao <hongyi.zhao@gmail.com>
Cc: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: Check/understand the Fortran Binary file format specification with Emacs.
Date: Thu, 17 Mar 2022 15:49:01 +0100 [thread overview]
Message-ID: <87czikzlb6.fsf@elite.giraud> (raw)
In-Reply-To: <CAGP6POLRpFBE5NsTNwqwQYpZ-nB92FcNkCHfBzt4zpqbri6Lwg@mail.gmail.com> (Hongyi Zhao's message of "Thu, 17 Mar 2022 22:21:41 +0800")
Hongyi Zhao <hongyi.zhao@gmail.com> writes:
> Any hints for achieving this aim with Emacs?
The file is small and can be opened using `hexl-find-file' which is
Emacs' hexadecimal editor.
Best regards,
--
Manuel Giraud
next prev parent reply other threads:[~2022-03-17 14:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 14:21 Check/understand the Fortran Binary file format specification with Emacs Hongyi Zhao
2022-03-17 14:49 ` Manuel Giraud [this message]
2022-03-17 15:47 ` Hongyi Zhao
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=87czikzlb6.fsf@elite.giraud \
--to=manuel@ledu-giraud.fr \
--cc=help-gnu-emacs@gnu.org \
--cc=hongyi.zhao@gmail.com \
/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).