Eshell help.

Eshell help.

[Steven Wu]

I looked into eshell, and felt that I really like it. Unfortunately, I 
wasn't able to find much documentation about it. Here is a question that 
I found: if I redefine eshell-prompt-function to something I like, i.e. 
no pathname, then completetion doesn't work. I kinda like to have the 
pathname printed on the window title bar, not at the prompt. Also, if I 
want to do shell programming, where can I find the elisp primitives?

thanks.
steve

Re: Eshell help.

[Dan Anderson]

Although I am in no way qualified to answer your LISP quesions, if you
want a fully functional shell try: M-x term

-Dan

Re: Eshell help.

[Vincenzo Di Somma]

I followed your suggestion and tryied to use M-x term, I had my shell 
working quit soon but, just after ther first 'ls' command emacs crashed 
immedialty, blocked without any life sign :)
What`s wrong ?
(emacs 21 on debian testing i386)
Thansk,
   Vincenzo

Dan Anderson wrote:
> Although I am in no way qualified to answer your LISP quesions, if you
> want a fully functional shell try: M-x term
> 
> -Dan
> 
> 
> 
> _______________________________________________
> Help-gnu-emacs mailing list
> Help-gnu-emacs@gnu.org
> http://mail.gnu.org/mailman/listinfo/help-gnu-emacs
> 

Re: Eshell help.

[Lute Kamstra]

Vincenzo Di Somma <enzo@reflab.it> writes:

> I followed your suggestion and tryied to use M-x term, I had my shell
> working quit soon but, 

Do you have to do anything special, apart from just typing M-x term
RET and then confirming Emacs suggestion of /bin/bash with RET?

> just after ther first 'ls' command emacs crashed immedialty, blocked
> without any life sign :) What`s wrong ?

Does Emacs really crash or does term just slurp all your keyboard
input?  Does C-c C-c do anything?  What if you have one Emacs with two
frames and you run term in one frame; does the other frame still
function?

> (emacs 21 on debian testing i386)

Which Emacs is that.  Tip: type C-u C-x C-e after the closing
parenthesis of (emacs-version).

  Lute.

-- 
(spook) => "Etacs investigation Sundevil"
(insert-file-contents "~/.signature") => (error "`~/.signature' too rude")

Re: Eshell help.

[Vincenzo Di Somma]

Lute Kamstra wrote:
> Vincenzo Di Somma <enzo@reflab.it> writes:
> 
> 
>>I followed your suggestion and tryied to use M-x term, I had my shell
>>working quit soon but, 
> 
> 
> Do you have to do anything special, apart from just typing M-x term
> RET and then confirming Emacs suggestion of /bin/bash with RET?

no

>>just after ther first 'ls' command emacs crashed immedialty, blocked
>>without any life sign :) What`s wrong ?
> 
> 
> Does Emacs really crash or does term just slurp all your keyboard
> input?  Does C-c C-c do anything?  What if you have one Emacs with two
> frames and you run term in one frame; does the other frame still
> function?

Nothing, I can`t do anything and the frames don`t even refresh, 
completly blocked.

>>(emacs 21 on debian testing i386)
> 
> 
> Which Emacs is that.  Tip: type C-u C-x C-e after the closing
> parenthesis of (emacs-version).

"GNU Emacs 21.2.1 (i386-debian-linux-gnu, X toolkit, Xaw3d scroll bars)
  of 2002-03-22 on raven, modified by Debian"

Vincenzo.

Re: Eshell help.

[punkind]

On Fri, 03 Oct 2003, Vincenzo Di Somma wrote:

> Dan Anderson wrote:
>> Although I am in no way qualified to answer your LISP quesions, if you
>> want a fully functional shell try: M-x term
>> -Dan

[...]

> I followed your suggestion and tryied to use M-x term, I had my shell
> working quit soon but, just after ther first 'ls' command emacs crashed
> immedialty, blocked without any life sign :)
> What`s wrong ?
> (emacs 21 on debian testing i386)

same happens here, (emacs-version) "GNU Emacs 21.2.1
(i386-debian-linux-gnu, X toolkit, Xaw3d scroll bars) of 2002-03-22 on
raven, modified by Debian"

*complete crash*

