all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: mode for preprocessed files
Date: Wed, 23 Jul 2008 20:00:23 -0700	[thread overview]
Message-ID: <200807240300.m6O30OgU007933@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <jwvljzsdnr4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 23 Jul 2008 22:24:15 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

  > > Currently C and C++ preprocessed files (.i and .ii, respectively) are
  > > opened in fundamental mode.
  > 
  > > Would anyone object if we would use c-mode and c++-mode for them by default?
  > > I've been doing this locally for a long time without any problem.
  > 
  > It might be OK, tho I wonder how often that's useful.
  > I.e. it's OK but put it way down the list, with a comment explaining why
  > .i and .ii are mapped to c-mode and c++-mode

Done.  But the list is created using autoloads... BTW, wasn't there a
plan to avoid doing that?

  >  (it wouldn't have occurred
  > to me that those extensions are actually used for C and C++ files).

They are the standard extensions that C/C++ compilers generate when you
tell them to save the preprocessed file.  Compilers accept files with
those extensions without wondering what the language is.




  reply	other threads:[~2008-07-24  3:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24  0:17 mode for preprocessed files Dan Nicolaescu
2008-07-24  2:24 ` Stefan Monnier
2008-07-24  3:00   ` Dan Nicolaescu [this message]
2008-07-24 12:52     ` Stefan Monnier
2008-07-24 14:14       ` Dan Nicolaescu
2008-07-24 21:09       ` Miles Bader
2008-07-24 22:05       ` Richard M Stallman
2008-07-24  2:30 ` David De La Harpe Golden

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=200807240300.m6O30OgU007933@sallyv1.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.