unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jonathan Walther <krooger@debian.org>
Subject: Re: Re: arch taglines for emacs
Date: Sun, 24 Aug 2003 12:38:47 -0700	[thread overview]
Message-ID: <20030824193847.GA20246@reactor-core.org> (raw)
In-Reply-To: <200308241859.LAA05271@morrowfield.regexps.com>


[-- Attachment #1.1: Type: text/plain, Size: 1279 bytes --]

On Sun, Aug 24, 2003 at 11:59:19AM -0700, Tom Lord wrote:
>   In favor of (a): going that route poses the least risk to my
>   degrees of freedom doing other changes to the "inventory" subsystem
>   of arch going forward -- but I'll qualify that by saying that I
>   don't see the risk of not doing (a) as huge.
>
>So, tell me what to do to help keep Emacs folks happy.  Your call.

I would love to be able to use arch-id: syntax for Xouvert.

Did anyone notice that switching to

    /* arch-id: "old-tag*/" */

won't work?  Because of the */ coming too early in the line.  C compiler
would emit an error about an unterminated string.

Jonathan

-- 

    It's not true unless it makes you laugh,                           
             but you don't understand it until it makes you weep.      

    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

                     Geek House Productions, Ltd.

  Providing Unix & Internet Contracting and Consulting,
  QA Testing, Technical Documentation, Systems Design & Implementation,
  General Programming, E-commerce, Web & Mail Services since 1998

Phone:   604-435-1205
Email:   djw@reactor-core.org
Webpage: http://reactor-core.org
Address: 2459 E 41st Ave, Vancouver, BC  V5R2W2

[-- Attachment #1.2: Type: application/pgp-signature, Size: 307 bytes --]

[-- Attachment #2: Type: text/plain, Size: 214 bytes --]

_______________________________________________
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/

  reply	other threads:[~2003-08-24 19:38 UTC|newest]

Thread overview: 22+ 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 [this message]
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

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=20030824193847.GA20246@reactor-core.org \
    --to=krooger@debian.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).