From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: MIME variables
Date: 06 Jul 1999 06:42:58 +0200 [thread overview]
Message-ID: <m3r9mmfkx9.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Hrvoje Niksic's message of "05 Jul 1999 15:54:10 +0200"
Hrvoje Niksic <hniksic@srce.hr> writes:
> (defun my-handle-tester (handle)
> ... lots of code here ...)
>
> ...and then I can stick `my-handle-tester' as the function.
You can just stick `(my-handle-tester handle)' into the alist.
> And it's more Lispy anyway. :-)
I agree with that, so I've now lambdified the variable.
> What you'll name the variable "Lars Magne Ingebrigtsen"???
:-)
> > Patches should be application/octet-stream or application/x-patch.
>
> Yuck. As an example, patches sent to xemacs-reviews are meant to be
> read by humans as least as much as they are meant for the machine. I
> think it's perfectly fine to send them off as text/plain.
text/x-patch would perhaps be better? That would mean that they are
human-readable, but not plain.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-07-06 4:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-04 5:21 Lars Magne Ingebrigtsen
1999-07-04 15:55 ` Hrvoje Niksic
1999-07-04 20:09 ` Kai.Grossjohann
1999-07-05 4:17 ` Lars Magne Ingebrigtsen
1999-07-05 4:16 ` Lars Magne Ingebrigtsen
1999-07-05 13:15 ` Hrvoje Niksic
1999-07-05 13:52 ` Lars Magne Ingebrigtsen
1999-07-05 13:54 ` Hrvoje Niksic
1999-07-06 4:42 ` Lars Magne Ingebrigtsen [this message]
1999-07-06 15:17 ` Hrvoje Niksic
1999-07-06 16:01 ` Lars Magne Ingebrigtsen
1999-07-06 21:41 ` David Kågedal
1999-07-07 11:53 ` Robert Bihlmeyer
1999-07-08 7:11 ` Lars Magne Ingebrigtsen
1999-07-04 20:06 ` Kai.Grossjohann
1999-07-05 4:20 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r9mmfkx9.fsf@quimbies.gnus.org \
--to=larsi@gnus.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 NNTP newsgroup(s).