From: Wojciech Meyer <wojciech.meyer@googlemail.com>
To: Ken Hori <fplemma@gmail.com>
Cc: Wojciech Meyer <wojciech.meyer@googlemail.com>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: feature suggestion for editing config files.
Date: Sun, 04 Jul 2010 01:16:25 +0100 [thread overview]
Message-ID: <87d3v4je3q.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTiniBdtwy5gknWxwCE8zwckqtyjvm3_mg7mCqfE0@mail.gmail.com> (Ken Hori's message of "Sat, 3 Jul 2010 14:26:39 -0700")
Ken Hori <fplemma@gmail.com> writes:
> I think this will be incredibly useful not just for editing config files, but
> for writing code. For example, Emacs can float a tooltip of the prototype of
> <function_name> right after "function_name(" is typed and let it sit below the
> cursor asynchronously for a certain amount of time. It is something modern IDEs
> has, which everyone seems to like but Emacs lacks.
>
Hi,
Yes, that is what I meant, for more complex grammars all the regex based
parsing, or hand cratfted recursive descent parsers in Emacs _could_ be
possibly substituted with Semantic. (which also maintains dependencies
between files, and know how to include the module), and despite the fact
I've seen Emacs modules like gcc-sense for C++ and I've seen ocaml-spot
for OCaml (which are both patches to a compiler, integrated with Emacs
by async process) which give an exact source code information, I am more
fond to see Semantic support as it is written natively in Elisp, and
makes the integration just easier (even if it is less precise). The
pain is that for C++, to be precise, one needs to write the frontend for
unrolling templates which is basically an interpreter. (but that's one
of side effects of `nice features' of C++)
Wojciech
prev parent reply other threads:[~2010-07-04 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 17:17 Fwd: feature suggestion for editing config files Richard Stallman
2010-06-11 18:20 ` Wojciech Meyer
2010-07-03 21:26 ` Ken Hori
2010-07-04 0:16 ` Wojciech Meyer [this message]
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=87d3v4je3q.fsf@gmail.com \
--to=wojciech.meyer@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=fplemma@gmail.com \
--cc=rms@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.