unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: Carsten Bormann <cabo@tzi.org>, 13513@debbugs.gnu.org
Subject: bug#13513: 24.3.50; Going "--non-interactive" is the wrong thing for SVN on OSX
Date: Wed, 30 Jan 2013 11:42:44 -0500	[thread overview]
Message-ID: <jwvlibad3uz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <bwbocgi94q.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 23 Jan 2013 03:41:41 -0500")

>> So, could someone explain to me when --non-interactive is needed?
>> The report seemed to be for w32, does that mean that it's only ever needed
>> for w32, or is it also sometimes needed under GNU/Linux?
> IIUC on GNU/Linux:
> Semi-recent svn default to using gnome-keyring to store encrypted
> passwords for svn servers that need them. So suppose you are working in
> a svn checkout of a remote repository that needs a password.  You've
> previously stored the password encrypted on your local disk.
> Now you type any command that needs to contact the server (eg svn status
> -u, or svn update). If at the command-line, you get a prompt:
>   Password for 'login' GNOME keyring:
> You enter your normal user password, it decrypts the stored svn password
> and everything then works.

But if DISPLAY is set, gnome-keyring should prompt you via an X11 dialog
box, AFAIK.

> If you call the same svn commands from Emacs VC prior to 24.1, it hangs
> forever with no indication of what's going on (bug#9993).  Using
> --non-interactive makes it abort instantly with a meaningful error
> message.

So I think the right way to go about it is to not use --non-interactive,
but add a process filter in vc-svn.el to detect such situations (and
then do something like query the password and send it to svn, or emit
an error).


        Stefan





  parent reply	other threads:[~2013-01-30 16:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-21 13:25 bug#13513: 24.3.50; Going "--non-interactive" is the wrong thing for SVN on OSX Carsten Bormann
2013-01-22  2:02 ` Glenn Morris
2013-01-22  7:06   ` Carsten Bormann
2013-01-22 14:57     ` Stefan Monnier
2013-01-22 16:59       ` Glenn Morris
2013-01-22 19:00         ` Stefan Monnier
2013-01-23  8:41           ` Glenn Morris
2013-01-23  8:46             ` Glenn Morris
2013-01-23 21:53             ` Carsten Bormann
2013-01-30 16:42             ` Stefan Monnier [this message]
2013-01-30 17:02               ` Glenn Morris
2013-01-30 20:58                 ` Stefan Monnier
2013-01-30 21:07                   ` Glenn Morris
2013-01-30 21:10                     ` Glenn Morris
2013-02-11  1:08                       ` Glenn Morris
2013-01-22 18:14 ` Glenn Morris
2013-01-22 22:09   ` Carsten Bormann

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=jwvlibad3uz.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=13513@debbugs.gnu.org \
    --cc=cabo@tzi.org \
    --cc=rgm@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).