unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
* -*- mode: XXX -*- tags in *in files
@ 2004-03-29  8:17 Juanma Barranquero
  2004-03-29 19:06 ` Eli Zaretskii
  0 siblings, 1 reply; 3+ messages in thread
From: Juanma Barranquero @ 2004-03-29  8:17 UTC (permalink / raw)


I'd like to put -*- mode: XXX -*- tags in some *in source files.

I'm specifically interested in putting -*- makefile -*- in the many
makefile.w32-in files, so they can be automatically edited in
makefile-mode, but I imagine the measure would be useful for other files
(*make.defs, configure.in, src/config.in...).

Does anyone oppose to it?

(OK, the following questions are stylistic/aesthetic trivia and should
be skipped by those not interested :)

Is there any stylistic preference for

  -*- makefile -*-

vs.

  -*- mode: makefile -*-

vs.

  Local Variables:
  mode: makefile
  Local End:

?

If using the -*- (mode:\s*)?makefile -*- form, what about files starting
with:

#
# blah blah blah blah blah blah blah blah blah blah blah blah blah blah
# Copyright blah blah blah

Any preference for left-alignment:

# -*- makefile -*-
# blah blah blah blah blah blah blah blah blah blah blah blah blah blah

vs right-aligment:

#                                                      -*- makefile -*-
# blah blah blah blah blah blah blah blah blah blah blah blah blah blah

What about 

#  Makefile for GNU Emacs on the Microsoft W32 API.
#  Copyright (c) 2000-2001 Free Software Foundation, Inc.

Is better

#  Makefile for GNU Emacs on the Microsoft W32 API.   -*- makefile -*-

or (left-or-right aligned).

# -*- makefile -*-
#  Makefile for GNU Emacs on the Microsoft W32 API.

I know all these ways are equivalent, but I also know sometimes people
have *strong* views regarding stylistic issues...

                                                                Juanma

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: -*- mode: XXX -*- tags in *in files
  2004-03-29  8:17 -*- mode: XXX -*- tags in *in files Juanma Barranquero
@ 2004-03-29 19:06 ` Eli Zaretskii
  2004-03-30  7:26   ` Juanma Barranquero
  0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2004-03-29 19:06 UTC (permalink / raw)
  Cc: emacs-devel

> Date: Mon, 29 Mar 2004 10:17:15 +0200
> From: Juanma Barranquero <jmbarranquero@wke.es>
> 
> I'm specifically interested in putting -*- makefile -*- in the many
> makefile.w32-in files, so they can be automatically edited in
> makefile-mode

That is good, I think.

> but I imagine the measure would be useful for other files
> (*make.defs, configure.in, src/config.in...).

configure.in already switches on the Autoconf mode, and config.in is
in C mode due to a Local Variables section int.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: -*- mode: XXX -*- tags in *in files
  2004-03-29 19:06 ` Eli Zaretskii
@ 2004-03-30  7:26   ` Juanma Barranquero
  0 siblings, 0 replies; 3+ messages in thread
From: Juanma Barranquero @ 2004-03-30  7:26 UTC (permalink / raw)



On Mon, 29 Mar 2004 21:06:11 +0200
"Eli Zaretskii" <eliz@gnu.org> wrote:

> That is good, I think.

Yeah. I get default-generic-mode while editing the .w32-in files, and as
I have globally set indent-tabs-mode to nil, I'm always afraid of
changing a tab by accident.

> configure.in already switches on the Autoconf mode, and config.in is
> in C mode due to a Local Variables section int.

You're right.

Thanks,

                                                                Juanma

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-03-30  7:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-29  8:17 -*- mode: XXX -*- tags in *in files Juanma Barranquero
2004-03-29 19:06 ` Eli Zaretskii
2004-03-30  7:26   ` Juanma Barranquero

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).