From: Eli Zaretskii <eliz@gnu.org>
Cc: nickrob@snap.net.nz, bug-cc-mode@gnu.org, emacs-devel@gnu.org
Subject: Re: c-submode-indicators at wrong place in minor-mode-alist
Date: Sat, 17 Dec 2005 10:22:18 +0200 [thread overview]
Message-ID: <uhd98nnet.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1051216092403.548B-100000@acm.acm> (message from Alan Mackenzie on Fri, 16 Dec 2005 10:18:35 +0000 (GMT))
> Date: Fri, 16 Dec 2005 10:18:35 +0000 (GMT)
> From: Alan Mackenzie <acm@muc.de>
> Cc: bug-cc-mode@gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
> emacs-devel@gnu.org
>
> >CC mode seems to have become much more complicated, but that might be
> >because its much more powerful. I don't know, I just find it hard to
> >understand.
>
> It is hard to understand. Partly, it's because C and friends are such a
> dreadful languages (to parse, that is ;-)
Really? as compared to what? From what I know, C is actually a
relatively easily parsable language.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-17 8:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 21:41 c-submode-indicators at wrong place in minor-mode-alist Stefan Monnier
2005-12-15 0:25 ` Nick Roberts
2005-12-15 14:25 ` Alan Mackenzie
2005-12-15 20:08 ` Nick Roberts
2005-12-16 10:18 ` Alan Mackenzie
2005-12-16 20:03 ` Nick Roberts
2005-12-17 8:22 ` Eli Zaretskii [this message]
2005-12-18 9:26 ` Alan Mackenzie
2005-12-15 20:40 ` Stefan Monnier
2005-12-16 10:57 ` Alan Mackenzie
2005-12-17 1:05 ` Richard M. Stallman
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=uhd98nnet.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-cc-mode@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).