From: Nordlöw <per.nordlow@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Navigating Mode-Specific Language Tokens
Date: Wed, 13 Jan 2010 02:33:45 -0800 (PST) [thread overview]
Message-ID: <37ad191f-d186-4a25-9f9c-45db5b32c89d@m3g2000yqf.googlegroups.com> (raw)
Has anyone written a function for navigating/iterating/forward/
backward mode-specifc (lexical) language tokens?
I always get frustrated when I navigate C-syntax-styled code in Emacs
after being used to the elegant way of navigating expression-list-
trees in lisp-mode.
I really believe the coding experience of Emacs would be enhanced
greatly enhanced in these cc-like modes if we had forward/backward-
token(). I think I would bind to M-f/b.
The function semantic-flex or semantic-lex-c-... can be used do the
job but how do I know at what character to start the first time I do
forward/backward-token?
Thanks in advance,
Nordlöw
next reply other threads:[~2010-01-13 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 10:33 Nordlöw [this message]
2010-01-13 16:44 ` Navigating Mode-Specific Language Tokens Glauber Alex Dias Prado
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=37ad191f-d186-4a25-9f9c-45db5b32c89d@m3g2000yqf.googlegroups.com \
--to=per.nordlow@gmail.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).