* eshell manual
@ 2009-01-27 17:52 Thierry Volpiatto
2009-01-28 3:44 ` Leo
0 siblings, 1 reply; 8+ messages in thread
From: Thierry Volpiatto @ 2009-01-27 17:52 UTC (permalink / raw)
To: emacs-devel
Hi,
actually the eshell manual is really ...empty.
On emacswiki we can find a texi file wrote by Christoph Conrad that seem
quite complete (i did'nt read all, i just install it now) you can find
it here:
http://www.emacswiki.org/emacs/EshellTexi
Even if it is outdated (2001), it contain a lot of useful info.
May be it can be merged it with the actual one (if Christoph is ok).
--
A + Thierry Volpiatto
Location: Saint-Cyr-Sur-Mer - France
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: eshell manual
2009-01-27 17:52 eshell manual Thierry Volpiatto
@ 2009-01-28 3:44 ` Leo
2009-01-28 4:19 ` Chong Yidong
0 siblings, 1 reply; 8+ messages in thread
From: Leo @ 2009-01-28 3:44 UTC (permalink / raw)
To: emacs-devel
On 2009-01-27 17:52 +0000, Thierry Volpiatto wrote:
> Hi,
>
> actually the eshell manual is really ...empty.
>
> On emacswiki we can find a texi file wrote by Christoph Conrad that seem
> quite complete (i did'nt read all, i just install it now) you can find
> it here:
> http://www.emacswiki.org/emacs/EshellTexi
>
> Even if it is outdated (2001), it contain a lot of useful info.
> May be it can be merged it with the actual one (if Christoph is ok).
That sounds like a good suggestion. What do the developers think of this?
Best,
--
.: Leo :. [ sdl.web AT gmail.com ] .: I use Emacs :.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: eshell manual
2009-01-28 3:44 ` Leo
@ 2009-01-28 4:19 ` Chong Yidong
2009-01-28 4:26 ` Glenn Morris
0 siblings, 1 reply; 8+ messages in thread
From: Chong Yidong @ 2009-01-28 4:19 UTC (permalink / raw)
To: Leo; +Cc: emacs-devel
Leo <sdl.web@gmail.com> writes:
>> On emacswiki we can find a texi file wrote by Christoph Conrad that
>> seem quite complete (i did'nt read all, i just install it now) you
>> can find it here: http://www.emacswiki.org/emacs/EshellTexi
>>
>> Even if it is outdated (2001), it contain a lot of useful info.
>> May be it can be merged it with the actual one (if Christoph is ok).
>
> That sounds like a good suggestion. What do the developers think of
> this?
That would be good, assuming Christoph Conrad is willing to sign a
copyright assignment. I have no time right now, but if someone else
wants to try contacting him about this, go ahead. Please also keep John
Wiegley, the author of Eshell, in the loop.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: eshell manual
2009-01-28 4:19 ` Chong Yidong
@ 2009-01-28 4:26 ` Glenn Morris
2009-01-29 14:31 ` Richard M Stallman
0 siblings, 1 reply; 8+ messages in thread
From: Glenn Morris @ 2009-01-28 4:26 UTC (permalink / raw)
To: Chong Yidong; +Cc: Leo, emacs-devel
Chong Yidong wrote:
> That would be good, assuming Christoph Conrad is willing to sign a
> copyright assignment. I have no time right now, but if someone else
> wants to try contacting him about this, go ahead.
He already has a general past and future Emacs assignment AFAICS
(assuming this is christoph.conrad at gmx.de), so he would just have
to agree to contribute this.
But how does one tell who wrote what on the wiki?
^ permalink raw reply [flat|nested] 8+ messages in thread
* Eshell manual
@ 2013-05-31 17:05 Stefan Monnier
2013-05-31 17:41 ` Nic Ferrier
2013-05-31 18:27 ` Michael Albinus
0 siblings, 2 replies; 8+ messages in thread
From: Stefan Monnier @ 2013-05-31 17:05 UTC (permalink / raw)
To: Nic Ferrier; +Cc: emacs-devel
IIUC the Eshell manual we bundle is still the old incomplete manual,
while there is a more complete manual out there. Is there any hope we
could fix this problem?
Stefan
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Eshell manual
2013-05-31 17:05 Eshell manual Stefan Monnier
@ 2013-05-31 17:41 ` Nic Ferrier
2013-05-31 18:27 ` Michael Albinus
1 sibling, 0 replies; 8+ messages in thread
From: Nic Ferrier @ 2013-05-31 17:41 UTC (permalink / raw)
To: Stefan Monnier; +Cc: emacs-devel
No, that's not quite correct.
The "other" manual is generated from the source code. It is not good
documentation, more of a starting point to a better manual.
Aidalgol is slowly moving the current core-Emacs packaged manual into a
state where it's good. In fact, in my opinion, it's already better than
the other one.
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> IIUC the Eshell manual we bundle is still the old incomplete manual,
> while there is a more complete manual out there. Is there any hope we
> could fix this problem?
>
>
> Stefan
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Eshell manual
2013-05-31 17:05 Eshell manual Stefan Monnier
2013-05-31 17:41 ` Nic Ferrier
@ 2013-05-31 18:27 ` Michael Albinus
1 sibling, 0 replies; 8+ messages in thread
From: Michael Albinus @ 2013-05-31 18:27 UTC (permalink / raw)
To: Stefan Monnier; +Cc: Nic Ferrier, emacs-devel
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> IIUC the Eshell manual we bundle is still the old incomplete manual,
> while there is a more complete manual out there. Is there any hope we
> could fix this problem?
There is also a good blog post about
<http://www.masteringemacs.org/articles/2010/12/13/complete-guide-mastering-eshell/>.
Maybe we ask Mickey Petersen for contribution?
> Stefan
Best regards, Michael.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2013-05-31 18:27 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-27 17:52 eshell manual Thierry Volpiatto
2009-01-28 3:44 ` Leo
2009-01-28 4:19 ` Chong Yidong
2009-01-28 4:26 ` Glenn Morris
2009-01-29 14:31 ` Richard M Stallman
-- strict thread matches above, loose matches on Subject: below --
2013-05-31 17:05 Eshell manual Stefan Monnier
2013-05-31 17:41 ` Nic Ferrier
2013-05-31 18:27 ` Michael Albinus
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).