From: Michael Heerdegen <michael_heerdegen@web.de>
To: Thien-Thi Nguyen <ttn@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: elisp programming - navigate through code?
Date: Sat, 29 Mar 2014 23:31:05 +0100 [thread overview]
Message-ID: <87eh1khc2e.fsf@web.de> (raw)
In-Reply-To: <87d2h4n2iy.fsf@zigzag.favinet> (Thien-Thi Nguyen's message of "Sat, 29 Mar 2014 22:00:37 +0100")
Thien-Thi Nguyen <ttn@gnu.org> writes:
> Any particular reason you use ‘pcase’ here instead of ‘cond’?
Yes, I want to get more used to it ;-). And this is a common use case,
since all "conditions" only depend on one value.
Michael.
next prev parent reply other threads:[~2014-03-29 22:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 16:49 elisp programming - navigate through code? Martin
2014-03-29 17:17 ` Thorsten Jolitz
2014-03-29 18:10 ` Michael Heerdegen
2014-03-29 21:00 ` Thien-Thi Nguyen
2014-03-29 22:31 ` Michael Heerdegen [this message]
2014-03-30 5:23 ` Alex Kost
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=87eh1khc2e.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=ttn@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).