From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Constantine Vetoshev <vetoshev@gmail.com>
Cc: 15402@debbugs.gnu.org
Subject: bug#15402: 24.3; Emacs and Mac OS Dock bad launch behavior
Date: Fri, 20 Sep 2013 09:05:55 +0200 [thread overview]
Message-ID: <EDCDBCE8-252F-4354-BBBF-A55C17FE29C5@swipnet.se> (raw)
In-Reply-To: <570386AE-EE19-49EB-B532-44F7F3705826@gmail.com>
Hello.
19 sep 2013 kl. 21:25 skrev Constantine Vetoshev <vetoshev@gmail.com>:
> Also, the real reason I submitted this bug report is bad behavior in term. This bad behavior happens to go away with a properly set LANG, but my init.el contains all sorts of invocations like:
>
> (set-language-environment "UTF-8")
> (prefer-coding-system 'utf-8)
> (defadvice multi-term (after cv/multi-term activate)
> (set-buffer-process-coding-system 'utf-8-unix 'utf-8-unix))
>
> This fixes the basic non-ASCII character display problems (I didn't even realize Emacs cared that much about LANG), but ansi-term still chokes on long lines containing non-ASCII characters — even though it displays them correctly. Shouldn't at least one of these settings get term working correctly, even without a properly-set LANG?
I agree that some of these settings should be taken into account. Don't know which though.
Maybe we should set utf-8-unix as default on OSX if LANG is not set?
FWIW M-x shell behaves correctly for me.
Jan D.
next prev parent reply other threads:[~2013-09-20 7:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 8:25 bug#15402: 24.3; Emacs and Mac OS Dock bad launch behavior Constantine Vetoshev
2013-09-17 18:04 ` Jan Djärv
2013-09-17 18:48 ` Constantine Vetoshev
2013-09-18 17:24 ` Stefan Monnier
2013-09-19 15:54 ` Jan Djärv
2013-09-19 19:25 ` Constantine Vetoshev
2013-09-20 7:05 ` Jan Djärv [this message]
2013-09-20 7:57 ` Constantine Vetoshev
2013-09-20 9:21 ` Jan Djärv
2013-09-20 11:25 ` Constantine Vetoshev
2013-09-19 21:30 ` Stefan Monnier
2013-09-29 17:11 ` Jan Djärv
2013-09-30 15:14 ` Constantine Vetoshev
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=EDCDBCE8-252F-4354-BBBF-A55C17FE29C5@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=15402@debbugs.gnu.org \
--cc=vetoshev@gmail.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.
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).