public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: jw schultz <jw@pegasys.ws>, linux-kernel@vger.kernel.org
Subject: Re: JFS default behavior
Date: Wed, 18 Feb 2004 23:58:45 +0000	[thread overview]
Message-ID: <20040218235845.GA914@mail.shareable.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0402180749120.2686@home.osdl.org>

Linus Torvalds wrote:
> Btw, from the screen man-page it appears that screen is not able to do 
> that either. You can put screen into utf-8 mode, but it sounds like it 
> just means that it passes UTF-8 through, not that it does any translation 
> from "latin1 vt100 to utf-8".

Screen works nicely.  Do this:

    echo 'defutf8 on' >> ~/.screenrc

Then screen presents a UTF-8 interface to the shell and other
programs, regardless of what kind of terminal you connect from :)

(It's a bit overkill, no actually it's a lot overkill, and you have the
annoyance of screen intercepting at least one commonly used editing key.)

(Just remember to set the LANG environment variable to include
".UTF-8" so that screen-oriented programs know to display properly.  I
do it automatically using a script which queries the current terminal,
to workaround ssh not forwarding LANG).

> I think there are a few editors that actually do ("mined" looks like it 
> should do it).

Emacs does, of course.

-- Jamie

  reply	other threads:[~2004-02-18 23:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15 23:03 JFS default behavior Nicolas Mailhot
2004-02-16  3:45 ` Jan Knutar
2004-02-16  8:30   ` Nicolas Mailhot
2004-02-16  8:54     ` Valdis.Kletnieks
2004-02-16  6:21 ` jw schultz
2004-02-16 15:55   ` Jamie Lokier
2004-02-17  6:47     ` jw schultz
2004-02-17 21:37       ` Jamie Lokier
2004-02-17 22:12         ` Linus Torvalds
2004-02-18  9:59           ` Jamie Lokier
2004-02-18 15:54             ` Linus Torvalds
2004-02-18 23:58               ` Jamie Lokier [this message]
2004-02-19 10:59 ` JFS default behavior / UTF-8 filenames kernel
2004-02-19 14:05   ` Dave Kleikamp
2004-02-19 23:47     ` kernel
2004-02-20 15:00       ` Dave Kleikamp
2004-02-22 19:22         ` kernel
2004-02-24 14:44           ` Dave Kleikamp
     [not found] <1pvUz-6j-1@gated-at.bofh.it>
     [not found] ` <1pRVj-2am-29@gated-at.bofh.it>
2004-02-16 15:32   ` JFS default behavior Pascal Schmidt
2004-02-16 19:05     ` Eduard Bloch
  -- strict thread matches above, loose matches on Subject: below --
2004-02-15 14:48 Pascal Schmidt
2004-02-16 14:24 ` Eduard Bloch
     [not found] <04Feb13.163954est.41760@gpu.utcc.utoronto.ca>
2004-02-14 14:27 ` Nicolas Mailhot
2004-02-14 15:40   ` viro
2004-02-14 17:47     ` Nicolas Mailhot
2004-02-14 17:59       ` Nicolas Mailhot
2004-02-14 23:06     ` Robin Rosenberg
2004-02-14 23:29       ` viro
2004-02-15  0:07         ` Robin Rosenberg
2004-02-15  2:41           ` Linus Torvalds
2004-02-15  3:33             ` Matthias Urlichs
2004-02-15  4:04               ` viro
2004-02-15  9:48                 ` Robin Rosenberg
2004-02-15 18:26                 ` yodaiken
2004-02-12 16:50 JFS default behavior (was: UTF-8 in file systems? xfs/extfs/etc.) Nicolas Mailhot
2004-02-13  3:03 ` Jamie Lokier
2004-02-13 18:06   ` Nicolas Mailhot
2004-02-13 18:15     ` viro
2004-02-13 18:31       ` Richard B. Johnson
2004-02-13 18:50         ` JFS default behavior Ulrich Drepper

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=20040218235845.GA914@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=jw@pegasys.ws \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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