From: "Buchs, Kevin" <buchs.kevin@mayo.edu>
To: <help-gnu-emacs@gnu.org>
Subject: RE: help reading assembly code
Date: Tue, 25 Oct 2011 10:43:42 -0500 [thread overview]
Message-ID: <F326B9A37B353A449FC7A09B36835F82D917B3@MACE.sppdg.ad> (raw)
> I would like to be able to read more easily assembly code (since I really don't do it very often). For example it would be nice to have some function which shows me a reference documentation given the operator.
Given my current infatuation with org-mode, I would accomplish the function you describe above (only) using org-mode. I would make each command a radio link, such that you could hypertext jump to the documentation on the command wherever it occurs in your program. I would take a file of command documentation and insert it at the end of my program. Each command name should be enclosed in << >>. The turn on org-mode.
Alternately, I would suggest writing a lisp function which parses out each command and replaces it with a link with the same text as the label and that link executes lisp code to bring up the definition, in the message area, a help buffer, new frame or whatever fits best for you.
Have you checked out asm-mode? That might give you syntax coloring for assembly that could be useful. You might have to create an child mode with custom syntax table, depending on your assembly language.
Kevin Buchs | Senior Engineer | Department of Physiology and Biomedical Engineering - SPPDG
507-538-5459 | buchs.kevin@mayo.edu | http://www.mayo.edu/sppdg
Mayo Clinic | 200 1st St. SW | Rochester, MN 55905
next reply other threads:[~2011-10-25 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 15:43 Buchs, Kevin [this message]
2011-10-26 14:35 ` help reading assembly code Andrea Crotti
[not found] <mailman.947.1319459367.15868.help-gnu-emacs@gnu.org>
2011-10-24 20:38 ` Pascal J. Bourguignon
2011-10-25 2:25 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2011-10-24 12:29 Andrea Crotti
2011-10-26 22:10 ` Peter Münster
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=F326B9A37B353A449FC7A09B36835F82D917B3@MACE.sppdg.ad \
--to=buchs.kevin@mayo.edu \
--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.