From: Miles Bader <miles@gnu.org>
Cc: Juri Linkov <juri@jurta.org>,
emacs-devel@gnu.org, rms@gnu.org, storm@cua.dk,
Miles Bader <miles@gnu.org>
Subject: Re: query-replace-interactive not documented
Date: Tue, 15 Jun 2004 22:11:44 -0400 [thread overview]
Message-ID: <20040616021144.GE16329@fencepost> (raw)
In-Reply-To: <x57ju845y4.fsf@lola.goethe.zz>
On Wed, Jun 16, 2004 at 04:01:07AM +0200, David Kastrup wrote:
> It has the disadvantage as compared to my more
> recent proposal \` that it has no running mate like ' to complete the
> expression in case that we want to write something like
> \`replace-count'}
> where otherwise replace-count} would become a single symbol.
Is it not possible to tweak the reader so that only `normal' variables are
read, and it stops reading at the "}"? That would make the common case very
convenient, and anyone who really wanted to use a weirdly named variable in
that location could just use (progn WEIRD{}34) instead. I think since it's
clearly an odd situation (a lisp expression embedded in the middle an
otherwise uninterpreted string), users would probably find such a reader
`restriction' fairly natural.
-Miles
--
I'm beginning to think that life is just one long Yoko Ono album; no rhyme
or reason, just a lot of incoherent shrieks and then it's over. --Ian Wolff
next prev parent reply other threads:[~2004-06-16 2:11 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-28 16:16 query-replace-interactive not documented Werner LEMBERG
2004-05-29 17:02 ` Richard Stallman
2004-05-29 17:37 ` Luc Teirlinck
2004-05-29 20:33 ` Juri Linkov
2004-06-11 8:19 ` Juri Linkov
2004-06-11 8:39 ` Kim F. Storm
2004-06-11 9:00 ` David Kastrup
2004-06-12 8:21 ` Juri Linkov
2004-06-12 1:50 ` Richard Stallman
2004-06-12 8:16 ` Juri Linkov
2004-06-13 0:01 ` Richard Stallman
2004-06-13 0:46 ` Miles Bader
2004-06-13 9:03 ` David Kastrup
2004-06-14 18:50 ` Richard Stallman
2004-06-14 20:49 ` Kim F. Storm
2004-06-14 21:20 ` David Kastrup
2004-06-15 14:29 ` Juri Linkov
2004-06-15 15:43 ` David Kastrup
2004-06-15 18:17 ` Juri Linkov
2004-06-15 20:23 ` David Kastrup
2004-06-15 22:30 ` Andreas Schwab
2004-06-15 22:36 ` David Kastrup
2004-06-15 22:43 ` Kim F. Storm
2004-06-15 23:13 ` David Kastrup
2004-06-16 1:16 ` David Kastrup
2004-06-16 8:08 ` Juri Linkov
2004-06-16 9:23 ` David Kastrup
2004-06-16 8:02 ` Juri Linkov
2004-06-17 5:06 ` Richard Stallman
2004-06-16 8:17 ` Juri Linkov
2004-06-16 9:01 ` David Kastrup
2004-06-16 17:06 ` Kevin Rodgers
2004-06-16 9:02 ` Andreas Schwab
2004-06-16 1:41 ` Miles Bader
2004-06-16 2:01 ` David Kastrup
2004-06-16 2:11 ` Miles Bader [this message]
2004-06-16 16:57 ` Richard Stallman
2004-06-15 22:25 ` Andreas Schwab
2004-06-15 22:28 ` Kim F. Storm
2004-06-16 9:00 ` Juri Linkov
2004-06-16 9:25 ` Andreas Schwab
2004-06-16 9:32 ` David Kastrup
2004-06-16 11:30 ` Kim F. Storm
2004-06-16 12:15 ` David Kastrup
2004-06-16 14:35 ` David Kastrup
2004-06-16 15:23 ` Juri Linkov
2004-06-16 21:15 ` David Kastrup
2004-06-16 22:26 ` Kim F. Storm
2004-06-17 0:56 ` David Kastrup
2004-06-17 12:14 ` David Kastrup
2004-06-17 13:05 ` Kim F. Storm
2004-06-17 13:29 ` David Kastrup
2004-06-17 14:10 ` Kim F. Storm
2004-06-17 14:56 ` David Kastrup
2004-06-17 15:33 ` Juri Linkov
2004-06-17 17:03 ` David Kastrup
2004-06-18 6:43 ` Juri Linkov
2004-06-18 7:13 ` David Kastrup
2004-06-16 15:27 ` Kim F. Storm
2004-06-16 17:28 ` Juri Linkov
2004-06-16 21:07 ` David Kastrup
2004-06-17 0:47 ` David Kastrup
2004-06-17 23:05 ` Richard Stallman
2004-06-18 6:55 ` Juri Linkov
2004-06-19 3:19 ` Richard Stallman
2004-06-19 7:00 ` David Kastrup
2004-06-20 19:18 ` Richard Stallman
2004-06-20 21:05 ` David Kastrup
2004-06-21 9:31 ` Richard Stallman
2004-06-21 9:50 ` David Kastrup
2004-06-22 23:16 ` Richard Stallman
2004-06-25 23:12 ` Juri Linkov
2004-06-26 7:34 ` David Kastrup
2004-06-26 16:18 ` Juri Linkov
2004-06-27 17:41 ` Richard Stallman
2004-06-21 9:31 ` Richard Stallman
2004-06-21 9:38 ` David Kastrup
2004-06-22 23:17 ` Richard Stallman
2004-06-22 23:20 ` David Kastrup
2004-06-17 5:07 ` Richard Stallman
2004-06-14 16:59 ` Juri Linkov
2004-06-12 8:21 ` David Kastrup
2004-05-30 19:41 ` Richard Stallman
2004-05-30 22:00 ` Luc Teirlinck
2004-06-08 6:55 ` Juri Linkov
2004-06-11 8:22 ` Juri Linkov
2004-06-12 1:50 ` Richard Stallman
2004-06-18 20:00 ` isearch hooks (was: query-replace-interactive not documented) Juri Linkov
2004-06-19 1:10 ` Miles Bader
2004-06-19 18:09 ` isearch hooks Juri Linkov
2004-06-19 3:19 ` isearch hooks (was: query-replace-interactive not documented) Richard Stallman
2004-06-19 18:36 ` isearch hooks Juri Linkov
2004-06-20 19:18 ` Richard Stallman
2004-06-21 21:56 ` Juri Linkov
2004-06-22 23:17 ` Richard Stallman
2004-06-25 18:07 ` Juri Linkov
2004-06-27 17:41 ` Richard Stallman
2004-06-27 22:34 ` Juri Linkov
2004-06-28 14:57 ` Richard Stallman
2004-06-29 0:25 ` isearch hooks (was: query-replace-interactive not documented) Stefan
2004-06-29 1:17 ` isearch hooks Juri Linkov
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=20040616021144.GE16329@fencepost \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rms@gnu.org \
--cc=storm@cua.dk \
/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).