From: Taylan Ulrich Bayirli/Kammer <taylanbayirli@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Extra echo when using libguilereadline
Date: Sat, 16 Aug 2014 16:09:50 +0200 [thread overview]
Message-ID: <878umowmoh.fsf@taylan.uni.cx> (raw)
In-Reply-To: <83bnrkehu1.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 16 Aug 2014 15:31:50 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Taylan Ulrich Bayirli/Kammer <taylanbayirli@gmail.com>
>> Cc: guile-devel@gnu.org
>> Date: Sat, 16 Aug 2014 14:23:24 +0200
>>
>> > scheme@(ice-9 readline)> %load-path
>> > %load-path
>> > $1 = ("d:/usr/share/guile/2.0" "d:/usr/share/guile/site/2.0" "d:/usr/share/guile/site" "d:/usr/share/guile")
>> > scheme@(ice-9 readline)> ,q
>> > ,q
>> >
>> > Is this expected, or is this a bug? If the former, how can I disable
>> > this double echo?
>>
>> On 2.0.11, I cannot reproduce this in any of xterm, M-x term, or M-x
>> shell. It feels like a familiar issue though, probably under a peculiar
>> setup; is there anything noteworthy about how you use the REPL, or your
>> terminal emulator, or such?
>
> It's a normal Windows terminal. I just invoke the guile executable
> and type at the prompt.
>
> Could this be due to failure to recognize that stdin/stdout are
> connected to a console?
>
> More generally, where's the code that could cause these echoes?
For what it's worth, "cat | guile | cat" works fine for me, except for
C-a, C-e, etc. inserting ^A, ^E, etc., but no echoing.
Taylan
prev parent reply other threads:[~2014-08-16 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 11:46 Extra echo when using libguilereadline Eli Zaretskii
2014-08-16 12:23 ` Taylan Ulrich Bayirli/Kammer
2014-08-16 12:31 ` Eli Zaretskii
2014-08-16 14:09 ` Taylan Ulrich Bayirli/Kammer [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878umowmoh.fsf@taylan.uni.cx \
--to=taylanbayirli@gmail.com \
--cc=eliz@gnu.org \
--cc=guile-devel@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).