From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: arch taglines for emacs Date: 22 Aug 2003 23:54:02 +0300 Organization: JURTA Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <87u189e7md.fsf@mail.jurta.org> References: <87he4cfkhf.fsf@mail.jurta.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1061625326 11999 80.91.224.253 (23 Aug 2003 07:55:26 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 23 Aug 2003 07:55:26 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sat Aug 23 09:55:24 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19qTF6-0003WN-00 for ; Sat, 23 Aug 2003 09:55:24 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19qTJe-0001iV-00 for ; Sat, 23 Aug 2003 10:00:06 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19qTDI-000515-Gh for emacs-devel@quimby.gnus.org; Sat, 23 Aug 2003 03:53:32 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19qLYg-000766-Gr for emacs-devel@gnu.org; Fri, 22 Aug 2003 19:43:06 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19qLJG-0001I5-73 for emacs-devel@gnu.org; Fri, 22 Aug 2003 19:27:41 -0400 Original-Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19qLE9-0007Kv-B8; Fri, 22 Aug 2003 19:21:53 -0400 Original-Received: from [64.246.52.22] (helo=ns5.tangramltd.com) by mx20.gnu.org with esmtp (Exim 4.20) id 19qLE8-0004FY-DA; Fri, 22 Aug 2003 19:21:52 -0400 Original-Received: from 80-235-40-204-dsl.mus.estpak.ee ([80.235.40.204] helo=thinkpad.jurta.org) by ns5.tangramltd.com with esmtp (Exim 4.20) id 19qJ3j-0001MK-6d; Sat, 23 Aug 2003 00:02:59 +0300 Original-To: Miles Bader In-Reply-To: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 Original-Lines: 37 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ns5.tangramltd.com X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - jurta.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:16095 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:16095 Miles Bader writes: > 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. You are right: RCS tags have a different purpose. But what I propose is only to use the same format, i.e. to enclose arch tags in the $ characters. This solves many problems: special comment delimiters are not needed anymore, the $ character delimits the arch tag; whitespace is allowed inside the arch tag: all whitespace until the $ character is considered as part of tag. There is no need in special warning (e.g. "Do not change this comment"), because users already know that everything inside the $ characters shouldn't be changed manually. > 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. Limiting the search by some constant value is not a good thing. I have a bad experience with time-stamp Emacs feature. It limits its search for a Time-stamp tag by only first 8 lines. Sometimes, the line with a Time-stamp tag gets accidentally shifted below 8 lines (by adding new comment lines above it) and becomes invisible for time-stamp to update it. So I would also propose to disable default limits for time-stamp by setting the default value of the variable `time-stamp-line-limit' to 0. > 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). OK, I continued this discussion on gnu-arch-users. -- http://www.jurta.org/emacs/