From: Andrea Crotti <andrea.crotti.0@gmail.com>
To: "Buchs, Kevin" <buchs.kevin@mayo.edu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: help reading assembly code
Date: Wed, 26 Oct 2011 15:35:40 +0100 [thread overview]
Message-ID: <4EA81ABC.6030103@gmail.com> (raw)
In-Reply-To: <F326B9A37B353A449FC7A09B36835F82D917B3@MACE.sppdg.ad>
On 10/25/2011 04:43 PM, Buchs, Kevin wrote:
> 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.
>
>
I also like a lot org-mode, but I don't think it would be so helpful in
this case...
Also a simple function to bind to some key in asm-mode would be
perfectly fine,
the only problem is that I can't find any reference web-site with all
the informations I want.
(which can be indexed easily with each node reachable)
next prev parent reply other threads:[~2011-10-26 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 15:43 help reading assembly code Buchs, Kevin
2011-10-26 14:35 ` Andrea Crotti [this message]
[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
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=4EA81ABC.6030103@gmail.com \
--to=andrea.crotti.0@gmail.com \
--cc=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.
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).