From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] uemacs doesn't clear ixon termios flag?
Date: Tue, 1 May 2012 23:51:02 +0000 (UTC) [thread overview]
Message-ID: <jnpst6$49t$1@dough.gmane.org> (raw)
In-Reply-To: 87lilbzhan.fsf@macbook.be.48ers.dk
On 2012-05-01, Peter Korsgaard <jacmet@uclibc.org> wrote:
>>>>>> "Grant" == Grant Edwards <grant.b.edwards@gmail.com> writes:
>
> Grant> This appears to be bug in uemacs that's been known about for
> Grant> several years. The fix below is from the busybox mailing list 3
> Grant> years ago
> Grant> http://lists.busybox.net/pipermail/busybox/2009-February/068304.html:
[...]
> That's afaik the uemacs upstream we're using.
That's what I thought. I haven't looked into why upstream has been
ignoring the bug fix, but it seemed to be rather widely known.
> Grant> If I submitted a patch and a modified uemacs.mk would it likely be
> Grant> accepted?
>
> Sure! Notice that I recently converted the uemacs package to gentargets,
> but it should be functionally equivalent.
Cool. I submitted the patch a few days ago:
https://bugs.busybox.net/show_bug.cgi?id=5144
I think the patch should work both pre and post gentargets conversion.
All it does is create a new patch file in the package directory. It
doesn't touch any existing files. As long as the gentargets call
applies all of the *.patch files in alphabetical order it should "just
work".
I can stumble along with either vi or nano, but it requires too
much concentration...
--
Grant Edwards grant.b.edwards Yow! I joined scientology
at at a garage sale!!
gmail.com
prev parent reply other threads:[~2012-05-01 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 14:24 [Buildroot] uemacs doesn't clear ixon termios flag? Grant Edwards
2012-04-25 20:55 ` Grant Edwards
2012-05-01 22:07 ` Peter Korsgaard
2012-05-01 23:51 ` Grant Edwards [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jnpst6$49t$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.