From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Glenn Brown Newsgroups: gmane.emacs.devel Subject: Re: Use of dedicated windows in gdb-mi.el Date: Tue, 24 Feb 2015 09:56:07 -0800 Message-ID: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a113a772c0a38a9050fd93ddf X-Trace: ger.gmane.org 1424800606 25930 80.91.229.3 (24 Feb 2015 17:56:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 24 Feb 2015 17:56:46 +0000 (UTC) Cc: ohwoeowho@gmail.com To: eliz@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 24 18:56:41 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YQJio-0007rJ-5L for ged-emacs-devel@m.gmane.org; Tue, 24 Feb 2015 18:56:38 +0100 Original-Received: from localhost ([::1]:50688 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQJin-0005T7-KF for ged-emacs-devel@m.gmane.org; Tue, 24 Feb 2015 12:56:37 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33332) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQJii-0005OT-3s for emacs-devel@gnu.org; Tue, 24 Feb 2015 12:56:33 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YQJig-0003pc-Tp for emacs-devel@gnu.org; Tue, 24 Feb 2015 12:56:32 -0500 Original-Received: from mail-qg0-x233.google.com ([2607:f8b0:400d:c04::233]:47637) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YQJig-0003pJ-P8 for emacs-devel@gnu.org; Tue, 24 Feb 2015 12:56:30 -0500 Original-Received: by mail-qg0-f51.google.com with SMTP id z60so31274942qgd.10 for ; Tue, 24 Feb 2015 09:56:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=gRBpdb6S9hJN9fumaECPty4SSq8QSoXg7S4x7soxRu0=; b=Th3n1Ulqxm8o9SFlPD4xd/O6WdjeOaNSW+/eJA6G+sQrupHVE+1pU5+z5ClJfdckRt VdxtGHiM4UwDQGNx22t8xt4uEO3m1KRPJ9nuOmXFsiKLqnqtfj+iJq/qQhrPQ6E+bPS3 6O14jgXhmJSK/Q+CC4gfaJnspbsdE4aXdxhzI3hU2Ph6jF7Cacwpv8rE9dlHSN+4AheR dOdcuG4Hd0tTy6ooihrJFAUnb8/FNOOD3Uiy/qRF2JQYMX3Gi2NQX+JRo3fjMvAMP0cm tsneeeOVeknBD1E+JFnZvSzPZS8XcUBx/qo1gTYqSlzQA7w7PL+mhx3Zkl7bj1h7z4Tl mdmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc :content-type; bh=gRBpdb6S9hJN9fumaECPty4SSq8QSoXg7S4x7soxRu0=; b=hUTWK2yxdE9L0WLedGPLp+VsKwE8vLhCOfgcpnz22U0OVQrDqfHaHO/jr3xQvsbCUp M1J98g6nTWqEw1zv4EguqQo5RVI9dhDgjqNj8xPOn4y3EqJD38pAyVniKTlT5iiJ3+Vr ZLPP2vudfw9TBvRdcmfbOwXVpDvkBTLkyMYEfGej64U2bjdkgklm74JlaV+WRvgBBU/b ptSJ/XRKG+UdQ+N8o//jCZOlT2IjU7x7deH/5uTz9wTM1Un6WXqLFMOh2Ca2KgiZTwLF Gof4IFjclGNLlJRZ/z6P8ghn+8tomNfvNZC/zAxDjP/M3CrUomIYgddJDYMwEDF+73yL i5xg== X-Gm-Message-State: ALoCoQl4jVhIMJmBw4h/MCcc27xCfDtb+WMnZ7plWH2EX1i4zph5zXCpL8j0yQ/ciQ9BhPMy+r0V X-Received: by 10.140.91.131 with SMTP id z3mr37168983qgd.1.1424800589940; Tue, 24 Feb 2015 09:56:29 -0800 (PST) Original-Received: by 10.229.155.201 with HTTP; Tue, 24 Feb 2015 09:56:07 -0800 (PST) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400d:c04::233 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:183458 Archived-At: --001a113a772c0a38a9050fd93ddf Content-Type: text/plain; charset=UTF-8 I applaud the efforts to make gdb-mode more friendly to novices. However, as as 20+ year users of 'M-x gdb' in emacs, I, too, find recent changes to the default 'M-x gdb' behavior frustrating and counter-productive for my own work: I miss inline output in the *gud* frame: I am daily annoyed at output opening a new window I didn't ask for, which I must manually close or 'Ctrl-x o' (other-window) past, since I am often in 'emacs -nw' (No mouse) on remote machines. I am annoyed that the new window-that-I-never-asked-for won't let me 'Ctrl-x b' (switch-to-buffer) to the buffer I actually want to see. I understand that novices tend to use print-debugging and the new input/output buffer can be useful to them. I appreciate that the default configuration should be optimized for novices doing native development in a windowed environment. But please understand that many professionals develop code where stdout-in-its-own-window is counter-productive. (In my daily use, the only output is from the testing framework I use.) Please understand that not everyone has access to a mouse when doing remote and/or embedded development. So please, gdb-mode maintainers, if you are going to change the default behaviour of gdb-mode, give us an easy way to get back access the old output-in-the-*gud*-buffer behavior, which is more productive for some of us professionals. Thanks for your consideration, --Glenn --001a113a772c0a38a9050fd93ddf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I applaud the efforts to make gdb-mode more friendly = to novices.

However, as as 20+ year users of '= M-x gdb' in emacs, I, too, find recent changes to the default 'M-x = gdb' behavior frustrating and counter-productive for my own work: I mis= s inline output in the *gud* frame: I am daily annoyed at output opening a = new window I didn't ask for, which I must manually close or 'Ctrl-x= o' (other-window) past, since I am often in 'emacs -nw' (No mo= use) on remote machines.=C2=A0 I am annoyed that the new window-that-I-neve= r-asked-for won't let me 'Ctrl-x b' (switch-to-buffer) to the b= uffer I actually want to see.

I understand that no= vices tend to use print-debugging and the new input/output buffer can be us= eful to them.=C2=A0 I appreciate that the default configuration should be o= ptimized for novices doing native development in a windowed environment.
But please understand that many professionals develop code where st= dout-in-its-own-window is counter-productive. =C2=A0(In my daily use, the o= nly output is from the testing framework I use.) =C2=A0Please understand th= at not everyone has access to a mouse when doing remote and/or embedded dev= elopment.

So please, gdb-mode maintainers, if you = are going to change the default behaviour of gdb-mode, give us an easy way = to get back access the old output-in-the-*gud*-buffer behavior, which is mo= re productive for some of us professionals.

Th= anks for your consideration,
--Glenn

--001a113a772c0a38a9050fd93ddf--