[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Multi-tty design (Re: Reordering etc/NEWS)

From: David Kastrup
Subject: Re: Multi-tty design (Re: Reordering etc/NEWS)
Date: Mon, 14 May 2007 23:27:14 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/23.0.51 (gnu/linux)

Dan Nicolaescu <address@hidden> writes:

> David Kastrup <address@hidden> writes:
>   > Dan Nicolaescu <address@hidden> writes:
>   > 
>   > > David Kastrup <address@hidden> writes:
>   > 
>   > >   > So reverting the change is not the right solution.  Personally,
>   > >   > I think the arguments of getenv and setenv are completely messed
>   > >   > up.
>   > 
>   > [You deleted the whole discussion and proposal for making a more
>   > stable solution]
> Yes, intentionally as it is irrelevant here. Before your change
> people were able to test the multi-tty functionality, after it they
> are not.  Nobody claimed the code was bug free, but it did do what
> was advertised to do.

Reality check.  It didn't.  It only worked when one started the main
Emacs from a tty with termcap/terminfo settings identical to those
where one later started emacsclient.

That was the problem I hit first and reported.  And part of the reason
is that getenv does not, as opposed to advertised, fetch a terminal-
or frame-specific environment variable.

So I changed it to do that in order to match its DOC string, and it
turns out that the code for _multitty_ (what this branch is supposed
to be about in the first place) does not yet fetch the right kind of

So you propose to tackle the problem by destroying multi-tty
capability, making everything rely on a single environment for all

If there is consensus among the multitty developers for that, I'll be
happy to revert the change and indeed not touch the multitty code
anymore at all.

David Kastrup, Kriemhildstr. 15, 44793 Bochum

reply via email to

[Prev in Thread] Current Thread [Next in Thread]