From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Killing unwanted post
Date: Fri, 22 Apr 2005 11:05:52 -0400 [thread overview]
Message-ID: <4n7jiuetrj.fsf@lifelogs.com> (raw)
In-Reply-To: <v9fyxkkn1e.fsf@marauder.physik.uni-ulm.de>
On Thu, 21 Apr 2005, reinersteib+from-uce@imap.cc wrote:
> I think it is sufficient to have it in the doc string. I don't see
> any benefit in putting everything in the name. (You ain't gonna win
> the International Longest Variable Name Competition with it anyhow
> because of `spam.el'. ;-))
It's fine with me, thanks for handling it.
I'm just looking for opportunities to win the ILVNC, just biding my
time... This is the real reason why I work in Emacs Lisp, all
variable names are global so you get to make them as long as you want :)
Ted
next prev parent reply other threads:[~2005-04-22 15:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 10:51 David Sumbler
2005-04-14 15:28 ` Ted Zlatanov
2005-04-14 16:29 ` Reiner Steib
2005-04-14 17:22 ` Ted Zlatanov
2005-04-21 18:22 ` Reiner Steib
2005-04-22 15:05 ` Ted Zlatanov [this message]
2005-04-14 17:29 ` David Sumbler
2005-04-15 20:28 ` Ted Zlatanov
2005-04-15 21:16 ` David Sumbler
2005-04-19 18:20 ` Ted Zlatanov
2005-04-16 13:20 ` Reiner Steib
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=4n7jiuetrj.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
/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).