i'd rather use Eshell though. i'll append the problems i found here:

  - when using unrecognized command options, isn't it supposed to call an
    external shell (say /bin/bash)? i'm getting:

    ~ $ ls -l
    total 35135
    usage: eshell/ls: (&rest ARGS)
    ~ $ 

  - sometimes, i open a shell in a message buffer, do some operation and
    close it by killing the process, going back to message-mode. couldn't
    find the way to do the same with Eshell.

tia

-- 
ti tocca tutto quello che ti e` toccato gia`- s'illuminano gli occhi

Re: Eshell help.

[Sean Richards]

punkind <intimisto@nihil.non> writes:

> On Fri, 03 Oct 2003, Vincenzo Di Somma wrote:
>
>> I followed your suggestion and tryied to use M-x term, I had my shell
>> working quit soon but, just after ther first 'ls' command emacs crashed
>> immedialty, blocked without any life sign :)
>> What`s wrong ?
>> (emacs 21 on debian testing i386)
>
> same happens here, (emacs-version) "GNU Emacs 21.2.1
> (i386-debian-linux-gnu, X toolkit, Xaw3d scroll bars) of 2002-03-22 on
> raven, modified by Debian"
>
> *complete crash*

This problem appears to be been fixed in 21.3.1. I had the same
experience with M-x term on 21.2.1 and after moving to 21.3.1 have not
had this problem appear.

Sean

-- 
"Hver sin smak", sa vintapperen, han drakk mens de andre sloss.

Re: Eshell help.

[FRC]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]

Eshell is worth investigating. U'll have to browse the source, but it's less
of a pain than u probably think.

"Dan Anderson" <dan@mathjunkies.com> a écrit dans le message de
news:mailman.950.1065031212.21628.help-gnu-emacs@gnu.org...
> Although I am in no way qualified to answer your LISP quesions, if you
> want a fully functional shell try: M-x term
>
> -Dan
>
>
>

Re: Eshell help.

[Matt Hodges]

>>>>> Steven Wu writes:

 > I looked into eshell, and felt that I really like it.
 > Unfortunately, I wasn't able to find much documentation about it.
 > Here is a question that I found: if I redefine
 > eshell-prompt-function to something I like, i.e. no pathname, then
 > completetion doesn't work. I kinda like to have the pathname
 > printed on the window title bar, not at the prompt.

You need to change eshell-prompt-regexp as well. For example:

     (setq eshell-prompt-function (lambda ()
                                    (if (= (user-uid) 0) "# " "$ "))
           eshell-prompt-regexp "^[$#] ")

(You may have to restart Eshell after making this change.)

Matt

Re: Eshell help.

[Peter Lee]

Does 'C-x BACKSPACE' (backward-kill-sentence), work for anyone else in
eshell?  It works for me in 'M-x shell' (where shell is cygwin bash).
In eshell I get:

byte-code: Text is read-only: #<buffer *eshell*>

I'm using the default prompt with the current (last week's) build of
cvs.

Re: Eshell help.

[Matt Hodges]

>>>>> Peter Lee writes:

 > Does 'C-x BACKSPACE' (backward-kill-sentence), work for anyone else
 > in eshell? It works for me in 'M-x shell' (where shell is cygwin
 > bash). In eshell I get:

 > byte-code: Text is read-only: #<buffer *eshell*>

There is eshell-kill-input (bound to C-c C-u by default) to kill all
input after the prompt.

Matt

Re: Eshell help.

[Steven Wu]

Matt Hodges wrote:
>>>>>>Steven Wu writes:
> 
> 
>  > I looked into eshell, and felt that I really like it.
>  > Unfortunately, I wasn't able to find much documentation about it.
>  > Here is a question that I found: if I redefine
>  > eshell-prompt-function to something I like, i.e. no pathname, then
>  > completetion doesn't work. I kinda like to have the pathname
>  > printed on the window title bar, not at the prompt.
> 
> You need to change eshell-prompt-regexp as well. For example:
> 
>      (setq eshell-prompt-function (lambda ()
>                                     (if (= (user-uid) 0) "# " "$ "))
>            eshell-prompt-regexp "^[$#] ")
> 

Thanks. Last time when I changed the prompt-regexp and prompt-function 
seperately, and that's why it didn't work. I just tried it, and it 
worked fine.

steve