From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org, miles@gnu.org
Subject: Re: arch taglines for emacs
Date: Sun, 24 Aug 2003 14:00:20 -0400 [thread overview]
Message-ID: <E19qzA4-0000Qb-4z@fencepost.gnu.org> (raw)
In-Reply-To: <200308231402.HAA00501@morrowfield.regexps.com> (message from Tom Lord on Sat, 23 Aug 2003 07:02:31 -0700 (PDT))
That is a specific variation on the general idea we've been kicking
around for what to do. It's likely we'll do something like that.
The specific proposal doesn't answer the question of changes to spaces
_within_ the tag:
/* arch-tag: tagged on 2003-01-01-12:12:12 by miles bader <miles@gnu.org>!! */
vs.
/* arch-tag: tagged on 2003-01-01-12:12:12 by miles bader<miles@gnu.org>!! */
Deletion of a single space is unlikely--filling won't do that, and
humans are likely to think of it as a real change and not do it
either.
By contrast, what is likely to happen is changes in number of spaces.
So if you treat all whitespace groups as equivalent to a single space,
you should avoid the problem.
Also, if you use string syntax with doublequotes, people are likely to
avoid changing anything inside that, even the number of spaces.
It would be best, I think, to make the change as a strictly
compatible extension.
I agree.
For example, tags using `arch-tag' comments
will continue to work as is, and tags using `arch-id' comments (or
some new string) will work in a new way that is delimited and not
so sensative to whitespace.
That is one way to do it. Or else you could use string syntax if the
tag begins with doublequote. That is similar to shell syntax and will
be easy to understand, and I doubt it will break any tags people are
using now (though that is not absolutely guaranteed).
next prev parent reply other threads:[~2003-08-24 18:00 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 [this message]
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
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=E19qzA4-0000Qb-4z@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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).