unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: MON KEY <monkey@sandpframing.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: authinfo gnutls netrc.el auth-sources & smtpmail-starttls-credentials
Date: Fri, 12 Jun 2009 17:05:04 -0400	[thread overview]
Message-ID: <87hbyl17un.fsf@sandpframing.com> (raw)
In-Reply-To: <87r5xpia2a.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 12 Jun 2009 13:25:17 -0500")

Ted Zlatanov <tzz@lifelogs.com> writes:

> I appreciate your suggestions very much.  I am just asking you to

No problem. Gladly.

> present them in a way that I can understand more readily.  From looking

This might be a problem.

> at the stream of Emacs bug reports for a while, most people can submit
> verbal explanations just fine, using code to support but not replace

I find that hard to believe. Does D. Armstrong have an 800#? 
I'll consider leaving a message next time :P

> them.  For reference, here's what M-x report-emacs-bug suggests:

This is not of itself a bug.

> Sure, let's hope whoever does will write a patch or explain it better.

Sure. why not.

> All right.  Please use e-mail next time, so you can be clear in what
> you're reporting.  It would have saved time, and is the standard way to
> report security issues.

See, as you say the issue at hand isn't of itself a bug. 

Ted, this 'time thing' is an entity of your concern and one to which I
don't subscribe.

Another possible approach might be not trying to save time by assuming
you know the answer before you understand the question.

> Your cleanup sets auth-sources to nil.  That would screw up my setup, at

No. 
Your setup would've been screwed when you failed to save state or
open a second session should that have been your primary concern. 

Setting auth-sources to nil was right proper and polite thing to do
given the context.

> least.  It's definitely not OK to just evaluate it; there were many

As you say. Not OK.

> other issues I don't have time to list and which are not really

If you knew Time as well as I do you wouldn't talk about wasting IT. 
It's HIM. 

> The patch is against Emacs CVS.  Let me know what you think.

Yes.

> MK> Is it reasonable for an hypothetical 'average Emacs user' to expect to
> MK> reliably debug/troubleshoot and configure an auth-source initiated
> MK> transaction config using the current 'auth regime' and expect a safe,
> MK> transparent, self cleaning, logging facility to aid in the process?

> Sure.  

There you have it.

> Now, what are you suggesting should be changed or improved?

Please see my post elsewhere on this thread vis a vis imap.el

> Can you give a specific example illustrating these problems, so I can

I have. 

s_P




  reply	other threads:[~2009-06-12 21:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11 23:44 authinfo gnutls netrc.el auth-sources & smtpmail-starttls-credentials MON KEY
2009-06-12 18:25 ` Ted Zlatanov
2009-06-12 21:05   ` MON KEY [this message]
2009-06-13 12:55     ` Ted Zlatanov
2009-06-15  0:52       ` MON KEY
2009-06-15 14:40         ` Ted Zlatanov
  -- strict thread matches above, loose matches on Subject: below --
2009-06-12  6:28 MON KEY
2009-06-10  3:49 MON KEY
2009-06-10 21:18 ` Ted Zlatanov
2009-06-10 20:43   ` MON KEY
2009-06-11 14:39     ` Ted Zlatanov

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=87hbyl17un.fsf@sandpframing.com \
    --to=monkey@sandpframing.com \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.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.
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).