From: Masatake YAMATO <jet@gyve.org>
Cc: emacs-devel@gnu.org
Subject: Re: font-lock in machine mode of gdba
Date: Wed, 20 Oct 2004 01:38:16 +0900 (JST) [thread overview]
Message-ID: <20041020.013816.97281206.jet@gyve.org> (raw)
In-Reply-To: <16757.5765.225553.503676@farnswood.snap.net.nz>
> > > I think it should at least be consistent with asm-mode where keywords like
> > > movl, andl, etc are fontified with font-lock-keyword-face and operands and
> > > registers are left unfontified.
> >
> > I have changed both gdb-ui.el and asm-mode.el; and used the same face in the
> > both mode for the same object. Do you think operand fontification is too decorative?
> >
> > Now font-lock-mode is turn-on in gdb-assembler-mode when global-font-lock-mode is
> > true. gdb-assembler-mode-hook is also provided. See the comments at the tail of
> > font-core.el.
>
> I don't know if the operand fontification too decorative but is it logical?
> Should a register name have font-lock-variable-face and an address
> font-lock-constant-face? I don't use disassembly for debugging or code in
> assembler. Perhaps someone who does can comment.
I'm using disassembly for hacking and understanding glibc's
/lib/ld-linux.so.2 on i386. (gdba is extremely useful.) I feel my
definition is not so bad. The face usage is consistent with asm-mode.
BTW, What I really need is fontification on x/i commands output.
Masatake YAMATO
next prev parent reply other threads:[~2004-10-19 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 15:29 font-lock in machine mode of gdba Masatake YAMATO
2004-10-17 16:55 ` Stefan Monnier
2004-10-18 2:14 ` Nick Roberts
2004-10-18 2:25 ` Nick Roberts
2004-10-19 2:26 ` Masatake YAMATO
2004-10-19 12:45 ` Stefan Monnier
2004-10-21 10:53 ` Nick Roberts
2004-10-19 13:28 ` Nick Roberts
2004-10-19 13:54 ` Stefan Monnier
2004-10-19 14:27 ` Masatake YAMATO
2004-10-19 16:38 ` Masatake YAMATO [this message]
2004-10-23 22:09 ` Nick Roberts
2004-10-23 23:49 ` Masatake YAMATO
2004-10-23 23:59 ` Nick Roberts
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=20041020.013816.97281206.jet@gyve.org \
--to=jet@gyve.org \
--cc=emacs-devel@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.