From: Miles Bader <miles@lsi.nec.co.jp>
Cc: gnu-arch-users@gnu.org, emacs-devel@gnu.org
Subject: Re: arch taglines for emacs
Date: 21 Aug 2003 13:36:14 +0900 [thread overview]
Message-ID: <buozni3wrsx.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <87he4cfkhf.fsf@mail.jurta.org>
Juri Linkov <juri@jurta.org> writes:
> The better and safer if it had a form of RCS keywords ($Id$, $Header$, etc.)
It's a very different concept than RCS keywords.
RCS keywords are a form of communication from RCS to the human reader of
the source code. Arch taglines, on the other hand, are strictly for the
use of arch (though I suppose you could choose to use them for similar
purposes in other tools). RCS tags change (which can be a huge source
of problems). Arch taglines _never_ -- by definition -- change.
Because taglines are meant for arch, not for the user, you also probably
don't want them in a very user-visible location; also arch only searches
for them in the first and last 1024-byte blocks of the file. For these
reasons, the convention is to make them the last line in the source
file, or thereabouts.
You are right that a less strictly line-oriented syntax would be more
convenient (in fact such a syntax is being discussed right now on
gnu-arch-users, in case you're reading this on emacs-devel).
> If initially the user enters strings of the form $Arch$, then arch
> could assign an unique tag to it automatically.
Because arch taglines never change, they are assigned only once;
as such, I suppose you could create a tool to automatically look for
`unfilled' tags and fill them in, if you find such a method of creating
taglines convenient.
I think there are currently script available which automatically add a
tagline to every un-tagged source file they find, for files who's type
the script knows. Because of the convention of putting taglines at the
end of the file, this probably works pretty well, and is slightly more
convenient than requiring the user to add an unfilled-in template
somewhere...
-Miles
--
Yo mama's so fat when she gets on an elevator it HAS to go down.
_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://mail.gnu.org/mailman/listinfo/gnu-arch-users
GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/
next prev parent reply other threads:[~2003-08-21 4:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 3:55 arch taglines for emacs Miles Bader
2003-08-20 2:42 ` Richard Stallman
2003-08-20 2:54 ` Miles Bader
2003-08-20 3:03 ` Tom Lord
2003-08-21 14:11 ` Richard Stallman
2003-08-21 14:56 ` Tom Lord
2003-08-23 3:59 ` Richard Stallman
2003-08-23 14:02 ` Tom Lord
2003-08-24 18:00 ` Richard Stallman
2003-08-24 18:00 ` Richard Stallman
2003-08-24 18:59 ` Tom Lord
2003-08-24 19:38 ` Jonathan Walther
2003-08-24 19:44 ` [Gnu-arch-users] " Tom Lord
2003-08-25 1:59 ` Miles Bader
2003-08-25 2:08 ` Tom Lord
2003-08-26 1:38 ` Richard Stallman
[not found] ` <87he4cfkhf.fsf@mail.jurta.org>
2003-08-21 4:36 ` Miles Bader [this message]
2003-08-22 20:54 ` Juri Linkov
2003-08-21 11:29 ` Florian Weimer
2003-08-22 1:47 ` Miles Bader
2003-08-22 12:07 ` Andreas Schwab
2003-08-22 20:55 ` Miles Bader
-- strict thread matches above, loose matches on Subject: below --
2003-09-01 16:03 Miles Bader
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=buozni3wrsx.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=gnu-arch-users@gnu.org \
--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 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).