GNU bug report logs - #19440
24.4; M-x run-scheme doesn't pop up a buffer

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 19440 in the body.
You can then email your comments to 19440 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Vasilij Schneidermann <v.schneidermann <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.4; M-x run-scheme doesn't pop up a buffer
Date: Thu, 25 Dec 2014 14:12:35 +0100

[Message part 1 (text/plain, inline)]

M-x run-scheme switches to a buffer running an inferiour scheme process.
I'm used to the alternative behaviour of inferiour processes spawning a
window if possible, such as M-x run-python, M-x inferior-octave and M-x
run-prolog (and the external M-x run-ruby for an example not included
within Emacs).  It seems as if M-x run-lisp behaves the same.  Is there
a guideline about that kind of behaviour?  If yes, is this behaviour of
M-x run-scheme considered to be a bug?



In GNU Emacs 24.4.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.14.3)
 of 2014-10-21 on bitzer.hoetzel.info
Windowing system distributor `The X.Org Foundation', version 11.0.11602000
System Description: Arch Linux

Configured using:
 `configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib
 --localstatedir=/var --with-x-toolkit=gtk3 --with-xft
 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong
 --param=ssp-buffer-size=4' CPPFLAGS=-D_FORTIFY_SOURCE=2
 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro'

Important settings:
  value of $LANG: en_US.UTF-8
  locale-coding-system: utf-8-unix

Major mode: Fundamental

Minor modes in effect:
  tooltip-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  buffer-read-only: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
M-x r e p <tab> <down-mouse-2> <mouse-2>

Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Making completion list...

Load-path shadows:
/usr/share/emacs/site-lisp/SuperCollider/tree-widget hides
/usr/share/emacs/24.4/lisp/tree-widget

Features:
(shadow sort gnus-util mail-extr emacsbug message idna format-spec
rfc822 mml mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231
mailabbrev gmm-utils mailheader sendmail rfc2047 rfc2045 ietf-drums
mm-util help-fns mail-prsvr mail-utils help-mode easymenu time-date
tooltip electric uniquify ediff-hook vc-hooks lisp-float-type mwheel
x-win x-dnd tool-bar dnd fontset image regexp-opt fringe tabulated-list
newcomment lisp-mode prog-mode register page menu-bar rfn-eshadow timer
select scroll-bar mouse jit-lock font-lock syntax facemenu font-core
frame cham georgian utf-8-lang misc-lang vietnamese tibetan thai
tai-viet lao korean japanese hebrew greek romanian slovak czech european
ethiopic indian cyrillic chinese case-table epa-hook jka-cmpr-hook help
simple abbrev minibuffer nadvice loaddefs button faces cus-face macroexp
files text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget hashtable-print-readable backquote make-network-process
dbusbind gfilenotify dynamic-setting system-font-setting
font-render-setting move-toolbar gtk x-toolkit x multi-tty emacs)

Memory information:
((conses 16 75015 7518)
 (symbols 48 17669 0)
 (miscs 40 80 113)
 (strings 32 9339 4456)
 (string-bytes 1 257582)
 (vectors 16 9065)
 (vector-slots 8 385368 16588)
 (floats 8 65 483)
 (intervals 56 264 21)
 (buffers 960 13)
 (heap 1024 30160 885))

[Message part 2 (text/html, inline)]

Message #8 received at 19440 <at> debbugs.gnu.org (full text, mbox):

From: Vasilij Schneidermann <v.schneidermann <at> gmail.com>
To: 19440 <at> debbugs.gnu.org
Subject: Re: bug#19440: Acknowledgement (24.4; M-x run-scheme doesn't pop up
 a buffer)
Date: Mon, 26 Jan 2015 17:55:52 +0100

Bump.

Message #11 received at 19440 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Vasilij Schneidermann <v.schneidermann <at> gmail.com>
Cc: 19440 <at> debbugs.gnu.org
Subject: Re: bug#19440: 24.4; M-x run-scheme doesn't pop up a buffer
Date: Fri, 28 May 2021 03:56:05 +0200

Vasilij Schneidermann <v.schneidermann <at> gmail.com> writes:

> M-x run-scheme switches to a buffer running an inferiour scheme process.
> I'm used to the alternative behaviour of inferiour processes spawning a
> window if possible, such as M-x run-python, M-x inferior-octave and M-x
> run-prolog (and the external M-x run-ruby for an example not included
> within Emacs).  It seems as if M-x run-lisp behaves the same.  Is there
> a guideline about that kind of behaviour?  If yes, is this behaviour of
> M-x run-scheme considered to be a bug?

(I'm going through old bug reports that unfortunately got no response at
the time.)

I don't think we have a specific policy for how these commands are
supposed to open windows -- and the list you mention aren't consistent,
either.  For instance, run-python pops open a new window, but doesn't
select it, while inferior-octave selects the new window.

I guess it depends on what the people who wrote these packages
preferred -- perhaps it's more likely that you type things in a scheme
buffer, but use a python inferior buffer only for evaling things from a
.py buffer?

So I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.