unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Keith Wright <kwright@gis.net>
Cc: larsa@sim.no, guile-user@gnu.org
Subject: Re: defining new character names?
Date: Mon, 19 Aug 2002 23:40:07 -0400	[thread overview]
Message-ID: <200208200340.g7K3e7I01435@fcs9.free-comp-shop.com> (raw)
In-Reply-To: <871y8uxvyd.fsf@zagadka.ping.de> (message from Marius Vollmer on 20 Aug 2002 01:36:26 +0200)

> Cc: guile-user@gnu.org
> From: Marius Vollmer <mvo@zagadka.ping.de>
> 
> "Lars J. Aas" <larsa@sim.no> writes:
> 
> > I'd like to be able to do something like this:
> > 
> > (define-character "paren-close" #\051) ; 051 is ")"
> >   and then later
> > (string-index line #\paren-close)
> 
> Not currently, but I think it's a good idea.

(A) Only in the context of a general mechanism to define constants.
(B) The double quotes around "paren-close" in the definition
     are surely wrong.

> > The reason i'd like to do this is that inserting #\) in the
> > scheme file makes the vim "%" command unusable over those
> > blocks
> 
> vim should be fixed then, no? ;)

Maybe so.  Not my job.

In the meantime, why not say
  (define close-char #\( ) % define )
  (string-index line close-char)

-- 
     -- Keith Wright  <kwright@free-comp-shop.com>

Programmer in Chief, Free Computer Shop <http://www.free-comp-shop.com>
         ---  Food, Shelter, Source code.  ---


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2002-08-20  3:40 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-19 10:07 defining new character names? Lars J. Aas
2002-08-19 23:36 ` Marius Vollmer
2002-08-20  3:40   ` Keith Wright [this message]
2002-08-21  4:01     ` Keith Wright
2002-08-21  8:12     ` Lars J. Aas
2002-08-21  8:43       ` rm
2002-08-21  8:51       ` Matthias Koeppe
2002-08-21  9:17         ` Lars J. Aas
2002-08-21  9:54         ` rm
2002-08-27 15:09           ` Matthias Koeppe
2002-09-01 16:24   ` Rob Browning
2002-09-01 16:49     ` Marius Vollmer
2002-08-20  8:20 ` Matthias Koeppe
2002-08-20 10:18   ` rm
2002-08-21  9:20     ` Matthias Koeppe
2002-08-21 10:00       ` rm
2002-08-21 18:01       ` Marius Vollmer
  -- strict thread matches above, loose matches on Subject: below --
2002-08-21 15:24 Lynn Winebarger
2002-08-21 17:33 ` Keith Wright
2002-08-21 18:27   ` Lynn Winebarger
2002-08-21 19:06     ` rm
2002-08-21 19:47       ` Lynn Winebarger
2002-08-21 23:04       ` Keith Wright
2002-08-21 23:07       ` Keith Wright
2002-08-21 19:40     ` Marius Vollmer
2002-08-22  4:12     ` Keith Wright
2002-08-22  5:16       ` Lynn Winebarger
2002-08-22  7:42         ` rm
2002-08-22  8:39           ` Lynn Winebarger

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200208200340.g7K3e7I01435@fcs9.free-comp-shop.com \
    --to=kwright@gis.net \
    --cc=guile-user@gnu.org \
    --cc=larsa@sim.no \
    /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.
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).