From: Michael Albinus <michael.albinus@gmx.de>
To: ding@gnus.org
Subject: Re: Password protection
Date: Thu, 30 Sep 2010 19:13:02 +0200 [thread overview]
Message-ID: <87r5gbw3xd.fsf@gmx.de> (raw)
In-Reply-To: <m34od7b2kh.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Thu, 30 Sep 2010 18:47:58 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> If it doesn't break existing code, doesn't slow Emacs down, and provides
>> needed functionality we can't get in any other way, they'll probably OK
>> it. Do you or Michael want to make a proposal or should I?
>
> I'm not quite sure how it's going to be used, either. Today, nnimap says
>
> (process-send-string ... (format "LOGIN %S %S" user password))
>
> That, obviously, can't work any more. So in what circumstances will
> this appear? If it's only in new functions like process-send-password,
> then it kinda seems like the type isn't needed, because we could just
> load it into the C layer without ever exporting it back to the Lisp
> layer at all...
The object might be used whereever a string is allowed, even as
substring of another string. Similar to objects handled by
number-or-marker-p, which accepts a number or a marker object.
process-send-string would recognize, that the string returned by (format
...) contains a password object, and it would expand it.
Best regards, Michael.
next prev parent reply other threads:[~2010-09-30 17:13 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 14:17 Lars Magne Ingebrigtsen
2010-09-28 14:43 ` Richard Riley
2010-09-29 14:01 ` Lars Magne Ingebrigtsen
2010-09-28 14:46 ` Julien Danjou
2010-09-28 14:50 ` Ted Zlatanov
2010-09-29 14:04 ` Lars Magne Ingebrigtsen
2010-09-28 14:47 ` Ted Zlatanov
2010-09-29 14:07 ` Lars Magne Ingebrigtsen
2010-09-29 16:56 ` Charles Philip Chan
2010-09-29 17:15 ` Ted Zlatanov
2010-09-29 19:27 ` Lars Magne Ingebrigtsen
2010-09-29 19:51 ` Ted Zlatanov
2010-09-29 20:35 ` Michael Albinus
2010-09-29 20:58 ` Ted Zlatanov
2010-09-30 3:32 ` Michael Albinus
2010-09-30 15:46 ` Ted Zlatanov
2010-09-30 17:19 ` Michael Albinus
2010-09-30 16:25 ` Lars Magne Ingebrigtsen
2010-09-30 16:43 ` Ted Zlatanov
2010-09-30 16:47 ` Lars Magne Ingebrigtsen
2010-09-30 17:07 ` Ted Zlatanov
2010-09-30 17:17 ` Lars Magne Ingebrigtsen
2010-09-30 17:45 ` Ted Zlatanov
2010-09-30 17:51 ` Lars Magne Ingebrigtsen
2010-09-30 19:11 ` Michael Albinus
2010-09-30 17:13 ` Michael Albinus [this message]
2010-09-30 17:16 ` Michael Albinus
2010-09-29 21:38 ` Lars Magne Ingebrigtsen
2011-02-25 22:18 ` Ted Zlatanov
2011-03-05 11:53 ` Lars Magne Ingebrigtsen
2011-03-07 17:27 ` Ted Zlatanov
2010-09-28 15:02 ` David Engster
2010-09-29 2:28 ` Daniel Pittman
2010-09-29 4:39 ` Richard Riley
2010-09-29 5:58 ` Daniel Pittman
2010-09-29 6:42 ` Richard Riley
2010-09-29 8:54 ` Gijs Hillenius
2010-09-29 9:07 ` Richard Riley
2010-09-29 10:23 ` Gijs Hillenius
2010-09-29 9:51 ` Tassilo Horn
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=87r5gbw3xd.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=ding@gnus.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 NNTP newsgroup(s).