From: Dani Moncayo <dmoncayo@gmail.com>
To: Bob Proulx <bob@proulx.com>, Dani Moncayo <dmoncayo@gmail.com>,
help-emacs-windows@gnu.org, help-gnu-emacs@gnu.org
Subject: Re: Emacs gdb interface
Date: Wed, 21 Mar 2012 11:26:23 +0100 [thread overview]
Message-ID: <CAH8Pv0ie5mRwhAQd8w3YZ-Xmh7rDpZ494aUqo3eVOr6AzFoYvw@mail.gmail.com> (raw)
In-Reply-To: <20120321092843.GA9383@discord.proulx.com>
>> If that was the case, it would cause a lot of confusion to users, but
>> fortunately, that's not the case (I've just tested it and I see no
>> output either).
>
> It may be confusing but it is no different from having this case:
>
> rwp@discord:~$ printf "Hello" ; printf "\r"
> rwp@discord:~$
>
> Question: Where did the output go? Answer: It was printed but then it
> was covered by the prompt and effectively hidden. Here I am using two
> printf statements because your program didn't include one but in the
> operation of gdm and emacs there is almost certainly one, which is
> represented here by the second printf.
Thanks for the explanation, but what I wanted to say is that the users
expect that the "input/output" buffer in Emacs contains _exclusively_
the input/output text sent to/taken from the process, and in this
case, the process does not write any "\r" character.
In any case, as you said, this doesn't seem to be the origin of the problem.
Thanks.
--
Dani Moncayo
next prev parent reply other threads:[~2012-03-21 10:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 20:21 Emacs gdb interface Dani Moncayo
2012-03-21 2:58 ` Matt McClure
2012-03-21 7:33 ` Dani Moncayo
2012-03-21 7:50 ` Bob Proulx
2012-03-21 8:39 ` Dani Moncayo
2012-03-21 8:54 ` Alberto Luaces
2012-03-21 9:28 ` Bob Proulx
2012-03-21 10:26 ` Dani Moncayo [this message]
2012-03-21 8:28 ` Peter Dyballa
2012-03-21 8:43 ` Dani Moncayo
2012-03-21 18:51 ` Eli Zaretskii
2012-03-21 20:09 ` Dani Moncayo
2012-03-21 21:30 ` Eli Zaretskii
2012-03-21 10:53 ` Sergei Organov
2012-03-21 12:11 ` Dani Moncayo
2012-03-21 13:32 ` [h-e-w] " Doug Lewan
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=CAH8Pv0ie5mRwhAQd8w3YZ-Xmh7rDpZ494aUqo3eVOr6AzFoYvw@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=bob@proulx.com \
--cc=help-emacs-windows@gnu.org \
--cc=help-gnu-emacs@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.
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).