On Mon, 2013-02-04 at 16:02 +0100, Vincent Lefevre wrote:
> On 2005-12-31 16:05:59 +, Colin Watson wrote:
> > Recent versions of the Linux kernel support an IUTF8 flag (see
> > http://www.cl.cam.ac.uk/~mgk25/unicode.html#mod) which allows the
> > character-erase function in cooked mode to handl
On 2005-12-31 16:05:59 +, Colin Watson wrote:
> Recent versions of the Linux kernel support an IUTF8 flag (see
> http://www.cl.cam.ac.uk/~mgk25/unicode.html#mod) which allows the
> character-erase function in cooked mode to handle UTF-8 characters
> correctly. I would like to allow this mode to
On 2008-05-12 09:35:46 -0500, Nicolas Williams wrote:
> What if the user reads three languages and doesn't know which the remote
> server has localizations for? What if the user doesn't have "dot files"
> on the server?
There's also the problem that if the user shell is bash, the .bashrc
(or .bas
On Mon, May 12, 2008 at 10:07:47AM +0200, Vincent Lefevre wrote:
> On 2008-05-11 21:00:55 -0500, Nicolas Williams wrote:
> > SunSSH 1.1 does (by having the client set per-channel LANG/LC_*
> > environment variables).
>
> I meant in a way that always works in practice.
It tends to, though only by
On Mon, May 12, 2008 at 10:07:47AM +0200, Vincent Lefevre wrote:
> On 2008-05-11 21:00:55 -0500, Nicolas Williams wrote:
> > On Mon, May 12, 2008 at 02:00:56AM +0200, Vincent Lefevre wrote:
> > > default one at the system level. Perhaps you mean that the SSH client
> > > should propagate the locale
On 2008-05-11 21:00:55 -0500, Nicolas Williams wrote:
> On Mon, May 12, 2008 at 02:00:56AM +0200, Vincent Lefevre wrote:
> > default one at the system level. Perhaps you mean that the SSH client
> > should propagate the locale (more precisely, the charmap) to the
>
> SunSSH 1.1 does (by having the
On Mon, May 12, 2008 at 02:00:56AM +0200, Vincent Lefevre wrote:
> On 2006-01-02 18:20:50 -0500, Jeffrey Hutzelman wrote:
> > One could argue that an SSH server running on such a system should look
> > at the configured locale and configure the PTY appropriately, and that's
> > probably even a g
On 2006-01-02 18:20:50 -0500, Jeffrey Hutzelman wrote:
> One could argue that an SSH server running on such a system should look
> at the configured locale and configure the PTY appropriately, and that's
> probably even a good idea.
What "configured locale"? The user may use a locale which is n
On Monday, January 02, 2006 04:43:58 PM -0600 Nicolas Williams
<[EMAIL PROTECTED]> wrote:
On Mon, Jan 02, 2006 at 05:29:40PM -0500, Bill Sommerfeld wrote:
In response to later messages:
> While setting LANG et al is indeed useful, it's not enough to make the
> kernel's terminal driver do th
On Mon, Jan 02, 2006 at 06:20:50PM -0500, Jeffrey Hutzelman wrote:
> The original request wasn't really about standardizing handling of UTF-8 in
> SSH data streams. That's really outside the scope of the protocol --
> unlike telnet, SSH doesn't provide a "virtual terminal"; it connects the
> sh
On Mon, Jan 02, 2006 at 05:29:40PM -0500, Bill Sommerfeld wrote:
> In response to later messages:
> > While setting LANG et al is indeed useful, it's not enough to make the
> > kernel's terminal driver do the right thing when erasing characters in
> > cooked mode. That's why the termios flag was in
On Sat, 2005-12-31 at 11:05, Colin Watson wrote:
> Recent versions of the Linux kernel support an IUTF8 flag (see
> http://www.cl.cam.ac.uk/~mgk25/unicode.html#mod) which allows the
> character-erase function in cooked mode to handle UTF-8 characters
> correctly. I would like to allow this mode to
Recent versions of the Linux kernel support an IUTF8 flag (see
http://www.cl.cam.ac.uk/~mgk25/unicode.html#mod) which allows the
character-erase function in cooked mode to handle UTF-8 characters
correctly. I would like to allow this mode to be preserved by SSH, but
there is no assignment for it at
13 matches
Mail list logo
