From: Chong Yidong <cyd@gnu.org>
To: axel.junker2@Safe-mail.net
Cc: 8837@debbugs.gnu.org
Subject: bug#8837: term.el: term does not work with custom fringe
Date: Wed, 20 Jun 2012 04:37:27 -0400 [thread overview]
Message-ID: <yyxmx3y9y60.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <N1B-1ZCJghoCCv@Safe-mail.net>
> When I set a custom fringe width via `(fring-mode '(1 . 0))', M-x term
> stops working. I still get basic terminal functionality (bash, ls,
> etc. work fine) - but any complex ncurse-based application stops
> working. The terminal just displays random subsets of the actual text
> that its supposed to show.
Fixed in trunk, thanks for the bug report.
prev parent reply other threads:[~2012-06-20 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 19:16 bug#8837: term.el: term does not work with custom fringe axel.junker2
2011-06-13 9:47 ` Peter Dyballa
2012-06-20 8:37 ` Chong Yidong [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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yyxmx3y9y60.fsf@fencepost.gnu.org \
--to=cyd@gnu.org \
--cc=8837@debbugs.gnu.org \
--cc=axel.junker2@Safe-mail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).