From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Emacs-like file buffers
Date: Sun, 07 May 2006 12:02:52 -0700 [thread overview]
Message-ID: <87u0811wv7.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <9c4a82e00605070018l16448e72q374ae255a35fe3e3@mail.gmail.com> (Jason Meade's message of "Sun, 7 May 2006 00:18:52 -0700")
"Jason Meade" <jemeade@gmail.com> writes:
> Under the "Cool Ideas" section of the Guile website, Emacs-like
> buffers are mentioned. I'm thinking this would be a really useful
> library, even independent of Guile. Once such a library is built,
> then extending it into guile shouldn't be too much extra effort.
>
> Is anyone actively pursuing this? If so, I'd be interested in
> assisting. If not, then I plan to give a shot at this independently.
> :)
If there's still a chance that Guile might eventually be used by
Emacs, then it would probably make sense to consider both Emacs
buffers and Emacs regular expressions when trying to decide what to
do, and even if there isn't a chance, Emacs is still a significant
precedent.
Also, you might want to look at Thien-Thi Nguyen's ttn-pers-scheme to
see if "Editing Buffers" are relevant. I don't know enough to comment
either way.
> * Full regular expression support (this touches upon another
> wish-list item)
I would really like to see Guile provide a fixed regular expression
format, one that doesn't vary depending on what the build platform has
available. Without that, you cannot write scripts that are portable,
at least not with respect to regular expressions.
Relevant questions:
- How is the addition of support for Unicode likely to affect any
regular expression or buffer work?
- What well-known form of regular expressions should be chosen -
POSIX, Emacs, Perl?
- Is it acceptable to add an external dependency for regular
expression suppport, or does the implementation need to be in
Guile's source tree? Note that the latter choice doesn't
necessarily rule out using an existing library if, for example,
the author of the library is willing to allow the inclusion of the
code in Guile.
Hope this helps.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-05-07 19:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-07 7:18 Emacs-like file buffers Jason Meade
2006-05-07 19:02 ` Rob Browning [this message]
2006-05-08 23:42 ` Kevin Ryde
2006-05-09 0:50 ` Rob Browning
2006-05-13 1:55 ` Kevin Ryde
2006-05-13 4:08 ` Rob Browning
[not found] ` <9c4a82e00605122309g6f3e061etd702479d88664b96@mail.gmail.com>
[not found] ` <87ejyx37af.fsf@trouble.defaultvalue.org>
[not found] ` <9c4a82e00605131824v23a934dah1404210beb57e1b3@mail.gmail.com>
2006-05-14 1:27 ` Fwd: " Jason Meade
2006-05-14 14:58 ` Bruce Korb
2006-05-14 22:34 ` Kevin Ryde
2006-05-14 22:11 ` Kevin Ryde
2006-05-19 12:12 ` Regular expressions Ludovic Courtès
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=87u0811wv7.fsf@trouble.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@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).