* eshell compatibility
@ 2009-11-23 15:40 Michael Albinus
2009-11-23 16:47 ` Stefan Monnier
0 siblings, 1 reply; 4+ messages in thread
From: Michael Albinus @ 2009-11-23 15:40 UTC (permalink / raw
To: emacs-devel
Hi,
I have prepared patches, which let eshell run processes on remote hosts
better than today. Those patches use `file-remote-p' and
`start-file-process', both introduced in GNU Emacs 22 and 23, respectively.
Eshell contains a lot of compatibility code. Does it mean, eshell is
still synchronized upstream, and I must add compatibility code as well?
Or could I trust, that the version in trunk is used in GNU Emacs 23, and
anybody moving it out must add compatibility code herself?
Best regards, Michael.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: eshell compatibility
2009-11-23 15:40 eshell compatibility Michael Albinus
@ 2009-11-23 16:47 ` Stefan Monnier
2009-11-24 10:43 ` Michael Albinus
2009-11-24 11:31 ` Leo
0 siblings, 2 replies; 4+ messages in thread
From: Stefan Monnier @ 2009-11-23 16:47 UTC (permalink / raw
To: Michael Albinus; +Cc: emacs-devel
> Eshell contains a lot of compatibility code. Does it mean, eshell is
> still synchronized upstream, and I must add compatibility code as well?
> Or could I trust, that the version in trunk is used in GNU Emacs 23, and
> anybody moving it out must add compatibility code herself?
I don't think there's any kind of "upstream" version of Eshell
any more. In any case I wouldn't worry about it.
Stefan
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: eshell compatibility
2009-11-23 16:47 ` Stefan Monnier
@ 2009-11-24 10:43 ` Michael Albinus
2009-11-24 11:31 ` Leo
1 sibling, 0 replies; 4+ messages in thread
From: Michael Albinus @ 2009-11-24 10:43 UTC (permalink / raw
To: Stefan Monnier; +Cc: emacs-devel
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Eshell contains a lot of compatibility code. Does it mean, eshell is
>> still synchronized upstream, and I must add compatibility code as well?
>> Or could I trust, that the version in trunk is used in GNU Emacs 23, and
>> anybody moving it out must add compatibility code herself?
>
> I don't think there's any kind of "upstream" version of Eshell
> any more. In any case I wouldn't worry about it.
Done. There are some things left to do, for example support of `getenv',
`setenv' and `executable-find' on remote hosts. But this might be
postponed until after the release.
> Stefan
Best regards, Michael.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: eshell compatibility
2009-11-23 16:47 ` Stefan Monnier
2009-11-24 10:43 ` Michael Albinus
@ 2009-11-24 11:31 ` Leo
1 sibling, 0 replies; 4+ messages in thread
From: Leo @ 2009-11-24 11:31 UTC (permalink / raw
To: emacs-devel
On 2009-11-23 16:47 +0000, Stefan Monnier wrote:
>> Eshell contains a lot of compatibility code. Does it mean, eshell is
>> still synchronized upstream, and I must add compatibility code as well?
>> Or could I trust, that the version in trunk is used in GNU Emacs 23, and
>> anybody moving it out must add compatibility code herself?
>
> I don't think there's any kind of "upstream" version of Eshell
> any more. In any case I wouldn't worry about it.
Eshell has a git repo here: http://github.com/jwiegley/eshell.
>
>
> Stefan
Leo
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2009-11-24 11:31 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-11-23 15:40 eshell compatibility Michael Albinus
2009-11-23 16:47 ` Stefan Monnier
2009-11-24 10:43 ` Michael Albinus
2009-11-24 11:31 ` Leo
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.