From: Lowell Kirsh <lkirsh@cs.ubc.ca>
Subject: Re: elisp macros problem
Date: Sun, 25 Jul 2004 21:13:15 -0700 [thread overview]
Message-ID: <ce20cu$4n7$1@mughi.cs.ubc.ca> (raw)
In-Reply-To: <87ekmz2z2o.fsf@thalassa.informatimago.com>
ok, ok. it seemed obvious to me but i guess it wasn't. i concede.
Pascal Bourguignon wrote:
> Lowell Kirsh <lkirsh@cs.ubc.ca> writes:
>
>
>>Rahul Jain wrote:
>>
>>>You probably mean "why does this not do X?" but you never tell us what X
>>>is, so we don't know how to help you achieve that.
>>
>>What I meant was why does this not do the obvoious thing I want it to do...
>
>
> Perhaps because telepathic computers have not been invented yet?
>
> Erase that. Perhaps because telepathic computers are not on the shelf items
> yet, and you don't work for the US Air Force, therefore you don't have one?
>
>
next prev parent reply other threads:[~2004-07-26 4:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 18:39 elisp macros problem Lowell Kirsh
2004-07-24 19:00 ` David Kastrup
2004-07-24 22:08 ` Lowell Kirsh
2004-07-24 23:41 ` David Kastrup
2004-07-25 1:58 ` Lowell Kirsh
2004-07-25 10:59 ` Kalle Olavi Niemitalo
2004-07-24 19:15 ` Barry Margolin
2004-07-24 19:59 ` Pascal Bourguignon
2004-07-24 20:50 ` David Kastrup
2004-07-24 21:49 ` Lowell Kirsh
2004-07-26 1:35 ` Lowell Kirsh
2004-07-26 1:55 ` Rahul Jain
2004-07-26 2:53 ` Lowell Kirsh
2004-07-26 4:05 ` Pascal Bourguignon
2004-07-26 4:13 ` Lowell Kirsh [this message]
2004-07-26 2:54 ` Lowell Kirsh
2004-07-26 22:16 ` Kalle Olavi Niemitalo
2004-07-26 22:58 ` Kevin Rodgers
2004-07-26 2:03 ` Barry Margolin
2004-07-26 3:06 ` Lowell Kirsh
2004-07-26 4:49 ` Barry Margolin
2004-07-26 5:20 ` Pascal Bourguignon
2004-07-26 6:10 ` Oliver Scholz
2004-07-26 5:55 ` David Kastrup
2004-07-27 6:38 ` Lowell Kirsh
2004-07-27 6:54 ` Lowell Kirsh
2004-07-27 7:14 ` David Kastrup
2004-07-27 8:10 ` Lowell Kirsh
2004-07-27 12:05 ` Pascal Bourguignon
2004-07-28 5:03 ` Rob Warnock
2004-07-31 20:46 ` Lowell Kirsh
2004-08-03 18:44 ` Michael Slass
2004-07-27 23:22 ` Barry Fishman
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='ce20cu$4n7$1@mughi.cs.ubc.ca' \
--to=lkirsh@cs.ubc.ca \
/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).