From: Matthias Koeppe <mkoeppe@mail.Math.Uni-Magdeburg.De>
Cc: guile-user@gnu.org
Subject: Re: defining new character names?
Date: Tue, 20 Aug 2002 10:20:05 +0200 [thread overview]
Message-ID: <uw5fzxakklm.fsf@saturn.math.uni-magdeburg.de> (raw)
In-Reply-To: <20020819100733.GA6177@sim.no> ("Lars J. Aas"'s message of "Mon, 19 Aug 2002 12:07:33 +0200")
"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)
>
> I can of course define a normal variable for this, but then
> it won't shine from the usage that it is a character in the
> way the above does.
Why not use the name `paren-close-character' then.
#\ is read-syntax for literal character constants. It is not a "type
annotation". (If you define constant numeric variables like `pi', the
name will not start with a digit either.)
> I've looked in libguile/chars.{c,h} and the guile docs, but
> didn't find any obvious way to do this. Is it possible?
> The reason i'd like to do this is that inserting #\) in the
> scheme file makes the vim "%" command unusable over those
> blocks (and it's not as easy on the eye either), and there was
> no alternate name for that char other than using the octal
> ascii value.
I think it's a bad idea to change the language only to make sure that
a simplistic editor implementation works with it. File a bug report
with vim instead; I'm sure it is easy to fix.
Regards,
--
Matthias Köppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-08-20 8:20 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
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 [this message]
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=uw5fzxakklm.fsf@saturn.math.uni-magdeburg.de \
--to=mkoeppe@mail.math.uni-magdeburg.de \
--cc=guile-user@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.
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).