From: Miles Bader <snogglethorpe@gmail.com>
Cc: Lennart Borgman <lennart.borgman.073@student.lu.se>, emacs-devel@gnu.org
Subject: Re: Translated from Japanese - how should the header look?
Date: Thu, 27 Oct 2005 10:33:27 +0900 [thread overview]
Message-ID: <fc339e4a0510261833t33c4b87bu@mail.gmail.com> (raw)
In-Reply-To: <E1EUwXB-0008Fb-00@etlken>
2005/10/27, Kenichi Handa <handa@m17n.org>:
> > Thanks, I see. The --*-- spec should be on the same line as the description:
>
> > ;;; cmd-mode.el --- Editing of MS Windows cmd and bat files ;; -*- Mode:
> > Emacs-Lisp ; coding: sjis-dos -*-
>
> You don't need "mode: Emacs-Lisp" because the file has
> extension ".el". Such a file is automatically visitted in
> emacs-lisp mode. And if the first line gets too longer,
> you can put coding: sjis-dos at the end of a file using
> locale variable section.
BTW, wouldn't it make sense to have checkdoc allow a "two line" header too?
It seems kind of silly to force all that stuff on one line when a
two-line version is arguably more readable (in those cases where you
need a long description).
I mean something like what Lennart originally tried:
;;; -*- Mode: Emacs-Lisp ; coding: sjis-dos -*-
;;; cmd-mode.el --- Editing of MS Windows cmd and bat files
I.e., the first line is just the mode vars, and the real header is the 2nd line.
[of course maybe it's not necessary in this case,, if Mode: Emacs-Lisp
is removed.]
-miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2005-10-27 1:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 7:15 Translated from Japanese - how should the header look? Lennart Borgman
2005-10-26 7:50 ` Kenichi Handa
2005-10-26 15:56 ` Lennart Borgman
2005-10-26 16:22 ` Reiner Steib
2005-10-26 16:34 ` Lennart Borgman
2005-10-27 1:26 ` Kenichi Handa
2005-10-27 1:33 ` Miles Bader [this message]
2005-10-28 3:47 ` Richard M. Stallman
2005-10-27 1:30 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc339e4a0510261833t33c4b87bu@mail.gmail.com \
--to=snogglethorpe@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
--cc=miles@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.