unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 18596@debbugs.gnu.org
Subject: bug#18596: 25.0.50; MS-Windows needs a different default for python-shell-interpreter-args
Date: Sat, 15 Nov 2014 09:37:20 +0200	[thread overview]
Message-ID: <83bno8hq33.fsf@gnu.org> (raw)
In-Reply-To: <jwvlhndz4ra.fsf-monnier+emacsbugs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: fgallina@gnu.org (Fabián Ezequiel Gallina),
>   18596@debbugs.gnu.org
> Date: Fri, 14 Nov 2014 19:29:43 -0500
> 
> > I'm surprised you consider documenting bugs to be a solution for those
> > bugs.  Bugs should be fixed, not documented.  If Emacs knows that in
> > certain situation it should invoke Python with -i, it should do that
> > automatically.  Or it should do something else to fix the hang, but
> > leaving the hanging behavior is IMO simply wrong, and even unbecoming.
> 
> Adding "-i" to a command received as argument would definitely be
> problematic

I agree.  When a command is given, run-python should obey it.  In this
case, it's the responsibility of whoever provides the command to make
it DTRT.

> but if the command specified is "nil", I agree that we should
> provide the needed args for the command to run correctly,
> (i.e. include "-i").

Obviously, I agree with that, too ;-)





  reply	other threads:[~2014-11-15  7:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01 15:12 bug#18596: 25.0.50; MS-Windows needs a different default for python-shell-interpreter-args Eli Zaretskii
2014-10-01 16:48 ` Glenn Morris
2014-10-01 16:50   ` Eli Zaretskii
2014-10-03  0:51 ` Fabián Ezequiel Gallina
2014-10-03  8:15   ` Eli Zaretskii
2014-10-16 10:22   ` Eli Zaretskii
2014-11-14  7:25     ` Fabián Ezequiel Gallina
2014-11-14 10:38       ` Eli Zaretskii
2014-11-14 13:05         ` Fabián Ezequiel Gallina
2014-11-14 14:29           ` Eli Zaretskii
2014-11-14 16:01             ` Fabián Ezequiel Gallina
2014-11-14 16:50               ` Eli Zaretskii
2014-11-14 20:55                 ` Fabián Ezequiel Gallina
2014-11-14 21:04                   ` Eli Zaretskii
2014-11-15  0:29                     ` Stefan Monnier
2014-11-15  7:37                       ` Eli Zaretskii [this message]
2014-11-16 14:21 ` Fabián Ezequiel Gallina
2014-11-16 15:45   ` Eli Zaretskii
2014-11-16 21:16     ` Fabián Ezequiel Gallina
2014-11-17  3:38       ` Eli Zaretskii

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=83bno8hq33.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18596@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).