From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: dash-0.5.8-3
Date: Tue, 24 Jan 2017 15:58:00 -0000 [thread overview]
Message-ID: <f859816f9fb978d6d45a5dc9713f8fbd@smtp-cloud3.xs4all.net> (raw)
In-Reply-To: <announce.544ED717.9000206@redhat.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]
On Mon, 27 Oct 2014 17:36:55, "Eric Blake (cygwin)" wrote:
> A new release of dash, 0.5.8-3, has been uploaded and will soon reach a
> mirror near you; replacing 0.5.8-2, and leaving the previous version at
> 0.5.7-1 on 32-bit and 0.5.7-4 on 64-bit.
A note to let you know ...
The dash interpreter has a minor problem with multi-byte characters ...
.. at least on Cygwin, NOT on Fedora 24.
When the omega symbol is entered, followed by a backspace, the input buffer
is NOT correctly cleared (or so it appears to me).
Executed in Windows Console:
(but similar behaviour when executed using mintty)
64-@@ uname -a
CYGWIN_NT-6.1 Seven 2.7.0(0.306/5/3) x86_64 Cygwin
(but same behaviour on x86)
64-@@ dash # latest package (0.5.8-3)
# enter alt-234 (omega symbol), followed by a backspace
$
dash: 1: â: not found
# enter alt-234
$ echo Ω | xxd
00000000: cea9 0a ...
# enter alt-234, followed by a backspace
$ echo | xxd
00000000: ce0a ..
NOTE: this behaviour already existed BEFORE Corinna made her
modification to cygwin1.dll in order to "please" Steven P.
Regards,
Henri
=====
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-01-24 15:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 23:40 Eric Blake (cygwin)
2017-01-24 15:58 ` Houder [this message]
2017-01-25 1:28 ` Steven Penny
2017-01-25 13:37 ` Houder
2017-01-25 20:31 ` cyg Simple
2017-01-28 14:36 ` Houder
2017-01-26 0:14 ` Steven Penny
2017-01-28 13:44 ` Houder
2017-01-31 10:04 ` Corinna Vinschen
2017-01-31 13:16 ` Corinna Vinschen
2017-01-31 15:02 ` Houder
2017-01-31 15:33 ` Corinna Vinschen
2017-01-31 15:42 ` Eric Blake
2017-02-01 8:46 ` Houder
2017-01-31 17:54 ` Houder
2017-02-01 9:17 ` Corinna Vinschen
2017-02-13 22:03 ` Thomas Wolff
2017-02-14 8:45 ` Corinna Vinschen
2017-02-14 19:40 ` Thomas Wolff
2017-02-14 19:56 ` Eric Blake
2017-02-14 20:29 ` Thomas Wolff
2017-02-14 20:35 ` Thomas Wolff
2017-02-15 22:19 ` Thomas Wolff
2017-02-16 12:49 ` Corinna Vinschen
2017-02-16 20:32 ` Thomas Wolff
2017-02-17 7:36 ` Thomas Wolff
2017-02-17 9:43 ` Corinna Vinschen
2017-02-17 22:30 ` Thomas Wolff
2017-02-18 22:46 ` Thomas Wolff
2017-02-20 9:11 ` Corinna Vinschen
2017-02-20 21:08 ` Thomas Wolff
2017-02-20 9:07 ` Corinna Vinschen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f859816f9fb978d6d45a5dc9713f8fbd@smtp-cloud3.xs4all.net \
--to=houder@xs4all.nl \
--cc=cygwin@cygwin.com \
/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).