From: Jesper Harder <harder@myrealbox.com>
Subject: Re: customize messing up .emacs symlink?
Date: Wed, 03 Mar 2004 02:02:11 +0100 [thread overview]
Message-ID: <m3oered9po.fsf@defun.localdomain> (raw)
In-Reply-To: 87oereda04.fsf@cs.uga.edu
Ed L Cashin <ecashin@uga.edu> writes:
> Something nice for that kind of lisp is "cond".
>
> (cond ((equal host "nilda")
> (set-background-color "SteelBlue4"))
> ((equal host "tougas")
> (progn
> (set-background-color "ivory4")
> (set-cursor-color "plum")))
> ...)))
You can dispense with the progns to make even nicer:
(cond ((equal host "nilda")
(set-background-color "SteelBlue4"))
((equal host "tougas")
(set-background-color "ivory4")
(set-cursor-color "plum")))
...)
next prev parent reply other threads:[~2004-03-03 1:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 2:00 customize messing up .emacs symlink? Ed L Cashin
2004-03-02 4:03 ` D. D. Brierton
2004-03-02 15:09 ` Ed L Cashin
2004-03-02 15:36 ` D. D. Brierton
2004-03-02 18:06 ` Ed L Cashin
2004-03-02 16:24 ` Floyd L. Davidson
2004-03-03 0:55 ` Ed L Cashin
2004-03-03 1:02 ` Jesper Harder [this message]
2004-03-02 18:52 ` Kevin Rodgers
2004-03-03 0:59 ` Ed L Cashin
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=m3oered9po.fsf@defun.localdomain \
--to=harder@myrealbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).