unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@surf.glug.org>
Cc: emacs-devel@gnu.org
Subject: Re: Possible change to startup.el
Date: Thu, 24 Mar 2005 11:49:55 +0100	[thread overview]
Message-ID: <E1DEPuV-0000Dk-00@surf.glug.org> (raw)
In-Reply-To: message from Richard Stallman on Wed, 23 Mar 2005 15:25:54 -0500

   From: Richard Stallman <rms@gnu.org>
   Date: Wed, 23 Mar 2005 15:25:54 -0500

   So how about adopting a convention [...]

three approaches come to mind:

(a) title on first line in file, ending w/ fullstop (period);

(b) a local variable "title-range" specifies the beginning and end
    character positions of the title in the text;

(c) separate file TUTORIAL.metainfo that maps locale to various
    things, such as the info in (b), coding system for read, a
    bug-report or support-group email address, etc.

of these, i favor (c), even though it has similar maintenance
requirement as the alist, because the file has the advantage of
being more efficient to access, and its format is extensible.
(we can also subsume TUTORIAL.translators into it.)

next, (b) is nice because the existing flow does not have to be
changed.  however, the full file needs to be read in, or at least
enough so that its title is present and its coding can be
established.

lastly, (a) is straightforward (less prone to botch-ups).  i do
not like it for esthetic reasons only.  same thinking applies for
any fixed-position approach.

thi

             reply	other threads:[~2005-03-24 10:49 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 10:49 Thien-Thi Nguyen [this message]
2005-03-24 19:05 ` Possible change to startup.el Miles Bader
2005-03-25  6:43 ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2005-04-03 10:31 Thien-Thi Nguyen
2005-04-07  6:55 ` Juri Linkov
2005-04-08  3:22   ` Richard Stallman
2005-04-08  6:31     ` Marcelo Toledo
2005-04-08  7:27       ` Kenichi Handa
2005-04-08 18:32       ` Juri Linkov
2005-04-08 18:43         ` Marcelo Toledo
2005-04-10  1:54         ` Richard Stallman
2005-04-08 10:44     ` Eli Zaretskii
2005-04-08 18:32       ` Juri Linkov
2005-04-09  8:00         ` Eli Zaretskii
2005-04-13 23:58           ` David Kastrup
2005-04-14  4:02             ` Eli Zaretskii
2005-04-14  9:46               ` David Kastrup
2005-04-15  8:15                 ` Eli Zaretskii
2005-04-14 19:03             ` Richard Stallman
2005-04-14 23:40               ` David Kastrup
2005-04-17  1:49                 ` Richard Stallman
2005-04-17  9:31                   ` David Kastrup
2005-04-17 19:20                     ` Richard Stallman
2005-04-17 19:51                       ` David Kastrup
2005-04-10  1:54         ` Richard Stallman
2005-03-31 12:01 Thien-Thi Nguyen
2005-03-31 12:59 ` Kim F. Storm
2005-03-31 13:43   ` David Kastrup
2005-03-31 22:19     ` Kim F. Storm
2005-04-01  4:10   ` Richard Stallman
2005-04-01  4:03 ` Juri Linkov
2005-04-03  5:20   ` Richard Stallman
2005-03-31 11:37 Thien-Thi Nguyen
2005-03-31 12:05 ` Miles Bader
2005-03-31 13:32   ` Thien-Thi Nguyen
2005-03-31 14:29     ` Miles Bader
2005-03-31 16:15       ` Thien-Thi Nguyen
2005-03-31 22:23         ` Miles Bader
2005-04-01  4:10   ` Richard Stallman
2005-03-30 22:47 Thien-Thi Nguyen
2005-03-30 23:38 ` David Kastrup
2005-04-01  4:11   ` Richard Stallman
2005-03-31  1:40 ` Miles Bader
2005-03-31  1:02   ` Marcelo Toledo
2005-03-31  3:20     ` Miles Bader
2005-03-31  2:21       ` Marcelo Toledo
2005-03-31  6:59 ` Juri Linkov
2005-04-01  4:11 ` Richard Stallman
2005-03-25 18:07 Thien-Thi Nguyen
2005-03-27  3:52 ` Richard Stallman
2005-03-27 23:15   ` Juri Linkov
2005-03-28 22:53     ` Richard Stallman
2005-03-29 20:19       ` Thien-Thi Nguyen
2005-03-30  4:08         ` Marcelo Toledo
2005-03-30  9:42           ` Thien-Thi Nguyen
2005-03-21 18:44 David Kastrup
2005-03-21 20:50 ` Thien-Thi Nguyen
2005-03-21 21:10   ` David Kastrup
2005-03-21 21:25     ` Andreas Schwab
2005-03-21 22:14       ` David Kastrup
2005-03-22  0:03         ` Andreas Schwab
2005-03-22  1:38         ` David Hansen
2005-03-23 18:25         ` James Cloos
2005-03-27  3:53           ` Richard Stallman
2005-03-22  4:55   ` Eli Zaretskii
2005-03-22  6:24     ` Miles Bader
2005-03-22  8:15       ` Kenichi Handa
2005-03-22  8:27         ` Miles Bader
2005-03-22 10:40           ` David Kastrup
2005-03-22 12:44             ` Jason Rumney
2005-03-22 20:31             ` Werner LEMBERG
2005-03-22 11:23           ` Kenichi Handa
2005-03-22 12:33           ` Juri Linkov
2005-03-22 19:32       ` Eli Zaretskii
2005-03-22 10:18     ` David Kastrup
2005-03-22 19:34       ` Eli Zaretskii
2005-03-22 22:24         ` David Kastrup
2005-03-22 20:44   ` Richard Stallman
2005-03-22 22:32     ` Thien-Thi Nguyen
2005-03-23  6:21       ` Richard Stallman
2005-03-23 13:55         ` Juri Linkov
2005-03-23 18:01           ` Werner LEMBERG
2005-03-25 12:51             ` Kenichi Handa
2005-03-23 20:25           ` Richard Stallman
2005-03-22 13:57 ` Richard 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=E1DEPuV-0000Dk-00@surf.glug.org \
    --to=ttn@surf.glug.org \
    --cc=emacs-devel@gnu.org \
    --cc=ttn@glug.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 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).