unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
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 23:42:14 +0900	[thread overview]
Message-ID: <933c9221-9a53-4a44-96cf-17ac132441b2@well-done.deisui.org> (raw)
In-Reply-To: <m2ac2wzqwf.fsf@kenny.sha-bang.de> (Sascha Wilde's message of "Sun, 12 Nov 2006 15:22:08 +0100")

>>>>> 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/

$ cat > test.el <<End
(eval-when-compile (require 'cl))
(defun foo (s) (subseq s 0 1))
End

$ emacs -Q -batch -f batch-byte-compile test.el
$ emacs -l test.elc
(foo "test")^J
Debugger entered--Lisp error: (void-function subseq)
  subseq("test" 0 1)

> > ;; 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='.
-- 
Daiki Ueno

  reply	other threads:[~2006-11-12 14:42 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 [this message]
2006-11-12 15:01                     ` Sascha Wilde
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

  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=933c9221-9a53-4a44-96cf-17ac132441b2@well-done.deisui.org \
    --to=ueno@unixuser.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).