From: Sascha Wilde <wilde@sha-bang.de>
Cc: ding <ding@gnus.org>, emacs-devel@gnu.org
Subject: Re: Patch: Show signature state in encrypted messages using pgg
Date: Sun, 12 Nov 2006 16:01:30 +0100 [thread overview]
Message-ID: <m264dkzp2t.fsf@kenny.sha-bang.de> (raw)
In-Reply-To: <933c9221-9a53-4a44-96cf-17ac132441b2@well-done.deisui.org> (Daiki Ueno's message of "Sun\, 12 Nov 2006 23\:42\:14 +0900")
Daiki Ueno <ueno@unixuser.org> wrote:
>>>>>> In <m2ac2wzqwf.fsf@kenny.sha-bang.de>
>>>>>> Sascha Wilde <wilde@sha-bang.de> wrote:
>> Daiki Ueno <ueno@unixuser.org> wrote:
>
>> >>>>>> In <m2k620evjt.fsf@kenny.sha-bang.de>
>> >>>>>> Sascha Wilde <wilde@sha-bang.de> wrote:
>> >> (string= "OK" (subseq ( ... ) 0 2))
>> >
>> >> work for XEmacs?
>> >
>> > Now, `subseq' is a cl function.
>
>> mm-uu.el requires cl anyway, so why not use it?
>
> s/anyway/when compiling/
Ok, my fault -- does XEmacs have substring then (Emacs 21.4 does)?
>> > ;; I would like `equal' in this situation rather than `string='.
>
>> Just out of curiosity, why?
>
> Because these are identical and `equal' has shorter name than `string='.
I see, I prefer `string=' for readability because it says
unambiguously what type of data is compared, but with a literal string
in the code like in this case this is isn't much on an issue...
cheers
--
Sascha Wilde : VI is to EMACS as masturbation is to making love:
: effective and always available but probably not your
: first choice...
next prev parent reply other threads:[~2006-11-12 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 22:30 Patch: Show signature state in encrypted messages using pgg Sascha Wilde
2006-11-10 22:31 ` Sascha Wilde
2006-11-11 2:19 ` Daiki Ueno
2006-11-11 21:48 ` Sascha Wilde
2006-11-12 0:28 ` Daiki Ueno
2006-11-12 11:05 ` Sascha Wilde
2006-11-12 11:09 ` David Kastrup
2006-11-12 11:47 ` Sascha Wilde
2006-11-12 12:31 ` Daiki Ueno
2006-11-12 14:22 ` Sascha Wilde
2006-11-12 14:42 ` Daiki Ueno
2006-11-12 15:01 ` Sascha Wilde [this message]
2006-11-12 13:26 ` 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=m264dkzp2t.fsf@kenny.sha-bang.de \
--to=wilde@sha-bang.de \
--cc=ding@gnus.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.